npo seminar training alcatel

1All Rights Reserved Alcatel-Lucent 2007

NPO Seminar

December 2007

All Rights Reserved Alcatel-Lucent 2007NPO Seminar PORTUGAL December 2007

NPO SEMINAR

DAY 1

2All Rights Reserved Alcatel-Lucent 2007NPO Seminar PORTUGAL December 2007

Agenda

1. Introduction

2. Differences between NPA/RNO and NPO

3. Getting Started with Analysis Desktop

4. Organization and concepts

5. Objects Execution

6. Propagate Network Objects

7. Topology Object Properties

8. Exercises


1 Introduction


Introduction

The main propose of this seminar is to present the differences between RNO and NPO.

Although, a global and rich view of NPO will be given to the trainees during this seminar.

Is recommended that every trainee has some experience on RNO in order to better understand the differences between this two tools.


Introduction

Powerful Graphical User Interface supporting all efficient use of the NPO A9159

QoS analysis

Tuning Sessions to configure Radio resources

Cartographic telecom management

Administration Facilities

QoS data customization

Extra functions to investigate and solve QoS issues

NPO (Network Performance Optimizer) offers a full range of multi-standard QoS Monitoring and radio network optimization facilities:

NPO includes the multi-standard version of the previous products deployed in Alcatel-Lucent networks: A9156 / A1353-UR RNO, NPA, and LASER.


Introduction

NPO supports GSM, UMTS and WiMAX Radio Access Networks.

This product includes a powerful Oracle database containing performance measurements and calculated indicators.

Performance measurements ensure:

Efficient planning of the network

Efficient optimization of the network

Usage statistics

Detailed investigation of a problem

Real-time analysis


Introduction

Have access to all data sources in order to satisfy any composite indicator requirement

Indicators combining all data sources

Import

storage

TopologyEventAlarmLog

RadioParam

QosData Inventory Planning

GeoData

Data Warehouse


2 Differences between NPA/RNO and NPO


Differences between NPA/RNO and NPO

To provide enhanced functionalities Answering to customer requests

Removing limitations of the previous generation

By using an up-to-date software technology

To reach higher capacity One NPO instance managing up to 24 000 cells and more in the future

New design for managing all standards (GSM, UMTS, WiMAX) NPO evolutions will benefit to all technologies

NPO is also embedded in the MS-OMC Portal (=> MS-NPO)

Why a new tool like NPO was necessary?



Network Performance Optimizer (NPO) Merge of NPA/RNO/LASER (previous tools)

Unique expert tool on the market

OMC-R



NPAy Access to all raw PM counters and some stored

indicators (KPI)y HMI based on Metrica and PM browsery Reporting based on Metrica means

RNOy Additional calculated QoS indicators (KPI)y Based on a well-recognized and field-proven HMIy Reporting including interface to EXCELy Optimization features: cell parameter values display,

rules checking on parameters, parameters tuning, neighbourhood management, diagnosis, cartography, interface with planning tools (RNP),

LASERy Network Element unavailability indicator computation

(inserted in NPA database)

y Alarm statisticsy Network remote inventory

++

++

NP

O



Easy to use One database and one tool in the same machine (hardware and software)

Integrated GUI with many usability improvements

Simplified QoS analysis: e.g. roll-up/drill down by a single click

Simplified administration: easy secured Oracle backup, administration through web

Flexibility and ability to customize the tool Graphical editors for indicators, views, reports, diagnosis scenarios,

More user preferences

Reference values and rules customization

Programming language for diagnosis scenario

Generalization/Extension of RNO functions Functions available on cells now available on any object

Export format: XLS but also PDF, CSV, HTML and XML



Improvement in the QoS analysis process

Spatial and temporal roll-up / drill-down by a single click

Granularity period of 15min PM data available

Indicators of the current day can be displayed

Views are available

Mixing parameters, counters and indicators in one single view

Easiness to create customer indicators based on counters (or other indicators)

Customer indicators can be built by temporal aggregation and they can be stored in the database



All administrative functions accessible through web No need to run the Analysis Desktop (AD) for administration purposes PM collection follow-up Access to scheduled reports through a standard web URL

Easy and secured back-up Thanks to Oracle archive system

External interfaces Web interface: EQL (Extensible Query Layer)

SQL interface (planned)



Single tool and database architecture

All data in one database

Merge of NPA, RNO and then LASER (starting from B10 MR2)

One hardware server instead of 2 or 3

Capacity to create indicators and reports mixing information previously located in different databases



Dimensioning and Hardware configurations

Same hardware for NPO as for NPA in B9

Same capacity as in B9

Possibility to reach higher capacities: up to 24000 cells

LASER remains an external product in B10 MR1

A9159 capacity

250 cellsEmbedded

2000 cells 5000 cells 8000 cells 10500 cells /12000 cells (**)

24000 cells (**)

B10 V490 2 CPUV880 2 CPU

V490 2 CPU

V880 2 CPU

V490 2 CPU(*)

V880 4 CPUV880 8 CPU V490 4 CPU (*)

V880 8 CPU (*)

2 xV490 4 CPU

(*)

(**) with B10 MR2 and with V490 with 146 GB disks in the external disk bay(*) with 3510 external disk bay



LAN

NPA server

OMC-ROMC-R

OMC-R

remote clients

RNO / LASERmain servers

WAN

Local RNO clients

RNO/LASERCitrix servers

LAN

NPO server

OMC-ROMC-R

OMC-R

remote clients

NPO HMIservers

WAN

Local NPO clients

NPO clients or NPO HMI servers

NPA/RNO NPO

10


RNO and LASER main servers can be reused as NPO HMI servers (Citrix) If equipped with 4 GB RAM min.

5 user sessions

If equipped with 8 GB RAM min. 10 user sessions

RNO and LASER clients can be reused as NPO clients If equipped with 1 GB RAM min.

RNO and LASER Citrix servers can be reused as NPO clients or NPO HMI servers

LAN

NPO server

OMC-ROMC-R

OMC-R

remote clients

NPO HMIservers

WAN

Local NPO clients

Local NPO clients



A9159 NPO = Merge of NPA + RNO + LASER

All functionalities included in one tool with one database

Providing enhanced functionalities and higher capacity

Generalizing concepts used in RNO

Removing limitations of the previous toolchain

This A9159 can then be upgraded as a MS-OMC Portal (A1353-MP). This allows adding the Multi-standard dimension and/or the Supervision functionality


11


3 Getting Started with Analysis Desktop


