You are on page 1of 27

NetAct 16.

Performance Management Overview


DN09140649
Issue: 3-0
Performance Management Overview Disclaimer

The information in this document applies solely to the hardware/software product (Product) specified herein, and only as
specified herein.

This document is intended for use by Nokia Solutions and Networks' customers (You) only, and it may not be used except
for the purposes defined in the agreement between You and Nokia Solutions and Networks (Agreement) under which this
document is distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form
or means without the prior written permission of Nokia Solutions and Networks. If you have not entered into an Agreement
applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any
manner and You are obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof.

The document has been prepared to be used by professional and properly trained personnel, and You assume full
responsibility when using it. Nokia Solutions and Networks welcome Your comments as part of the process of continuous
development and improvement of the documentation.

This document and its contents are provided as a convenience to You. Any information or statements concerning the
suitability, capacity, fitness for purpose or performance of the Product are given solely on an as is and as available basis
in this document, and Nokia Solutions and Networks reserves the right to change any such information and statements
without notice. Nokia Solutions and Networks has made all reasonable efforts to ensure that the content of this document is
adequate and free of material errors and omissions, and Nokia Solutions and Networks will correct errors that You identify
in this document. But, Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the
correction of such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Product will be
uninterrupted or error-free.

N O WA RRAN T Y OF AN Y KI ND , EI T HER E X P R E S S OR I M P L I E D , I N C L U D I N G B U T N O T L I M I T E D
TO A NY WAR RA NT Y OF AVAI LABI LIT Y, AC CU RA C Y, R E L I A B I L I T Y, T I T L E , N O N - I N F R I N G E M E N T,
M ER C HANTA BI LI T Y OR F IT N ESS F OR A PA RT IC UL A R P U R P O S E , I S M A D E I N R E L AT I O N TO T H E
C ONT ENT O F TH IS DO CU M EN T. IN N O E V E N T W I L L N O K I A S O L U T I O N S A N D N E T W O R K S B E
L IA BLE F O R AN Y DA M A GES, I NC LUD IN G B U T N OT L I M I T E D TO S P E C I A L , D I R E C T, I N D I R E C T,
I NC I DENTAL OR CO NS EQ UEN T IAL OR AN Y L OS S E S , S U C H A S B U T N O T L I M I T E D TO L O S S O F
PRO FI T, RE VEN UE , BU SI NESS IN T ER RU P T I ON , B U S I N E S S O P P O RT U N I T Y O R D ATA T H AT M AY
ARI SE FRO M T H E US E O F T H IS DO CU M E N T O R T HE I N F O R M AT I O N I N I T, E V E N I N T H E C A S E O F
ERR O RS I N OR OM I SSI ON S F RO M T H IS DO CU M E N T O R I T S C O N T E N T.

This document is Nokia Solutions and Networks proprietary and confidential information, which may not be distributed or
disclosed to any third parties without the prior written consent of Nokia Solutions and Networks.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks
of their respective owners, and they are mentioned for identification purposes only

Copyright 2016 Nokia Solutions and Networks. All rights reserved.

Important Notice on Product Safety


This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having
carefully read the safety information applicable to this product.
The safety information is provided in the Safety Information section in the Legal, Safety and Environmental Information part
of this document or documentation set.

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its products and services.
We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment.
Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and
their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please
contact us at Nokia Solutions and Networks for any additional information.
Performance Management Overview Table of Contents

Contents
1 About this document...................................................................................................................................... 4

2 Overview of performance management........................................................................................................ 5


2.1 Purpose of performance management..................................................................................................... 5
2.2 Using the performance information...........................................................................................................5
2.3 Performance management process.......................................................................................................... 7
2.3.1 Defining or revising Quality of Service goals................................................................................... 7
2.3.2 Translating Quality of Service goals to network performance requirements.................................... 8
2.3.3 Defining reporting requirements....................................................................................................... 8
2.3.4 Identifying other reporting needs......................................................................................................8
2.3.5 Defining reports.................................................................................................................................8
2.3.6 Adapting the measurement load and the OSS................................................................................ 9
2.3.7 Initializing measurements................................................................................................................. 9
2.3.8 Defining thresholds........................................................................................................................... 9
2.3.9 Collecting data.................................................................................................................................. 9
2.3.10 Monitoring network performance.................................................................................................. 10
2.3.11 Generating and distributing reports.............................................................................................. 10
2.3.12 Analyzing the results.................................................................................................................... 10

3 Measurement collection and processing in Performance Manager.........................................................12


3.1 Collecting measurement data in Performance Manager........................................................................ 12
3.2 Loading measurement data into the Performance Manager database...................................................12
3.3 PM data in the Performance Manager database................................................................................... 12
3.3.1 Database Partitioning Manager...................................................................................................... 14
3.3.2 Time zone support.......................................................................................................................... 15
3.4 Post-processing measurement data in Performance Manager.............................................................. 19
3.5 Using historical MO and parameter data for measurement processing................................................. 19
3.6 Parallelization of aggregation, export and import................................................................................... 20