Getting Started with Analysis Desktop

Analysis Desktop Functions

QoS analysis through counters, indicators and reports

Reference values

Rules and diagnosis

Events

Logical and design parameters

Tuning

Cartographic display

Thematic Layers

Network stability and availability, alarms

QoS Data Customization

User preferences

12



Initialize Analysis Desktop

Starting from M2.3, NPO Client (Analysis Desktop) is installed on client by a remotely way.

No CDs are needed to install the client, instead of this, client is installed automatically.

If the server is migrated to a further version, the client will be migrated as well automatically.

To download the client start up file use the following link:

http:///iconbox/WEB-INF/webstart.jnlp

Notes:

= ip address or the hostname of npo server

= number of MUSE instance



To see the client traces on java console, enable Show console in JavaTM Control Panel localized on Windows Control Panel.

13



Launch Iconbox

To launch iconbox just click on webstart.jnlp.

After that, a login window will appear.



Iconbox Optimization menu

Notes:

RIDM Remote Inventory Data Management

NUART Network Unavailability and Alarm Reporting Tool

14



Iconbox Security menu



Iconbox Log menu

15



Iconbox Platform and Administrator menu



Iconbox NPO Help menu

16



Initialize Analysis Desktop

AD is launched from: MUSE Applications-> Optimization -> Analysis Desktop



Initialize Analysis Desktop Select Working Zone

Every time that AD starts, user can choose the working zone which will be loaded into AD.

This is a behaviour similar to RNO.

First time

Second time and so on

17



Tip of the day

After AD initialization, a Tip of the day window appears by default.

This feature can be invoked by selecting menu Help -> Tip of the day


4 Organization and concepts

18


Standard Tab

Mode Tabs

Topology Browser Functions Browser

Browser for:

- Reports

- Tuning

- Detailed Diagnosis

- Cartography

View Browser

Analysis Desktop

Organization and concepts



Standard Tabs

In standard tabs we can use the following technologies:

GSM

UMTS

WIMAX

Only the installed technologies are available/visible in AD.

It is possible to define the pretended technologies to use. Right click on a standard and select Organize Standards

19



Mode Tabs

Each standard has a set of modes.

These modes represent one type/zone of network elements and some of them are new in NPO:

- MFS- SGSN_IP_NSVC- SGSN_ITF - Adjacencies2GTo3G- TRX TS- X25- N7LS- BTS BSC LAPD- Generic Zones- GSM 2G External Cells- GSM 3G External Cells

According to the selected mode, the list of functions can be different. Functions are filtered according to their availability domain.

11 NEW MODES



Mode Tabs

Like Standard tabs, it is also possible to organize modes using right click on a mode.

The Organize Modes window opens, displaying the available modes.

20



Mode Tabs

It is possible to hide one mode without going into Organize mode.

User can select Hide Mode directly after a right click.

This option is also valid in Standard Tabs



Mode TabsThe availability of modes will depend on the number of cells. NEW

If there are more than 1000 cells in All classification tab, 10 modes will not be displayed in order to maintain an acceptable performance.

To see all the modes we need to open a standard

working zone.

21



Topology Browser

This browser is composed by 3 zones:

Topology Classification Tabs

Topology Tree

Topology Status Bar

Topology Classification Tabs

Topology Tree

Topology Status Bar



Topology Browser - Topology Classification Tabs

These are the set of tabs for topology mode classification.

If all tabs cannot be displayed due to the width of the Topology Browser, arrow buttons appear allowing the user to scroll among all the existing tabs.

Topology Tab Menu

Different tree gadgets are used to display the network resources by different classification criteria.

22




Each Topology Classification can vary from Mode to Mode.

Cell:

BSS / X25 / BTS_BSC_LAPD / N7SL / N7LS / AIC / GPU:

SGSN_IP_NSVC:

MFS / SGSN_ITF / GSM 2G External Cells / GSM 3G External Cells:

Adjacencies / Adjacencies2GTo3G:

Traffic Zones:

TRX:

TRX TS:




BTS / BSC_MFS_LAPD:

PVC / Bearer Channel:

Cell Zones / TRX Zones:

Generic Zones:

These are the default topology classification tabs presented by NPO.

Anyway, NPO user can create their own topology classification using Topology Classification

Editor.

New topology classification in NPO: BTS_D, GPU, To External and LAC -> LAC.

23



Topology Classification Editor

To open this editor there are 3 possibilities:

1. Right click on topology classification

tab and select Topology Classification

2. Use menu Topology -> Topology Classification

3. Press Ctrl+T



Toolbar

Properties and Definition PanelObject Selection Tree

Sub-Object Selection Tree

Topology Classification Editor

24



Topology Classification Editor - Create Topology Classification

1. In the toolbar, click on Create button

2. Fill the appropriated fields

3. Drag and drop sub-objects to classification definition

Creation of Topology Classification to group all cells with EDGE activated



Topology Classification Editor - Create Topology Classification

4. Click on Apply and confirm with Yes on the following window.

In this case, it was been created a new topology based on EN_EGPRS parameter.

As this parameter has two options: Enable or Disable, the tree will be displayed according to these two options.

25



Select Filter on Topology Classification

NPO user can choose one of the available filters associated to a mode and apply it on a topology classification of the concerned mode.

1. Select a topology classification, right-click and choose Select Filter.

A window with the list of existing filters is displayed, but without the current active filter. The first item is labeled No Filter and is used to remove any filter on the classification.

2. Select the appropriate pre-defined filter.

The topology tree is refreshed according to the filtered classification.

Remark: 18 cells didnt have value for EN_GPRS. N/A values are ignored by this filter



Functions Browser

This browser is composed by 3 zones:

Functions Tabs

Functions Tree

Functions Status Bar

26



Functions Browser

Tab menu from this browser is very similar to Topology Browser.

The Classification can vary from Function to Function.

Functions available in NPO:

View NEW

Free Fields NEW

Counter

Indicator

Logical

Diagnosis Scenarios

Thematics

Rules

Design

Report

Tuning

EventsThe list of functions vary with the selected mode



Functions Browser Functions distribution

Cell / SGSN_IP_NSVC:

BSS:

MFS / SGSN_ITF:

Adjacencies:

Adjacencies2GTo3G:

Traffic Zones / Cell Zones / TRX Zones / Generic Zones:

TRX / GSM 2G External Cells:

TRX TS:

BTS:

27



Functions Browser Functions distribution

X25 / BTS_BSC_LAPD / BSC_MFS_LAPD / N7SL / N7LS / AIC /GPU / PVC / Bearer Channel:

GSM 3G External Cells:



Function Classifications

The Function Classification defines how functions are classified in a tree structure.

It is not dependant on the used technology.

Function Classifications can be:

System, as defined by Alcatel-Lucent

Customer, when defined by the user

In Analysis Desktop, the Function Classification Trees display only:

Public and owned private objects

Visible objects

28



Function Classification Editor

To open this editor there are 3 possibilities:

1. Right click on functions classification

tab and select Function Classification

2. Use menu Data -> Function Classification

3. Press Ctrl+U



Function Classification Editor

29



Function Classification Editor - Create Function Classification

In this example, it is shown how to display the indicators by their unit.

1. In the toolbar, click on Create button

2. Fill the appropriated fields

3. Drag and drop sub-objects to classification definition. Unit in this case.

Creation of Function Classification to organize Indicators by unit



Function Classification Editor - Create Function Classification

4. Click on Apply and confirm with Yes on the following window.

If we choose this new classification, then the result will be a tree organized by the indicators unit.

NOTICE: Tuning, Events and Free Fields cannot be managed in function classification editor.

30



View Browser

The view browser is the target place to drag and drop one or more network resources and one or more functions.

It contains views NEW that are used to display values of counters, indicators, view templates NEW, logical and design parameters, rules, events, free fields NEW and diagnosis.

The displayed data in the view can be exported to Excel for further analysis. This action can be done by a single copy and paste NEW.

Two mode forms are available: tabular and graphical.



Report Browser

The report browser is the target place to drag and drop one or more network resources and one or more functions. Cartography and Tuning Sessions are managed in this browser.

This browser can manage reports, view templates, indicators, logical and design parameters, diagnosis, thematics (Cartography), rules, tuning (Tuning Sessions) and Events.

A report is composed of several views, each displaying a set of defined indicators or parameters for a user defined report period.

Data displayed in the report can be exported to Excel for further analysis. This action can be done by a single copy and paste NEW.

31


5 Objects Execution


Objects Execution

NPO allows the operator to execute views (on counters or indicators) with more periodicities than RNO.

On counters NPO allows the following periodicities during view execution:

- Provides counters normalized at quarter level NEW

- Provides counters normalized at quarter level NEW

Raw - Provides counters as they are in the PM files NEW

Hourly - Provides counters normalized at hourly level

32


Objects Execution

NPO allows the operator to select a default period of time using Default Dates NEW.

The default time period varies from each periodicity.

Hour, , , Provides all the previous hours for the current day.

Day Provides the previous day.

Week Provides the previous week.

Month Provides the previous month.

Trend on hours of day Provides last 7 days sice yesterday.

Trend on hours of week Provides last 14 days since yesterday.

Trend on days of week Provides last 28 days since yesterday.

Trend on days of month Provides last 84 days since yesterday.


Objects Execution

There are some execution options available in NPO.

The option to select the QoS Requirement in execution context is new in NPO.

33


Objects Execution

Forecast Values in Tuning Sessions NEW (1/3)

To select tuning sessions/jobs for forecast values:

1. Click on [Tuning Sessions]

The list of all owned tuning sessions and all tuning jobs are displayed.

The limit for the number of tuning sessions and jobs that can be selected to be displayed is 20 by default.

The Tuning Sessions are available only for parameters.


Objects Execution


To select tuning sessions/jobs for forecast values:

2. Select one or more tuning sessions/jobs from which the corresponding forecast values would be displayed in the view.

34


Objects Execution


This value is mandatory if forecast is chosen to be displayed for parameters in the view template or in the user preferences.

This value is not needed if forecast was not chosen or if there is no parameter in the view.


Objects Execution

Filter Unavailable Objects NEW

The user can choose to filter warning reports, based on:

1. QoS Availability Indicator2. Comparison Operator3. Threshold value

This field is not used if Execution Context is not subject for a warning report. If the execution does not imply a warning report then the panel is grayed.

QoS Availability Indicators are used to filter objects based on the Comparison Operator and the Threshold Value.

The following values are used as comparison operators: >,

35


Objects Execution

Event Synthesis (1/3)

Select Display Event Synthesis, to display the Event Synthesis in both tabular and graphical modes for the given network object.

This feature is used in case of a Mono-Object evolution view with daily periodicity that contains only standard indicators and/or parameters.

Click on [ Show Event Synthesis options ] to view the list of available events.

Select from the Event Synthesis Options list, the event type that composes the event synthesis. It is mandatory to select one type if Display Event Synthesis is set to Yes.


Objects Execution


36


Objects Execution


It is possible to check more details from Events in Event Details button.


6 Propagate Network Objects

37


Like was in RNO, also in NPO is possible to propagate network objects in order to associate several types of objects. It is just a matter of drag and drop and if you see this symbol ( ) it means that it is not possible to propagate the relation.

A total of 41 new propagations are available in NPO.

From Cell: 1) BSS2) MFSNEW

3) Traffic Zone4) BTSNEW

5) GPUNEW

6) Cell ZoneNEW

7) Generic ZoneNEW

8) Adjacencies9) Adjacencies2GTo3GNEW

10) TRX11) TRX TSNEW

Propagate Network Objects



Propagations available in NPO

From BSS: 1) Cell2) MFSNEW

3) Traffic Zone4) BTSNEW

5) GPUNEW

6) Generic ZonesNEW

7) Adjacencies8) Adjacencies2GTo3GNEW

9) TRX10) TRX TSNEW

11) X25NEW

12) BTS_BSC_LAPDNEW

13) BSC_MFS_LAPDNEW

14) N7SLNEW

15) N7LSNEW

16) AICNEW

38




From BTS: 1) CellNEW

2) BSSNEW

3) Traffic ZoneNEW

4) GPUNEW

5) Generic ZonesNEW

6) AdjacenciesNEW

7) Adjacencies2GTo3GNEW

From GPU:1) CellNEW

2) BSSNEW

3) BTSNEW

4) PVCNEW

5) BCNEW

6) Generic ZonesNEW




From PVC: 1) Bearer ChannelNEW

2) Generic ZonesNEW

3) GPUNEW

From Bearer Channel:1) GPUNEW

2) Generic ZonesNEW

From MFS:1) BSSNEW

2) GPUNEW

From BTS_BSC_LAPD / BSC_MFS_LAPD / N7SL / N7LS / X25 / A Interface: 1) BSSNEW

2) Generic ZonesNEW