4 Creating and analyzing measurement data with Performance Manager................................................. 21


4.1 Performance indicators and key performance indicators....................................................................... 21
4.2 Creating a report with Performance Manager........................................................................................ 23
4.2.1 Creating KPIs..................................................................................................................................23
4.2.2 Creating reports.............................................................................................................................. 24
4.3 Managing permissions............................................................................................................................ 25
4.4 Caching and Scheduling report.............................................................................................................. 25
4.5 Analyzing the measurement results with Performance Manager........................................................... 26

3
Performance Management Overview About this document

1 About this document


Performance Management Overview describes the performance management (PM) applications that
you can use for analyzing and troubleshooting your network. The document also serves as a source of
information on PM in general.

Performance Manager is a family of applications for processing, analyzing, and visualizing


performance data that is coming from different sources. Raw data becomes meaningful information
that is visualized in graphical and textual reports. Performance Manager gives a view of the network
and service performance and makes it possible to analyze network data, create reports based on the
data and distribute the information within your organization.

Performance Manager is multi vendor-capable and collects data from your entire network that consists
of network elements from Nokia and from other vendors. Performance Manager processes and stores
the data, from days to years, depending on your requirements. Performance Manager includes also
several ready-made report packages.

The general PM information in this document is intended for management, customer care, and
planning or marketing personnel; see Overview of performance management on page 5.

The Performance Manager related parts of the document are primarily intended for technical
personnel who are responsible for the PM area and monitor the transfer of traffic data and
performance data from the network with Nokia applications:

Chapter Measurement collection and processing in Performance Manager


Chapter Visualizing and analyzing measurement data with Performance Manager

DN09140649 3-0 2016 Nokia Solutions and Networks 4


Performance Management Overview Overview of performance management

2 Overview of performance management


This chapter describes the key concepts of performance management (PM).

2.1 Purpose of performance management


The aim of any performance management activity is to collect data to support the following activities:

Verifying the physical and logical configuration of the telecommunications network.


Monitoring continuously how the network functions.
Localizing potential problems as early as possible.
Monitoring subscriber behavior.
Providing optimum services to mobile subscribers.

Depending on how the performance management applications use the collected data, they can be
divided into two main types: performance monitoring and performance reporting applications.

Performance monitoring is online-oriented and provides you with relatively real-time information on the
network. So, performance monitoring applications generally use shorter measurement output intervals
because faster reaction is needed in severe problem cases, in which a 24 hour interval would be too
long. The outputs of performance monitoring applications are mainly used as additional information for
problem cases in which no alarm information is available. Performance monitoring rules are intelligent
threshold rules and can be calculated before or after the measurements are stored in the database.

Performance reporting is offline-oriented and provides information on what happened in the network
over a certain period of time. Performance reporting applications mainly rely on counters, KPIs
and produce reports, which you can use, for example, when you are troubleshooting, planning, or
optimizing the network. For more information on performance reporting, see section Performance
management process.

2.2 Using the performance information


Network elements produce data to support performance evaluation, for example on the following
areas:

Traffic levels within the PLMN, including the level of both the user traffic and the signalling traffic
Verification of the network configuration
Resource access measurements
Quality of Service (QoS)
Resource availability

You can use the various types of performance information for monitoring and managing the network.

DN09140649 3-0 2016 Nokia Solutions and Networks 5


Performance Management Overview Overview of performance management

When you monitor a network to manage its performance, you collect data for locating potential
problems as early as possible and verifying the physical and logical configuration of the network. You
can also use performance data to monitor subscriber behavior by charting out the usage of different
services that are available to the end-users. Such information provides you with input for business and
service management decisions when you are optimizing and expanding your network.

Networks continuously produce an enormous amount of performance data. PM applications need


to filter the information to suit the needs of various users. The following aspects can be identified for
reporting needs:

End-user perception of the services about traffic, quality, or availability of the services.
Technical considerations in the network, for example monitoring the radio access and the core
network separately.
Management and operational levels at the operator.

The following table describes examples of how various user groups can use performance
measurement data for managing the network and what kind of PM applications they can use.

User group PM objectives Report needs Characteristics of a typical report

Top - Monitoring the current network - PLMN-level information - Monthly or longer periods
management status with ad-hoc reports condensed in few reports
- Historical information, tendencies
- Forecasting future trends with - Mainly about trends
- With graphs
longer-term reports
- In graphical format
- For example, network outages of
- Following the trends of the
- Mainly offline report generation the last month (number, length, and
network development, for
number of affected sites)
example, monitoring QoS and
usage statistics of various
services

Technical - Observing subscriber behavior - Higher-level information with - Weekly or monthly, with more
management and capacity issues from longer- drilling possibility to problem details on the last day or week
and marketing term reports based on QoS and areas
- Graphs or tables
usage statistics
- Checking daily the most
- BSC level is important
- Planning new services by important counters at the PLMN
analyzing the recent and current level or for each maintenance - For example service usage

trends region, and if necessary, for each statistics

NEs

- Tracking measurements and