39


7 Topology Object Properties


Topology Object Properties

The operator can check several properties from network objects using properties button of right-click menu over the object.

In cells and TRXs there is more information below this properties table.

40



In cell properties user can find the following information:

Frequencies and TRX Mapping Neighbourhood OMC External View



If the user open the right-click menu over one network object a list of features are available to manage the selection of objects.

The resulting cells are added to the selection, the tree can be expanded, but it is not scrolled.

Alcatel-Lucent provides the following predefined and non-modifiable set of cell classes, known as system cell classes: Rural Suburban Urban Dense urban IndoorSystem cell classes cannot be viewed, modified, or deleted using the Network Object Class Editor.In order to fit with their own optimization methods, the optimizer may define additional customer cell classes.

41



Post-Its

In NPO it is possible to add, edit and removed post-its associated to one network object.Post-Its are visible to all users and are clearly visible in topology or function trees.A yellow icon ( ) being attached to them, then a tooltip comes up with the post-it.

Similar to Note feature in RNO.



Manage Tuning Inhibition of Network Objects

By default, all network objects are admitted for tuning, but the tuning operation can beforbidden on some network objects and a reason can be described.

If the operator inhibit network objects, then they are no longer accepted for tuning and their labels appear in italic format.

A notification is sent to all the clients about the new status of the concerned network objects.

Similar to Inhibit Cell tuning in RNO.

42


8 Exercises


Exercises

1. Hide the following modes: N7LS and TRX TS.

2. Find a way to see Cells based on their number of TRX.

3. Find a way to see Rules organized by Severity.

4. Try to find Events in the Network and specify the events if you find them.

5. How many cells has s222 BSC?

6. What is the GPU of cells 99 and 44502?

7. What is the external ID and friendly name of the parent object of cell 44500?

43


Exercises

8. Add a new Post-It. Then find another Post- it and try edit this Post-it.

9. Check the Notification Window.


NPO SEMINAR

DAY 2

44


Agenda

1. Counters and Indicators

2. Parameters

3. Exercises

4. Views

5. Reports

6. Exercises


1 Counters and Indicators

45


Counters and Indicators

Introduction

Counters are retrieved from the BSS and MFS and used as building blocks in the formation of indicators.

The indicator is computed from counters, other indicators or any other available network parameter values such as radio parameters.

An indicator can be stored. For stored indicators, the storage duration can be configured.

In order to perform some actions in NPO it is necessary to install a specific license.

MUSE_QOS__LICENSE - To declare QoS data sources for a given technology MUSE_QOS_INDICATOR_CREATION_LICENSE - To create customer indicators MUSE_QOS_HISTORY_LICENSE To save historical QoS data more than one week.



Storage

Counters values are not stored into NPO database.

Basic indicators are always stored, but only a limited number of basic indicators is supported.

Calculated indicators are not stored in the database unless they have an associated stored temporal aggregation.

Every stored indicator has an indicator group and the table name will be related to this group. In the data warehouse, each indicator group corresponds to a different table.

46



A counter is defined by:

Reference Unique counter reference (ASCII) Long Name Unique long counter name (mnemonic) StructureType 4 types are supported - scalar, axis, vector or matrix Description Counter description Source Network Object Type of object supporting the counter Collecting Network Object - Type of object collecting the counter PMType PM Group files per Type LoadMapFormula Simple formula to apply before loading the counter (ex: *100,

means counter*100) Interpolation Method used to compute the missing values Consolidation Method used to compute hourly value - Normalization. Unit Counter Unit Precision Number of significant digit displayed to the operator

There are more counter attributes and they are described in NPO User Guide.

GSM only


A Telecom Indicator has two types.

Basic Indicator (stored and based on a counter formula)

Calculated Indicator (not stored and based on a indicators formula)


Counters Formula

Indicators Formula

Interpolation method

Consolidationmethod

Indicator Group

47



Indicators Dictionary Attributes

Name Version Date Author Description Type - {System, Customer}

Release Attributes

Technology Supplier Name Version Description

Dictionary example



Indicator Group

Name Spatial Aggregation Path

Telecom Indicator Definition

Long Name Reference Description Unit Upper is fault Flag to indicate whether the quality is better when the value is higher

or the opposite. Structure Type {Scalar, Axis, Vector, Matrix}

Each structure type has their own attributes like value type, size, etc

48



Telecom Indicator Definition

Here is an example of a matrix indicator.



Basic Indicator Definition

First Method Interpolation First Method Parameter Provide the padding value for the first interpolation method Second Method Interpolation Second Method Parameter Consolidation Method Interpol change allowed Group Spatial Aggregation

Counter Formula attributes

Technology Supplier Release Spatial Aggregation on Loading Counter Formula

49



Basic Indicator Definition

Here is an example of a matrix basic indicator.



Indicator presentation

Some attributes can be defined to manage the presentation of each indicator in AD.

Availability domain The object type and temporal level where the indicator is available. Unit Precision The number of significant digits. Sampling indicator Sampling indicator long name Threshold values Threshold values for each QoS Requirement Sampling values - Sampling values for each QoS Requirement Reliability Indicator Reliability indicator long name Access Right {Private, Public} isVisible {True, False} Default value: True. If the indicator doesnt have a family, this

boolean is forced to False whatever the dictionary value.

50



Indicator presentation template



Temporal Aggregation

Some indicators have distinct temporal aggregations like Busy Hour, Maximum, Average, value based on all hours or working hours, etc

Constraint: Indicator Name, reference and (reference+ReferenceExtension) should be unique in NPO.

TA Indicator Attributes

Long name Reference extension Description extension Availability domain Unit Precision Sampling indicator Thresholds values

51




TA Indicator Attributes (continuation)

Sampling values Reliability indicator Access right isVisible Stored Temporal Aggregation Function used to perform temporal aggregation (from

Normalized table to Daily, Weekly or Monthly). Relevant Hour {All Hours, Working Hours} By default: All Hours. Group Busy Hour indicator Long name of the indicator used to compute the busy hour. Calculated Formula

When imported a new temporal aggregation with the same long name as the global indicator there will be a migration problem. In this case, it is mandatory to specify a different long name for TA indicator.




Busy hour example

52



Telecom Family

Counters and Indicators need a family in order to be available in AD.The family attributes are:

Name Order List of indicators

Indicators and counters can have till 4 sub-families.Dictionary Analysis Desktop


Consolidation

Indicator consolidation is used to normalize and optionally to aggregate QoS data inside the data warehouse.

Aggregation and normalization apply only on indicators.

It is possible to calculate multiple temporal aggregation from the same indicator at a raw level.

The scheduler launches the consolidation scripts every night. If the previous day consolidation is not finished, the system waits for the completion of the ongoing loading of files before launching the consolidation for the current day. If any files are missing, the consolidation starts anyway.

The administrator can manually launch a manual consolidation if he finds out that there is recovered data that has not been consolidated yet.


53


Consolidation Steps

It performs the following tasks once a day at 01:00 (Local Time - Oracle Scheduler)

Data transfer from RDB to HDB

Transfer daily indicator from RDB to daily tables

Normalize data from HDB to normalized tables

Daily spatial aggregation

Spatial aggregation

Temporal aggregation

Purge of old partitions



Consolidation Steps


XDaily

Import from PM

Spatial aggregation

Temporal aggregation

Normalisation(Ind)

X Daily

Aggregation(Formula(Ind))


XDaily

XWeekly

XMonthly

Aggregation(Ind) X Raw

XNormalized

XNormalized

Aggregation(Ind)

Aggregation(Ind)

Aggregation(Ind)

Aggregation(Ind)

Aggregation(Ind)

XWeekly

XMonthly

XWeekly

XMonthly

Basic Indicators calculation

XNormalized


MPM Files

QoS

consolidation

Time

Plug-in

TopologySpatial

AggregationPath

Generic Loader

Daily indicator

Indicators Stored

Data optionally stored

Data not stored

54


Consolidation Normalization and Aggregation

The consolidation scripts include:

Data normalization - normalized indicator tables are computed using the default normalization methods

Data aggregation - aggregated tables are computed using normalized indicators and aggregation methods.

The obtained indicator data is aggregated spatially and then temporally.

Daily aggregation is performed every day.

Weekly and Monthly aggregations are only performed on the first day of the week or of the month.



Normalization

In the telecom context the measurements can be reported with different periods, different synchronizations.

The measurements can be lost for different reasons, normal network management or incident in the process.

If we use directly those measurements it is not possible to compare the different objects and the different measurements.

To allow the comparison between different objects and different periods, it is used the normalization.


Cell A

Cell B

Cell C

Cell D

Cell E

1 h 1 h 53 mn 1 h 1 h

h1 h

h h h hhh h h h h h h h h h

1 h

2 h 2 h

h h

hhhh h

time

55


Normalization

The normalization aims are:

Order the measurements

Interpolate missing data

The normalization process can be divided in different steps:

1. Retrieve the needed data

2. Order the data

3. Synchronize data to display period

4. Interpolate missing and NULL data

5. Consolidate to the requested period size



Normalization

Retrieve and order data

The measurements can arrive in wrong order or with some delay.

The aim of this step is to provide time-sorted data to the next step.


BR2 BR1 ER2

BR3 ER3

BR4 BR5ER5

BR6ER6

vR1 vR2 vR3 vR4

vR5vR6

ER1 ER4

vR: value raw dataBR: Begin period raw dataER: End period raw data

56


Normalization

Synchronize data to display period

The aim of this step (also called alignment) is to divide all the periods that are covering two (or more) display periods.

This period alignment (time shift), will set the same measurement period for all measurement data involved in the aggregation or formula calculation (for example 4H, 1H, 15mn).


tD tD tD tD tD tD tD

BR2 BR1 ER2

BR3 ER3

BR4 BR5ER5

BR6ER6

vR1 vR2 vaR3 vaR4

vR5

vaR6

ER1 ER4tD tD tD tD tD

vbR3 vbR4vbR6

TD: time Display period

vaR or vbR : values raw data aligned


Normalization


The aim of this (optional) step is to provide values for all the missing time intervals.

In RNO there are only 2 interpolation methods, linear and padding by zero. In NPO there are 4 new methods.


57


Normalization


In NPO, six customizable interpolation methods are supported:

None - only the existing values are used (no interpolation)

Only OK value - when a display period is not fully available, a NULL value is provided for that displayed period NEW

Extend - only the existing values are used and they are extended to the wanted displayed period NEW

Zero - all the missing periods are set to the zero value



Normalization


Interpolation methods (continuation):

Linear - the missing values are replaced by a linear interpolation between the previous known value and the next known value. The linear interpolation can be specific if the values before or after are not known.

Padding - all the missing periods are set to a padding value. This is zero by default, but can be configurable through the Padding parameter. NEW


58


Normalization

Interpolate missing data or NULL data


No interpolation(Raw Data)

Paddinginterpolation(0 or any other constant)

Extend interpolation

Linear interpolation

ONLY_OK interpolation.In further operation any combination with NULL will result in NULL

Original GPs

Interpolation ofmissing values

Extend interpolation

No interpolation(Raw Data)

Paddinginterpolation(0 or any other constant)

Linear interpolation

ONLY_OK interpolation, in further operation any combination with NULL will result in NULL

Original GPswith NULL ( _ )values

Interpolation ofNULL values


Normalization

Consolidate to the requested period size

The aim of this step is to provide only one value per display period.

This consolidation will return a consolidated value for the whole display period.

7 methods of consolidation are supported by NPO.


vD1

tD tD tD tD tDtDtD

vD2 vD3 vD4vD5 vD6 vD7

vD: final values for display

59


Consolidation methods

Sum - This method sums all available data to get the consolidated value.

Average - This method computes the temporal average of all available data to get the consolidated value. It varies between intensive and cumulative cases (value is already depending on the collection interval).

Maximum - This method gets the maximum of all available data to get the consolidated value.

Minimum - This method gets the minimum of all available data to get the consolidated value.

The consolidation result for these 4 methods will be NULL if a NULL value is provided.



Consolidation methods (continuation)

Count - This method counts all contributing data to get the consolidated value. For instance, if PM data are collected every 15 minutes, a consolidated hour should be composed of 4 measurements, so 4 will be the consolidation result even if there is missing PM data.

Count Present This method sum the duration of each available data and compute the ratio with the display period to get the consolidated value. For instance, if PM data are collected every 15 minutes and only one quarter was collected, for a display period of one hour, 0.25 will be returned.

Count Missing - This method returns the missing data ratio as consolidated value. It is the opposite of Count Present method.


60


Consolidation methods

Example 2 PMs of 30 minutes.PM1 = 4 PM2 = 2


Sumconsolidation

Averageconsolidation

Maxconsolidation

Consolidation

Minconsolidation

Count consolidation Count Present

consolidation