observations accurately to
monitor, for example, the MSC,
BSC, and BTS levels separately

Operations - Detecting faults by enabling - Low-level information and - Daily KPI reports, especially on
and measurement-based alarms easy access to all the counter failing NEs
Maintenance information
- Localizing potential problem - Mainly textual and some graphical
areas by evaluating longer-term - Fast navigation, switching reports
reports on network coverage between counters, when checking
for particular counters in a
- Solving faults by using PM
certain network element or a
reports for root-cause analysis

DN09140649 3-0 2016 Nokia Solutions and Networks 6


Performance Management Overview Overview of performance management

User group PM objectives Report needs Characteristics of a typical report

group of network elements for


troubleshooting

PM Analysis, - Monitoring network capacity by - BSC and MSC level that - Tendency reports at higher or
Optimization, evaluating longer-term reports on can be processed into traffic lower level, depending on the
Planning the use of network resources profiles to provide information planning work
on subscriber behavior and
- Monitoring network quality by - Both raw and summarized
the overall performance of the
evaluating reports that include information if performed at the
network and the network usage
counters or kpis about the quality lowest level
through time and locations
of the services
- Mainly textual and some graphical
- Quality of service (QoS)
- Verifying radio network coverage reports
monitoring, which can include
by evaluating reports that include
monitoring the quality of service
counters or kpis such as the
as seen by the subscribers, and
number and percentage of hand
the quality of the network from the
over failures in a geographic
technical point of view
distribution
- Longer-term traffic profiles to
determine pricing strategies

Customer Care - Informing subscribers about - Frequent, preferably daily, - Frequent and regular
current problems by obtaining and status reports on the status of
analyzing up-to-date information the network and on the status of
on the network status from ad-hoc failing NEs
reports

- Responding more quickly to


service complaints by identifying
the cause of network problems

Table 1: Using PM information to achieve PM objectives

2.3 Performance management process


This section has a description of a view on the performance management process. For the
implementation of this process with Nokia tools, see Figure Performance management process.

2.3.1 Defining or revising Quality of Service goals


When you are managing a particular network, the Quality of Service (QoS) of your network means
the effective maintenance of the quality for the network services according to some agreed criteria.
Maintaining and improving the QoS of your network includes regular monitoring of the service
performance and the evaluation of the service performance problems with respect to the targeted level
of service delivery.

To improve the service, you need to define QoS goals that guide the evaluation of network and service
performance. These goals can represent, for example, the point of view of the operator (efficient
hardware usage, for example efficient use of network elements considering the type and capacity

DN09140649 3-0 2016 Nokia Solutions and Networks 7


Performance Management Overview Overview of performance management

of the NEs, their location and number to support the services) or the point of view of the subscriber
(availability, speed, and accuracy of the service).

As you develop and expand your network, you might have to update and revise your QoS goals.
Mature operators competing for more market share benefit from introducing new services to
differentiate themselves from other service providers. At this point, all kinds of service and profile
measurements are useful. The quality of service becomes extremely important and, for example,
optimization measurements must be taken. The following tasks belong to this stage:

Setting objectives for the desired level of quality


Measuring the quality of service by monitoring real-time data and long-term trends
Planning corrective actions

2.3.2 Translating Quality of Service goals to network performance requirements


To achieve the QoS goals that you defined, prepare or update the detailed requirements for the
network, including the requirements on network performance. For example, the quality of a voice
service can be correlated with the number and ratio of dropped calls, while the accuracy of an IP
service can be correlated with the number of received packets.

2.3.3 Defining reporting requirements


The network performance requirements serve as the basis for reporting requirements and provide
information on which measurements you have to monitor with the PM applications.

2.3.4 Identifying other reporting needs


Monitoring the day-to-day performance of the network is not the only reason for using performance
reports. You can also gather information from reports, for example, if you want to examine short-
term changes when you are upgrading your system or if you want to check long-term trends to gather
information for optimizing or expanding the existing network.

If you can translate these reporting needs into measurements, you can directly define the reporting
requirements for them and translate them into measurement activation criteria. However, some
reporting requirements can give rise to a need for a new or an additional PM application.

You might also need a new or additional PM report when you are investigating uncommon situations or
when you have upgraded or expanded your network.

Before you establish new reports, it is recommended that you check whether the active measurements
already provide the counter information that you need, or whether the required measurements are
available but have not been activated yet, or whether it is sufficient to change the measurement
settings to obtain the information that you need.

2.3.5 Defining reports


You can define and schedule your reports based on the reporting requirements.

DN09140649 3-0 2016 Nokia Solutions and Networks 8


Performance Management Overview Overview of performance management

The details of defining reports mostly depend on your OSS solution. For the solution provided by
Performance Manager, see Section Creating a report with Performance Manager.

2.3.6 Adapting the measurement load and the OSS


If you need a new measurement, you have to ensure that the capacity of the OSS and Performance
Manager, for example, disk space and insertion time, is not exceeded when the new measurement
is implemented and activated. If the OSS or Performance Manager capacity could be exceeded, you
can adapt the entire measurement set by reducing the number of the measurements or increase the
measurement intervals, or you can increase the OSS or Performance manager capacity, for example,
with additional processors. If the capacity has not been exceeded, you can proceed with initializing the
additional measurements.

2.3.7 Initializing measurements


Activating all the necessary measurements across the network could impose a significant but
unnecessary load on the database and the PM processes. So, it is recommended to consider the
following factors:

Period when measurements are active in the network element or the measurement information
is uploaded from the network element to the network management system and the umbrella
performance system (Performance Manager)
Measurement intervals
Number and distribution of the network elements for which the measurement is activated

2.3.8 Defining thresholds


Network management systems allow you to define thresholds for the measurements. When a
measurement value exceeds a threshold, an alarm is raised. So, you can follow the status of network
performance with the fault management applications in which the alarm is visible and also with the
performance management applications in which the measurement information is processed.

For more information on thresholds see Reference information on measurement thresholds.

2.3.9 Collecting data


The measurement information can be preprocessed in the network element, depending on the NE
type and the configuration of the NE. If preprocessing is applied, the data is filtered, that is, not all of
the measurement information is forwarded to the network management system) or some calculation is
done on the measurement data before it is uploaded to the OSS through the NE-specific interface.

The data can also undergo further processing in a post-processing phase, for example, when busy
hour information is needed for a report. The results of the post-processing are also stored in the OSS
database. The data is used by the reporting applications or is exported through the open interfaces to
external systems.

DN09140649 3-0 2016 Nokia Solutions and Networks 9


Performance Management Overview Overview of performance management

For more information, see Section Collecting measurement data in Performance Manager.

2.3.10 Monitoring network performance


You can typically find performance-related problems by checking the alarms, the measurements, and
the customer complaint reports. You also can use information from drive tests and call detail reports
(CDRs).

Regular reporting such as running a report once a day or once a week is too slow for continuous
network monitoring. Furthermore, the default measurement interval for most counters, one hour,
may create a huge delay. However, you can also analyze the traffic statistics and collect detailed
information from the network for further analysis with reports when you discover a problem. Prompt
reaction is sometimes required. So, it is recommended that you set thresholds for the counters or kpis
so that the Performance Manager raises alarms based on those values in unusual situations or when
errors occur.

2.3.11 Generating and distributing reports


When you defined the reporting requirements, you also gathered information on the user groups
and on the types and frequency of the reports that they need. You have to ensure that the users of
the Performance Manager have access to or receive the reports that best support their work. For
overview information on what report types the various user groups could need, see Section Using the
performance information.

Reporting applications allow you to turn the often overwhelming amount of measurement data into
information on the performance of the resources in your network, which you can use for determining
whether the network performance goals are met and whether problem-determination procedures
should be initiated based on performance.

2.3.12 Analyzing the results


PM reports are mostly used for two purposes: to gather information for troubleshooting (short-term
reports and ad-hoc reports), for prevention, and for developing the network and the services (longer-
term reports).

For example, the top management of an operator can use PM reports for obtaining high-level
information on the network operation at a glance. It is possible to use a report about the length of the
calls to determine whether the service is becoming more or less popular among the subscribers and in
what times of the day subscribers use particular services the most. The call durations plotted against
the day gives information on the preferences of the subscribers and helps you decide about marketing
campaigns, special rates for busy hours or off-peak hours.

You can also monitor whether a network expansion has the expected results on the quality of services
by regularly checking your own customized reports. With regular checks you can avoid significant
negative impact by taking corrective actions as soon as deviations are observed in the quality of the
service.

DN09140649 3-0 2016 Nokia Solutions and Networks 10


Performance Management Overview Overview of performance management

When you have to optimize your network or when you consider an expansion, you can use various
PM reports to gather information on the past. You can also use the reports for monitoring the network
performance over a certain period of time and check how the QoS and other quality objectives are
met and identify possible problem areas in the network. For optimization, for example, you might
need detailed quality information on particular measurements in a particular BSS. For expansion and
planning, you might need a less detailed report but over a longer period of time to observe trends in
the subscriber behavior or network resource usage.

For more examples, see Section Using the performance information.

DN09140649 3-0 2016 Nokia Solutions and Networks 11


Performance Management Overview Measurement collection and processing in Performance Manager

3 Measurement collection and processing in


Performance Manager
This chapter briefly describes how you can manage data with Performance Manager. The
performance management system can be seen as a PM pipe. The data flow through the pipe can be
split in the following actions:

The input for this pipe is the measurement data collected from network elements (Nokia and other
vendors). For information, see Section Collecting measurement data in Performance Manager.
The pipe is a set of processes that store the measurement data in the database and aggregate
it to enable faster reporting. For information, see Section Loading measurement data into the
Performance Manager database and Section Post-processing measurement data in Performance
Manager
The output of the pipe is used by reporting applications, see Section Analyzing the measurement
results with Performance Manager.

3.1 Collecting measurement data in Performance Manager