Count Missingconsolidation


Aggregation

Indicators can be aggregated in two modes:


It aggregates data of one network element into one value that defines the parent in the period hierarchy. Period hierarchy = {Hour, Day, Week, Month}

Spatial Aggregation

It aggregated data of several network elements into one value that defines the parent in the network hierarchy. Example of network hierarchy = {TRX, Cell, BSC, Network}

Counters and Parameters can be aggregated as well but is not so common as on indicators.


61



Two types of temporal aggregation can be defined:

Stored Aggregation

Calculated Aggregation To avoid too much stored aggregations when it is possible to calculate it using other indicators

A Daily value is computed from hourly values based on the following temporal aggregation methods: SUM, MIN, MAX, AVG, BH.

A Weekly value is computed from daily values based on the following temporal aggregation methods: SUM, MIN, MAX, AVG, BH, nDAV

A Monthly value is computed from daily values based on the following temporal aggregation methods: SUM, MIN, MAX, AVG, BH, nDAV



Temporal Aggregation Methods

The next functions are used to compute spatial or temporal aggregated values. In the temporal case, they are used to compute Daily, Weekly and Monthly aggregated data, below daily periodicity, the normalization process is used instead.

SUM - This method sums the non-NULL present measurements.

AVG - This method computes the average value of non-NULL present measurements.

MAX - This method returns the maximum value of non-NULL present measurements.

MIN - This method returns the minimum value of non-NULL present measurements.

COUNT - This method counts the number of non-NULL present measurements.

Busy Hour, 3DAV and 5DAV are presented in the next slides.


62


Busy Hour Aggregations

All Busy Hour aggregations are working on plain hours (xx:00:00 to xx:59:59), sliding hours are not supported.

The Busy Hour principle consists in retrieving the hourly value of an indicator when the peak of traffic is measured during the day. The traffic peak is identified thanks to a traffic indicator called reference indicator.

Input:

Indicator

Reference indicator

Output:

Hourly indicator value





Monday Tuesday Wednesday Thursday Friday Saturday Sunday Day

Erlang

- Busy hour function: hour to da y

Monday Tuesday Wednesday Thursday Friday Saturday Sunday hour

Erlang

max

nb

nb

Week

nb

Used to select maximum day for the weekly busy hour (Attention : we use the last Busy Hour

and not other aggregation day)

Used to select maximum hour for the daily busy hour

- Busy hour function: BH day to week BH day to month

max

max

Week

%

fresult

O utput

63



Busy Hour algorithm:

1. Identify the hour of the day that corresponds the maximum hourly value for the reference indicator (1 value per day the first value in case the same value is present several times).

2. Retrieve indicator values for the identified hour.

3. Compute the calculated indicator value (if necessary).

In RNO/NPO, the reference indicator for GSM is:

RTCH_occy_total (GTCTRT)

And for GPRS is:

GPRS_useful_throughput_radio_avg (GTRPDXA)

Note: Due to the fact that NPO supports several technologies, all the GSM refnames start by G on NPO (starting since B10). So, from RNO to NPO, the operator should add a G in the beginning of the indicators refname.




Busy Hour Position

This function returns the hourly (GMT) position of the busy hour (0 to 23).

Input:

Reference indicator

Output:

Hourly position (0 to 23)


00hours

Erlang

Result : 13

03 06 12 18 24

1st max

13

64


Daily Average Value (DAV)

The objective of Daily Average Value computation is to get an average busy hour value for a given period (several days).

Algorithm:

1. Select the n hours that correspond to the maximum values for the hourly reference indicator (one maximum per day)

2. Retrieve the hourly indicators values at the n hours,

3. Average the n values for each indicator

4. Compute the calculated indicator from the average values (if necessary).

nDAV: n is the number of data (generally 3 or 5)



Daily Average Value (DAV)


M o nd a y Tuesd a y W ed nesd a y Thursd a y Fr id a y Sa tu rd a y Su nd a y

Select 3 h o u rs tha t co rresp o n d to the m a xim um o f Iref (fo r 3 d ifferen t d a ys),

Avera g e

W ee

%

Iref

3 D A V ( I 1 , I r e f ) W ith : I1 = f(I2 , I3) = I2 / I3 I2 , I3 ho u rly sto red in d ica to r

I2 I3

ho u r

Er la ngm a x

m a x

m a x

nb

nbnbI2 I3

O n th e 3 selected h o urs, ta ke th e h o ur ly ind ica to rs va lues (I2 , I3 )

Avera g eI2 : I3 :M a ke a n a vera g e w ith th e selected va lues (I2 , I3 )

fC o m p ute th e resu lt o n th e selected va lue I1 3 D AV b y w eek

resu lt

A

B

C

D

In p u t

O u tp ut

65


Spatial Aggregation

It consists in data coming from several network elements into one value for a related upper object in the topology model using one of the following spatial aggregation methods:

SUM

MIN

MAX

AVG

COUNT

Usually the related upper object is the parent one, but sometimes topology levels can bypass or a relation can be used to reach another object.

The spatial aggregation is always done on normalized indicators tables, except for daily indicators.



Consolidation Traces

During the consolidation execution, a file is written in real time with useful information about the process, this file is called a trace.

In NPO Server, traces regarding consolidation can be found in: /alcatel/muse/data/trace/CONSO_LOG_0.traces (Standard consolidation)

/alcatel/muse/data/trace/admintrace__0.traces (Manual consolidation)

/alcatel/muse/data/trace/scripttrace__0.traces (Manual consolidation)

Trace Keywords:

started & ended: each step of the consolidation is described by a trace like:************RBD to HDB transfer started************

***************Normalization started***************

************Spatial Aggregation started************

************Spatial Aggregation started************

************Daily Aggregation started************

************Weekly Aggregation started************

************Monthly Aggregation started************

All Errors or Exception found in the traces have to be analyzed.


66


PM Purge Data

As soon as the consolidation is completed, the data whose storage duration has expired is purged / removed from NPO data warehouse.

This is done for performance and storage space reasons, and depends on the configured storage durations. The minimum purge granularity is the day.

The following table provides an illustration of the default size of each partition and their storage duration:


From 6 to 36 MonthsMonthly

From 3 to 36 MonthsWeekly

From 3 to 14 MonthsDaily

2 MonthsNormalized

60 daysRAW

Storage DurationTable Type


Reliability

The value of the reliability indicator informs the operator about loss of QoS data.

The reliability indicators detect:

Lost objects - If any object is lost, the number of the observed objects is lower than the number of the expected objects.

Lost periods - If any period is lost, the observed time is lower than the expected time.

Indicators are always displayed, even if some data is missing and the propose of reliability is to inform if the displayed value is reliable or not.

An indicator value is displayed in italic when the reliability indicator threshold associated is not green.

The reliability display has priority over sampling or thresholds display.

Note: The reliability indicator is not developed for the adjacency object.


67


Threshold and Sampling

When creating an indicator, you can associate thresholds and sampling to it.

Thresholds are used for highlighting QoS values. This is done using colors in a

view or report, in order to quickly see which values are critical, major, etc.



Indicators Restrictions After B9 NPA Data Import into NPO

The following restrictions are applicable for indicators migrated from NPA to NPO:

1. Reliability Indicators

In both NPA and NPO the reliability indicators follow the group structure of the stored indicators groups.

When groups change (split/join), the old reliability indicators are no longer relevant.

The group structure is very different in NPO compared to NPA, this is why the reliability indicators are ignored during data import.

For historical data, the reliability indicators do not hold any values in NPO. Therefore operator should not check the reliability when displaying the historical data - all this data appears as unreliable.


68


Indicators Restrictions After B9 NPA Data Import into NPO

2. B8 specific indicators

Every new release should have values from the old release.

Indicators from older releases than the previous one will be rejected.

NPO supports B9/B10 GSM releases, so B8 indicators are not migrated into NPO.

3. NPA B9 MR1 specific indicators

NPO dictionaries are aligned with B9 MR4.

Migration from NPA B9 MR1 is possible but with some restrictions.

Indicators removed in B9 MR4 are not imported into NPO.

4. Provisioned or unused indicators

Provisioned stored indicators present in the NPA database are not migrated to NPO.



Propagate Counters and Indicators NEW

In NPO, you can propagate:

Counters to Indicators (Counters directly or indirectly on Indicators)

Indicators to Counters, Views, Diagnosis and THL.


69


Find Indicator from Counter NEW

If you know the counter, you can easily find the associated indicator with this feature. This procedure only shows the indicators which have the counter directly in their formula.

To use this new feature, press Find Indicators from Counter on indicators tree menu.


Write the counters refname

After pressing [Search] the indicator is selected.


Display Counter Properties (1/5)

Use right-click menu to get

properties from the counter.


70






B10 Definition


71







72


Display Indicator Properties (1/4)

Use right-click menu to get

properties from the indicator.





73







74



Display Type 110 Counters NEW

In NPO it is possible to show all the main QoS counters (type 110) for one cell.

To see the 110 Counters select the appropriate cell and choose Display type 100 countersfrom the right-click menu.

Label of the cellList Network Objects / Cell labels

List of Long Names

List of Counter Names

End time of the PM CounterEnd Time

Start time of the PM CounterStart Time

Label of the cellCell label

The id of the cell provided

in the URL

(---)

Cell ID

Name of the modeMode Name

DescriptionAttribute




Cell Mode (1/10)

This feature takes into account

also other modes linked to cell:

TRX

BSC

N7SL

75




Cell Mode (2/10)




Cell Mode (3/10)

76




Cell Mode (4/10)




Cell Mode (5/10)

77




Cell Mode (6/10)




Cell Mode (7/10)

78




Cell Mode (8/10)




Cell Mode (9/10)

79




Cell Mode (10/10)




TRX Mode (1/2)

80




TRX Mode (2/2)




BSC Mode

81




N7SL Mode




It is possible to open these pages in a web browser and to obtain the link is very easy using right-click menu.

With the html tables, user can select them and copy and paste them into Excel worksheets or in other tools.

82



Counter execution

To check a value from a counter, NPO user must drag and drop a selected counter or group of counters to the view browser.



Counter execution

In the execution context user can manipulate several options. The most common is the time period.

Finally press [Execute]

83



Counter execution

The values are then displayed in the view browser.



Indicator execution

The indicator execution is identical to counters but this time there are more available periodicities.

84



Indicator execution

Indicators result in the view browser.


2 Parameters

85


Parameters

Radio parameters are used for QoS interpretation and to know some characteristics of the network.

There are two types of parameters on NPO:

Logical Telecom Parameters (Network optimization)

Design Radio Network Architecture (Coverage and capacity)

Licenses required by NPO Server to manage parameters:

MUSE_PARAM__LICENSE To create parameters for a given technology

MUSE_PARAM_HISTORY_LICENSE To display historical values from parameters


Parameters

Type of values displayed by NPO regarding logical and design parameters:

Operational

Historical

Forecast (Only available from tuning session)

Reference (Min, Default and Max values)

Planned

86


Parameters

Parameter Properties

In parameters properties, operator can see the following information:

Name Reference Formula Type Description Default Value Min Max Unit Availability Domain Step Planned Cell Zone criteria


Parameters

Parameter Properties

Parameters attributes (continuation):

Outage Visible Technology specific attributes Supported Release Information {Release, Supplier, Name, Version, Description} Dictionary Information {Name, Version, Date, Author, Description} Families 4 sub-families can be defined

Use right-click menu over the parameter

to obtain the properties.

87


Parameters

Logical Parameter Properties (1/3)


Parameters


88


Parameters



Parameters

Design Parameter Properties (1/3)

89


Parameters



Parameters


90


Parameters

Propagate Parameters

You can propagate both design and logical parameters to:

View Template

This retrieves all View Templates referencing the selected parameters in their tabular list.

Rules

This retrieves all Rules using the selected parameters in their definition.

Thematics

This retrieves all Thematic Layer Templates referencing the selected parameters.


Parameters

Manage Parameters

1. Import Parameters Dictionary

Parameter dictionaries describe all the supported parameters for the network objects.

Dictionaries are specific for each managed technology.

Costumer can easily import dictionaries through Web Administration Interface.

2. Load Parameters Data

The parameters data of the whole network is loaded each night.

Costumer can perform a manual load every time he wants to do it.

3. Parameters Historical Data Purge

For performance and storage space reasons, a regular data purge of the oldest historical values is performed.

The purge process is launched every night after the daily import of operational values.

It deletes every records that contain a date older of a specified number of days than the current date.

91


3 Exercises


Exercises

1. Imagine that we have 1 PM every 15 min. There is no interpolation for the missing data.

PM1 = 2; PM2 = 4; PM3 = 6; PM4 = missing

What will be the result for the following consolidation methods?

Sum

Max

Min

Avg

Count

Count Present

Count Missing

92


Exercises

2. Check if there is missing data for MC718 in the cell 44620 at 30/11/2007.

If there is missing data, what kind of interpolation is used on this counter?

3. Find the basic indicator of this counter and retrieve it at cell level for the same day per hour. What is the aggregation used (type and method) between 2 and 3?


Exercises

4. Is EDGE activated in cell 44583?

5. What is the maximum coding scheme allowed for GPRS and EDGE for cell 44610?

6. How many rules are associated with MAX_PDCH parameter?

93


4 Views


Views

Presentation

Views enable to display results coming from any analysis service

Results can be displayed as tabular or graphical mode

There are two ways to create a view:

View templates - Views already defined in NPO

Interactively Functions executed in view browser.

A view is also known as an Executed View and appears in the view browser.

The default limit for the maximum number of views in the view browser is 20. NEW

94


Views

View Templates (1/2)

View templates are localized in View function tab


Views

View Templates (2/2)

95


Views

Interactive view (1/2)

If we drag and drop functions (ex: indicators) for the view browser, then we have a view defined by the selected indicators.


Views

Interactive view (2/2)

Even if the indicators are the same, we can obtain a different view presentation.

96


Views

Classification

View modes:

Tabular Display values in tables

Graphical Display values through columns and lines

View types:

Standard View which has scalar indicators/parameters, rules, events or free fields

Vector - View which has one or more vectors inside

Matrix View which has one or more matrices inside

Equipment View for alarms and availability


Views

Display View Properties (1/6)

To see view properties, use right-click menu from one view.

97


Views



Views


98


Views



Views


99


Views



Views

Edit Executed View

The user can change the display properties of each executed view.

The update appears directly on the displayed executed view.

It is possible to edit the view title and update the current view.

Edit Title NEW

The view title can be edited by double-clicking on it.

100


Views

Edit Executed View

Edit View Tab NEW

The view tab can be edited by double-clicking on it.


Views

Edit Executed View

Update the current executed view NEW

It is possible to add functions in the current executed view using Ctrl+Drag&Drop It is possible to remove functions in the current executed view using Ctrl+Shift+Drag&Drop With this option, the execution context is not necessary.

Functions available to update executed view:

Indicators

Counters

Parameters (logical and design)

Rules

Events

Free Fields

To use this feature properly, press and release Ctrl+Drag&Drop at the same time

101


Views

Edit Executed View


Add one Indicator (Ctrl)


Views

Edit Executed View


New indicator

102


Views

Edit Executed View


Remove one Indicator (Ctrl+Shift)


Views

View functionalities

There are some functionalities in the left-side of the view (Toolbar): Toggle Display Type NEW

Propagate

Save View As Template NEW

Export View Spatial Rollup NEW

Spatial Drill Down NEW

Temporal Rollup NEW

Temporal Drill Down NEW

Show Legend Highlight NEW

Rotate View NEW

Clear All Filter(s) Filter Repeated Values Show Filter List

103


Views


Toggle Display Type NEW

This function changes the view from tabular mode to graphical mode and vice-versa.


Views


Save View As Template NEW

This function saves a executed view as a template one.

By default, the view template has User Defined family

104


Views


Spatial Rollup NEW

This function allows operator to roll up spatially in the executed view

Typical Network Levels in ascending order: {TRX, Cell, BSC, NETWORK}


Views


Spatial Drill Down NEW

This function allows operator to drill down spatially in the executed view

All the cells of the BSC are displayed after a spatial drill down.

105


Views


Temporal Rollup NEW

This function allows operator to roll up temporally in the executed view

Typical Periodicities in ascending order: {Hour, Day, Week, Month}

Hourly Data

Daily Data


Views


Temporal Drill Down NEW

This function allows operator to drill down temporally in the executed view

Weekly Data

Daily Data

106


Views


Highlight NEW

NPO user can highlight the view results on all functions except for counters and events

The color for each function has a different meaning

Style and colors for Indicators after Highlight:

Italic: Reliability test is wrong

Grey: The associated sampling value is too low for the tested value

Black: The indicator does not have a threshold

Green: Result value is less or greater (depending on UpperIsFault) than yellow threshold

Yellow: Result value is between the yellow and orange threshold

Orange:Result value is between the orange and red threshold

Red: Result value is less or greater (depending on UpperIsFault) than red threshold


Views


Highlight NEW

Colors for Parameters after Highlight:

Black: Impossible to test the parameter value. (Operational, planned)

Green: The values (historical, reference) are equal to the operational value

Orange:The value changed between current and previous date

Red: The values are different than the operational value

Colors for Rules after Highlight:

Black: Rule result is N/A

Green: Rule result is true

Orange:Rule result is false and is a warning rule.

Red: Rule result is false.

107


Views


Highlight NEW

Colors for Synthetic Diagnosis after Highlight:

Black: Diagnosis result is unknown

Green: Diagnosis result is nopbfound (no problem found)

Red: Diagnosis result is pbfound (problem found)

Note: Synthetic Diagnosis are the ones which are executed in the view browser.


Views


Highlight NEW

Indicators example

Parameters example

108


Views


Highlight NEW

Ruless example

Synthetic Diagnosiss example


Views


Rotate View NEW

This functions rotate the executed view

This function can be very useful before extract view to excel (256 columns at maximum)

109


5 Reports


Reports

Presentation

Reports enable user to display functions in several views.

Every function executed to Report Browser originates a Executed Report

Licenses needed by NPO regarding Reports

MUSE_REPORT_TEMPLATE_CREATION_LICENSE

This license is needed to create reports in NPO.

MUSE_REPORT_LICENSE

This license is needed to execute reports in NPO.

110


Reports

Report type

There are four types of report:

Mono-Object Evolution

Multi-Object Evolution

Multi-Object Comparison

Mono-Object Distribution

Mono-Object Distribution Reports are not available in WiMAX.

It is possible to edit the report title and update the current executed Report. NEW


Reports

Edit Report Title NEW

The report title can be edited by a right click on the title and select Rename

111


Reports

Update Executed Report NEW

It is possible to add Views in the current executed Report using Ctrl+Drag&Drop

To use this feature properly, press and release Ctrl+Drag&Drop at the same time


Reports

Update Executed Report NEW

It is possible to add Views in the current executed Report using Ctrl+Shif

npo seminar training alcatel

Documents

npo seminar portugal

npo seminar day

npo seminardecember

npo instance

technologies npo

alcatellucent networks

wimax npo evolutions

rich view of npo