This section has a brief description of how measurement data is transferred from the OSS to
Performance Manager.

At the end of a NE's measurement interval, measurement data is put into measurement files. The
files are stored for some time in the NE and also transferred to OSS through measurement collection
interfaces, for example FTP, SFTP, SNMP.

This data is transferred to Performance Manager via push method.

For an overview of the measurement collection interfaces, see Performance Management data flow.

3.2 Loading measurement data into the Performance Manager database


This section has a description of how measurement data is loaded into the Performance Manager
database.

Performance Manager includes a subsystem, PM Data Extraction, Transaction, and Loading


(ETLOAD), that inserts the raw data that was uploaded from the NEs into the Performance Manager
database. ETLOAD takes the OMeS files as input, fetches the data contained in the OMeS files, and
loads the data into adaptation-specific tables in the database.

DN09140649 3-0 2016 Nokia Solutions and Networks 12


Performance Management Overview Measurement collection and processing in Performance Manager

3.3 PM data in the Performance Manager database


This section has a description of the content of PM database, the part of the Performance Manager
database that stores measurement data and related information.

The PM database part of the Performance Manager database contains measurement data in database
tables. For load reduction and data access reasons, measurement tables in the strictest sense,
marked with _P_ in the following figure, are not accessed directly by data processing or reporting
applications, but ETLOAD writes raw data into this table.

Figure 1: Relationship between performance measurement tables and views

Measurement tables marked with _PV_ in the above figure are used by the General PM process
cosprcmx.pl writes raw and aggregated measurement data to the Performance Manager
database
Measurement views marked with _PS_ in the figure, are used by the reporting applications, for
reading raw and aggregated measurement data from the Performance Manager database
ETLOAD access the database marked _P_ to write into raw tables.

All the database objects that are represented with rectangles in the figure, that is, the _P_, _PV_, and
_PS_ database objects use the following naming convention:

<adaptation>_<db_object>_<Reporter_meas_type>_<object_level>_<granularity>

where the meaning of the components is as follows:

<adaptation>

6-character abbreviation of the adaptation from which the measurements are stored in the
database table

Example: NOKAXC for Nokia AXC

<db_object>

Type of the PM database object

Possible values: P (database table, not accessed directly), PV (measurement table, written to
by cosprcmx.pl), and PS (measurement view, read by reporting applications)

DN09140649 3-0 2016 Nokia Solutions and Networks 13


Performance Management Overview Measurement collection and processing in Performance Manager

<Reporter_meas_type>

Measurements collected from a NE are grouped to various measurement types


by Performance Manager, as defined by the adaptation-specific configuration file
(<adaptation>sys__mx.cf).

<object_level>

Lowest level in the object hierarchy for which data is available in the database object.

<granularity>

Time-level for which the database object contains aggregated measurement data. For P
objects that contain data that is not aggregated, the value of this part is typically O2, for PS
and PV objects, the value of this part is RAW.

<tgr>

This refers to time granularity.

The following table names correspond to the boxes in the figure for Nokia AXC:

Raw and aggregated measurement data is contained in database objects with the following
names (these database objects are not accessed directly by data processing or reporting
applications):

NOKAXC_P_MEAS_PDH_O2 and NOKAXC_P_PDH_PPTT1_DAY

Measurement table that is used for writing data into the Performance Manager database:

NOKAXC_PV_PDH_PPTT1_RAW and NOKAXC_PV_PDH_PPTT1_DAY

Measurement views that are used for reading data from the Performance Manager database:

NOKAXC_PS_PDH_PPTT1_RAW and NOKAXC_PS_PDH_PPTT1_DAY

Note:

The aggregation process only needs the raw measurement table for those adaptations that
use the OMeS 2.0 measurement data format. Adaptations that use the OMeS 1.0 format,
for example, Packet Core Adaptation, also need information from the P_MeasuredObject
table for the aggregation.

The Performance Manager database also contains metadata tables. PM Data Extraction and Loading
accesses one type of metadata tables when it is loading the raw data to the Performance Manager
database. The Performance Manager applications reads from and writes to other metadata table that
contains report-specific information.

3.3.1 Database Partitioning Manager


Partitioning Manager maintains the partitioned measurement tables. The expired data is cleaned up
with partition dropping.

DN09140649 3-0 2016 Nokia Solutions and Networks 14


Performance Management Overview Measurement collection and processing in Performance Manager

The usage of partitioning in a measurement table makes a large table more manageable when only a
part of the data is the target and it is delimited by the measurement time period. Partitioning is useful
for large volumes of data. Also, if a measurement table contains historical data, and new data is added
into the newest partition, it means that a rolling window of data is stored.

Local index partitioning is applied for the indexes of the measurement tables. A local index is
automatically partitioned in the same way as the table is partitioned. New internal alarms are raised
and canceled by PM DB Partitioning Manager.

The benefits of partitioning are:

Clean-up of expired data is faster when a partition gets dropped instead of data being deleted.
Query performance is better. The results of a typical query of PM data can be achieved by
accessing a subset of partitions rather than the entire table.
PM data insertion into a partitioned table is faster.
Index rebuilding can be done for partitions and not the whole index.

3.3.2 Time zone support


When the NetAct Cluster has network elements on different time zones integrated into NetAct, the PM
data going to the NetAct database can be stored using one of the following options:

Network element time (Default): Keep the time stamp from the network elements with their local
time.

Any requests to the PM database for raw data returns with the original network element time
stamp.

For more information see Network element time zone handling.

NetAct time: Configure NetAct to convert the network element time stamp to NetAct time. Using
this option PM data is stored in the database using NetAct time zone.

When this option is enabled, PM data is stored in the database using NetAct time zone.

For more information see NetAct time zone handling. To enable this option, see Configuring
multiple time zone handling.

Note: The NetAct time option is not supported by SGSN and BSC network elements.

Network element time overview

Using the default time zone configuration, the local time sent by the network elements is stored on the
NetAct database. This means that the NetAct server where data aggregation is executed is not aligned
with the network elements time stamp.

Depending where the server is located, two types of problems can arise because of different time
zones.

DN09140649 3-0 2016 Nokia Solutions and Networks 15


Performance Management Overview Measurement collection and processing in Performance Manager

1. If NetAct server is located to the west of the network element, there is a risk of data arriving from
"the future". For example, if the server is located in Seattle, and aggregation is scheduled for
midnight on a Tuesday, data still arrives from New York City where it is already Wednesday. See
the following figure for the representation of the problem.

Figure 2: Network element time ahead of the server time zone

2. If the server is located to the east of the network element, data can keep arriving after the day
is over for the server. This results in unnecessary re-aggregation. For example, if the server is
located in New York City, and aggregation is scheduled for midnight, aggregation is executed with
a three-hour delay, waiting for and re-aggregating data from Seattle. See the following figure for
the representation of this problem.

DN09140649 3-0 2016 Nokia Solutions and Networks 16


Performance Management Overview Measurement collection and processing in Performance Manager

Figure 3: Network element time zone behind the server time zone

The following table lists and describes the possible situations that happen when network elements are
sent to the database from different time zones.

Time stamp of
Network element time NetAct
NE time measurements Impact on measurement aggregation
zone time
from the NE

NE in the same time 22:00 22:00 22:00 Aggregation happens according to the schedule.
zone as NetAct

NE ahead of the server 23:00 20:00 23:00 Data from the server ahead of the time zone arrives
from 'the future'.

NE behind the server 20:00 23:00 20:00 Data arriving after the aggregation is scheduled
in the time zone of the server is 'late data'. All
data, including late data, gets re-aggregated for an
updated daily summary.

Table 2: Examples of processing problems of network elements from different time zones

The time zone support in the reporting tools solve the problems described above by always taking
into account the local time of the network elements. If the client of the reporting tool is located in a
different time zone from that of the server, the reporting period queried by the tool is the reporting
period according to the client's time zone. If the client wants to query data from the period of the
previous two days up to the current time, the reporting tool selects all data up to the latest data sent by
the network elements. If there are network elements from a time zone ahead of the time zone of the
client, their data is displayed too, because the meaning of 'current time' is always the current time of
the network elements.

DN09140649 3-0 2016 Nokia Solutions and Networks 17


Performance Management Overview Measurement collection and processing in Performance Manager

NetAct time

Using the NetAct time configuration, the network elements local time is sent to NetAct, but when
storing the PM data NetAct adjusts the time according to the network element time zone. With NetAct
time enabled for time zone handling, the PM data aggregation is executed with the network elements
time stamp already aligned with NetAct.

There are impacts during activation of this functionality, depending on the location of NetAct server
and the network element.

1. During activation, if the NetAct server is located west of the network element time zone, as data
arrives and NetAct time is used to process the information we have an overlaps with the existing
PM data. During the synchronization period the NetAct system performance can be affected.

Figure 4: Multiple time zone handling with NE time ahead of the NetAct time

2. During activation, if the NetAct server is located east of the network element time zone, as data
arrives and NetAct time is used to process the information a gap is created on the PM data.

DN09140649 3-0 2016 Nokia Solutions and Networks 18


Performance Management Overview Measurement collection and processing in Performance Manager

Figure 5: Multiple time zone handling with NE time behind of the NetAct time

Note: When NetAct time zone handling is enabled, the overlap and gap can also occur in
regions that use daylight saving time while NetAct server and network element time is not
aligned.

3.4 Post-processing measurement data in Performance Manager


This section has a description of the further processing done in Performance Manager on the
measurement data.

Performance Manager also performs post-processing on the measurement data to enhance the
performance of the processes. Performance Manager supports aggregation to speed up data
processing, allow flexible report generation from the measurement data, and avoid database overload
by not storing raw data for more than a few of weeks. PM data is typically aggregated for each counter
in time and network element (object) dimensions.

DN09140649 3-0 2016 Nokia Solutions and Networks 19


Performance Management Overview Measurement collection and processing in Performance Manager

3.5 Using historical MO and parameter data for measurement


processing
This section has a description of the Performance Manager functionality that provides historical
information on managed objects and radio network parameters.

Object History compiles information on managed objects from Topology Platform (TPF) and on radio
network parameter settings from NetAct Configurator. The information is compiled daily.

3.6 Parallelization of aggregation, export and import


To improve the performance of the aggregation of raw data into summary data, the aggregation
process is parallelized. The parallelization considerably reduces the time required by Performance
Manager to aggregate raw data.

DN09140649 3-0 2016 Nokia Solutions and Networks 20


Performance Management Overview Creating and analyzing measurement data with Performance
Manager

4 Creating and analyzing measurement data with


Performance Manager
This chapter has a description of the main reporting applications of Performance Manager.

Performance Manager is designed to help you analyze and optimize the entire managed network. It
facilitates the decision-making processes of everyday operations that guarantee quality for end users,
the processes that govern technical development to cope with capacity and coverage demands, and
the processes of long-term forecasting for future network growth.

Performance Manager provides you with a unified and scalable reporting environment in which
you can create reports with easy-to-use applications, according to your operator-specific needs.
The applications can offer key statistical information on faults and the multi vendor capability of
Performance Manager assists you to monitor the performance of the entire network that can contain
elements from Nokia and other vendors.

Performance Manager is mainly metadata-driven. The Performance Manager users can use all data
sources that have been integrated, whether they are Nokia network elements or third-party systems.
You can freely combine data from different object levels and from different vendors' network elements
into the same report.

The reporting applications and the reporting contents are based on measurement data that is based
on raw or aggregated measurement data. For more information, see Section Performance indicators
and key performance indicators.

4.1 Performance indicators and key performance indicators


This section has a description on how measurement information is filtered and the performance
analysis is narrowed with PIs and KPIs and how they provide you with a manageable set of indicators
from among the high number of measurements in the network.

DN09140649 3-0 2016 Nokia Solutions and Networks 21


Performance Management Overview Creating and analyzing measurement data with Performance
Manager

Figure 6: Performance indicators and key performance indicators

The database contains a very large number of counters which all are elementary performance
indicators. For practical purposes, however, it can be difficult to interpret the indicators, because they
often provide data on a very specific aspect of the network. It can also be difficult to determine the
relevance of a counter value with respect to network performance if you study the counter in isolation.

You can detect the first signs of performance degradation with KPIs and prevent network problems
from becoming critical. You can use the KPIs at the regional level for analyzing performance trends, for
example, at the RNC level for locating problems, and at the cell level for troubleshooting specific cells.

KPIs are stored in the database separately from the measurement data and you can modify them
independently: if you modify a KPI you do not modify a counter or a measurement.

Nokia recommends a set of KPIs for each subnetwork, for example, RAN, BSS, SCN, or PCN. KPIs
are implemented in optional content products, such as Performance Manager.

The predefined set of counters produce a very high volume of measurement information. However, it is
very likely that you are not interested in all the counters from a network element or a network element
class unless you are troubleshooting a specific problem. So, the first step in filtering out unwanted
information are sets of PIs that are predefined by the available measurements and counters in the
network. You can further refine and focus your PM monitoring if you use predefined KPIs or you define
your own KPIs in NetAct. Finally, you can use the different KPIs in different reports, allowing further
filtering of PM data for particular reports.

DN09140649 3-0 2016 Nokia Solutions and Networks 22


Performance Management Overview Creating and analyzing measurement data with Performance
Manager

4.2 Creating a report with Performance Manager


The Performance Manager presents reports in graphical and tabular format. By changing the settings
of the reports at run-time, you can focus on various dimensions in the data, for example, on a
particular time period (time dimension) or a network element type (object dimension).

You can create KPIs and reports, without being experienced in SQL, with Performance Manager,
which has been designed for creating and running a wide range of various reports on the performance
data from different network technologies. Furthermore, you can administer access rights to reports and
formulas for the web-based reporting applications.

You can build up and administer the reports (Detailed Reports and Saved Reports) panel, which is
a structured list of the provided and created reports, and the KPI panel, which contains all of the PIs
from the adaptations as well as the KPIs that have been created with KPI Creator.

If the KPIs that you need in your report do not exist yet, you first have to create the KPIs with KPI
Creator. For instructions, see KPI Creator help in Performance Manager Online Help.

You can create a permanent report with the Report Creator Wizard application of Performance
Manager. For instructions, see Report Creator help in Performance Manager Online Help.

Furthermore, Performance Manager provides numerous data-analyzing capabilities and an enhanced


XLSX or CSV export interface keeping the format settings during the export operation.

4.2.1 Creating KPIs


KPI support is a core feature of Performance Manager. You can create, modify, or delete KPIs. Since
KPIs are logical entities that are not bound to a certain aggregation level, you usually only have to
define them once. Depending on the permission that you assign to them, the KPIs can be available for
any type of reports at different levels once they have been created.

Figure 7: KPI Creator application

With KPI Creator you can:

DN09140649 3-0 2016 Nokia Solutions and Networks 23


Performance Management Overview Creating and analyzing measurement data with Performance
Manager

1. Create or edit custom KPIs from existing KPIs or counters or both.


2. Define the name of the new formula and add a description of the formula.
3. Define the unit of the new formula.
4. Use ORACLE functions to build formulas.
5. KPI formula validation.

4.2.2 Creating reports


You can create reports in with the PIs and KPIs that are already available. A report is defined by the
following components:

A combination of facts (PIs or KPIs)


Dimension selections for each fact, for example, time or network elements
Visual settings

The flexibility of the metadata-driven approach provides you with various options for facts and
dimensions. For example, support is available for different time hierarchies, maintenance regions,
working sets, adjacencies, and CI/LAC addressing.

Figure 8: Report Creator Wizard application

The Report Creator Wizard guides you through all the steps of creating a report. The wizard consists
of five panels that include the following tasks:

1. Selection of the object based on the Technology, Hierarchies and Report Level selected.
2. Selection of the time period in which the report runs.
3. Selection of KPIs or counters, or both, to be included in the report.
4. Assign the report Name and Description and preview the report results before saving the report.

DN09140649 3-0 2016 Nokia Solutions and Networks 24


Performance Management Overview Creating and analyzing measurement data with Performance
Manager

5. Customizing the report dashboard by adding or removing panels and setting the chart options.

4.3 Managing permissions


You can set and change permission of the KPIs and reports in two ways:

Private

The reports are available only for the report owner in the My Reports panel. The KPIs are
available only for the report owner in the Custom KPIs panel.

Published

You can set the KPIs and reports to become available to all users. Administration rights are
required to publish the KPIs and reports. The reports become available to all users in Detailed
Reports panel.

For more information and instructions, see KPI Publisher help and Detailed Reports Publisher help in
the Performance Manager Online Help.

4.4 Caching and Scheduling report


Every report, which can be cached is written to a cache after the report has been generated. If you
call the report a second time, it comes from the cache instead of the various database tables. If the
internally calculated expiry date of the report cache has elapsed, an automatic cleanup process
removes the expired report cache. The automatic cleanup process runs every night.

Performance Manager can also schedule reports. Scheduling a report allows you to run the reports
at regular intervals, at times that you can specify. When the scheduling time is reached, the report is
written to the cache. Additionally, you can define e-mail addresses to which the report, namely the
table and the chart, is sent after report creation.

Caching and Scheduling supports the daily processes of PM reporting and increases the usability
of viewing reports. Routine tasks of checking regular reports can be accelerated by precalculated
reports. Scheduled reports are calculated at a specific time, for example, during the night and stored
for fast execution when they are demanded. Scheduled reports can even be sent to an e-mail recipient
after execution. Calculating complex KPI reports generally takes some time for the query execution.
Performance consuming reports, which are needed on a regular basis, can be precalculated at certain
intervals and are available immediately when the user accesses them. Frequently accessed reports
can be cached for a certain period of time and are available for all the users without recalculation and
the system is not loaded again for the same report.

All the reports may be scheduled for a certain time on daily, weekly, monthly recurrence or one time
only. Scheduled reports are marked in the Saved Reports panel with an icon, so that you can see
which reports you can call with a guaranteed response time.

DN09140649 3-0 2016 Nokia Solutions and Networks 25


Performance Management Overview Creating and analyzing measurement data with Performance
Manager

4.5 Analyzing the measurement results with Performance Manager


This section has a description of the applications with which you can access Nokia defined reports or
reports that were created with Performance manager application.

The Performance Manager you to view predefined reports or browse KPI/PIs at any time and place. In
graphs and tables, it provides fast graphical visualization of reports, PIs, KPIs, and formulas that you
can manage. You can configure for a report to show a table, a chart or both.

With the Change Selections panel you can easily change the reports parameters and generate the
report output.

Figure 9: Change selections

The Report Output panel allows you to visualize the report results and customize the outputs with the
following functionalities:

Quick Time selection - Allows you to change the time settings with one click. The available time
settings are configurable for each report by the administrator.
Quick Object selection - Allows you to change the report object in the same object level.
Quick Time Level selection - Allows you to change the report time level.
Exports the report information as an XLSX or CSV file.
Report Information - Displays the Report Info (technology, report level, object level, object
selection, time level, description and KPI selection) the KPI Details and the Data Reliability
information.

DN09140649 3-0 2016 Nokia Solutions and Networks 26


Performance Management Overview Creating and analyzing measurement data with Performance
Manager

View options - Allows you to change the output results between the table mode or the several
chart modes available.
Chart Options - Allows you to set KPIs for the Primary and Secondary Y-Axis, Enables or disables
the toggle data point or set the axis limits.
Show options - Allows you to display all captions in a separate window or filter the start time period
and the KPI values range.

Figure 10: Report Output

For monitoring and managing the NetAct PM pipe and aggregation that provide the measurement data
in your reports, use the optional functionalities of the Admin Toolkit.

DN09140649 3-0 2016 Nokia Solutions and Networks 27