NPO Manual

Alcatel-Lucent

NPO User Guide

NPO Document

User Guide

Release B10, M2, UA5, UA6

3BK 21216 AAAA PCZZA Ed.26

Status RELEASED

Short title NPO Document

All rights reserved. Passing on and copying of this document, useand communication of its contents not permitted without writtenauthorization from Alcatel-Lucent.

BLANK PAGE BREAK

2 / 664 3BK 21216 AAAA PCZZA Ed.26

Contents

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.2 NPO Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

1.2.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251.2.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

1.3 NPO Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281.3.1 QoS Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281.3.2 Reference Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291.3.3 Rules and Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291.3.4 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291.3.5 Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291.3.6 Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301.3.7 Cartography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301.3.8 Network Stability and Availability, Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311.3.9 Remote Inventory Data Management (RIDM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311.3.10 Customizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311.3.11 Advanced Optimization Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

2 Getting Started with Analysis Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352.1 Initialize Analysis Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362.2 Exit Analysis Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362.3 Title Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372.4 Standards / Modes / Topology Classifications / Function Classifications . . . . . . . . . . . . . . . . . 37

2.4.1 Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.4.2 Customizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

2.5 Tooltips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552.6 Display Values of Functions Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552.7 Create and Execute Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562.8 Diagnose QoS Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562.9 Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582.10 Cartography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582.11 QoS Analysis Using THL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582.12 Network Stability and Availability, Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592.13 Remote Inventory Data Management (RIDM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592.14 Access Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602.15 Tip of the Day . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612.16 Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622.17 Notification Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642.18 Consolidation Follow Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652.19 Select / Deselect All Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

3 Common Tasks in Functional Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673.1 Drag and Drop Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683.2 Propagate Network Objects or Object Zones Between Topology Classification or Zone

Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723.3 Display and Edit Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

3.3.1 Display Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733.3.2 Edit Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.3.3 Copy URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

3.4 Generic Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.4.1 Generic Editor Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.4.2 Generic Editor Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

3.5 Refreshing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803.6 Searching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

3BK 21216 AAAA PCZZA Ed.26 3 / 664

Contents

3.7 Execution Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833.7.1 Periodicity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833.7.2 Execute Reports Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843.7.3 Date and Hour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843.7.4 Trend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863.7.5 QoS Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873.7.6 Interpolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873.7.7 Sampling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883.7.8 Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883.7.9 Forecast Values in Tuning Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883.7.10 Filter Unavailable Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883.7.11 Event Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903.7.12 Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

4 Set QoS Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

5 Topology Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

5.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 945.2 Topology Objects Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 955.3 Display Topology Object Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045.4 Add Associated Network Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1115.5 Network Object Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

5.5.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125.5.2 Network Object Class Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1145.5.3 Assign Operational Network Object Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

6 Object Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1196.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

6.1.1 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1206.1.2 Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1216.1.3 QoS for Object Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1236.1.4 Compute Object Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

6.2 Display Object Zone Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1246.3 Object Zone Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

6.3.1 Open Object Zone Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1276.3.2 Object Zone Operations Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1286.3.3 Create Object Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1286.3.4 Create Object Zone by Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1346.3.5 Create Object Zone Interactively . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1346.3.6 Edit Object Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1346.3.7 Delete Object Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

7 Topology Classifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1377.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1387.2 Open Topology Classification Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1387.3 Create Topology Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1397.4 Create Topology Classification by Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1417.5 Edit Topology Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1427.6 Apply Filter on Topology Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1437.7 Delete Topology Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

8 Function Classifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

8.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1468.2 Open Function Classification Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1468.3 Create Function Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1478.4 Create Function Classification by Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1498.5 Edit Function Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1508.6 Delete Function Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

9 Working Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

4 / 664 3BK 21216 AAAA PCZZA Ed.26

Contents

9.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1529.2 Working Zone Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

9.2.1 Open Working Zone Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1549.2.2 Working Zone Operations Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1549.2.3 Create Working Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1559.2.4 Create Working Zone by Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1589.2.5 Edit Working Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1599.2.6 Delete Working Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

9.3 Create Sub Working Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1609.3.1 Create Sub Working Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1609.3.2 Create Sub Working Zone from Object Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1609.3.3 Create Sub Working Zone from Topology Objects List . . . . . . . . . . . . . . . . . . . . . 1619.3.4 Create and Open Sub Working Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1619.3.5 Create Sub Working Zone by Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

9.4 Change Current Working Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

10 Counters and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16310.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

10.1.1 Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16410.1.2 Basic/Calculated Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16610.1.3 Scalar/Vector/Matrix/Axis Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16810.1.4 Indicator Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16910.1.5 Counter Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17010.1.6 Indicator Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17610.1.7 Consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18610.1.8 PM Data Purge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19210.1.9 Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19310.1.10 Threshold and Sampling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19410.1.11 Indicator Formula Operands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19510.1.12 Propagate Counters and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20510.1.13 Indicators Restrictions After B9 NPA Data Import into NPO . . . . . . . . . . . . . . . . 206

10.2 Display Counters and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20610.3 Display Counter Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20610.4 Display Type 110 Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21110.5 Display Indicator Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21310.6 Find Indicator from Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21810.7 Indicator Template Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

10.7.1 Open Indicator Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21810.7.2 Create Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22110.7.3 Create Customer Indicator by Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22710.7.4 Edit Customer Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22710.7.5 Edit Indicator Threshold / Sampling Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22710.7.6 Delete Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

11 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22911.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23011.2 Display Logical/Design Parameter Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23211.3 Display Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23511.4 Propagate Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23611.5 Manage Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

11.5.1 Import Parameters Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23611.5.2 Load Parameters Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23611.5.3 Parameters Historical Data Purge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

12 Reference Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23912.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

12.1.1 Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24012.1.2 Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24012.1.3 File Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

3BK 21216 AAAA PCZZA Ed.26 5 / 664

Contents

12.1.4 Columns Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24212.1.5 Reference Values Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24312.1.6 Reference Values Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24412.1.7 Expression Grammar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24412.1.8 Compare Different Values of Reference Values . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

12.2 User Defined Reference Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

13 Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25313.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

13.1.1 Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25413.1.2 Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25413.1.3 Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25413.1.4 File Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25513.1.5 Columns Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25713.1.6 Rules Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25813.1.7 Rules Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26013.1.8 Highlighting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26113.1.9 Expression Grammar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

13.2 Display Rules Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26213.3 Execute Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26313.4 User Defined Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

14 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26714.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26814.2 Display Event Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27014.3 Display Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

14.3.1 Execute Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27314.3.2 Open Events Details Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27414.3.3 Tabular Mode for Executed Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27414.3.4 Tabular Mode for Standard View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

14.4 Display Event Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27714.4.1 Event Synthesis in Tabular Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27714.4.2 Event Synthesis in Graphical Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

15 Free Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

15.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28015.1.1 Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28015.1.2 Free Fields File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

15.2 Display Free Field Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28315.3 Free Fields Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28415.4 Execute Free Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

16 User Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28516.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28616.2 User Notes Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

16.2.1 Display User Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28716.2.2 Create User Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28816.2.3 Edit User Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28816.2.4 Delete User Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

17 Favorites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28917.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29017.2 Favorites Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

17.2.1 Select Favorite Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29017.2.2 Add a Function to Favorite Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29117.2.3 Create Group to Add Favorites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29217.2.4 Rename Group of Favorites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29317.2.5 Delete Favorite/Group of Favorites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29417.2.6 Organize Favorites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29517.2.7 Move Favorite/Group of Favorites to Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

6 / 664 3BK 21216 AAAA PCZZA Ed.26

Contents

17.3 Import Favorites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29717.4 Export Favorites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

18 Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

18.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30218.1.1 Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30218.1.2 Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30318.1.3 Tabular and Graphical Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30518.1.4 Standard View Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30618.1.5 Vector View Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30618.1.6 Matrix View Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30618.1.7 Equipment View Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30818.1.8 Extension and Restriction of Availability Domain . . . . . . . . . . . . . . . . . . . . . . . . . . 308

18.2 Display View Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31118.2.1 Display Standard View Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31118.2.2 Display Vector View Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31318.2.3 Display Matrix View Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31518.2.4 Display Equipment View Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

18.3 View Template Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31918.3.1 Open View Template Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31918.3.2 Create View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31918.3.3 Create View by Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33018.3.4 Edit View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33018.3.5 Delete View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

18.4 Execute View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33218.4.1 Execute View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33218.4.2 Examples of Executed Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33318.4.3 Edit Executed View Interactively . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33918.4.4 Edit Executed View Using Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

18.5 Using Executed View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34818.5.1 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34818.5.2 Highlight in View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35018.5.3 Show Legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35318.5.4 Sort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35518.5.5 Filter in View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35618.5.6 Hide/Unhide Rows/Columns/Repeated Values . . . . . . . . . . . . . . . . . . . . . . . . . . . 35918.5.7 Change View Display Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36018.5.8 Resize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36118.5.9 Copy to System Clipboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36218.5.10 Copy Executed View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36218.5.11 Duplicate Executed View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36218.5.12 Rename Executed View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36218.5.13 Save Executed View as Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36318.5.14 Close Executed View(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36318.5.15 Export Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

19 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36919.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370

19.1.1 Mono-Object Evolution Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37119.1.2 Multi-Object Evolution Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37319.1.3 Multi-Object Comparison Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37319.1.4 Mono-Object Distribution Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37419.1.5 Warning Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37519.1.6 Report Title/Subtitle Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380

19.2 Report Template Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38119.2.1 Open Report Template Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38119.2.2 Create Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38219.2.3 Create Report by Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

3BK 21216 AAAA PCZZA Ed.26 7 / 664

Contents

19.2.4 Edit Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38619.2.5 Delete Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387

19.3 Execute Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38819.3.1 Execute Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38819.3.2 Edit Executed Report Interactively . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39119.3.3 Edit Executed Report Using Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39619.3.4 Schedule Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39819.3.5 Display Pending Executed Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40319.3.6 Show Second Report Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

19.4 Using Executed Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40519.4.1 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40519.4.2 Synchronize Cursors in Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40619.4.3 Synchronize Zooming in Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40719.4.4 Filter in Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40719.4.5 Highlight in All Report Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40719.4.6 Display Grid in All Report Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40919.4.7 Edit View from Executed Report Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40919.4.8 Duplicate Executed Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40919.4.9 Rename Executed Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41019.4.10 Automatic Views and Legends Resizing in Report . . . . . . . . . . . . . . . . . . . . . . . . 41019.4.11 Save Executed Report as Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41019.4.12 Close Executed Report(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41119.4.13 Export Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41219.4.14 Export Views from Executed Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416

20 Web Publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417

20.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41820.2 Display Published Executed Views/Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41920.3 Re-execute Published Executed Views/Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

21 Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42721.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42821.2 Display Diagnosis Scenario Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42921.3 Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433

21.3.1 Propagate Diagnosis Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43321.3.2 Propagate Selection Between Synthetic and Detailed Report and Topology

Classifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43321.4 Open Diagnosis Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43321.5 Execute Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434

21.5.1 Synthetic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43421.5.2 Detailed Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435

21.6 Display Execution Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43721.7 Edit Detailed Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438

21.7.1 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43821.7.2 Edit Diagnosis Execution Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43921.7.3 Edit Diagnosis Spatial Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

21.8 Copy Diagnosis View to System Clipboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43921.9 Schedule Executed Diagnosis Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44021.10 Display Pending Executed Diagnoses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44021.11 Close Executed Detailed Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44121.12 Export Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442

22 Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44522.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446

22.1.1 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44622.1.2 Purge Completed Tuning Job(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44622.1.3 Tuning Session Life Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

22.2 Display Tuning Operation Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44822.3 Tuning Session Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450

8 / 664 3BK 21216 AAAA PCZZA Ed.26

Contents

22.3.1 Open Tuning Sessions Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45022.3.2 Display Tuning Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45122.3.3 Create Tuning Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45222.3.4 Create Tuning Session by Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45422.3.5 Check Tuning Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45422.3.6 Apply Tuning Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45522.3.7 Delete Tuning Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456

22.4 Tuning Jobs Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45722.4.1 Open Tuning Jobs Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45722.4.2 Change Classification in Tuning Jobs Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45822.4.3 Display Existing Tuning Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45922.4.4 Display Tuning Job Follow Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45922.4.5 Open Tuning Job(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459

22.5 Tuning Session Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46022.5.1 Display Tuning Session Operation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46022.5.2 Display Tuning Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46222.5.3 Edit Tuning Session Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46322.5.4 Show/Hide Tuning Session Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46322.5.5 Save Tuning Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46422.5.6 Clear Tuning Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46422.5.7 Toggle Display Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46422.5.8 Close Tuning Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46522.5.9 Create Parameter Tuning Operation(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46522.5.10 Create Topology Relation Tuning Operation(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . 46922.5.11 Create Frequency Tuning Operation(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47322.5.12 Create Advice Tuning Operation(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47622.5.13 Edit Tuning Operation(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47722.5.14 Copy Tuning Operation(s) to System Clipboard . . . . . . . . . . . . . . . . . . . . . . . . . . . 47722.5.15 Delete Tuning Operation(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477

22.6 Propagate from Tuning Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47822.6.1 Propagate Tuning Session Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47822.6.2 Propagate Tuned Parameters of Network Object(s) . . . . . . . . . . . . . . . . . . . . . . 47822.6.3 Propagate Tuned Network Objects of Parameter(s) . . . . . . . . . . . . . . . . . . . . . . . 479

22.7 Manage Reference Object(s) for Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48022.7.1 Declare Network Object(s) as Reference Object(s) for Tuning . . . . . . . . . . . . . 48022.7.2 Undeclare Network Object(s) as Reference Object(s) for Tuning . . . . . . . . . . . 481

22.8 Manage Tuning Inhibition of Network Object(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48222.8.1 Inhibit Tuning of Network Object(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48222.8.2 Allow Tuning of Network Object(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483

23 Cartography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48523.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486

23.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48623.1.2 Cartography Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48923.1.3 Display Network Objects in Viewport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49123.1.4 Density Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49323.1.5 Graphic Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49423.1.6 Compute Voronoi Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49723.1.7 Common Cartography Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498

23.2 Open Cartography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49923.3 Layer Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499

23.3.1 Display Layer/Layer List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49923.3.2 Show/Hide Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50023.3.3 Display Layer Legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50123.3.4 Modify Display Properties of a Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50323.3.5 Modify Order of a Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50523.3.6 Add Layer in Layer Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50523.3.7 Remove Layer from Layer Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507

3BK 21216 AAAA PCZZA Ed.26 9 / 664

Contents

23.3.8 Export Displayed Layers/Viewport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50823.3.9 Google Earth Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510

23.4 Cartography Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51523.4.1 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51523.4.2 Single/Circular Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51523.4.3 Pan Rendering Viewport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51623.4.4 Zoom In/Out/Rectangular . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51623.4.5 Center Viewport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51923.4.6 Compute Distance Between Points/ Network Objects . . . . . . . . . . . . . . . . . . . . . 52023.4.7 Navigate in Viewport Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52123.4.8 Save Viewport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52223.4.9 Display Information Interactively . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52223.4.10 Minimap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522

23.5 Network Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52423.5.1 Select Network Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52423.5.2 Display Network Objects Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52423.5.3 Add Network Objects in Viewport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52523.5.4 Remove Network Objects from Viewport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52823.5.5 Propagate Network Objects Selection from Cartographic Viewer into Mode 52923.5.6 Propagate Executed View to Highlight Network Objects in Cartography . . . . . 52923.5.7 Highlight Network Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53023.5.8 Filter Network Objects in a Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532

23.6 Thematic Layer Template (THL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53623.6.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53623.6.2 Display THL Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53623.6.3 Propagate THL to Function Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53723.6.4 THL Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53823.6.5 Execute THL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54923.6.6 Display Thematics for Adjacencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55223.6.7 Frequency Reuse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55223.6.8 Show THL Legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55423.6.9 Export THL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555

23.7 Adjacencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55623.7.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55623.7.2 Adjacency Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55823.7.3 Select Adjacencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56223.7.4 Display Adjacencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56223.7.5 Display Adjacency Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56223.7.6 Open Packed Link Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56423.7.7 Run Adjacency Analysis Wizard to Create/Delete Adjacencies . . . . . . . . . . . . . 56523.7.8 Show Legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569

24 Alerters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57124.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572

24.1.1 Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57224.1.2 Types, Severities and States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57224.1.3 Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57424.1.4 Examples of Alerter Validity Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577

24.2 Alerter Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58124.2.1 Open Alerter Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58124.2.2 Create Alerter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58224.2.3 Create Alerter by Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58724.2.4 Edit Alerter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58724.2.5 Delete Alerter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587

24.3 Display Alerter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58824.3.1 Display Alerter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58824.3.2 Actions in "Alerter List" Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589

24.4 Display Alerts List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590

10 / 664 3BK 21216 AAAA PCZZA Ed.26

Contents

25 Network Unavailability and Alarm Reporting Tool (NUART) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59325.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59425.2 Open NUART Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59725.3 Close NUART Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59925.4 Change Working Zone in NUART Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59925.5 Display Basic Unavailability (BU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60025.6 Display Suspect Origin of Basic Unavailability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60325.7 Display Alarms and Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60525.8 Manage Filter for Alarms and Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60725.9 Define Sort Criteria for Alarms and Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60925.10 LASER Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61125.11 Delete Failed LASER File Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613

26 Remote Inventory Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615

26.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61626.1.1 Remote Hardware Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61626.1.2 Customer Acceptance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617

26.2 Start Remote Inventory Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61826.3 Change Working Zone in RIDM Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62026.4 Display End of Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62126.5 Search for Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62326.6 Display Board Type Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62526.7 Display Board Historic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62726.8 Display Customer Acceptance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63026.9 Display Boards Not in Customer Acceptance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63226.10 Manage Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634

27 User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63727.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63827.2 Configure User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638

27.2.1 General User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63927.2.2 Views/Reports User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64127.2.3 Cartography User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644

27.3 Layout User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64527.4 Save User Preferences Implicitly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645

28 Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64728.1 Toolbar Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64828.2 Topology Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65028.3 Functions Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660

3BK 21216 AAAA PCZZA Ed.26 11 / 664

Contents

12 / 664 3BK 21216 AAAA PCZZA Ed.26

Preface

Preface

Purpose This guide describes how to use the Network Performance Optimizer (NPO) inorder to view and manage counter and indicator values for various networkobjects, and to know how to monitor and optimize the radio network.

Procedures for the administration of NPO are described in NPO AdministrationGuide.

Procedures for the administration of MUSE are described in 9953 MP / NPOPlatform Administration Guide.

Alcatel-Lucent 9953 MS-OMC PORTAL will be later referred as 9953 MP.

NPO generic name refers to 9159 NPO, 9359 NPO, and 9759 NPO.

What’s New In Edition 26The following sections are updated:

Display Basic Unavailability (BU) (Section 25.5)

Presentation (Section 23.6.1)

Definition (Section 18.1.1).

In Edition 25The following sections are updated:

Presentation (Section 7.1)

Propagate Diagnosis Scenario (Section 21.3.1).


Initialize Analysis Desktop (Section 2.1)

Create Tuning Session (Section 22.3.3)

Create Tuning Session by Copy (Section 22.3.4)

Definition (Section 18.1.1)

3BK 21216 AAAA PCZZA Ed.26 13 / 664

Preface

Presentation (Section 19.1)

Display Customer Acceptance List (Section 26.8)

In Edition 23Schedule Reports (Section 19.3.4) is updated.


Aggregation (Section 10.1.7.2)

Roll Up / Drill Down Temporally (Section 18.4.3.4)

Initialize Analysis Desktop (Section 2.1)

Create Tuning Session (Section 22.3.3)

Create Tuning Session by Copy (Section 22.3.4)

Presentation (Section 5.1).

In Edition 21New section is added: Close NUART Web Interface (Section 25.3).

The Detailed Mode (Section 21.5.2) is updated with a relevat snapshot.

The sections: Open NUART Web Interface (Section 25.2) and Start RemoteInventory Data Management (Section 26.2) are updated with a notice in thestep 2.


Display Pending Executed Reports (Section 19.3.5)

Display Pending Executed Diagnoses (Section 21.10)

LASER Reports (Section 25.10)

Edit Detailed Diagnosis (Section 21.7)

A new section is added: Create and Open Sub Working Zone (Section 9.3.4).

Update the sections with information about the W-CDMA.

In Edition 19Working Zone - Presentation is updated with the new classification of workingzones: Standard Working Zone <=2000 cells, and Large Working Zone >2000cells.

A notice is added in Calculated Indicators (Section 10.1.2.2).

A notice is added in Reliability (Section 10.1.9).

In Edition 18A new section is added: Compare Different Values of Reference Values(Section 12.1.8).

In Edition 17

14 / 664 3BK 21216 AAAA PCZZA Ed.26

Preface

Section Working Zone - Presentation is updated.

"Alcatel-Lucent 9953 MP MS-OMC PORTAL” name is changed to“Alcatel-Lucent 9953 MS-OMC PORTAL”.


PM Data Purge (Section 10.1.8)

Export Views (Section 18.5.15)

Export Reports (Section 19.4.13)

The document administrative part is updated.


Network Unavailability and Alarm Reporting Tool (NUART) (Section 25)

Remote Inventory Data Management (Section 26).

In Edition 14Display Adjacency Properties (Section 23.7.5) is updated.


Customizing (Section 1.3.10)

Date and Hour (Section 3.7.3) with ’Default Dates’

Automatic Views and Legends Resizing in Report (Section 19.4.10)

Views/Reports User Preferences (Section 27.2.2), for ’Text synthetic output’.


Create Object Zone (Section 6.3.3)

Create Object Zone by Copy (Section 6.3.4)

Edit Object Zone (Section 6.3.6).

Create Working Zone (Section 9.2.3).

Restrictions are added in Create Frequency Tuning Operation(s) (Section22.5.11).

A restriction is removed from Initialize Analysis Desktop (Section 2.1) for thecase when NPOe Analysis Desktop remains blocked at 75%.

In Edition 11New chapters are added:

Execute Reports Options (Section 3.7.2)

Web Publishing (Section 20)

LASER Reports (Section 25.10).

New section is added: Show Second Report Browser (Section 19.3.6).

3BK 21216 AAAA PCZZA Ed.26 15 / 664

Preface

The following chapters are updated:

Date and Hour (Section 3.7.3)

Buttons (Section 3.7.12)

Schedule Reports (Section 19.3.4)

Schedule Executed Diagnosis Reports (Section 21.9)

Topology Icons (Section 28.2) is updated with “Unknown frequency band”and ”Unknown cell type” icons explanation.

New chapter is added: Google Earth Export (Section 23.3.9).

Export Displayed Layers/Viewport (Section 23.3.8) is updated.The following sections are updated:

View Toolbar (Section 18.5.1)

Create Standard View (Section 18.3.2.1)

Execute View (Section 18.4.1)

Filter on Period (Section 18.5.5.4)

Execute Report (Section 19.3.1).

Tuning Session Manager (Section 22.3)

Export Displayed Layers/Viewport (Section 23.3.8)

A notice is added in Create Customer Indicator by Copy (Section 10.7.3)

Section “Create Topology Object Tuning Operation(s)” is removed, as it wasonly developed for internal tests.New sections are added:

Examples of Executed Views (Section 18.4.2)

Create Object Zone Interactively (Section 6.3.5)

Find Indicator from Counter (Section 10.6)

Display Thematics for Adjacencies (Section 23.6.6)The following sections are updated:

Add Views to Report (Section 19.3.2.3)

Paste View into Report (Section 19.3.2.4)

Remove Views from Report (Section 19.3.2.6)

Execute Report (Section 19.3.1)

Executed Diagnosis in Detailed Mode (Section 21.5.2)

Display Tuning Session (Section 22.3.2)

Open Cartography (Section 23.2)

Edit Title (Section 19.3.2.1) for an Executed Report

Searching (Section 3.6)

Indicator Formula Operands (Section 10.1.11)

16 / 664 3BK 21216 AAAA PCZZA Ed.26

Preface

A note on setting the security level in Excel for the export procedure is added inthe following sections:



The restriction regarding basic indicators with one step interpolation is removedfrom Create Indicator (Section 10.7.2).The following sections are updated with a note that ”From“ and “To” Date fieldsrepresent the start time of the last value to be displayed:

Date and Hour (Section 3.7.3)

Display Basic Unavailability (BU) (Section 25.5), step 2

Display Alarms and Logs (Section 25.7), step 2

Display End of Warranty (Section 26.4), step 3

Display Board Historic (Section 26.7), step 3.

Chapter “Export Interfaces” is moved to document ”NPO Export Interfaces”.A notice on a limitation when exporting in Excel is added in the followingsections:



Export Diagnosis (Section 21.12)

Execute Data Query

Execute Report Request

Snaptshots are updated.

A note is addded to pay attention to the number of selected network objectswhen navigating to NUART, as there is a limitation in the URL to 2,048characters.

The URL is updated in “Execute Report Request”.

A notice is added in Views (Section 18) and Reports (Section 19) thatMono-Object Distribution Views/Reports are not available in WiMAX.

Types, Severities and States (Section 24.1.2) is updated

Examples of Alerter Validity Period (Section 24.1.4) is added.New sections are added:

Remote Inventory Data Management (RIDM) (Section 1.3.9)

Remote Inventory Data Management (RIDM) (Section 2.13)

Presentation (Section 26.1) of Remote Inventory Data Management

Extension and Restriction of Availability Domain (Section 18.1.8).New sections are added:

Network Stability and Availability, Alarms (Section 1.3.8).

Network Stability and Availability, Alarms (Section 2.12)

Consolidation Follow Up (Section 2.18)

3BK 21216 AAAA PCZZA Ed.26 17 / 664

Preface

Alerters (Section 24)

Remote Inventory Data Management (Section 26)

Licensing (Section 2.16) is updated.The following sections are updated:

Cartography (Section 1.3.7)

Highlight Network Objects (Section 23.5.7)

Graphic Modes (Section 23.1.5)

Presentation (Section 23.6.1)

Configure User Preferences (Section 27.2)The following sections are added:

Tip of the Day (Section 2.15)

Network Unavailability and Alarm Reporting Tool (NUART) (Section 25)Restrictions are removed from the following chapters:

Create Indicator (Section 10.7.2), regarding computed vector indicators

involving "MIDDLE" functions

Aggregation (Section 10.1.7.2), regarding DAV3 and DAV5 aggregation

Calculated Indicators (Section 10.1.2.2), regarding DAV indicators creation

Views Sort (Section 18.5.4).


Topology Objects Tabs (Section 5.2)

Display Topology Object Properties (Section 5.3)

Open Object Zone Editor (Section 6.3.1)

Open Working Zone Editor (Section 9.2.1).

New icons are added in Topology Icons (Section 28.2).Restrictions are added in the following sections:

Create Indicator (Section 10.7.2), regarding computed vector indicators

involving "MIDDLE" functions

Create Indicator (Section 10.7.2), regarding the creation of basic indicatorswith one step interpolation

Calculated Indicators (Section 10.1.2.2), regarding the customer DAV

indicators creation

Aggregation (Section 10.1.7.2), regarding DAV3 and DAV5 aggregation

malfunction

Sort (Section 18.5.4) Views.

A new chapter is added: Indicators Restrictions After B9 NPA Data Importinto NPO (Section 10.1.13).

In Edition 04

18 / 664 3BK 21216 AAAA PCZZA Ed.26

Preface

The following new sections are added:

Display Type 110 Counters (Section 10.4)

Execute Dynamic Excel Page

A restriction is added in Initialize Analysis Desktop (Section 2.1) for the casewhen NPOe Analysis Desktop remains blocked at 75%.

Overall document review.

In Edition 03New section is added: Compute Voronoi Maps (Section 23.1.6).

Show/Hide Layer (Section 23.3.2) is updated.

In Edition 02Adjacencies (Section 23.7) is updated.Minor updates in:

User Notes (Section 16)

Reports (Section 19).

In Edition 10Thematic Layer Template (THL) (Section 23.6) is updated.

A notice is added in Indicator Formula Operands (Section 10.1.11) that bracesare not supported for indicator boolean expressions.

In Edition 01First official release of document.

Audience This document is intended for engineers responsible for the day-to-dayoptimization of the network.

Assumed Knowledge You must have a basic understanding of the Alcatel-Lucent operations andmaintenance concepts for the BSS and RNS.

3BK 21216 AAAA PCZZA Ed.26 19 / 664

Preface

20 / 664 3BK 21216 AAAA PCZZA Ed.26

1 Introduction

1 Introduction

This section provides an overview of NPO functions and features, andintroduces current terminology.

3BK 21216 AAAA PCZZA Ed.26 21 / 664

1 Introduction

1.1 TerminologyThis document uses the following terms:

NetworkObject

A Network Object is the generic term used to refer to individual topology objects suchas a cell, an RNC, BSS, BSC, BTS, adjacency or TRX.

Topology Tree A topology tree is a tree displaying network objects.

Function A function is the generic term used to refer to individual objects of a data group or analysisservice class. So, depending on the considered domain, a function is a counter, anindicator, a design / logical parameter, an event, a rule, a synthetic diagnosis, a viewtemplate or a report template.

Function Tree A function tree is a tree in a mode displaying counters, indicators, parameters, events,rules, synthetic diagnosis, view templates or report templates.

Mode A Mode is characterized by: an Object Type, a list of available topology classifications forthe objects of that type, and a list of available data/functions applicable to these objects.

Typical modes for 2G are: BSC, Cell, Adjacency, TRX, Traffic Zone.

Typical modes for 3G are: RNC, Cell, Adjacency.

Depending on the selected mode, the user has a specific list of available topologyclassifications and functions.

All available modes are grouped in the Mode Manager.

DesignParameters

Parameters that define the radio network architecture in term of coverage and mobilitycapability.

LogicalParameters

Parameters that permit the telecom behavior optimization. They are also called telecomalgorithm parameters.

QoS Counter QoS Counters are used as building blocks in the formation of QoS Indicators.

QoS Indicator An Optimization Application view used to track the quality of service in a radio network.

It is computed from Performance Measurements / Counters values, other indicators, orany other available network parameters values (e.g.: radio parameters).

ReferenceValues

Excel files that express the default value that a parameter for a given network objectshould have.

Rules Excel files that express the dependency between two or more parameters of a givenobject, and are stored in the Oracle database.

Events Events are historicized network configuration data keeping track of logical/designparameter modifications and/or topology modifications.

Filter In a topology or function classification, a filter is a set of criteria that can be applied ontop of the classification. It allows hiding of objects that do not match the filtering criteriain the classification.

In a view, whether on its own or in a report, filtering allows hiding of tabular data basedon user defined criteria.

22 / 664 3BK 21216 AAAA PCZZA Ed.26

1 Introduction

Classification A Classification defines how a set of objects are classified using some criteria.The resultof a classification applied to a set of objects is a tree structure in which the objects arethe leaves, and the classification criteria are the nodes.

A Classification can be applied to Network Objects (Topology Classification), ObjectZones (Zone Classification), and Functions (Function Classification).

Typical Classifications are: flat classification (All classification), OMC classification(OMC/BSC/cell), by LAC, by frequency…

Working Zone A Working Zone is a set of criteria applied on the entire network to compute thesub-network that is displayed in the Analysis Desktop.

The Global Working Zone is defined with no criteria and allows visualizing the entirenetwork.

This subset of cells can be:

Global: All the objects in the database are accessible.

User-defined: Using the Working Zone Manager, you define the cells that are

accessible within a particular Working Zone.

You can open only one Working Zone at a time on your workstation.

Object Zone An Object Zone refers to the logical topology objects that allow the manipulation of a setof network objects as a single topology object.

The Global Object Zone is defined with no criteria and allows visualization of the entireWorking Zone.

View A view displays the results coming from counters, indicators or parameters, in a tabular orgraphical way.

A view contains the network objects, functions, and Execution Context (period, interval,sampling, interpolation, reliability options).

View Template A view template is a formal description of a graphical representation of QoS indicator orparameter values, depending on the type of view template.

The view template is used when building a view.

As a report template is composed of view templates, a report is composed of views.

Report A report displays the results coming from indicators or parameters in view templates, in atabular or graphical way.

A report contains the network objects, views, comment zones, and an Execution Context.

A report is also known as an executed report and is displayed in the report viewer.

ReportTemplate

A report template describes a sequence of graphical representations of QoS indicator orparameter values.

A report template is mainly composed of one or more view templates and comment zones.

The report template is used when building a report.

A report template is composed of view templates, as a report is composed of views.

3BK 21216 AAAA PCZZA Ed.26 23 / 664

1 Introduction

ExecutionContext

The Execution Context contains what is needed to obtain the indicator or counter valueson a set of network objects, for example: periodicity (raw, hour, day, week, busy hours),time interval, sampling, interpolation, reliability options. When referring to the ExecutionContext, the spatial scope itself (set of network objects) is not included.

The Execution Context is used when creating views and reports.

CommentZone

A comment zone is an area of text that may be entered in a report template and istherefore displayed in an executed report.

Comment zones are not mandatory. They may be interleaved with the view templates inthe report template.

AvailabilityDomain

This defines the availability of counters, indicators, parameters, view templates, and reporttemplates both spatially and temporally.

The availability domain of a view template is the intersection of indicators’ or parameters’availability domain used in the view template. The view templates that are displayedin the mode RNC, for example, mean that the RNC is in the availability domain for theview template.

The availability domain of a report template is the intersection of the contained viewtemplates’ availability domain used in the report template. The report templates that aredisplayed in the mode RNC, for example, mean that the RNC is in the availability domainfor the report template.

Tuning Tuning is a preparation mode consisting of a significant set of modifications needed tocorrect misbehaviors of the network or to enhance its quality of service.

A Tuning Session contains Tuning Operations such as parameter modifications ortopology changes.

A Tuning Session can be applied whenever necessary. All Tuning Operations are thenbe forwarded to the concerned OMC-Rs. All these operations have to be considered asrecommendations sent to the OMC-R operator(s).

DiagnosisScenario

Diagnosis scenarios provide information on the possible causes of a QoS problem andsuggest ways to solve it.

The result of the diagnosis appears in the executed view or as an HTML file.

The following modes are defined:

Detailed mode - when executed in detailed mode, the diagnosis scenario reportcontains a precise reporting execution description for each node of the scenario

Synthetic mode - when executed in Synthetic mode, the diagnosis report contains

a synthetic status associated with a description string for the whole scenario. Theexecution process is stopped at the first for the first error encountered

Tuning mode - the diagnosis can be triggered for checking the Tunning Session.

Alerter Based on the reported Performance Measurement data, alerters are defined to detectQoS problems and generate QoS alarms in the OMC-R.

HardwareInventory

Collection of hardware and firmware information of the network elements, coming fromthe associated OMC-Rs.

24 / 664 3BK 21216 AAAA PCZZA Ed.26

1 Introduction

1.2 NPO Overview

1.2.1 Presentation

NPO offers a full range of multi-standard QoS Monitoring and radio networkoptimization facilities:

Powerful Graphical User Interface supporting all efficient use of the NPOfunctions

QoS analysis

QoS decrease cause diagnosis

Radio resource configuration tuning

Cartographic telecom management

Manage hardware inventory

Customizing.

It includes the multi-standard version of the previous products deployed inAlcatel-Lucent networks: RNO, NPA, and LASER.

NPO supports GSM, W-CDMA and WiMAX Radio Access Networks.

This product includes a powerful Oracle™ database containing performancemeasurements and calculated indicators. Based on them, the detection ofQoS degradation is done much faster, NPO also proposing the appropriatecorrection tasks and an improved logical configuration for the radio network,even in multi-standard environments.

Performance measurements ensure:

Efficient planning and optimization of the network

Efficient optimization of the network

Usage statistics

Detailed investigation of a past problem

Real-time analysis.

3BK 21216 AAAA PCZZA Ed.26 25 / 664

1 Introduction

NPO is delivered by Alcatel-Lucent as part of different products: 9953 MP andalso other OMC-Rs. Depending on the bought product and commercial option,not all modes and technologies may be available.For example, M1 9953 MP supports only GSM and W-CDMA; while OMCWiMAX W2 supports only NPO.

1.2.2 User Interface

Just as for its ancestor - the A9156 RNO, the user interface is a main asset ofNPO. The user interface is intuitive, allowing the optimizer to interact with thetool in a friendly way, being provided with all needed information, commands,processing results.

The NPO user interface uses the latest graphical methods to provide a clearrepresentation of any kind of data. So-called gadgets are used to presentobjects (e.g. GSM or W-CDMA cells, QoS indicators, logical parameters, etc.)and sort data by different criteria. Gadgets are grouped into tabs according totheir use (e.g. selection of cells and parameters, or display of QoS indicators).Data is displayed in tables or charts, and some facilities allow the user toquickly reorganize the user-interface look.

The next figure shows the main MMI window: the analysis desktop.

Figure 1: QoS Analysis Desktop View

The user interface is based on an object-oriented design, all actions beingaccessible through contextual menus. Depending on the selected object(s),only the relevant commands are provided. Most operations can be done throughthe drag-and-drop mechanism or with the help of menu bars and toolbars.

The main NPO user interface (analysis desktop) is composed of five areas:

Standards and Modes BrowserStandards define the technologies available on NPO (GSM, W-CDMA,WiMAX).

26 / 664 3BK 21216 AAAA PCZZA Ed.26

1 Introduction

Each standard tab has a set of modes. According to the selected mode, thelist of displayed counters / indicators / parameters / reports / views is not thesame. It is filtered according to their availability domain.

Topology Classification BrowserRadio resources (cells), as well as physical resources (BTS, NodeB, BSC,RNC…) are displayed in tree gadgets and can be selected from there.Different tree gadgets are used to display the network resources by differentclassification criteria. The classification can be done for example by LAC,hardware topology, cell type, routing area (for GPRS).

Function Classification BrowserFunctions belonging to a selected network resource from the topologybrowser are also displayed inside tree gadgets and can be selected fromthere. This area allows the operator to select: QoS indicators, QoS counters,logical / design parameters, or views / reports (grouped into families).

View BrowserThe view browser is the target place for drag and drop of one or morenetwork resources and one or more functions.It contains views that are used to display values of logical / designparameters, indicators, and counters.The displayed data in the view can be exported to Excel for further analysis.Two mode forms are proposed: tabular and graphical.

Report BrowserThe report browser is the target place for drag and drop of one or morenetwork resources and one or more views.A report is composed of several views, each displaying a set of definedindicators or parameters for a user defined report period.Data displayed in the report can be exported to Excel for further analysis.

Tuning BrowserThe tuning components offer services to create, edit, and apply tuningsessions on tunable systems (OMC-Rs). A Tuning Session (TS) is a setof changes (object/parameters/adjacencies/frequency creation, update ordeletion), it can be created, updated and applied.

Detailed Diagnosis Report BrowserThe detailed diagnosis report browser gives information on the possiblecause of a detected QoS problem, and offers hyperlinks to view thePython node code.

Cartography BrowserThe geographical representation capability is a complement to the treegadgets representation. GSM cells, W-CDMA cells, BTSs, NodeBs, BSCs,RNCs, MSCs, OMC-Rs or adjacencies are displayed with geographicalmaps in the background. Thus the location of the network elements, thesectoring, the type and the status of cells can be seen at a glance. Thisgeographical representation offers zooming facilities and searching facilities(by dragging & dropping objects from tree gadgets representations).

3BK 21216 AAAA PCZZA Ed.26 27 / 664

1 Introduction

1.3 NPO FunctionsThe NPO enables you to optimize:

QoS analysis

Reference values

Rules and diagnosis

Events

Configuration parameters

Tuning

Cartographic display

Network stability and availability, alarms

Customizing.

1.3.1 QoS Analysis

The NPO collects periodical measurements of the radio traffic, radio resourceusage, and handover behavior from the network elements through the declaredOMC-Rs. These measurements serve the quality of service monitoring at theNPO, and back-office activities such as network optimization and networkplanning.

The permanent network-wide QoS monitoring relies on the regular collection ofthe same performance counters on all managed Network Elements.

Raw measurements are stored in the NPO database. Based on rawmeasurements, indicators are calculated and stored for up to two years. Theseindicators are consolidated in daily, weekly, and monthly values, and can beadditionally consolidated on a group of Network Elements. The indicatorscorrespond to high level information which can be directly managed by theoperator and are defined by Alcatel-Lucent.

The user can select and launch any predefined or user-defined QoS report. theNPO provides a powerful dynamic graphical user interface that eases QoSreport analysis. For specific needs where the provided standard indicatorsare not appropriate, the operator can define via an Indicator Manager its ownindicators called Customer Indicators.

The NPO operator can display the results in the form of reports containing bothtables and graphs (several indicators graphically displayed simultaneously).The customer can also customize reports, for an easier adaptation to operatorneeds.

Special functions allow identification of the worst or best cells related to a QoSindicator, to get reports on the QoS evolution, and to compare the service qualityof different cells. Comparing QoS indicator values with predefined thresholds,the NPO ensures rapid verification of the quality of service in each single cell.

28 / 664 3BK 21216 AAAA PCZZA Ed.26

1 Introduction

1.3.2 Reference Values

The feature described in this section is not yet available for W-CDMA.

Reference values are recommended values of parameters. They allow aquick audit of the network and allow the operator to detect which objects arenot following recommendations for parameter values. The reference valuesfor a parameter depend on different criteria, such as cell type, cell class,frequency, BTS type, etc.

NPO is delivered with a default set of reference values, which can becustomized to fit the operator’s needs.

1.3.3 Rules and Diagnosis


NPO is used to investigate and diagnose QoS problems. Depending on theraised problem, it proposes some corrective actions and/or extra investigations.

In order to benefit directly from any optimizer’s field experience, NPO allowsintegrating new diagnosis scenarios. Thus the network optimizer can rely onthe diagnosis rules supplied by Alcatel-Lucent, but also on the ones derivedfrom their own optimization experience.

Whenever a QoS indicator reaches its alert threshold, NPO offers thediagnosis feature to the optimizer, in order to find out the possible cause ofthe QoS degradation.

1.3.4 Events

Events show when key information of a parameter (identifier, BSC,frequency…), or topology (eg. Move BTS) is changed, based on the QoSevolution of the network.

NPO is delivered with a default set of events.

Note: For W-CDMA, only the following events are available: cell, adjacency, networkelement creation/deletion.

1.3.5 Configuration Parameters

The configuration function is used to verify the operational logical parametersettings. This is done by comparing the operational values with the referencevalues.

Additionally, the operational cell design is verified by comparison with theplanned design. In order to follow the evolution of the logical parametersettings, the imported operational values are stored in the NPO database.Appropriate reports can be requested at any time.

3BK 21216 AAAA PCZZA Ed.26 29 / 664

1 Introduction

1.3.6 Tuning


After a network optimization session is completed, a radio parameter tuning isperformed using NPO. This is done in order to correct the network misbehaviorand uses functions of monitoring, checking, and diagnosis. The NPO user canprepare radio resource configuration modifications, frequency changes andneighborhood modification and apply them through the managed OMC-Rs.

1.3.7 Cartography

Using the cartography module, the location of the network elements, thesectoring, the type and the status of cells can be seen at a glance. Cells,adjacencies, BTSs and BSCs can be displayed with geographical maps inthe background, coming from RNP. The integrated cartography editor offerszooming, highlighting, searching, exporting facilities.

Contextual menus on cells allow a quick identification of interfered cells,serving-cell area, neighborhood, etc. Finally, it is possible to choose any groupof cells in the geographical re-presentation and make them selected in thedifferent tree gadgets. NPO geographical representation supports standardvector formats.

30 / 664 3BK 21216 AAAA PCZZA Ed.26

1 Introduction

1.3.8 Network Stability and Availability, Alarms

The feature described in this section is not planned for W-CDMA.

NUART (Network Unavailability and Alarm Reporting Tool) gives you thepossibility to analyze and report system quality degradation, detect the impacton stability and unavailability, highlight faulty equipment, extract unavailabilityrelated to managed objects for a specified time period, filter and sort statistics.

Based on the reported PM data, alerters detect QoS problems and generateQoS alarms.

1.3.9 Remote Inventory Data Management (RIDM)


NPO can manage the hardware inventory for Network Elements from theOMC-Rs that send data automatically. You can remotely read informationabout the needed equipment.

NPO offers support for statistics, search, comparison with the list of alloweditems called CAL (Customer Acceptance List).

1.3.10 Customizing

In order to allow immediate use of the NPO, all adaptable values are set withdefault values provided by Alcatel-Lucent at delivery. The customizing isperformed by the operator, as specific access rights are required.

The following values can be customized:

User defined QoS indicatorsNPO users can create their own indicators when needed.

QoS indicator thresholdsThe user can define three alert thresholds corresponding to three QoSrequirement levels, for each QoS indicator.

ViewsA view is an arrangement of consistent graphs and tables for a set of QoSindicators, parameters, and other functions.Four types of views are defined: standard, vector, and matrix and equipment.

Apart from the specific case of Equipment, views can also be grouped intofour types of evolution and comparison:

Mono-Object Evolution View

Multi-Object Evolution View

Multi-Object Comparison View

Mono-Object Distribution View.

ReportsA report is composed of one or several views, and enables the user todisplay results coming from QoS indicators, parameters, and other functionsin view templates.

NPO provides the five types of reports:

3BK 21216 AAAA PCZZA Ed.26 31 / 664

1 Introduction

Mono-Object Evolution Report

Multi-Object Evolution Report

Multi-Object Comparison Report

Mono-Object Distribution Report.

Warning Report.

Working zonesA Working Zone defines an area on which an optimizer performs his networkoptimization activities (network resource filter).

Object zonesAn object zone is a user-defined filter that works on the current WorkingZone.

Topology classificationsThe topology classification defines how network objects are classifiedin a tree structure, depending on the selected mode. It isdependant onused technology.

Function classificationsThe function classification defines how functions are classified in a treestructure. It is not dependant on the used technology.

Free field definitionsFree fields are attributes than can be defined on any topology objects (suchas cells, BSCs, RNCs). Sorting and filtering capabilities can then be used totake advantage of the information provided by these fields.

Parameter reference values


The reference value of a logical parameter is the one recommended bythe optimization expert.

Parameter checking rules


A parameter checking rule expresses the functional dependency between aset of parameters of objects like cell, BSS or adjacent cells.

Diagnosis scenariosA diagnosis scenario is an analysis tree that contains ways to investigate aquality of service problem using the data available in NPO. Scenarios canbe system or user defined.

AlertersAlerters are defined to detect QoS problems and generate QoS alarms inthe OMC-R, on the basis of reported Performance Measurement data, thenautomatically loaded inside the NPO. They are calculated from indicators.

32 / 664 3BK 21216 AAAA PCZZA Ed.26

1 Introduction

1.3.11 Advanced Optimization Features

1.3.11.1 Working ZonesWorking zones are used to facilitate the work on a specific set of networkobjects and functions. They are sub-network definitions, the operator beingable to work only in some Working Zones.

When the user starts the Analysis Desktop, they select the preffered WorkingZone to work with and they will only see the objects from this Working Zone.

Working Zones are managed through SEC (Profiles/users relations), and canbe created public or private.

To define a Working Zone, a set of criteria on base objects (for example cells) isprovided – other accessible objects are deduced from this basic set of objects.

The Global Working Zone is a Working Zone with no filter that containsall objects.

1.3.11.2 Radio Measurement StatisticsEven if the “Radio Measurement Statistics” (RMS) feature is a GSM-specificfeature, NPO offers some services based on it because it is of primeimportance for GSM operators and the aim of NPO is to offer all the means tooptimize radio network whatever the used technology.

Using this feature, the operator is able to:

Detect interfered frequencies

Assess the quality of cell coverage

Assess the traffic distribution in the cell using statistics on reported neighbor

cells

Evaluate the voice quality in the cell.

To Import RMS Template Values (GSM specific), refer to “NPO AdministrationGuide”.

1.3.11.3 QoS and Resource Unavailability Correlation

This section is not applicable for W-CDMA.

When a cell has a bad QoS (congestion for example), it is important for theoptimizer to know if this bad QoS is due to a pure radio problem, or to ahardware failure or maintenance action that led to the unavailability of thecorresponding equipment. For example, if a cell with 4 TRX had 2 of the 4TREs out of service during the day, there is a strong probability that there wouldhave been some congestion during this period.

LASER calculates unavailability indicators based on information collectedfrom the managed OMC-Rs, which are then imported in NPO. Each indicatorreflects the availability percentage of the corresponding resource (cell or TRX,for example). The operator can display these indicators or use them as anoptional filter for warning reports (for example, to display the 20 worst cells ofthe Working Zone, in terms of congestion, and having an unavailability lessthan 5% during the day).

3BK 21216 AAAA PCZZA Ed.26 33 / 664

1 Introduction

1.3.11.4 User Defined IndicatorsThe NPO provides a rich set of default QoS indicators that allow the optimizerto carefully follow the network’s quality of service and take corrective actions incase they are not optimal.

At the same time, it also allows operators to define their own QoS indicatorformulas, using a graphical editor. Once the indicators are created, they areavailable for all QoS related functions, such as QoS reports.

Alcatel-Lucent delivers its own set of indicators (system indicators), but theoperator can create its own (customer indicators).

The threshold of system indicators can be updated by the optimizer.

1.3.11.5 User Defined RulesNPO interface allows changing the rules applicable and checked onparameters. Rules are the dependencies between two or more parameters ofa given network object (for example, a timer must be higher than another).The format of the rules file is Microsoft EXCEL™.

Default rules are provided with the system, but they can also be changed tobetter suit the customer needs. The maximum value of rules provided withinthe NPO application (per RNS/BSS release) is 200. The operator can createup to 50 rules.

1.3.11.6 User Defined DiagnosisNPO investigates the causes of QoS weaknesses for particular QoS indicatorsand complex rules, using predefined diagnosis scenarios. It then suggestscorrective actions and/or further investigation.

System diagnosis scenarios are provided by the NPO, but optimizers cancreate their own diagnosis scenarios, using the Eclipse editor. The procedure isexplained in the NPO Diagnosis Development Guide.

1.3.11.7 User Defined Thematic LayersThematic layer is a feature that allows the user to visualize QoS informationon the geographical representation. Its purpose is to color parts of thegeographical representation, according to user requests on the QoS indicators,parameter values, analysis results, etc.

NPO provides a thematic layer editor where each operator is free to enter hisown requests and the associated colors depending on the results. The productis delivered with some default layers like traffic distribution or frequency reusing.

The results are mapped on cell contours (when analysis is done on cells) toprovide a good representation, even at low zoom level.

1.3.11.8 User Defined Topology ObjectsBesides the imported topology objects, the customer can create their own.The procedure is defined in “NPO Administration Guide”, chapter CustomerTopology Objects Management.

34 / 664 3BK 21216 AAAA PCZZA Ed.26

2 Getting Started with Analysis Desktop


This section describes how to initialize and perform simple tasks using theAnalysis Desktop main window.

3BK 21216 AAAA PCZZA Ed.26 35 / 664


2.1 Initialize Analysis DesktopTo initialize the Analysis Desktop main window, refer to NPO Getting Started.

If Analysis Desktop... Then...

Is started for the firsttime

1. The ’Select Working Zone’ window opens.

2. Select the appropriate Working Zone, ’Global’ or user defined, then clickon [ Open ].

The default standard, mode, topology classification and function classificationare displayed for the selected Working Zone.

The topology and function trees are created, but only the first level treesare displayed.

The QoS requirement is set as that of the Working Zone.

Is not started for thefirst time

1. The following question appears:Last Working Zone was <working_zone_type>, would you like to

open it?

If you click on:

[ Yes ], the last selected Working Zone is initialized.The last accessed standard, mode, topology classification and functionclassification are loaded for the selected Working Zone, with everythingthat the user had accessed the last time.However, only the first level function and topology trees are displayed.

[ No ], the ’Select Working Zone’ window opens.

2. Select the appropriate Working Zone, then click on [ Open ].

The default standard, mode, topology classification and function classificationare displayed for the selected Working Zone.

The topology and function trees are created, but only the first level treesare displayed.

The QoS requirement is set as that of the Working Zone.

2.2 Exit Analysis DesktopTo exit the Analysis Desktop main window:

1. Select Analysis Desktop -> Exit or click on the icon from the toolar.

2. If the user preferences are set with ’Prompt to confirmon exit’ option, the following confirmation appears:Do you want to exit Analysis Desktop?

Click on [ OK ].

36 / 664 3BK 21216 AAAA PCZZA Ed.26


2.3 Title BarThe title bar is the strip at the top of Analysis Desktop window. It contains thecurrent working zone and QoS Requirement.

On the left, the icon and company name are displayed. On the right, severalicons allow to minimize, maximize or close the application.

2.4 Standards / Modes / Topology Classifications / FunctionClassifications

This section describes the main window for the Analysis Desktop. If the userhas logged in for the first time, the first level tree is expanded.

The standard browser comprises:

Mode Browser

Topology Classification BrowserNetwork Objects

Function Classification BrowserFunctions

Executed View BrowserExecuted Views

Executed Report BrowserExecuted Reports

Executed Cartography BrowserCartography Information, containing three main regions: toolbar, viewport, and minimap

Tuning BrowserTuning Sessions

Diagnosis BrowserDetailed Diagnosis Scenario Execution.

3BK 21216 AAAA PCZZA Ed.26 37 / 664


2.4.1 Organization

The following figure shows how Analisys Desktop is organized in browsersand tabs:

38 / 664 3BK 21216 AAAA PCZZA Ed.26


2.4.1.1 Standards and Modes BrowserThe standards define the available technologies: GSM, W-CDMA, WiMAX.

When one standard is selected, the tab is highlighted. This is called the’active standard’.

Arrow buttons are available for accessing all standards if they are not visibledue to the width of the standard browser.

Each standard tab has a set of modes. When one mode is selected, it ishighlighted. This is called the ’active mode’

According to the selected mode, the list of displayed counters / indicators /parameters / reports / views is not the same. It is filtered according to theiravailability domain.

3BK 21216 AAAA PCZZA Ed.26 39 / 664


Organize Modes 1. Right click on a mode and select Organize Modes...The Organize Modes window opens, displaying the available modes.

2. Only the modes which you want to display must be selected.

To hide a mode, unselect it.

3. To reorganize it, select it and click on:

[ Move Up ], to move it one position higher

[ Move Down ], to move it one position lower

[ Show ], to display it

[ Hide ], to hide it.The Unselected Mode and its Topology Classifications and

functions will also be hidden confirmation message appears.Click on [ Yes ].

4. Click on [ OK ].

The following message appears: Are you sure you want to see the

changes in the modes? Click on [ Yes ].

40 / 664 3BK 21216 AAAA PCZZA Ed.26


Hide Mode 1. Right click on a mode and select Hide ModeThe following message appears:

2. Click on [ Yes ]. The selected mode and its corresponding topologyclassification and data trees are hidden.

Refresh Mode 1. Right click on a mode and select Refresh Mode .

2. The selected mode is refreshed.

3BK 21216 AAAA PCZZA Ed.26 41 / 664


2.4.1.2 Topology Classification BrowserThe topology browser comprises:

Topology Classification TabsThese 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 Status BarThe topology status bar displays the number of selected objects and the totalnumber of objects. It is dynamically refreshed when the selection changes.

Topology TreeThe Topology Tree displays the network objects as a tree, for the selectedmode and topology classification. The ’All’ classification is applicablefor all modes.

42 / 664 3BK 21216 AAAA PCZZA Ed.26


3BK 21216 AAAA PCZZA Ed.26 43 / 664


Organize Topology

Classification Trees

1. Right click on a function tree and select Organize Trees...The Organize Topology Classification window opens, displaying theavailable classifications.

2. Only the classifications which you want to display must be selected.

To hide a classification, unselect it.





[ Hide ], to hide it.The Unselected Topology Classifications will be hidden

confirmation message appears. Click on [ Yes ].

4. Click on [ OK ].


changes in the topology classifications? Click on [ Yes ].

44 / 664 3BK 21216 AAAA PCZZA Ed.26


Hide Topology

Classification

1. Right click on a classification and select Hide TreeThe following message appears:

2. Click on [ Yes ]. The selected topology classification is hidden.

Refresh Tree 1. Right click on a classification and select Refresh Tree .

2. The selected topology classification is refreshed.

Apply Filter on Topology

Classification

1. Right-click on a topology classification and select Select Filter .

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

2. Select the appropriate pre-defined filter.

The topology tree is refreshed according to the filtered classification.

For more information, refer to Topology Classifications (Section 7).

3BK 21216 AAAA PCZZA Ed.26 45 / 664


2.4.1.3 Function Classification BrowserThe function browser comprises:

Function TabsThe function tabs include the set of tabs for the selected mode.If all tabs cannot be displayed due to the width of the Function Browser,arrow buttons appear allowing the user to scroll among all the existing tabs.

Function Status BarThe function status bar displays the number of selected functions and thetotal number of functions. It is dynamically refreshed when the selectionchanges.

46 / 664 3BK 21216 AAAA PCZZA Ed.26


Functions Tree

3BK 21216 AAAA PCZZA Ed.26 47 / 664


48 / 664 3BK 21216 AAAA PCZZA Ed.26


The function tree displays the following list of functions per selected modeand function:

CountersOnly the scalar counters are displayed in the functions tree. However,when creating indicators, all types of counters, i.e. Scalar, Matrix, Vectorand Axis are displayed in the tree. Counters are classified as Family /Sub-Family, with up to four levels of sub-families.

DesignDesign parameters can have four sub-levels in the family hierarchy (i.e.family and sub-family).

IndicatorsOnly presentation indicators are displayed in the indicator tree. Axisindicators are displayed in the indicator tree only when creatingindicators and view templates.

Indicators can be displayed in two different classifications:

Indicator Type / Family / Sub-Family ClassificationIn this classification, the indicator type can be Scalar / Vector / Matrix.Four levels of family / sub-family classification are supported.

Family / Sub-Family ClassificationNo indicator type is present for the indicator. Four levels of family /sub-family classification are supported.It is possible to sort indicators per indicator type.

LogicalLogical parameters can have four sub-levels in the family hierarchy (i.e.family and sub-family).

Report

Report Templates can be displayed in three different classifications:

Report Template Type / Family / Sub-Family ClassificationIn this classification, the Report Template Type can be Mono-ObjectEvolution, Multi-Object Evolution etc.The family / sub-family classification can be up to four levels.

Family / Sub-Family ClassificationNo report template type is mentioned for the report. Four levels offamily / sub-family classification are supported.

Report Type ClassificationIn this classification, the Report Template Type can be Mono-ObjectEvolution, Multi-Object Evolution etc.

View

View Templates can be displayed in two different classifications:

View Template Type / Family / Sub-Family ClassificationIn this classification, the View Template Type can be Scalar / Vector /Matrix / Equipment. Four levels of family / sub-family classificationare supported.

Family / Sub-Family ClassificationNo view template type is mentioned for the view. Four levels of family/ sub-family classification are supported.

3BK 21216 AAAA PCZZA Ed.26 49 / 664


Free FieldsFree Fields are displayed in alphabetic order and no user-definedclassification can be created for them.No icon is associated to the free field.

Diagnosis ScenariosDiagnoses are displayed classified by their family and sub-familiesproperties.One Diagnosis can be associated to more than one family/sub-familyand thus be displayed more than once.

RulesRules are displayed classified by their family and sub-families properties.One Rule can be associated to more than one family/sub-family and thusbe displayed more than once.

ThematicsTHL are displayed classified by their family and sub-families properties.One THL can be associated to more than one family/sub-family and thusbe displayed more than once.

TuningTuning classification contains Tuning Operations. Most of the TuningOperations are leaves and can be dragged and dropped in a TuningSession.Tuning Operations are sorted by alphabetical order and Parameters aredisplayed classified by their family and sub-families properties under aStandard node. Only Parameters for which the ‘Visible’ property is set to‘True’ and that are tagged as being Tunable are displayed.

Events.Events are displayed classified by standard.

50 / 664 3BK 21216 AAAA PCZZA Ed.26


Organize Function Trees 1. Right click on a function tree and select Organize Trees...The Organize Data Trees window opens, displaying the available functiontrees.

2. Only the function trees which you want to display must be selected.

To hide a function, unselect it.





[ Hide ], to hide it.

3BK 21216 AAAA PCZZA Ed.26 51 / 664


The Unselected Data Trees will be hidden confirmation messageappears. Click on [ Yes ].

4. Click on [ OK ].


changes in the data trees? Click on [ Yes ].

Hide Tree 1. Right click on a function tree and select HideThe following message appears:

2. Click on [ Yes ]. The selected function tree is hidden.

Refresh Tree 1. Right click on a function tree and select Refresh Tree .

2. The function tree is refreshed.

Select a Function

Classification

1. Right click on a function tree and select Classification

design / logical parameters, and counters: Family / Sub-Family

for indicators and views:

2. Select as appropriate:

Family / Sub-Family , for design / logical parameters, counters,

indicators, views, reports, tuning, events, free fields

Type , for reports, diagnosis scenarios, rules

Type / Family / Sub-Family , for indicators, views, reports

<Customer Defined>, for all functions, if customer functionclassifications are created (see Create Function Classification (Section

8.3)).

The function tree is classified based on the chosen option.

For more information, refer to Function Classifications (Section 8).

52 / 664 3BK 21216 AAAA PCZZA Ed.26


2.4.1.4 Executed View BrowserThe executed view browser can contain:

One or more network objects

One or more counters / indicators / view templates / parameters (design or

logical) / rules / events / free fields / diagnosis.

2.4.1.5 Executed Report BrowserThe executed report browser can contain:

One or more network objects

One or more view templates / report templates.

2.4.1.6 Cartography BrowserThe cartography browser contains:

A viewport with the geographical representation of the evaluated zonecontaining several network objects

The Layer Manager with a list of layers and sub-layers.

2.4.1.7 Detailed Diagnosis Report BrowserThe Detailed Diagnosis Report Browser contains test nodes grouped in trees,giving information on the possible cause of a detected QoS problem, andoffering hyperlinks to see the Python node code.

2.4.1.8 Tuning BrowserThe tuning browser can contain:

One or more tuning sessions

One or more tuning jobs

Synthesis table.

3BK 21216 AAAA PCZZA Ed.26 53 / 664


2.4.2 Customizing

2.4.2.1 User PreferencesThe behavior of Analysis Desktop can be customized to fit user preferences.Refer to Configure User Preferences (Section 27.2).

The window location, splitter position and window size are stored as implicituser preferences.

2.4.2.2 ResizingA horizontal splitter separates the Mode Browser and Executed View Browser;and a vertical splitter separates the Mode Browser and Executed ReportBrowser. The browsers can be resized and the splitters act as partitions (SeeLayout User Preferences (Section 27.3)).

2.4.2.3 Visibility ManagementIf a Sub-Family is not defined, then the function object is displayed under theFamily. If a Family is not defined, then the function object is invisible and canonly be seen by the Administrator at the root level.

Visibility management for objects in the modes and functions browser takes intoconsideration the following factors:

When an object has no family, it is only visible to the Administrator

When an object has a family, it is visible only if the ’Visible’ flag is set to ’true’

When an operator removes the family associated with an object, the ’Visible’

flag is automatically set to ’false’ and cannot be changed until a new family

is reentered

When an operator associates a family with an object, the ’Visible’ flag is

automatically set to ’true’ but can then be changed before being saved

For System objects, only the Administrator can change the ’Visible’ property.

Reorganization 1. Select from the menu bar Edit -> Organize -> Standards... / Modes... /Topology... , as appropriate.

The ’Organize Standards / Modes / Topology’ window opens.

2. Select the technology whose standard / mode / topology you want to modify.

3. Click on [ Move Up ] to move it one position higher.

Click on [ Move Down ] to move it one position lower.

Click on [ Show ] to show it.

Click on [ Hide ] to hide it.

54 / 664 3BK 21216 AAAA PCZZA Ed.26


2.5 TooltipsTo enhance the information on an item, NPO provides tool tips by hovering thecursor over the item, without clicking it.

A small box appears with supplementary information regarding the item beinghovered over.

Tooltips are available for all NEs, functions, views/reports, user notes, cursorsin graphics, etc.

Figure 2: Examples of Tooltips

2.6 Display Values of Functions BrowserTo display the values of indicators / counters / parameters / views / reports:

1. You can either use the drag and drop facility, or the menu toolbar. Selectone or more network objects / indicators / counters / parameters / views /reports, then:

Drag and drop them in the Executed View / Report browser, OR

Select from the menu toolbar, as appropriate:

View -> Display QoS... for indicators / counters / parameters / views

Report -> Display QoS... for reports.

OR

Press:

Ctrl+Q, for indicators / counters / parameters / views

Ctrl+Shift+Q, for reports.

2. The Execution Context window opens.

Set the appropriate values for periodicity, interval date and time,interpolation, sampling, reliability, tuning session for forecast value, andfilter for warning reports.

3. Click on [ OK ].

The values appear in theExecuted View browser.

To view:

The View templates , select the appropriate view, then:

3BK 21216 AAAA PCZZA Ed.26 55 / 664


Right click and select View Template , OR

Select Data-> View Template from the toolbar.

The ’View Template Editor’ window opens, displaying the properties of theselected view template.

The Report templates , select the appropriate report, then:

Right click and select Report Template , OR

Select Data-> Report Template from the toolbar.

The ’Report Template Editor’ window opens, displaying the propertiesof the selected report template.

The Indicators , select the appropriate indicator, then:

Right click and select Indicator... , OR

Select Data-> Indicators... from the toolbar, OR

Press Ctrl+N.

The ’Indicator Editor’ window opens, displaying the properties of theselected indicator.

2.7 Create and Execute ReportsReports are created to display QoS reports based on user’s own selections. Areport is composed of graphs and tables, each displaying a set of defined QoSfunctions for a selected set of network resources and the defined report period(See Create Report (Section 19.2.2)).

For an easier adaptation to operator needs, the operator can customize QoSreports. (See Edit Report (Section 19.2.4))

NPO provides five types of QoS reports: mono-object evolution report,multi-object evolution report, multi-object comparison report, multi-objectdistribution report, and warning reports.

The user may choose to:

Execute Report (Section 19.3), or

Schedule Reports (Section 19.3.4)

After their execution, the reports are made available in a repository.

2.8 Diagnose QoS ProblemsIn case a QoS weaknesses is detected in NPO, the diagnosis function is usedto find its root cause and propose corrective actions and/or further investigation.

NPO has its own system diagnosis scenarios, but the operator can create theirown to better suit their needs. For this, Open Diagnosis Editor (Section 21.4),then refer to the Create Scenario procedure explained in “NPO DiagnosisDevelopment Guide”.

To trigger an investigation of the identified QoS problems, execute a view in:

Synthetic Mode (Section 21.5.1), for a short presentation of where the

problem is

56 / 664 3BK 21216 AAAA PCZZA Ed.26


Detailed Mode (Section 21.5.2), to see the detailed report of theinvestigation.

3BK 21216 AAAA PCZZA Ed.26 57 / 664


2.9 TuningNPO uses the results from the optimized reports to tune the radio configuration.

You can then define and propose network modifications to the OMC-Roperator, such as:

Create Parameter Tuning Operation(s) (Section 22.5.9)

Create Topology Relation Tuning Operation(s) (Section 22.5.10)

Create Frequency Tuning Operation(s) (Section 22.5.11)

Create Advice Tuning Operation(s) (Section 22.5.12)

The tuning session is then applied (see Apply Tuning Session (Section 22.3.6)).NPO generates tuning files, which can be viewed and exported to the OMC-R.

2.10 CartographyNPO offers a geographical representation capability for its network objects.

Before being able to visualize the layers, the administrator has to import rasterand vector file - these procedures are explained in the “NPO AdministrationGuide”, chapters Import Vector File and Import Raster File.

The operator may then:

Add Layer in Layer Manager

Add Network Objects in Viewport

Perform the needed operations with the displayed result:

Pan Rendering Viewport

Zoom In/Out/Rectangular

Single/Circular Selection

Highlight Network Objects

Compute Distance Between Points/ Network Objects, etc.

Propagate Network Objects Selection from Cartographic Viewer into Mode

Propagate Executed View to Highlight Network Objects in Cartography

Export Displayed Layers/Viewport (Section 23.3.8)

2.11 QoS Analysis Using THLThe values of logical/design parameters, QoS indicators, diagnosis, rules,geographic (ex: distance from the POI) and customer data (free fields) canbe displayed graphically using Thematic Layers.

Thematic Layers are used to display a visual analysis of one property for agroup of network objects in the map window.

NPO offers a default Thematic Layer when installed, but you can create, modifyand delete your own. See Thematic Layer Template (THL) (Section 23.6).

58 / 664 3BK 21216 AAAA PCZZA Ed.26


2.12 Network Stability and Availability, Alarms


Based on the OMC-R imported data, NUART (Network Unavailability andAlarm Reporting Tool) monitors the system stability and availability, gatheredunder the generic terminology of ‘system quality’.

The procedure to import LASER dictionaries is described in “NPOAdministradtion Guide”, sectionImport Laser Dictionary.

To load NUART data on demand, refer to “NPO Administradtion Guide”,sectionLoad Laser Data.

NUART user application enables you to display various reports:

Display Basic Unavailability (BU) (Section 25.5)

Display Suspect Origin of Basic Unavailability (Section 25.6)

Display Alarms and Logs (Section 25.7).

You can also update these reports by:

Manage Filter for Alarms and Logs (Section 25.8)

Define Sort Criteria for Alarms and Logs (Section 25.9).

Based on the reported PM data, alerters detect QoS problems and generateQoS alarms.

You can perform the following operations using alerters:

Create, Edit, and Delete Alerter

Display Alerter List (Section 24.3)

Display Alerts List (Section 24.4).

2.13 Remote Inventory Data Management (RIDM)


The HW inventory data of the entire network is necessary to prepareinterventions on sites. You can remotely read information about the neededequipment.

Examples of information that you can read include:

OMC-R hostname

Equipment first commissioning date

Exact location of the board (its rack number, shelf number and slot number)

Serial number of the board and its part number

Date of end of warranty for a piece of equipment.

3BK 21216 AAAA PCZZA Ed.26 59 / 664


Customer Acceptance List (CAL) files are used to compare the equipmentswhich should be in the customer field with what is actually present there.

The automatic collection of hardware inventory is available for 9100 BTS, 9130BSC Evolution, all types of MFS, and for TC supervised from OMC-R. Allthese equipments provide inventory data for all the active boards, for racksand some support equipments: fans, power supplies. Elements like cables,plugs are not part of the inventory.

Hardware inventory data can be imported automatically, or on-demand. Forthis, refer to “NPO Administration Guide”, section Load Inventory.

Refer to Remote Inventory Data Management (Section 26) for information onhow to view NE boards, end of warranty, boards in CAL or not in CAL.

2.14 Access Online HelpTo consult the documentation associated to:

all NPO functions, select from the toolbar: Help -> Analysis Desktophelp... , or press F1

the major panels of the Analysis Desktop, click on [ Help ] in the concernedopened window.

The online help documentation appears. The information is shown in HTMLformat, including hyperlinks to allow easy browsing between related domains.

If the Online help browser is already open, its content is updated with the newlyrequested documentation.

The operator can use the back / next navigation facilities to navigate throughthe history of the displayed help pages. Back is allowed only when at least twodifferent pages have been displayed. Next is allowed only after at least oneBack has been triggered.

Figure 3: Online Help for ”Pending Executed Reports”

60 / 664 3BK 21216 AAAA PCZZA Ed.26


2.15 Tip of the DayAt the Analysis Desktop initialization, a"Tip of the day" window appears, listinga tip which is chosen randomly among the list of available tips.

The "Tip of the day" window can also be invoked by selecting Help -> Tip ofthe Day from the menu bar.

Click on:

[ Next Tip ] to display the next available tip

[ Previous Tip ] to display the previously displayed tip.

If you want to disable the display of tips at Analysis Desktop startup, unselectthe [ Show Tips on Startup ] checkbox.

The default option is as set in the “Display tips on startup” user preference.

3BK 21216 AAAA PCZZA Ed.26 61 / 664


2.16 LicensingThe following table gives the list of licensed features available with NPO.

License Name Description

MUSE_AD_MAX_INSTANCES_LICENSE Gives the maximum number of authorized of AD instancesrunning at the same time.

Default value = 5.

MUSE_QOS_<TECHNO>_LICENSE Needed for the administrator to declare a QoS data sourcefor the given technologies (GSM, W-CDMA,…).

MUSE_PARAM_<TECHNO>_LICENSE Needed for the administrator to declare a Param data sourcefor the given technologies (GSM, W-CDMA,…).

MUSE_PLANNED_<TECHNO>_LICENSE Needed to declare a Planned data source for a giventechnology (GSM, W-CDMA, …).

MUSE_PARAM_HISTORY_LICENSE Needed for the history of parameters to be kept.

MUSE_QOS_HISTORY_LICENSE Limits the history of the QoS Data to one week.

MUSE_CUSTOMER_RULES_LICENSE Needed to import or export the rules where the supplier is“customer”.

MUSE_QOS_INDICATOR_CREATION

_LICENSE

Needed to create / update / delete indicator threshold, create/ edit an indicator, create a customer indicator by copy, deletecustomer indicator, create / edit / save temporary indicator oredit thresholds / sampling value of temporary indicator.

MUSE_REPORT_TEMPLATE_CREATION

_LICENSE

Needed to create report templates by the operator oradministrator.

MUSE_OBJECT_ZONE_LICENSE Makes all Object Zone modes available. The special modeNetwork is not displayed.

If the license is not available:

All items in popup menus, menu bar related to Object

Zones are grayed

All items in dialog windows (such as the Working Zoneeditor) related to Object Zones are grayed

The special mode Network is displayed.

MUSE_REPORT_LICENSE Needed to execute reports.

MUSE_SCHEDULING_LICENSE Needed to schedule reports.

62 / 664 3BK 21216 AAAA PCZZA Ed.26


License Name Description

MUSE_WORKING_ZONE_LICENSE Makes Working Zone Editor available.

If the license is not available:

All items in menu bar and popup menu are hidden and

not just grayed

It is not possible to change the current Working Zone

When launching the Analysis Desktop, no Working

Zone list is displayed and the GLOBAL Working Zone isautomatically loaded.

MUSE_TUNING_LICENSE Allows tuning operations.

MUSE_DIAGNOSIS_LICENSE Allows diagnosis operations.

MUSE_MAX_CELL Maximum number of cells.

MUSE_CARTOGRAPHY_LICENSE Makes the whole cartography viewer available from theNPO client. The cartography servers are started. Theadministration functions (imports) are available.

MUSE_RMS_GPRS_TUNING_LICENSE Needed to import/edit/export RMS template and GPRSThreshold values.

Note: This is not applicable for W-CDMA.

MUSE_REMOTE_INVENTORY_LICENSE Makes the Inventory features available. The import inventorydata and the Web Inventory Management tool are available.

MUSE_LASER_<TECHNO>_LICENSE Needed to declare a LASER data source for the giventechnology.

Note: This is not planned for W-CDMA.

MUSE_ALERTER_LICENSE Makes Alerter related features available (Alerter Editor,Alerter List, Alerts List).

MUSE_MAX_CUSTOMER_INDICATOR Maximum number of customer indicators.

To view the installed licenses, refer to the ’NPO Administration Guide’ andsee Display Licenses.

To install a new license, refer to the ’9953 MP/NPO Platform AdministrationGuide’ and see Activate New License.

3BK 21216 AAAA PCZZA Ed.26 63 / 664


2.17 Notification ManagementAs soon as an object is created / deleted / modified in NPO, you are informed ofthis through a notification window.

As NPO is not connected in real time to the OMC-Rs, the newly created objectin the OMC-R does not cause an immediate notification. This is only done atthe next refresh (at most one night).

To manually launch notifications, perform the following:

1. Perform one of the following options:

Click on icon from the toolbar, OR

Select Window -> Notification Management... from the toolbar, OR

Press Ctrl+W.

The Notification Window opens, listing all the unaknowledged messages.

2. Select the notification messages you want to acknowledge, then clickon [ Acknowledge ].

The selected notification messages are removed from the window.

3. Click on [ Close ].

4. Refresh the Analysis Desktop.

64 / 664 3BK 21216 AAAA PCZZA Ed.26


2.18 Consolidation Follow UpTo view the Consolidation Follow Up:

1. Click in the Analysis Desktop menu bar on .

The "NPO Administration" window opens.

2. Enter the appropriate username and password.

The "NPO Data Management - Consolidation Follow up" window opens,displaying the consolidation activity status. Each row displays the status ofthe consolidation for a day (five recoverable days appear by default).Thecolumns contain the following information:

Date of the consolidation

Status: OK when the consolidation was successful, Not performed,Failed, or Ongoing

Last Performed Step: RR/HR Transfer, Normalization, etc.This information appears only if the Status of that consolidation isFailed or Ongoing.

Recovered data: Yes or NoYes means that since the consolidation, new data is loaded (is present inRR tables) and so a recovery consolidation can be launched in orderto take it into account.No means that no data has been loaded since the consolidation.

An action hyperlink: Recover/Consolidate.There is no action hyperlink if the status is “OK” or “NotPerformed”and the Recovered Data is “No”, or if there is at least one Ongoingconsolidation for another displayed day.

3. To refresh data, click on [ Refresh ].

4. To exit the Consolidation Follow Up page, click on [ Cancel ].

To recover or consolidate data, refer to section Launch Consolidation Follow-Upfrom “NPO Administration Guide”.

2.19 Select / Deselect All ItemsTo select all necessary items:

Click in the window where the needed items must be selected

Select Edit -> Select All from the toolbar menu, OR

Press Ctrl+A.

To deselect all selected items, select Edit -> Deselect All from the toolbarmenu.

3BK 21216 AAAA PCZZA Ed.26 65 / 664


66 / 664 3BK 21216 AAAA PCZZA Ed.26

3 Common Tasks in Functional Windows


This section describes the common tasks in the functional windows.

3BK 21216 AAAA PCZZA Ed.26 67 / 664


3.1 Drag and Drop ObjectsMany operations inside the Analysis Desktop can be done using drag and drop.This facility can be used for single or multiple objects.

The following table describes the objects which can be dragged and dropped inthe different views.

ViewerName

ParameterName

Allowed Draggable Objects Allowed Droppable Objects

ExecutedViewBrowser

ExecutedViewBrowser

None. One or more Network Objects

One or more counter(s) / indicator(s) /parameter(s) / view template(s) / events /

rules / diagnosis / free fields.The user can drop a non-double selection,for example network objects withoutfunctions.Counters, parameters, indicators and / orview templates cannot be mixed in a thesame selection.

ExecutedReportBrowser

ExecutedReportBrowser

None. One or more Network Objects

One or more view / report templates /

diagnosis.The user cannot drop a non-doubleselection, for example, network objectswithout functions.

68 / 664 3BK 21216 AAAA PCZZA Ed.26


ViewerName

ParameterName


ViewTemplateTree

None. None.

Indicators Indicators

The user can drag one or severalindicators at a time and dropthem in the ’Properties’ panel.

None.

Counters Counters

The user can drag one or morecounters at a time.

None.

DesignParameters

Design Parameters

The user can drag one or severaldesign parameters at a time anddrop them in the ’Properties’panel.

None.

LogicalParameters

Logical Parameters

The user can drag one or severallogical parameters at a time anddrop them in the ’Properties’panel.

None.

TabularPropertiesPanel

Indicators / Counters / Logicaland Design Parameters

Indicators / Counters / Logical and DesignParameters.

PrimaryGraphicsPanel

None. Indicators / Counters / Logical and DesignParameters.

ViewTemplateEditor

SecondaryGraphicsPanel

None. Indicators / counters / Logical and DesignParameters.

TabularView

Indicators / Parameters /Counters / Rules / Events in thetabular view.

QoS Indicator / QoS Counters / QoSParameters.

One or more QoS Indicators / Counters /Parameters that are not already in the tabularview.

PrimaryGraphic

View Indicators / Parameters /Counters in the tabular view.

QoS Indicator / Parameter / Counter containedin the tabular view.

StandardViewTemplates

SecondaryGraphic

View Indicators / Parameters /Counters in the tabular view.

QoS Indicator/Parameter/Counter contained intabular view

3BK 21216 AAAA PCZZA Ed.26 69 / 664


ViewerName

ParameterName


TabularView

Vector Indicators in the tabularview.

QoS Vector Indicators, One or more QoSVector Indicators that are not already in thetabular view.

PrimaryGraphic

View Vector Indicators in thetabular view

QoS Vector Indicators contained in the tabularview.

VectorViewTemplates

SecondaryGraphic

View Vector Indicators in thetabular view

QoS Vector Indicator contained in the tabularview.

TabularView

Matrix Indicators in the tabularview.

QoS Matrix Indicators. One or more QoSMatrix Indicators that are not already in thetabular view.

MatrixViewTemplates

AxisIndicator

Matrix Indicators in the tabularview.

QoS Matrix Indicator contained in tabular view

EquipmentViewTemplates

- - -

TabularView

Indicators / Parameters /Counters in the tabular view.

QoS Indicator / QoS Counters / QoSParameters. One or more QoS Indicators /Counters / Parameters that are not already inthe tabular view.

PrimaryGraphicView



ViewPropertiesPanel

SecondaryGraphicView



ReportTemplateEditor

ViewTemplateTree

View Template

The user can drag one or severalview templates at a time.

None.

ReportPropertiesPanel

View andCommentZone list

None. View Template

One or several view templates that are notalready in the view template list.

ExecutedReport

SpatialScope

None. Network objects that are the same type asthose in the current spatial scope.

TuningFunctionTree

Tuning operations or tunableparameters can be dragged.

None.

70 / 664 3BK 21216 AAAA PCZZA Ed.26


ViewerName

ParameterName


TopologyClassificationTree

All the Topology objects in thetree can be dragged. User candrag one or more objects at atime.

None.

TuningSessionViewerOperationsTree

None. Topology objects / Tuning operations / Tunableparameters.

User can drag one or more topologyobjects/tunable parameters at a time. But onlyone tuning operation can be dragged at a time.

Note: To change the drag & drop modifier to add / remove, refer to "Configure UserPreferences", step (2).

3BK 21216 AAAA PCZZA Ed.26 71 / 664


3.2 Propagate Network Objects or Object Zones BetweenTopology Classification or Zone Modes

This section describes how to propagate a selection of network objects orobject zones between topology classifications and zone modes.

The following propagations are possible:

Network objects to topology classification or zone modes

Object zones to network objects

Network objects to object zones.

Propagate the required network object or object zone:

1. Click on the network object or object zone you want to propagate.

If it is a leaf node, the object is selected. If it is a non-leaf node, all objectsunder that node are selected.

It is possible to perform multiple selections and de-selections.

2. Drag the selected network object / object zone and drop it to a different zonemode or topology classification.

During the dragging process, if the mode or classification are incompatiblewith the selected network object / object zone, the mouse pointer changes to

. Continue the dragging process to an appropriate mode / classification,

where the mouse pointer is .

3. Depending on how the parameter ’Display time before a tab is raisedand made active’ is set as a user preference, the target mode or targetclassification, with the highlighted propagated network object or object zone:

Is automatically displayed, OR

You have to switch to the target mode / classification to view it.

The view is auto-scrolled until the first selected object is visible.

Note: If a filter is applied on the target classification , some dropped objects maynot be visible. In this case, a message appears and you must either choose toremove the current filter (i.e. switch to ’No Filter’), or to drop it.

72 / 664 3BK 21216 AAAA PCZZA Ed.26


3.3 Display and Edit Properties

3.3.1 Display Properties

To display the properties:

Right click on the network object / counter / indicator / design parameter/ logical parameter / report / view, then select Properties... from the

popup menu, OR

Double click on the item whose properties you want to view, OR

To view the properties of an item in the topology classification:

Select the item, then:

Select Topology -> Properties... from the toolbar, OR

Press Alt+Enter.

OR

To view the properties of a counter / indicator / design parameter / logical

parameter / report / view:

Select the item, then:

Select Data -> Properties... from the toolbar, OR

Press Ctrl+P.

The ’Properties’ window for the selected object opens.

Hyperlinks are included to allow easy browsing of related properties. Clickingon one of these hyperlinks refreshes the current ’Properties’ window or opens anew one, depending on the ’Default behavior for hyperlinks’ user preference.

When a non-leaf object is selected, the properties of this object are displayed. Ifthe non-leaf object has no associated properties, then the ’Properties’ windowdisplays only the name of the object.

If the operator selects another object in a function tree when the propertywindow is still open, the window is refreshed and displays the properties ofthe newly selected object.

Note that the newly selected object can be of a different type compared to theprevious one (i.e. select a counter, open the ’Properties’ window by selectingan indicator, and the Indicator properties in the previously opened ’Properties’window should appear).

Note: Only one ’Properties’ window can be opened at a time.

To keep a copy of the ’Properties’ window and display several on screen at the

same time, use the Snapshot feature. For this, click on .

3BK 21216 AAAA PCZZA Ed.26 73 / 664


3.3.1.1 Actions Available in Properties WindowThe following actions are available in the "Properties" window:

To edit the properties, refer to Edit Properties (Section 3.3.2)

To view the previous object in the same category, click on

.

To view the next object in the same category, click on .To view the previous page in the same category, click on

.

To view the next page in the same category, click on .

To copy the URL of a properties page refer to Copy URL (Section 3.3.3)

To close the window, click on [ Close ] .

3.3.1.2 Detailed InformationRefer to the following sections for detailed information related to specificitem properties:

Display Topology Object Properties (Section 5.3)

Display Object Zone Properties (Section 6.2)

Display Counter Properties (Section 10.3)

Display Indicator Properties (Section 10.5)

Display Logical/Design Parameter Properties (Section 11.2)

Display Rules Properties (Section 13.2)

Display Event Properties (Section 14.2)

Display Free Field Properties (Section 15.2)

Display Standard View Properties (Section 18.2.1)

Display Vector View Properties (Section 18.2.2)

Display Matrix View Properties (Section 18.2.3)

Display Equipment View Properties (Section 18.2.4)

Display Diagnosis Scenario Properties (Section 21.2)

Display Tuning Operation Properties (Section 22.2)

Display Network Objects Properties (Section 23.5.2)

Display THL Properties (Section 23.6.2) .

3.3.2 Edit Properties

Change the display properties:

1. In the ’Properties’ window, click on [ Edit ].

The specific template opens.

74 / 664 3BK 21216 AAAA PCZZA Ed.26


2. Click on .

Perform the appropriate changes, then click on to save thechanges.

Click on [ Close ] to close the template.

3. To view the results of the edit, reselect the object, right click and selectProperties .

3.3.3 Copy URL

This task is used to visualize and print an objects properties page from outsideAnalysis Desktop, using a web browser.

To copy the URL of a properties page:

1. Right click in the "Properties" window.

The [ Copy URL ] pop-up appears.

2. Click on [ Copy URL ].

The HTTP URL of the properties page is copied to the System Clipboardand it can be pasted in any web-browser (IE, Firefox…).

3BK 21216 AAAA PCZZA Ed.26 75 / 664


3.4 Generic EditorWhen creating or editing an indicator / view / report /cartography / topologyclassification / object zone / working zone, an editor with a generic format isused.

The window is resizable, by dragging the edges and corners.

Figure 4: Example of View Template Editor

Note: In case a FAD is not allocated to an item, it is grayed.

3.4.1 Generic Editor Panels

3.4.1.1 Object Selection TreeThe left panel displays all the objects, irrespective of the mode, sorted as in theFunction Browser.

The following functions can be performed within the object selection tree:

Copy

Refer as appropriate to:

Create Customer Indicator by Copy (Section 10.7.3)

Create Object Zone by Copy (Section 6.3.4)

Create Topology Classification by Copy (Section 7.4)

Create Function Classification by Copy (Section 8.4).

Create Working Zone by Copy (Section 9.2.4).

Create Sub Working Zone by Copy (Section 9.3.5).

76 / 664 3BK 21216 AAAA PCZZA Ed.26


Create View by Copy (Section 18.3.3)

Create Report by Copy (Section 19.2.3)

Create Tuning Session by Copy (Section 22.3.4).

Edit


Edit Network Object Class (Section 5.5.2.3)

Edit Object Zone (Section 6.3.6)

Edit Topology Classification (Section 7.5)

Edit Function Classification (Section 8.5)

Edit Working Zone (Section 9.2.5)

Edit Customer Indicator (Section 10.7.4)

Edit Indicator Threshold / Sampling Values (Section 10.7.5)

Edit View (Section 18.3.4)

Edit Report (Section 19.2.4)

Delete


Delete Network Object Class (Section 5.5.2.4)

Delete Object Zone (Section 6.3.7)

Delete Topology Classification (Section 7.7)

Delete Function Classification (Section 8.6)

Delete Working Zone (Section 9.2.6)

Delete Indicator (Section 10.7.6)

Delete View (Section 18.3.5)

Delete Report (Section 19.2.5)

RefreshRight click on an item and select [ Refresh ]. The entire tree is refreshed.

When selecting an item on the left panel, its properties are displayed inthe middle pannel.If there is an on-going creation or edition, the items on the left panel aregreyed.

3BK 21216 AAAA PCZZA Ed.26 77 / 664


3.4.1.2 Properties PanelThe middle panel is the working area for the object editor. This is where thedisplaying, creation and updates are actually done.

Specificities for each kind of object are described in dedicated sections.

For creation, refer as appropriate to:

Create Network Object Class (Section 5.5.2.2)

Create Object Zone (Section 6.3.3)

Create Topology Classification (Section 7.3)

Create Function Classification (Section 8.3)

Create Working Zone (Section 9.2.3)

Create Sub Working Zone (Section 9.3)

Create Indicator (Section 10.7.2)

Create View (Section 18.3.2)

Create Report (Section 19.2.2)

For updates, refer as appropriate to:

Edit Network Object Class (Section 5.5.2.3)

Edit Object Zone (Section 6.3.6)

Edit Topology Classification (Section 7.5)

Edit Function Classification (Section 8.5)

Edit Working Zone (Section 9.2.5)

Edit Customer Indicator (Section 10.7.4)

Edit Indicator Threshold / Sampling Values (Section 10.7.5)

Edit View (Section 18.3.4)

Edit Report (Section 19.2.4)

Functions from the right frame can be dropped in the properties panel.

78 / 664 3BK 21216 AAAA PCZZA Ed.26


3.4.1.3 Sub-Object Selection TreeThe right panel contains a set of function trees to fill the object editor fields.

Sub-objects can be dragged and dropped in the properties panel.

The sub-object selection list is filtered according to the objects that can beused in the object editor. For example, if a Mono Object distribution report isbeing created, then only vector and matrix view templates are displayed inthe sub object selection list.

The following functions can be performed within the sub-object selection tree:

Drag items to the middle working area

View PropertiesRight click on an item and select [ Properties ]. The ’Properties’ window forthe selected object opens.

RefreshRight click on an item and select [ Refresh ]. The entire tree is refreshed.

3.4.1.4 SplittersThe left splitter is used to adjust the object selection tree size.

The right splitter is used to adjust the sub-object selection tree size.

3.4.2 Generic Editor Buttons

Button Description

Creates a new template.

The user becomes the owner of the new template.

Copies selected item to a new one.

The user becomes the owner of the new template.The template properties window is filled with thepre-defined values.

Launches the editor mode.

Deletes the on-going operation.

Applies the on-going operation.

Cancels the on-going operation.

3BK 21216 AAAA PCZZA Ed.26 79 / 664


Button Description

Closes the window.

If the user performed changes which have not beenapplied, and they chose to close the window, thenthe Editor prompts a save option.

Opens on-line help in a separate widow.

See Access Online Help (Section 2.14) for moredetails.

Depending on the allowed operations, the buttons on the toolbar are activatedor grayed dynamically.

3.5 RefreshingTo refresh:

All the functions of the Analysis Desktop, select from the toolbar Edit ->Refresh -> All , or press the [ F5 ] key

All topology and function trees of the selected mode, select from the toolbarEdit -> Refresh -> Active Mode

Only the selected topology/function tree:

Select from the toolbar Topology -> Refresh Active Tree , OR

Select from the toolbar Data -> Refresh Active Tree , OR

Right click in the topology/function tree and select Refresh Tree .

80 / 664 3BK 21216 AAAA PCZZA Ed.26


3.6 SearchingThe searching facility is available in all windows of the Analysis Desktop(Topology/Function/Tuning Operations Trees, Object Editors, etc).

1. To display the search window:

Select from the toolbar menu Edit -> Find... , or

In the appropriate operation tree, right click and select Find... , or

Press Ctrl+F.

The search window is displayed. The first time you open the window all itsfields are unchecked by default, then the last used values are automaticallyfilled in.

2. Type the name of the object you want to search. If necessary, select oneof the following options:

’Match case’If ’Match case’ is not checked, then the search ignores case differences(eXaMple = example).

’Find whole words only’If ’Find whole words only’ is checked, then partial match is not considereda search result (e.g. searching for ’cell’ does not find ’cell_12’).

’Use wildcards’If ’Use wildcards’ is checked, then ’*’ is interpreted as wildcard for anynumber of unknown characters.If it is not checked, ’*’ is interpreted as standard characters, allowingtheir usage in names of searches.

’Search order’

’Down’ - the search is made then from the first selected object to the

end of the tree

’Up’ - the search is made from the first selected object to thebeginning of the tree

’All’ - the search is made from the beginning till the end of the tree.

If ’Include User Notes’ is checked, then the content of the user notes isalso searched while exploring the tree.’Creation’ or ’Modification date’ of the user notes, as well as ’Owner’ of itis also checked when the search is triggered.

3BK 21216 AAAA PCZZA Ed.26 81 / 664


3. Click on [ Find Next ].

If any matching object is found, it is selected and the tree is automaticallyscrolled to make it visible (nodes can be expanded if they were notpreviously). Note that the search is only performed in the activeclassification, and that no special search limited to a sub-tree or to asub-selection is needed.

82 / 664 3BK 21216 AAAA PCZZA Ed.26


3.7 Execution ContextWhen executing a view/report/diagnosis/rules/events/free fields/THL, theexecution context information must be filled in.

The window is composed of two tabs:

General

Options.

3.7.1 Periodicity

To define the granularity of the executed view/report/function, the periodicitymust be set.

Periodicity choices are dynamic and depend on the intersection of availabilitydomain of the objects (Counters / Indicators / Parameters) to be displayed.Depending on the selected view/report/function(s), indicator(s) or counter(s)or parameter(s), some periodicity units are grayed and are not available forselection.

The periodicity options are: Hour, Day, Week, Month, 1/4 Hour, 1/2 Hour, Raw(available for counters only), Busy Hour choices, Trend choices (hours of day,hours of week, days of week, and days of month). This list may vary.

For diagnosis, periodicity Less than Hour and Raw are not allowed.

For equipment view, the available periodicities are H/D/W/M only.

“Periodicity” is not needed in case of a parameter with no historical valuerequested, or in case of an Equipment View of Alarm (only H/D/W/M areaccessible in this case).

3BK 21216 AAAA PCZZA Ed.26 83 / 664


3.7.2 Execute Reports Options

In the case of reports execution, two extra options are presentin the "General" tab of the "Execution Context" window:

Immediate ExecutionUse this option to execute the report immediately. n this case, fill in theappropriate Date and Hour, and all necessary fields from "Options" tab.

To Be ScheduledUse this option to postpone the report execution to a later time. A newpanel with three tabs appears (Date, General, Repeat), as presentedin the figure below.

Refer to Schedule Reports (Section 19.3.4) for detailed information onhow to use this options.

3.7.3 Date and Hour

The following times must be set for the execution:

Starting Date (“From”) - Date and time for start of view/report/function

execution. Any date prior to 2000 is invalid.

Ending Date (“To”) - Date and time for end of view/report/function execution,or for a single date time when multiple network objects and functions

are selected.

Note: ”From“ and “To” Date fields represent the start time of the last value to bedisplayed.

For example, to visualize an hourly report with the following set times: “From:09:00 - To: 17:00”, the hourly report displays values for the “09:00 - 18:00“interval.

The dates chosen cannot be higher than the current day. If the ending dateextends past the current day, then the ending date is decreased to thebeginning of the period.

The hour cannot be higher than the current hour -1 (except if the chosen hourequal to 0 o’clock). If the user enters an hour higher or equal to the current hour,the hour is automatically set to the current hour - 1, if the hour is not equal to 0.

84 / 664 3BK 21216 AAAA PCZZA Ed.26


Dates are automatically normalized when selecting the [ OK ] button accordingto the periodicity, as follows:

1/4 Hour: the minutes are decreased to the last 1/4 hour interval (00,

15, 30, or 45)

1/2 Hour: the minutes are decreased to the last 1/2 hour interval (00 or 30)

Hour: the minutes are decreased to 00

Week: the date is decreased (if necessary) to match a first day of week

Month: the day of the month is forced to 1.

Based on the periodicity selection, the date is displayed in the following format:

1/4 Hour: <date> <HH>:<MM>

1/2 Hour: <date> <HH>:<MM>

Hour: <date> <HH>:<MM>

Day: <date>

Week: <date>

Month: <date>.

The default values for starting and ending dates are:

To set the default start and end date and time values, click on [ Default Dates ] .Depending on the periodicity, the following values are automatically filled:

Periodicity Default Starting Date Default Ending Date

5 Minutes Today 00:00 The first minute of the last completed 5 minutes beforecurrent time (now)

1/4 Hour Today 00:00 The first minute of the last completed quarter before currenttime (now)

1/2 Hour Today 00:00 The first minute of the last completed half-hour beforecurrent time (now)

Hour Today 00:00 The first minute of the last completed hour before currenttime (now)

Day Yesterday Yesterday

Week 1st day of the previousweek

1st day of the previous week

Month 1st day of the previousmonth

1st day of previous month

Trend on hoursof day

Today - 7days Yesterday

Trend on hoursof week


3BK 21216 AAAA PCZZA Ed.26 85 / 664


Periodicity Default Starting Date Default Ending Date

Trend on daysof week


Trend on daysof month


3.7.4 Trend

The following checks are done if a trend is selected:

For the trend on hours of day, the period must cover at least 1 day (24 hours)

For the trend on hours of week, the period must cover at least 1 week

For the trend on days of week, the period must cover at least 1 week

For the trend on days of month, the period must cover at least 1 month.

Trend on hours of day and trend on hours of week are available if Hour period isalso available.

Trend on days of week and trend on days of month are available if Day period isalso available.

The following table presents information on the trend calculation :

Periodicity Calculation

Trend on hoursof day

There are 24 columns from 00h, 01h, 02h, … 23h.

The value at hour n is the average for all selected day at hour n.

For example, value at 1AM is the average of the value at Monday 1AM, Tuesday 1AM…

Trend on hoursof week

There are 7 * 24 columns.

The first column is the first day of the week (according to the system preferences)followed by ’ – ’ and then followed by HHh.

For example, if Monday is the first day of the week, then the columns start and end

as:

The value at hour n for day d is the average.for all selected week at hour n and day d

86 / 664 3BK 21216 AAAA PCZZA Ed.26


Periodicity Calculation

Trend on days ofweek

The days of the week are displayed in 7 columns

The first column is the first day of the week as defined in the system preferences.

For example, if the first day of the week is Monday, then the columns

are:

The value at day d is the average of the value at day d for all selected week.

For example, value at Monday is the average of the value of Monday the 1st week andMonday the 2nd week.

Trend on days ofmonth

The days of the month are displayed as DD.

For example if the month of September is used, then the days are: 01, 02, 03, …, 30.

If, for example, the months of Sept – Dec are used, then the days are: 01, 02, …, 30, 31.

The value of the n day, is the average of the value of the indicator at day n for anyselected month.

Table 1: Trend Calculation

The trend calculation is not applied directly on the indicator formula, but on thestored indicators (basic indicators) belonging to the formula.

For example an indicator I = A / B, where A and B are stored indicator, then atrend calculation on the indicator I become trend(I) = avg(A) / Avg(B).

3.7.5 QoS Requirement

The values of QoS Requirement are: Low, Medium, High, as previously setas user preference.

This changes which values are highlighted in the view from the Legend, basedon the threshold values per QoS requirement set in the indicator definition.

3.7.6 Interpolation

Interpolation is used to automatically complete the missing values in thedata warehouse.

You can either use the default interpolation on the QoS data, or select from thedisplayed list the first and second interpolation methods:

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

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

Only OK value - when a display period is not fully available, a NULL value is

provided for that displayed period

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

3BK 21216 AAAA PCZZA Ed.26 87 / 664


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

Padding - all the missing periods are set to a padding value. This is zero by

defaut, but can be configurable through the ’Padding’ parameter.

“Interpolation” is only needed if there are indicators in the view and ’AllowDynamic Interpolation’ user preference is true.

3.7.7 Sampling

When Sampling is set, if the value of the sampling indicator is smaller than thesampling value defined in the indicator, the values are displayed in gray.

In the other cases, values are displayed in their normal style.

3.7.8 Reliability

When Reliability is set, if the value of the reliability indicator is “wrong” (notgreen), the values are displayed in italic.

In the other cases, values are displayed in their normal style.

Note: The chosen values are stored as implicit user preferences. When the samescreen is reopened, these values are displayed as default one.

3.7.9 Forecast Values in Tuning Sessions


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 selectedto be displayed is 20 by default.

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

The tuning sessions/jobs that are opened in the current Analysis Desktop andare modified without being saved are marked with an ’*’ after their name.

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

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

3.7.10 Filter Unavailable Objects

The user can choose to filter warning reports, based on the values of availabilityindicator, comparison operator, and threshold value of the network object typeon which this warning report is being executed.

This field is only used if Execution Context is subject for a warningreport. If the execution does not imply a warning report and QoS AvailabilityIndicators, then the list is grayed.

If ’Filter Unavailable Objects’ is checked, then the following parameters mustalso be set:

88 / 664 3BK 21216 AAAA PCZZA Ed.26


QoS Availability Indicator

Comparison Operator

Threshold Value.

Figure 5: Filter Options Panel inside Execution Context Window

To define the family of the indicators defined in the list, updatethe ’qosUnAvailabilityFamily’ parameter from the following file:/alcatel/muse/technologies/GSM/QoS/metadata/MaatQueryMetadata.xml

3.7.10.1 QoS Availability IndicatorQoS Availability Indicators are used to filter objects based on the ComparisonOperator and the Threshold Value.

Select one value from the list that displays the Long Names (Reference Names)of the indicators which are part of the ’System Parameter Filtering UnavailableObjects’ family, defined in system user preferences for the network object onwhich the warning report is being executed.

The implicit user preference keeps the last value used for this network object

type. To display it, click on .

If no value was defined in the system user preference, or the family does notexist, then no indicators are shown and the filtering option is grayed.

3.7.10.2 Comparison OperatorThe following values are used as comparison operators: >, <, =, <>, <=,

>=. Select from the list the appropriate one.

3.7.10.3 Threshold ValueType a real number for the ’Threshold Value’.

3BK 21216 AAAA PCZZA Ed.26 89 / 664


3.7.11 Event Synthesis


Select ’Display Event Synthesis’, to display the Event Synthesis in both tabularand graphical modes for the given network object. This parameter is used incase of a Mono-Object evolution view with “day” periodicity that contains onlystandard 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 composesthe event synthesis. It is mandatory to select one type in case ’Display EventSynthesis’ is set to ’Yes’.

Figure 6: Event Synthesis

3.7.12 Buttons

To execute views/reports/functions, click on [ Execute ]

To execute and publish views/reports/functions, click on [ Execute and

Publish ]Refer to Web Publishing (Section 20) for more information.

To cancel the on-going execution, click on [ Cancel ]

To open on-line help, click on [ Help ].Refer to Access Online Help (Section 2.14) for more information.

90 / 664 3BK 21216 AAAA PCZZA Ed.26

4 Set QoS Requirement

4 Set QoS RequirementThis section describes the behavior for setting the QoS requirement.

To set the QoS requirement levels:

1. In the menu bar, select Analysis Desktop -> Set QoS Requirement...

2. Select the appropriate QoS Requirement Level (Low, Medium or High),according to the desired sensitivity of the threshold (see Threshold andSampling (Section 10.1.10)).

3. Click on [ OK ].

The ’QoS Requirement Level’ window closes.

The newly set QoS requirement becomes the default one in the ExecutionContext used when executing views and reports.

3BK 21216 AAAA PCZZA Ed.26 91 / 664

4 Set QoS Requirement

92 / 664 3BK 21216 AAAA PCZZA Ed.26

5 Topology Objects

5 Topology Objects

This section describes the common tasks when dealing with topology objects.

3BK 21216 AAAA PCZZA Ed.26 93 / 664

5 Topology Objects

5.1 PresentationThe objects found in the Topology window represent objects in your network.They appear in different relational lists represented by tabs and sub-tabs.

These objects are discovered by NPO through files retrieved from the declareddata sources (e.g.: parameter files, PM files). At this moment, they areconsidered as operational objects. When a network object disappears fromthe network, the OMC is no more reporting data on it. NPO will detect it butwill however keep it in its database as so-called soft-deleted object (marked

with the red cross icon ). They can be filtered from different menu and areexcluded from aggregations.

To use network objects, drag and drop them together with their appropriateparameters and functions in the other functional windows.

94 / 664 3BK 21216 AAAA PCZZA Ed.26

5 Topology Objects

To create/load/delete customer topology objects, refer to “NPO AdministrationGuide”, chapter Customer Topology Objects Management.

Free Fields are attributes that can be declared on any topology object presentin the NPO database. Refer to “NPO Administration Guide”, chapter ImportFree Fields.

For a network element you can assign a different network object class. Referto Create Network Object Class (Section 5.5.2.2).

To create sub-working zones from the selected topology objects, refer to CreateSub Working Zone from Topology Objects List (Section 9.3.3)

The list of topology objects icons is presented in Topology Icons (Section 28.2).

5.2 Topology Objects TabsBelow are details of the GSM object class tabs and their correspondingsub-tabs.

Cells

The Cells sub-tabs are:

All

BSS Release

BTS_D

Cell Class

Cell Freq. Band

Cell Type

GPU

LAC

OMC (represents an OMC-R)

RA

BSS

The BSS sub-tabs are:

All

BSS Release

MFS


Adjacencies

The Adjacencies sub-tabs are:

All

BSS Release

Band -> Band

Cell Class

Cell Type

To External

3BK 21216 AAAA PCZZA Ed.26 95 / 664

5 Topology Objects

LAC

LAC -> LAC


RA

Type -> Type

Adjacencies 2G to 3G

The Adjacencies 2G to 3G sub-tabs are:

All

BSS Release

Band -> Band

Cell Class

Cell Type

To External

LAC

LAC -> LAC


RA

Type -> Type

Traffic Zones

The Traffic Zones sub-tabs are:

All Traffic Zones

BSS Release

Cell Class

Cell Freq. Band

Cell Type

GPU

LAC


RA.

TRX

The TRX sub-tabs are:

All TRX

BSS Release

Cell Class

Cell Type

LAC


RA.

96 / 664 3BK 21216 AAAA PCZZA Ed.26

5 Topology Objects

TRX TS

The TRX TS sub-tabs are:

All TRX

BSS Release

Cell Class

Cell Type

LAC


RA.

BTS

The BTS sub-tabs are:

All

BSS Release

GPU

MFS


X25

The X25 sub-tabs are:

All

BSS Release

MFS


BTS_BSC_LAPD

The BTS_BSC_LAPD sub-tabs are:

All

BSS Release

MFS


BTS_MFS_LAPD

The BTS_MFS_LAPD sub-tabs are:

All

BSS Release

MFS


N7SL

The N7SL sub-tabs are:

All

3BK 21216 AAAA PCZZA Ed.26 97 / 664

5 Topology Objects

BSS Release

MFS


N7LS

The N7SL sub-tabs are:

All

BSS Release

MFS


AIC

The AIC sub-tabs are:

All

BSS Release

MFS


GPU

The GPU sub-tabs are:

All

BSS Release

MFS


PVC

The PVC sub-tabs are:

All

MFS


Bearer Channel

The Bearer Channel sub-tabs are:

All

MFS


Cell ZonesThe only Cell Zones sub-tab is: SubObjectZones.

TRX ZonesThe only TRX Zones sub-tab is: SubObjectZones.

Generic Zones

The Generic Zones sub-tabs are:

98 / 664 3BK 21216 AAAA PCZZA Ed.26

5 Topology Objects

SubObjectZones

Family/Sub Family.

GSM 2G External CellsThe only GSM 2G External Cells sub-tab is: All.

GSM 3G External CellsThe only GSM 3G External Cells sub-tab is: All.

Below are details of the W-CDMA object class tabs and their correspondingsub-tabs.

Object Zone

Object Zone sub-tabs are:

Family/SubFamily

SubObjectZones

RNCThe only RNC sub-tab is: All.

TMU

TMU sub-tabs are:

All

Topology

IuR

IuR sub-tabs are:

All

Source_RNC

Target_RNC

IuB

IuB sub-tabs are:

All

Topology

Cell 3G

Cell 3G sub-tabs are:

All

Topology

LAC_RAC

DlFreq

Cell Zone

Cell Zone sub-tabs are:

Family/SubFamily

SubObjectZones

3BK 21216 AAAA PCZZA Ed.26 99 / 664

5 Topology Objects

3G ADJ

3G ADJ sub-tabs are:

All

Cell_Source

Cell_Target

frequencyClassification

LAC_RACClassification

PLMNClassification

2G ADJ

2G ADJ sub-tabs are:

All

Cell_Source

3G Ext CellThe only 3G Ext Cell sub-tab is: All.

2G Ext CellThe only 2G Ext Cell sub-tab is: All.

NodeB

NodeB sub-tabs are:

All

Topology

HSDPA

HSDPA sub-tabs are:

All

Topology

Cell Group

Cell Group sub-tabs are:

All

Topology

Board

Board sub-tabs are:

All

Topology

PC

PC sub-tabs are:

All

Topology

100 / 664 3BK 21216 AAAA PCZZA Ed.26

5 Topology Objects

DDMPA

DDMPA sub-tabs are:

All

Topology

PA

PA sub-tabs are:

All

Topology

PCM

PCM sub-tabs are:

All

Topology

IMA Group

IMA Group sub-tabs are:

All

Topology

NodeB Vcc

NodeB Vcc sub-tabs are:

All

Topology

Aal1

Aal1 sub-tabs are:

All

Topology

Aal12

Aal2 sub-tabs are:

All

Topology

Aal5

Aal5 sub-tabs are:

All

Topology

IP Itf

IP Itf sub-tabs are:

All

Topology

3BK 21216 AAAA PCZZA Ed.26 101 / 664

5 Topology Objects

ATM NodeThe only ATM Node sub-tab is: All.

ATM Port

ATM Port sub-tabs are:

All

Topology

Vpc

Vpc sub-tabs are:

All

Topology

Vcc

Vcc sub-tabs are:

All

Topology

LP

LP sub-tabs are:

All

Topology

AP

AP sub-tabs are:

All

Topology

µNodeB

µNodeB sub-tabs are:

All

Topology

CCP

CCP sub-tabs are:

All

Topology

ITFB

ITFB sub-tabs are:

All

Topology

Control Port

Control Port sub-tabs are:

102 / 664 3BK 21216 AAAA PCZZA Ed.26

5 Topology Objects

All

Topology

Sector

Sector sub-tabs are:

All

Topology

UserDataPort

UserDataPort sub-tabs are:

All

Topology

3BK 21216 AAAA PCZZA Ed.26 103 / 664

5 Topology Objects

5.3 Display Topology Object PropertiesSee Display and Edit Properties (Section 3.3).

Figure 7: Example of BSC Properties

ParameterName

Description Mandatory Read-Only

Object ID The Muse ID of the object or the ID of the relation

For relations, MUSE ID is the concatenation of the MUSE ID ofthe source and the MUSE ID of the target.

Yes Yes

Object Type The type of the displayed object or relation (2G Cell, RNC,Network for example)

Yes Yes

External IDDescription

The External ID Label of the object or relation Yes Yes

External ID External ID value of the object or relation Yes Yes

104 / 664 3BK 21216 AAAA PCZZA Ed.26

5 Topology Objects

ParameterName


Parent ID A link to the parent object. The link opens the parent propertieswindow.

Yes Yes

Parent Type Type and friendly name of the parent object. Yes Yes

Friendly Name Friendly name of the object or relation. Yes Yes

Discovery Date Date and time at which the object has been created in MUSE Yes Yes

Children Types A list of links that displays available children types. Each linkopens the properties page of the selected child.

No Yes

OutgoingRelation Types

A list of links that displays available Outgoing relation types.The link displays a page that shows the list of related objects.

No Yes

IncomingRelation Types

A list of links that displays available Incoming relation types.The link displays a page that shows the list of related objects.

No Yes

3BK 21216 AAAA PCZZA Ed.26 105 / 664

5 Topology Objects

Figure 8: Example of Cell 2G Properties

106 / 664 3BK 21216 AAAA PCZZA Ed.26

5 Topology Objects

Additional parameters are added for the cells properties pages, as presentedin the tables below:

Parameter Name Description Mandatory Read-Only

Frequencies & TRXmapping

Link to Frequency and TRX mapping for the selectedcell. This lists all the TRX under the cell with theircorresponding frequency values.

Yes, ifCell2Ghas TRX

Yes

With Hopping Configuration

Number Of TRX(Operational)

Value obtained from the radio parameter Number_Of_TRX. Yes Yes

Number OfTRX(Planned)

Value obtained from the radio parameter Number_Of_TRXfrom RNP.

Yes Yes

Number Of TCH Value obtained from the radio parameter Number_Of_TCH. Yes Yes

Number Of SDCCH Value obtained from the radio parameterNumber_Of_SDCCH.

Yes Yes

Combined BCCH Value obtained from the radio parameter Combined_BCCH. Yes Yes

Configuration For each time slot n, n = from 0 to 7.

Value of the radio parameter TRX.channelConfTSn

Yes Yes

Frequency Frequency for TRX #n is computed asFrequencies[TRX.frequencyIndex_n]

It can contain multiple values that are displayed commaseparated.

Yes Yes

FHS Id For each time slot n, n = from 0 to 7.

Value of the radio parameter TRX.fhsTSn_

Yes Yes

HSN For each time slot n, n = from 0 to 7.

Value of the radio parameter computed for FHS objectgiven by TRX.fhsTSn_, get FHS.HSN_

Yes Yes

MAIO For each time slot n, n = from 0 to 7.

Value of the radio parameter TRX.maioTSn

Yes Yes

Without Hopping Configuration

Number Of TRX(Operational)

Value obtained from the radio parameter Number_Of_TRX. Yes Yes

Number OfTRX(Planned)

Value obtained from the radio parameter Number_Of_TRXfrom RNP

Yes Yes

Number Of TCH Value obtained from the radio parameter Number_Of_TCH Yes Yes

Number Of SDCCH Value obtained from the radio parameterNumber_Of_SDCCH

Yes Yes

3BK 21216 AAAA PCZZA Ed.26 107 / 664

5 Topology Objects


Combined BCCH Value obtained from the radio parameter Combined_BCCH Yes Yes

Configuration For each time slot n, n = from 0 to 7.

Value of the radio parameter TRX.channelConfTSn

Yes Yes

Frequency Computed: get Frequencies[ TRX.frequencyIndex_n] Yes Yes

Table 2: Cell2G Object Properties – Frequencies & TRX Mapping


Neighborhood Link to display the neighboring cells of the selectedCell2G object.

Yes Yes

Operational Name Operational name of the neighboring cell Yes Yes

Planned Name Planned name of the neighboring cell Yes Yes

Operational Serving Operational serving = O, if the cell from the current row isoperational serving for the current cell; nothing otherwise.

Yes Yes

Planned Serving Planned serving = P, if the cell from the current row isplanned serving for the current cell; nothing otherwise.

Yes Yes

Operational Target Operational target = O, if the cell from the current row isoperational target for the current cell; nothing otherwise

Yes Yes

Planned Target Planned target = P, if the cell from the current row isplanned target for the current cell; nothing otherwise.

Yes Yes

Table 3: Cell2G Object Properties – Neighborhood


OMC External View Link to display how the selected Cell2G is seen by theOMC-Rs where it is declared as "external cell".

Displayed parameters contain values that come fromthese OMC-Rs on this external cell.

Yes Yes

OMC -R OMC-R where the selected cell is seen as external Valueof the radio parameter

Yes Yes

LAC LAC Value of the radio parameter OMCExternalCell . Yes Yes

BCCH BCCHFrequency_ Value of the radio parameter Yes Yes

BCC OMCExternalCell .BCC_ Value of the radio parameter Yes Yes

NCC OMCExternalCell .NCC_ Value of the radio parameter Yes Yes

108 / 664 3BK 21216 AAAA PCZZA Ed.26

5 Topology Objects


Cell Type CELLTYPE Value of the radio parameter Yes Yes

Frequency Range OMCExternalCell .frequencyRange_ Yes Yes

Cell_Reselect_Offset Value of the radio parameter CELL_RESELECT_OFFSET

Yes Yes

EN_BI_BAND_MS Value of the radio parameter EN_BI_BAND_MS(n) Yes Yes

EN_OUTGOING_GPRS_REDIR

Value of the radio parameter EN_OUTGOING_GPRS_REDIR

Yes Yes

EN_SOLSA Value of the radio parameter EN_SOLSA Yes Yes

FREELEVEL_DR Value of the radio parameter FREELEVEL_DR Yes Yes

GPRS_HCS_THR Value of the radio parameter GPRS_HCS_THR Yes Yes

GPRS_MS_TXPWR_MAX_CCH_1800

Value of the radio parameter GPRS_MS_ TXPWR_MAX_CCH_1800

Yes Yes

GPRS_MS_TXPWR_MAX_CCH_900

Value of the radio parameter GPRS_MS_ TXPWR_MAX_CCH_900

Yes Yes

GPRS_PENALTY_ TIME(n)

Value of the radio parameter GPRS_PENALTY_ TIME(n) Yes Yes

GPRS_PRIORITY_CLASSValue of the radio parameter GPRS_PRIORITY_ CLASS Yes Yes

GPRS_RESELECTTION_OFFSET (n)

Value of the Radio parameter GPRS_RESELECTION_OFFSET(n)

Yes Yes

GPRS_RXLEV_ACESS_MIN

Value of the radio parameter GPRS_RXLEV_ACCESS_MIN

Yes Yes

GPRS_TEMPORARY_OFFSET (n)

Value of the radio parameter GPRS_TEMPORARY_OFFSET(n)

Yes Yes

L_RXL_DR Value of the radio parameter L_RXLEV_NCELL_ DR Yes Yes

MS_TXPWR_MAX_1800

Value of the radio parameter MS_TXPWR_ MAX_1800 Yes Yes

MS_TXPWR_ MAX_900 Value of the radio parameter MS_TXPWR_ MAX_900 Yes Yes

MS_TXPWR_MAX_CCH_1800

Value of the radio parameter MS_TXPWR_MAX_CCH_1800

Yes Yes

MS_TXPWR_MAX_CCH_900

Value of the radio parameter MS_TXPWR_MAX_CCH_900

Yes Yes

NC_REPORTING_PERIOD_T

Value of the radio parameter NC_REPORTING_PERIOD_T

Yes Yes

3BK 21216 AAAA PCZZA Ed.26 109 / 664

5 Topology Objects


NETWORK_CONTROL_ORDER

Value of the radio parameter NETWORK_CONTROL_ORDER

Yes Yes

PENALTY_TIME Value of the radio parameter PENALTY_TIME Yes Yes

RX_LEV_ ACCESS_MIN Value of the radio parameter RX_LEV_ ACCESS_MIN Yes Yes

RX_LEV_MIN Value of the radio parameter RX_LEV_MIN Yes Yes

Table 4: Cell2G Object Properties – OMC External View

Note: The list of OMC External View Parameters can be configured and is obtainedfrom the file file ExternalOmcCell.csv

Figure 9: Example of Network Properties

110 / 664 3BK 21216 AAAA PCZZA Ed.26

5 Topology Objects

5.4 Add Associated Network ObjectsAssociated network objects like reverse adjacencies and neighboring cells canbe added to the topology.

1. While being in the ’Adjacency’ mode, select the necessary adjacencies,right click and select Add Reverse Adjacencies , or select from the menubar Topology -> Add Reverse Adjacencies .

The resulting reverse adjacencies are added to the selection (soft-deletedadjacencies must not be considered when retrieving the list of adjacencies).The tree can be expanded, but it is not scrolled.

2. While being in the ’Cell’ mode, select the necessary cells, then right clickand select as appropriate:

Add Target Cells , or select from the menu bar Topology -> AddTarget Cells .The target cells of the previously selected cells are added to the selection.

Add Serving Cells , or select from the menu bar Topology -> AddServing Cells .The serving cells of the previously selected cells are added to theselection.

Add Neighboring Cells , or select from the menu bar Topology ->Add Neighboring Cells .Both target and serving cells of the previously selected cells are addedto the selection.

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

3BK 21216 AAAA PCZZA Ed.26 111 / 664

5 Topology Objects

5.5 Network Object Class

For B10 GSM, only Cell Class is available.

5.5.1 Presentation

5.5.1.1 DefinitionCell Class is a parameter that describes the geographic environment andpredicted traffic of cells.

A cell class is associated to each cell through the RNP interface.

It is used by NPO as:

Filtering criteria for logical parameter reference values and rules

Optimization method of the network.

A new tab is added in the Topology Classification panel: Cell Class.

112 / 664 3BK 21216 AAAA PCZZA Ed.26

5 Topology Objects

5.5.1.2 ClassificationNPO manages two different cell classes:

Planned Cell Class - this value comes from RNP

Operational Cell Class - this value is either chosen in NPO or comes from

the OMC-R (when Cell Class is supported in the OMC-R, i.e in W-CDMA).

Besides the two values (planned and operational), NPO manages an additionalflag allowing to remember if the Operational Cell Class has been set to thePlanned value or not.

Alcatel-Lucent provides the following predefined and non-modifiable set of cellclasses, known as system cell classes :

Rural

Suburban

Urban

Dense urban

Indoor.

System cell classes cannot be viewed, modified, or deleted using the NetworkObject Class Editor.

In order to fit with their own optimisation methods, the optimizer may defineadditional customer cell classes .

3BK 21216 AAAA PCZZA Ed.26 113 / 664

5 Topology Objects

5.5.2 Network Object Class Editor

5.5.2.1 Open Network Object Class EditorTo open Network Object Class Editor, select a network object and performone of the following actions:

From the Menu Bar, select Topology -> Network Object Class... , OR

Right click and select Network Object Class... , OR

Press Ctrl+L .

The Network Object Class Editor opens.

The Network Object Class Tree contains the customer defined network objectclasses, classified on their system network object classes.

The Network Object Class Properties Panel is used to display and edit theproperties of the selected network object class.

114 / 664 3BK 21216 AAAA PCZZA Ed.26

5 Topology Objects

5.5.2.2 Create Network Object ClassTo create a Network Object Class:

1. Select the appropriate network object and Open Network Object ClassEditor.

2. Click on

3. Fill in the following fields:

Field Name Description

Name Name of the network object class.

Default value: <NetworkObject_Class>_<owner>_n

where<owner> is the owner of the network object class, and n is an incrementalnumber to define a unique name.

Description Operator description for network objects class.

Mode List of applicable modes.

Typical modes for 2G are: BSC, Cell, Adjacency, TRX, Traffic Zone.

Typical modes for 3G are: RNC, Cell, Adjacency.

System Class List of System defined network object classes for the object type for whom customernetwork object class is being created.

By default, this is set to the first value in the list.

4. Click on .

Click on [ Yes ] at the confirmation message: Are you sure you want to

create Network Object Class <NetworkObjectClassName>?

When maximum number of network object classes are reached the operatoris notified about it. The maximum number is a configurable value for eachobject type and by default it is set to 64.

5.5.2.3 Edit Network Object ClassTo edit a Network Object Class:

1. Select the appropriate network object and Open Network Object ClassEditor.

2. Click on ..

The Network Object Class Properties Panel is displayed in editable mode.The network object class name is grayed and non-editable.

3. Edit the needed values as appropriate.

4. Click on .

The updates are performed.

3BK 21216 AAAA PCZZA Ed.26 115 / 664

5 Topology Objects

5.5.2.4 Delete Network Object Class1. Select the appropriate network object and Open Network Object Class

Editor.

2. Click on .

3. Click on [ Yes ] at the confirmation message: Are you sure you want to

delete Network Object Class <NetworkObjectClassName>?

The selected network object class is deleted.

If the deleted network object class was used in a Rule, Diagnosis, WorkingZone, THL, or any Reference Value definition, or was associated to anetwork object, then the deletion is rejected and an error message is shown.

Note: Multiple network object classes can be selected for removal.

5.5.3 Assign Operational Network Object Class

Note: The MUSE_NPO_ASSIGN_CELL_CLASS FAD must be installed for the ClassAssignment option to be enabled.

To Assign Operational Network Object Class:

1. Select the appropriate cell(s), then:

Right click and select Network Object Class Assignment , OR

Select Topology -> Network Object Class Assignment from the

menu bar.

A list of the current system and customer Network Object Class is displayedin alphabetical order. If the selected network object(s) is a planned object(s)(coming from RNP), then the list contains an additional option: [planned].

If multiple network objects are selected and they are all currently assignedthe same network object class, this appears as checked in the list. Thesame holds true for a single network object.

If multiple network objects are selected and they have different networkobject classes, no network object class appears as checked.

In case of [planned] network object class, this does not appear as checkedin the sub-list, but its planned value does (e.g ”INDOOR”).

2. Select the appropriate network object class to assign.

Click on [ Yes ] at the confirmation message: Are you

sure you want to change the Network Object Class to

<New_Network_Object_Class>?

116 / 664 3BK 21216 AAAA PCZZA Ed.26

5 Topology Objects

The new network object class is assigned. At the next preview of thesub-menu of network object classes, it will appear as checked.

Note: If [planned] network object class is selected for a certain cell, with the

“INDOOR” value for example, AND

An RNP project is imported that has for the same cell a different cell class,

“URBAN” for example

then the cell is allocated with the newly imported network object class,“URBAN” for this example.

Note: If a system or customer network object class is selected for a certain cell,

with the “INDOOR” value for example, AND

An RNP project is imported that has for the same cell a different cell class,“URBAN” for example

then the cell is allocated with the initial network object class, “INDOOR” forthis example.

3BK 21216 AAAA PCZZA Ed.26 117 / 664

5 Topology Objects

118 / 664 3BK 21216 AAAA PCZZA Ed.26

6 Object Zone

6 Object Zone

This section describes how to manipulate objects as a group with objects zones.

3BK 21216 AAAA PCZZA Ed.26 119 / 664

6 Object Zone

6.1 Presentation

Note: The MUSE_OBJECT_ZONE_LICENSE must be installed for the Object ZoneEditor to be displayed.

6.1.1 Definitions

An object zone describes a set of network objects of the same type, filtered bya set of filters. The operator can define, for example, an Object Zone containingall cells having a call-drop of 3% or more.

The filters are dynamically applied to the current Working Zone, in order toobtain the list of objects contained in the zone. This list of objects is thereforedynamic and depends on the opened Working Zone.

The operation to apply filters defined in an object zone to the current WorkingZone is called ’computation of the object zone ’. Object Zones can becomputed only when needed (i.e. when used), on user demand, or duringAnalysis Desktop initialization (auto-compute property). When an object zoneis computed (whatever the reason for this computation), its name is updated todisplay the number of objects contained in the zone (in parenthesis after theobject zone name).

An object type is associated with object zones to indicate which type of objectsis the result of its computation. For example, an object zone containing cells iscalled a Cell Zone. A 2G Cell Zone is an ObjectZone(2G Cell).

If an object zone contains as a filter another object zone, it is called asub-object zone . Whenever the parent object zone criteria are changed, thechanges are also inherited by the sub-object zone (i.e. criteria are not copied inthe sub-object zone, but a reference to the parent object zone is kept).

If an object zone contains as a filter criteria a Working Zone, it does not becomea sub-object zone and the Working Zone criteria is not copied (a reference tothe Working Zone is kept).

An object zone can be manipulated as a standard network object. It can beused, for example, as the topology dimension of an execute view or executereport operation.

Depending on the installed technology plug, some modes can be Zone Modescontaining only Object Zones of a certain type (in GSM, for example, CellZone, Traffic Zone and TRX Zone are dedicated modes). A generic ObjectZone mode can also be used and, in that case, it can contain Object Zones ofdifferent types.

120 / 664 3BK 21216 AAAA PCZZA Ed.26

6 Object Zone

For the Traffic Zone mode, NPO generates one Object Zone (of TRX type)for each Traffic Zone of each cell. The Traffic Zone mode displays thesezones as described below:

Example:

6.1.2 Filtering

A list of pre-defined topology filters is associated to each mode. All filters of amode can be applied on any Topology Classification of the concerned mode.

Filters can be used to restrict the list of displayed objects using additionalcriteria such as ’only GPRS’, ’only B9’ for example.

The operator can apply a filter on any available Topology Classification ofthe mode.

The criteria defined in the filter are then applied to the chosen classification

and this one is updated displaying only the filtered objects.

If a filtered non-leaf object has no child, it is also hidden.

The ’No Filter’ option can be used to remove any filter applied to a

classification.

Applying a filter on a Topology Classification doesn’t change the otherTopology Classifications.

Whenever some objects are dropped on a filtered classification, if some ofthe dropped objects are not visible due to the applied filter, then the user isinformed and proposed to remove the filter or to ignore the non visible objects.

3BK 21216 AAAA PCZZA Ed.26 121 / 664

6 Object Zone

The following criteria may be used to filter a set of objects:

QoS criteria, to filter for example objects with a bad Call Drop or a low

Call Success

Parameter (Logical and Design) criteria, to filter for example objects of aparticular frequency band or class

Topological criteria, to filter for example cells of a particular BSS

Explicit designation, to focus for example on specific cells of high interest

Free field criteria, to filter for example cells according to free fields.

For each type of criteria defined above, a Reference Period and a ReferenceDate must be chosen to define how to apply the criteria.

The following comparison operators may be used as filtering criteria:

>

>=

<

<=

=

!=

contains

doesn’t contain

like (foe is like ’f*’ but not like ’f*e*o’)

MUSE specific comparison operators such as ’IsGreen()’

User-defined comparison operators

Criteria can also be combined in a filter using the following operators:

AND

OR

Not

Parenthesis

Mathematical operations can be included in the filtering formula:

+

-

*

/

% (Modulo)

Example: to filter cells for which: I:(Call_Drop_Radio / Call_Drop_BSS

> 2) .

122 / 664 3BK 21216 AAAA PCZZA Ed.26

6 Object Zone

When defining a filter for objects of type A, it is possible to use criteria of objectsof type B if there is a topological relation between A and B.

It is then possible to filter all cells of a particular BSC or all cells having aparticular type of Traffic Zone. When using descending topology links, theresult can be more than one (i.e. one object has only one father but can havemany children). In this case, a particular topology operator must be used:’at_least_one_child’ or ’all_children’.

Examples :

Cell filter to have only cells with a call_drop (fictional indicator name) higher

than 3%:I:(Call_Drop > 3) , where I stands for Indicator.

Cell filter to have only cells of BSC1:filter on BSC and then: T:(OFN = ’BSC1’) , where T stands for topologyattributes.

Cell filter to have only cells having only GSM 1800 Traffic Zones:Filter on Traffic Zone with "All Children" selected and thenP:(InternalCell.frequencyRange__TZ = ’GSM1800’) , where P standsfor Parameter.

Define a filter criteria using contains and doesn’t contain operators:P:(azimuthAntennaAngle>5) AND P:(cellClass CONTAINS

*{*’URBAN’*}*)

P:(azimuthAntennaAngle>5) AND P:(cellClass DOES_NOT_CONTAIN

*{*’URBAN’*}*)

6.1.3 QoS for Object Zone

The object zone may be dragged & dropped on the viewer, in this case theobject zone behaves as a single object.

Spatial aggregation is used to calculate the indicator value over the object zone(refer to Aggregation (Section 10.1.7.2)).

6.1.4 Compute Object Zone

To trigger the computation of an Object Zone select an object zone in theobject zone tree, then:

Right click and select Compute Object Zone , OR

Select from the menu Topology -> Compute Object Zone .

Analysis Desktop computes the object zone and the object zone tree isupdated to indicate the number of objects contained in the zone in parenthesisafter its name.

Note: Object zones that are auto computed can be re-computed in the samemanner as described above. Computation of an object zone also takes intoconsideration the soft deleted network objects.

3BK 21216 AAAA PCZZA Ed.26 123 / 664

6 Object Zone

6.2 Display Object Zone PropertiesSee Display and Edit Properties (Section 3.3).

ParameterName


Name Name of the Object Zone Yes Yes

Owner Creator of the Object Zone Yes Yes

Created Date when the object zone was created Yes Yes

Modified Date when the object zone was last updated Yes Yes

System Yes, if the object zone is a System Object Zone

No, otherwise.

Yes Yes

Access rights Public or Private Yes Yes

124 / 664 3BK 21216 AAAA PCZZA Ed.26

6 Object Zone

ParameterName


Visible Yes, if this object zone is visible to operators.

No, if this object zone is not visible to operators other than theAdministrator.

Yes Yes

Auto-Compute Yes if the Object Zone must be automatically computed when auser session is opened

Yes Yes

Description Operator description for the object zone Yes Yes

Object Type Type of objects contained in the Object Zone. Yes Yes

Families Table of associated family and sub families of the counter.

Family - The family to which this object zone belongs.

Sub-Family Depth 1 - The sub-family to which this object

zone belongs

Sub-Family Depth 2 - The sub-sub-family to which this objectzone belongs

Sub-Family Depth 3 - The sub-sub-sub-family to which this

object zone belongs

Sub-Family Depth 4 - The sub-sub-sub-sub-family to which

this object zone belongs

Yes forFamily

No forsub-families

Yes

Object ZoneFilter Tree

A TAB spaced tree that describes the filter that is applied tocreate the object Zone. Each node of the tree contains thefilter details i.e. for Filters the Filter Name, Formula, ReferencePeriod, Absolute Flag and Reference Date. For Working Zonesand Object Zones the node contains the zone names. Eachnode may contain topology or function objects, such objects areshown as hyperlinks so that clicking on the link the user cansee the objects details.

Yes Yes

The following properties apply for the Object Properties window :

ParameterName


Dialog Box ”<Object name> Properties” a title specifying the object forwhich the properties are displayed

Yes N/A

Title BarButtons

Buttons appearing in upper-right-hand corner of title bar Yes N/A

Resizable Able to resize the dialog box Yes N/A

PropertiesPanel

Properties panel where the properties are displayed Yes Yes

3BK 21216 AAAA PCZZA Ed.26 125 / 664

6 Object Zone

ParameterName


Previous Page Displays the previously displayed object’s Properties. Yes Yes

Next Page Displays the previously displayed object’s Properties displayedbefore pressing Back button

Yes Yes

Snapshot Launches a snap shot window which is exact copy of theproperties window with out any buttons

Yes Yes

Previous Object Displays the properties of the previous object to the currentselected object in tree. A tool tip is displayed when mouse isover this icon.

Yes Yes

Next Object Displays the properties of the Next object to the current selectedobject in tree. A tool tip is displayed when mouse is over thisicon.

Yes Yes

Close (defaultselected button)

Closes the properties window Yes Yes

Edit Opens the object editor for the object. Yes No

The following Object Properties Window Characteristics apply:

Parameter Name Description

Always on top The window is always on Top and cannot be minimized.

Modal The modal windows block the other GUI components until the window is closed.

Multi instance Multiple instances of same window can be opened.

126 / 664 3BK 21216 AAAA PCZZA Ed.26

6 Object Zone

6.3 Object Zone Editor

6.3.1 Open Object Zone Editor

Open the Object Zone Editor:

In the Alcatel-Lucent Analysis Desktop window, click on the icon, OR

In the Analysis Desktop main window, select Topology -> Object Zone... ,

OR

Press Ctrl+B.

The ’Object Zone Editor’ window opens.

3BK 21216 AAAA PCZZA Ed.26 127 / 664

6 Object Zone

6.3.2 Object Zone Operations Toolbar

The following toolbar icons are available for the object zone operations:

The following table gives a brief description of the object zone operationstoolbar icons:

Icon Description

Add Union

Add Intersection

Add Exclusion

Remove Operation

Clear Criteria

Status

6.3.3 Create Object Zone

When creating Object Zones, use only operational values for parameters.

To create an Object Zone:

1. In the ’Object Zone Editor’ window, click on .

The ’Object Zone Editor’ appears with default values and editable fields.

2. Fill in the appropriate fields, as described in the following table.

Field Name Description Default Value

Name Name of the Object Zone to be created. ObjectZone_<owner>_n

where<owner> is theowner of the objectzone, and “n” isincremented to finda unique name (n canbe 1, 2, 3...)

Owner User who is creating the Object Zone.

This field is read-only.

The usernameyou logged in theapplication

128 / 664 3BK 21216 AAAA PCZZA Ed.26

6 Object Zone


Created Date when the Object Zone was created.


Modified Date when the Object Zone was last modified, in case of anObject Zone update.


AccessRights

Access rights for Public or Private. Private

Object Type Type of objects contained in the Object Zone.

A list of types is possible.

First object type of thecurrent technology

Visible Yes, if this Object Zone is visible to operators.

No, if this Object Zone is not visible to operators other than theAdministrator.

True

Auto-Compute True if the Object Zone must automatically be computed when auser session is opened.

False, otherwise.

False

System True if the object zone is a System Object Zone – thus it cannot bemodified or deleted except for certain fields (Family, Subfamilies)only by the Administrator.

False, otherwise.

Description Text box to be filled in with operator description for the currentobject zone.

Family The family to which this object zone belongs.

Sub-FamilyDepth

The sub-family to which this object zone belongs.

Sub-Sub-Family Depth

The sub-sub-family to which this object zone belongs.

Sub-Sub-Sub-FamilyDepth

The sub-sub-sub-family to which this object zone belongs.

Sub-Sub-Sub-Sub-FamilyDepth

The sub-sub-sub-sub-family to which this object zone belongs.

Object ZoneFilter Tree

Tree composed of FilterTreeNodes describing the filter formula.

3BK 21216 AAAA PCZZA Ed.26 129 / 664

6 Object Zone

3. In the ’Families’ panel, type the family to which this object zone belongs.

In the ’Sub-Family Depth’, type the sub-family to which this object zonebelongs.

4. In the Object Zone Filter Tree, the following options apply:

Filter

The trees available under the Filter tab are:

QoS indicator

Design Parameter (design primitives included)

Logical Parameter

Topology Parameter

Free Field Parameter.

Object ZoneThe trees available under the Object Zones tab are the Object Zones.

Working ZoneThe trees available under the Working Zones tab are the Working Zones.

Check the appropriate option between Filter, Object Zone, or Working Zone.

Depending on your choice, add by a drag & drop operation from the rightpanel:

The appropriate filtering criteria - for Filter (Refer to Filtering Object

Zone (in section ).)

A referenced Object Zone - for Object Zone

A referenced Working Zone - for Working Zone.

The following operations apply: union, intersection, exclusion .

To delete an operation, select it and click on .

To delete a criteria for Filter, click on .

The allowed operators are: >, <, >=, <=, =, !=, contains, doesn’t contain,like. Operands can also contain mathematical operations (+, -, *, /, numericconstants).

Unitary NPO Specific Operators such as IsGreen can also be used.

The status of the object zone criteria is shown in the icon.

IconColor

Criteria

Green All the nodes are checked and are valid.

Orange One or more nodes is not checked.

Red One or more nodes has the Criteria is not valid status.

130 / 664 3BK 21216 AAAA PCZZA Ed.26

6 Object Zone

Filtering Object Zone For Filter, the following parameters apply:

Parameter Name Description Default Value

Topology Object toFilter

By default, the Filter is applied on the objects of the type ofthe Object Zone.

Filters are used to change the objects on which the filter areapplied. It is possible to apply the filter on upper or lowertopology levels compared to the Object Zone’s type.

When referring to lower topology level, the user must preciseif the filter is considered as true if ’all_children’ fulfill thecondition or if ’at_least_one’ child fulfills it.

Type of the ObjectZone

TopologyReference Period

Period that is used when taking into account a Topologycriteria while computing the filter (can be Daily, Weekly orMonthly).

Daily

TopologyReference Date

Date that is used when taking into account a Topology criteriawhile computing the object zone.

The available values depend on the chosen TopologyReference Period.

If the Topology Reference Period is Daily, Reference Datecan be:

yesterday

an explicit date (yesterday or earlier only)

a relative date (today – x, x being more than 1).

If Topology Reference Period is Weekly, Reference Date canbe:

last week

an explicit week (last week or earlier only)

a relative week (current week – x, x being more than 1).

If Topology Reference Period is Monthly, Reference Datecan be:

last month

an explicit month (last month or earlier only)

a relative month (current month – x, x being more than 1).

Yesterday ifReference Period

is Daily

Last Week ifReference Period

is Weekly

Last Month ifReference Period

is Monthly.

QoS ReferencePeriod

Period that is used when taking into account a QoS criteriawhile computing the filter (can be Daily, Weekly or Monthly).

Daily

3BK 21216 AAAA PCZZA Ed.26 131 / 664

6 Object Zone


QoS ReferenceDate

Date that is used when taking into account a QoS criteriawhile computing the object zone.

The available values depend on the chosen QoS ReferencePeriod.

If QoS Reference Period is Daily, Reference Date can be:

yesterday


a relative date (today – x, x being more than 1).

If QoS Reference Period is Weekly, Reference Date can be:

last week



If QoS Reference Period is Monthly, Reference Date can be:

last month



Yesterday if

Reference Periodis Daily


is Weekly


is Monthly.

ParameterReference Period

Period that is used when taking into account a Parametercriteria while computing the filter (can be Daily, Weekly orMonthly).

Daily

132 / 664 3BK 21216 AAAA PCZZA Ed.26

6 Object Zone


ParameterReference Date

Date that is used when taking into account a Parametercriteria while computing the object zone.

The available values depend on the chosen ParameterReference Period.

If Parameter Reference Period is Daily, Reference Date canbe:

yesterday


a relative date (today – x, x being more than 1)

If Parameter Reference Period is Weekly, Reference Datecan be:

last week



If Parameter Reference Period is Monthly, Reference Datecan be:

last month



Yesterday if

Reference Periodis Daily


is Weekly


is Monthly.

Filter Formula The filter formula can contain binary operators (And, Or),unitary operators (Not), parenthesis to define the order inwhich formula should be evaluated, and Criteria.

For more information refer to to Filtering (Section 6.1.2).

5. Click on .

6. The following confirmation popup window appears:Are you sure you want to create object zone

<object_zone_name>?.

Click on [ Yes ].

The Object Zone is created and the tree in the Object Zone mode isrefreshed.

3BK 21216 AAAA PCZZA Ed.26 133 / 664

6 Object Zone

6.3.4 Create Object Zone by Copy

To copy an object zone:

1. In the Object Zone Editor, click on .

The ’Properties’ panel appears with the default name and properties of theselected object zone. The value of the ’Access Rights’ field is ’Private’ bydefault, regardless of the value from the coppied object zone.

2. Perform all the necessary updates.

For the name of the copied object zone, use the following format:<oldname_Copy_n> .

Only operational values of parameters must be used inside object zones.

3. Click on [ Apply ].

4. In the confirmation window, click on [ OK ].

6.3.5 Create Object Zone Interactively

To create an object zone interactively:

1. Select the appropriate cells from the Topology Browser, right click andselect Create Object Zone... .

The ’Enter Object Zone Name’ window opens.

2. Type the appropriate name for the object zone, then click on [ OK ].

The new object zone is created.

6.3.6 Edit Object Zone

To edit an object zone:

1. In the Object Zone Editor, click on .

The ’Object Properties’ panel appears.

2. Edit the appropriate values.

The ’Name’ field is restricted.

Only operational values of parameters must be used inside object zones.


4. In the confirmation window, click on [ OK ].

6.3.7 Delete Object Zone

To delete an object zone:

1. In the Object Zone Editor, select the Object Zone(s) to be deleted.

134 / 664 3BK 21216 AAAA PCZZA Ed.26

6 Object Zone

2. Click on .

3. In the deletion confirmation window, click on [ OK ].

3BK 21216 AAAA PCZZA Ed.26 135 / 664

6 Object Zone

136 / 664 3BK 21216 AAAA PCZZA Ed.26

7 Topology Classifications


This section describes how to manipulate Network Objects within TopologyClassifications.

3BK 21216 AAAA PCZZA Ed.26 137 / 664


7.1 PresentationThe Topology Classification defines how Network Objects are classified in atree structure, depending on the selected mode.

Topology Classifications are specific to the used technology.

Topology Classifications can be:

System, as defined by Alcatel-Lucent

Customer, when defined by the user (see Create Topology Classification

(Section 7.3) or Create Topology Classification by Copy (Section 7.4)).

In the Topology Classification, the operator can update the:

User label of some network objects (mainly 2G Cell and 3G Cell objects)A network object label is defined as being the concatenation of a set ofattributes. Some of these attributes are defined (by the Administrator)for all users of MUSE; others are defined on a per-operator basis usinguser preferences.The choice of which user label to display in the Analysis Desktop (betweenthe Operational cell name retrieved from the OMC-R and the planned cellname retrieved from RNP) must be made by each operator.

Icons associated to network objects (mainly 2G Cell and 3G Cell objects)The list of icons to be displayed can be chosen for each object based on alist of attributes; for example, for 2G Cells, dedicated icons can showVendor or Frequency Band.

If parameters are not loaded for all topology objects there can be differentnumber of objects in topology classifications for a certain mode. Also, if one ofthe OMCs is undeclared, the same situation may appear (the objects of thatOMC will no longer be displayed in the OMC classification for example).The correct number of objects is displayed in the ’All’ classification of any mode.

See also:

Organize Topology Classification Trees (in section 2.4.1.2)

Hide Topology Classification (in section 2.4.1.2)

Refresh Tree (in section 2.4.1.2)

Apply Filter on Topology Classification (in section 2.4.1.2)

7.2 Open Topology Classification EditorOpen a topology classification editor:

In the Alcatel-Lucent Analysis Desktop window, click on Topology ->Topology Classification... , OR

Press Ctrl+T

The ’Topology Classification Editor’ window opens.

138 / 664 3BK 21216 AAAA PCZZA Ed.26


7.3 Create Topology ClassificationTo create a topology classification specifying how network objects are displayedin a topology tree:

1. In the ’Topology Classification Editor’ window, click on .

The ’Topology Classification Editor’ window opens.


FieldName

Description Default Value

Name Name of the topology classification to be created. Topology_<owner>_n

where<owner> is theowner of the topologyclassification.

Owner User who is creating the topology classification.


The usernameyou logged in theapplication.

Created Date of topology classification creation.


Modified Date of topology classification last update.


AccessRights

Access rights for Public or Private

If the new topology classification is set to ’Public’, the other usersare notified of its availability as soon as it is created.

Private.

Mode Mode for the newly created topology classification. The active Mode objecttype when the TopologyClassification Editorwas started.

System True, if this topology classification is a System one - thus it cannotbe modified or deleted except certain fields (Visible) only by theAdministrator.

Grayed, otherwise.

Description Text box to be filled in with operator description for the currenttopology classification.

3. In the ’Classification Definition’ panel, define the the list of classificationcriteria which give the levels to be displayed in the classification. For this,drag the needed object attributes and topology objects from the right panel,and drop them to the topology classification tree. The drop is based on:

relations and attributes of objects

relations of parent-child.

3BK 21216 AAAA PCZZA Ed.26 139 / 664


Dropping them on a node makes them parent of that node. If a drop is not

allowed, the cursor shows that . Validation occurs when dragging,therefore the example tree is immediately updated.

The maximum number of allowed levels in a topology classification is set bydefault to six.When defining the levels of the desired classifications, thefollowing rules must be respected:

The first level cannot be changed. It is always the Working Zone

All intermediate levels can be Topology Objects or Object Attributes

Leaves are always the Object Type of the mode for which the topology

classification is defined

Topology Objects or Object Attributes cannot be used twice in the same

Topology Classification (i.e. not possible to define RNC->Cell->RNC).

The resulted tree has collapsible and expandable nodes containing exampledata.

To remove a selected node, click on .

As for all classifications, non-leaves levels are displayed using a

(configurable) icon indicating if the branch is opened or not .

Also, for the dragged objects, the associated icons are displayed:

Topology, Logical, Design, Topology Parameters, FreeFields.

4. Click on .

5. The following confirmation popup window appears:Are you sure you want to create topology classification

<topology_classification_name>?.

Click on [ Yes ].

The new topology classification is created and displayed in the mode. Nofilter is associated to this new classification.

If the topology classification is public, other users are notified and theyhave to manually refresh the tree.

Note: The new topology classifications can be saved as an implicit User Preferencefor the Mode, as well as the new current active topology classification.

140 / 664 3BK 21216 AAAA PCZZA Ed.26


7.4 Create Topology Classification by CopyTo create a topology classification by copy:

1. In the ’Topology Classification Editor’ window, select from the left frame the

topology classification to copy, then click on .

2. The new topology classification is created with a default name:<oldname>_Copy_n , where n is an incremental number to define a uniquename.

Access rights are reset to the default values, but you can change them asneeded.

You can also modify the topology classification properties if needed.

The user becomes the owner of the topology classification.

3. Edit the appropriate fields, then click on .

4. The following confirmation popup window appears:Are you sure you want to create topology classification

<topology_classification_name>?.

Click on [ Yes ].

The new topology classification is created and displayed in the mode. Nofilter is associated to this new classification.

If the topology classification is public, other users are notified and theyhave to manually refresh the tree.

Note: The new topology classification can be saved as an implicit User Preference forthe Mode, as well as the new current active topology classification.

3BK 21216 AAAA PCZZA Ed.26 141 / 664


7.5 Edit Topology ClassificationTo edit a topology classification:

1. Open the topology classification you want to modify.

2. In the ’Topology Classification Editor’ window, click on .

The Topology Classification Properties Panel interface is displayed with thecurrent attribute values.

3. Edit the appropriate editable fields.

Only the owner of the topology classification or the Administrator canupdate its values.

The operator is not allowed to modify the owner of the topology classification.

If the owner of the topology classification is not the one viewing it, the[ Edit ] button is grayed.

4. To save the changes, click on .

The topology classification is updated. If it is not hidden, the associatedtopology tree is refreshed with its previous associated filter, if any.

Click on [ Close ] to close the ’Topology Classification Editor’ window.

142 / 664 3BK 21216 AAAA PCZZA Ed.26


7.6 Apply Filter on Topology ClassificationThe operator can choose one of the available filters associated to a mode andapply 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 currentactive filter. The first item is labeled ’No Filter’ and is used to remove anyfilter on the classification.

2. Select the appropriate pre-defined filter.

The topology tree is refreshed according to the filtered classification.

3BK 21216 AAAA PCZZA Ed.26 143 / 664


7.7 Delete Topology ClassificationTo delete a topology classification, select it, then:

From the "Topology Classification Editor" window, click on , OR

Select Edit -> Delete from the toolbar, OR

Press [ Delete ] button from the keyboard.

The following question appears: Are you sure you want to delete

topology classification <topology_classification_name>?

If only one topology classification is selected to be deleted, click on [ Yes ]

If multiple topology classifications are selected to be deleted, click on

[ Yes to All ].

The topology classification/s is / are deleted from the mode.

If the deleted topology classification is public, other users are notified about thedeletion and they must manually refresh their mode.

144 / 664 3BK 21216 AAAA PCZZA Ed.26

8 Function Classifications


This section describes how to manipulate functions within the FunctionClassifications.

3BK 21216 AAAA PCZZA Ed.26 145 / 664


8.1 PresentationThe Function Classification defines how functions are classified in a treestructure. It is not dependant on the used technology.

Function Classifications can be:

System, as defined by Alcatel-Lucent

Customer, when defined by the user (see Create Function Classification

(Section 8.3) or Create Function Classification by Copy (Section 8.4)).

In Analysis Desktop, the Function Classification Trees display only:

public and owned private objects

visible objects

The Administrator can see though all private objects. They can also visualizethe non-visible objects, but using a particular graphical style and only in theObject Editors trees (not in Analysis Desktop main function trees).

Organize Function Trees (in section 2.4.1.3)

Hide Tree (in section 2.4.1.3)

Refresh Tree (in section 2.4.1.3)

Select a Function Classification (in section 2.4.1.3)

8.2 Open Function Classification EditorTo open a function classification editor:

In the Alcatel-Lucent Analysis Desktop window, click on Data -> FunctionClassification... , OR

Right click on a function tab and select Function Classification... , OR

Press Ctrl+U

The ’Function Classification Editor’ window opens.

146 / 664 3BK 21216 AAAA PCZZA Ed.26


8.3 Create Function ClassificationTo create a function classification specifying how network objects are displayedin a function tree:

1. In the ’Function Classification Editor’ window, click on .


FieldName


Name Name of the function classification to be created. Function_<owner>_n

where<owner> is theowner of the functionclassification.

Owner User who is creating the function classification.



Created Date of function classification creation.


Modified Date of function classification last update.


AccessRights


If the new function classification is set to ’Public’, the other usersare notified of its availability as soon as it is created.

Private.

Mode Mode for the newly created function classification. The active Mode objecttype when the FunctionClassification Editorwas started.

FunctionType

Drop down list containing all available function types (i.e. allavailable for selected standard including the non-visible ones)except Tuning, Event, Free Fields.The leaf node for the functionclassification are of this type.

Current active functiontype on functionbrowser.

Visible Checked, if this function classification is visible to operators.

Unchecked, if this function classification is not visible to operatorsother than the Administrator.

Checked.

System True, if this function classification is a System one - thus it cannotbe modified or deleted except certain fields (Visible) only by theAdministrator.

Grayed, otherwise.

Description Text box to be filled in with operator description for the currentfunction classification.

3BK 21216 AAAA PCZZA Ed.26 147 / 664


3. In the ’Classification Definition’ panel, define the the list of classificationcriteria which give the levels to be displayed in the classification. For this,drag the needed functions from the right panel, and drop them to thefunction classification tree.

Function attributes cannot be used twice in the same function classification.

Note: If the “Family” attribute is chosen to classify the functions, then it must be at thelowest level of the classification definition. “Family” attribute cannot be droppedbetween other function attributes.

In case a function classification tree contains the “Family” attribute, the functionclassification editor displays all the levels of family and sub-family.

The following function types cannot be created or modified in the functionclassification editor: Tuning, Event, Free Fields.

Dropping them on a node makes them parent of that node. If a drop is not

allowed, the cursor shows that . Validation occurs when dragging

, therefore the example tree is immediately updated.

The maximum number of allowed levels in a function classification is set bydefault to six.

The resulted tree has collapsible and expandable nodes containing exampledata.

To remove a selected node, click on .

As for all classifications, non-leaves levels are displayed using a

(configurable) icon indicating if the branch is opened or not .

The “Example Tree” in the right frame of the ’Classification Definition’ panel,shows a replica of the classification levels that are being defined. The tree isupdated every time the classification level tree is updated.

4. Click on .

5. The following confirmation popup window appears:Are you sure you want to create function classification

<function_classification_name>?.

Click on [ Yes ].

The new function classification is created and displayed in the FunctionClassification Tabs. No filter is associated to this new classification.

If the function classification is public, other users are notified and theyhave to manually refresh the tree.

Note: The new function classifications can be saved as an implicit User Preferencefor the Mode, as well as the new current active function classification.

148 / 664 3BK 21216 AAAA PCZZA Ed.26


8.4 Create Function Classification by CopyTo create a function classification by copy:

1. In the ’Function Classification Editor’ window, select from the left frame the

function classification to copy, then click on .

2. The new function classification is created with a default name:<oldname>_Copy_n , where n is an incremental number to define a uniquename.


You can also modify the function classification properties if needed.

The user becomes the owner of the function classification.


4. The following confirmation popup window appears:Are you sure you want to create function classification

<function_classification_name>?.

Click on [ Yes ].

The new function classification is created. No filter is associated to thisnew classification.

If the function classification is public, other users are notified and theyhave to manually refresh the tree.

Note: The new function classification can be saved as an implicit User Preference forthe Mode, as well as the new current active function classification.

3BK 21216 AAAA PCZZA Ed.26 149 / 664


8.5 Edit Function ClassificationTo edit a function classification:

1. Open the function classification you want to modify.

2. In the ’Function Classification Editor’ window, click on .

The Function Classification Properties Panel interface is displayed with thecurrent attribute values.


Only the owner of the function classification or the Administrator canupdate its values.

The operator is not allowed to modify the owner of the function classification.

If the owner of the function classification is not the one viewing it, the[ Edit ] button is grayed.


The function classification is updated. If it is not hidden, the associatedfunction tree is refreshed with its previous associated filter, if any.

Click on [ Close ] to close the ’Function Classification Editor’ window.

8.6 Delete Function ClassificationTo delete a function classification, select it, then:

From the "Function Classification Editor" window, click on , OR



The following question appears: Are you sure you want to delete

function classification <function_classification_name>?

If only one function classification is selected to be deleted, click on [ Yes ]

If multiple function classifications are selected to be deleted, click on

[ Yes to All ].

The function classification/s is / are deleted from the mode.

If the deleted function classification is public, other users are notified about thedeletion and they must manually refresh their mode.

150 / 664 3BK 21216 AAAA PCZZA Ed.26

9 Working Zone

9 Working Zone

This section describes how to manage the Working Zone editor. It describeshow to create, create by copy, edit and delete a Working Zone.

3BK 21216 AAAA PCZZA Ed.26 151 / 664

9 Working Zone

9.1 Presentation

Note: The MUSE_WORKING_ZONE license must be installed for the WorkingZone Editor to be displayed.

The Working Zone Manager allows the optimizer to define a specific subset ofcells in the network as a personal working zone.

It is also defined by a set of filters dynamically applied to the databasewhenever needed (when opening the Working Zone). Therefore, the set ofnetwork elements retrieved through the filters may vary as the operationalnetwork changes in the database.

To compute a Working Zone, the list of objects contained in the zone for eachstandard is computed and the results are merged into one single zone.

If a Working Zone contains as a filter another Working Zone, it is called a SubWorking Zone . Such Working Zones inherit the filters of their parent andwhenever the parent Working Zone criteria are changed, the Sub Working Zonecriteria are also updated (when opened).

The Working Zone is also used to manage secured access to some parts ofthe network. When defining a Working Zone, the administrator can restrict itsaccess to a limited set of operators. Only the administrator can create publicWorking Zones. An OAD identifier is automatically associated with eachpublic Working Zone and can be used in SECUSM to grant access to theWorking Zones to different users.

The Global Working Zone is a system Working Zone that contains the entirenetwork. It cannot be deleted but, using SECUSM, particular access rightscan be defined on it.

Regular operators can only restrict a Working Zone they can access. Theycannot create Working Zones that are not Sub Working Zones. These SubWorking Zones have the same security access as their reference Working Zone(the one from which they have been created), sharing the same OAD identifier.Sub Working Zones created by users can only be private .

Depending on the pre-defined number of cells, Working Zones are classified intwo categories:

Standard Working Zones - containing less than 2000 cells and all modes

Large Working Zones - containing more than 2000 cells. In this case, not allmodes are available (Adjacency Mode for example).

If you want that "Adjacency Mode" to be available, you must set the’WorkingZonesAllowed’ parameter for ADJ to ’true’, from the following file:

/alcatel/muse/technologies/GSM/QoS/metadata/MaatQueryMetadata.xml

If you want to change the limit of 2000 cells for

Standard Working Zones, you must modify the’MAX_CORE_OBJECT_COUNT’ parameter from the following file:

/alcatel/muse/MUSE_MAAT/topology/rsc/com/alcatel/muse/maat/

topology/config/maatTopo.cfg

This change requires a stop/start NPO from Process Monitoring page inorder to be taken into account in NPO, refer to NPO/9953 MS SUP PlatformAdministration Guide.

152 / 664 3BK 21216 AAAA PCZZA Ed.26

9 Working Zone

Changing these parameters is not under Alcatel-Lucent responsibility. Puttinghigher values then the values tested in Alcatel-Lucent labs may cause higherresponse time or even request that do not answer.

Each technology can specify what are the modes available for Standard orLarge Working Zones.

To update the number of cells that can be monitored in a working zone, refer tosection Modify Working Zone Dimension from “NPO Administration Guide”.

3BK 21216 AAAA PCZZA Ed.26 153 / 664

9 Working Zone

9.2 Working Zone Editor

9.2.1 Open Working Zone Editor

Open working zone:

In the Analysis Desktop main window, click on Topology -> WorkingZone... OR

Press Ctrl+Z.

The ’Working Zone Editor’ window opens.

9.2.2 Working Zone Operations Toolbar

The following toolbar icons are available for the working zone operations:

The following table gives a brief description of the working zone operationstoolbar icons:

Icon Description

Add Union

Add Intersection

Add Exclusion

Remove Operation

Clear Criteria

Status

154 / 664 3BK 21216 AAAA PCZZA Ed.26

9 Working Zone

9.2.3 Create Working Zone

To create a Working Zone:

1. Open Working Zone Editor (Section 9.2.1).

2. In the ’Working Zone Editor’ window, click on .

The ’Working Zone Editor’ appears with default values and editable fields.


FieldName


Name Name of the Working Zone to be created. WorkingZone_<owner>_n

where<owner> is theowner of the workingzone, and “n” is anincremented number tofind a unique name (ncan be 1, 2, 3...).

Owner User who is creating the Working Zone.



Created Date when the working zone was created.


Modified Date when the working zone was last modified, in case of a workingzone update.


AccessRights

Access rights can be:

Public, when the action is done by admin or user with

administration rights

Private, when the action is done by normal user.

Public for adminuser

Private for

non-admin user.

QoSrequirement

QoS Requirement associated to the working zone.

Possible values: Low, Medium, High.

Medium.

Secured Possible values: Yes or No

OAD Label used in SEC to give users access to this working zone.

This field is only used if the working zone is secured, and it isautomatically filled in.

Name of the WorkingZone.

Name of the sourceWorking Zone in caseof Sub Working Zone

Visible Yes, if this working zone is visible to operators.

No, if this working zone is not visible to operators other than theAdministrator.

True.

3BK 21216 AAAA PCZZA Ed.26 155 / 664

9 Working Zone

FieldName


ParentWorkingZone

Left empty in case of Working Zone.

Name of Parent Working Zone in case of Sub Working Zone.

Description Text box to be filled in with operator description for the currentworking zone.

4. If the ’Secured’ option was given to the working zone, the ’Users’ panelbecomes available.

To give access to one or several users to the created working zone, select

them from the ’Users without access’ list and click on . This includesthem in the ’Users with access’ list.

5. In the ’Manage Layer’ panel:

To add new Background/CCA layers, click on [ Add ]. Select the

appropriate imported layer, choose the background or the CCA type,then click on [ OK ]If no layer is loaded, a default tree structure with four nodes (with out theroot node) are displayed in the layer manager.If no layers are associated with the working zone and no layers are savedin the user preferences, a default world map is loaded.

To remove an existing Background/CCA layer from the Layer List, selectit and click on [ Remove ]

To order an existing layer up or down in the Layer List, click on [ Move

Up ] or [ Move Down ] respectively.The Layers in the top of the list are rendered on the top in the cartographyviewport.

The order of layer in the layer manager must always be as below :

Thematic Layer

Network Objects

CCA

Backgrounds

The created Layer List is the list of layers to download at the start of theapplication.

6. In the Working Zone Filter Tree, the following options apply:

Filter

The trees available under the Filter tab are:

Design Parameter

Logical Parameter

Free Field Parameter

Topology Parameter

Operators.

156 / 664 3BK 21216 AAAA PCZZA Ed.26

9 Working Zone

Working ZoneThe trees available under the Working Zones tab are the Working Zones.

Check the appropriate option between Filter or Working Zone.

Depending on your choice, add by a drag & drop operation from the rightpanel:

the appropriate filtering criteria - for Filter (Refer to Filtering (Section

6.1.2) and toFiltering Object Zone (in section ).)

a referenced Working Zone - for Working Zone.

The following operations apply: union, intersection, exclusion .

To delete an operation, select it and click on .

To delete a criteria for Filter, click on .

The allowed operators are: >, <, >=, <=, =, !=, contains, doesn’t contain,like. Operands can also contain mathematical operations (+, -, *, /, numericconstants).

Unitary NPO Specific Operators such as IsGreen can also be used.

The status of the object zone criteria is shown in the icon.

IconColor

Criteria

Green All the nodes are checked and are valid.

Orange One or more nodes is not checked.

Red One or more nodes has the Criteria is not valid status.

7. Click on .

3BK 21216 AAAA PCZZA Ed.26 157 / 664

9 Working Zone

8. The following confirmation popup window appears:Are you sure you want to create working zone

<working_zone_name>?.

Click on [ Yes ].

The Working Zone is created and SEC is updated according to the operatorsallowed to open this new Working Zone.

9.2.4 Create Working Zone by Copy

To copy a Working Zone:


2. Select a working zone which you want to copy, then click on .

The Working Zone ’Properties’ panel appears with the default name and theeditable properties panel.

3. Type a name and title.

The format for the name is <old name>_Copy_n, where n is incremented tofind a unique name (n can be 1, 2, 3...). .

While copying the properties, the Operator list is added to the ’Properties’panel, in the case of a Working Zone.

4. Click on .

The new working zone is created.

158 / 664 3BK 21216 AAAA PCZZA Ed.26

9 Working Zone

9.2.5 Edit Working Zone

To edit a Working Zone:


2. Select the working zone you want to update, then click on .

The Working Zone ’Properties’ panel appears. All fields except for thename can be edited.

3. Edit the required fields with the appropriate values.Two restrictions apply:

A Sub Working Zone cannot be changed into a Working Zone

The Operator List is not available during the edit operation.

4. Click on .

9.2.6 Delete Working Zone

To delete a Working Zone:


2. Select the Working Zone to be deleted and click on .

3. Click on [ OK ] to confirm the deletion.

3BK 21216 AAAA PCZZA Ed.26 159 / 664

9 Working Zone

9.3 Create Sub Working Zone

9.3.1 Create Sub Working Zone

To create a Sub Working Zone, use the procedure described for CreateWorking Zone (Section 9.2.3), but in the ’Parent Working Zone’ add from thedrop down list a reference to the Parent Working Zone.

When computing the Sub Working Zone, the resulting filter to be used is: Filterof Parent Working Zone INTERSECTION Filter of Working Zone.

9.3.2 Create Sub Working Zone from Object Zone

Note: The ’Create Sub Working Zone from Object Zone’ is only available forCore-Object Zones. (i.e. Cell3G Zone for W-CDMA, Cell2G Zone for GSM).

To create a Sub Working Zone from the Object Zone:

1. Select an Object Zone in the Topology Browser.

2. Right click on it and select Create Sub Working Zone ...

The "Enter Working Zone Name" window appears.

3. Type a name for the Sub Working Zone, and click on [ OK ]. A new SubWorking Zone is created with the following default properties:

The Parent Working Zone is the current open Working Zone

Access is set to ’Private’

Filtering criteria, except for the non-applicable criteria, is copied from

the selected Object Zone.If the Object Zone contains even one QoS criteria, a warning appearsindicating that it is not possible to create a Sub Working Zone fromthat Object Zone.

160 / 664 3BK 21216 AAAA PCZZA Ed.26

9 Working Zone

9.3.3 Create Sub Working Zone from Topology Objects List

To create a Sub Working Zone from the Topology Objects list:

1. Select a list of Topology Objects in the Topology Browser.

2. Right click on the list and select Create Sub Working Zone ...

The "Enter Working Zone Name" window appears.




Filtering criteria is defined using the object list source of the operation.If the Object Zone contains even one QoS criteria, a warning appearsindicating that it is not possible to create a Sub Working Zone fromthat Object Zone.

9.3.4 Create and Open Sub Working Zone

To create and open a Sub Working Zone from the Topology Objects listor from the Object Zone:

1. Selects one or more Topology Objects or an Object Zone in the TopologyBrowser.

2. Right click on the list and select Create and Open Sub Working Zone ...

The "Create and Open Sub Working Zone" window appears with a messageindicating that the newly created working zone will be opened after creationand the change cannot be canceled.




Filtering criteria is defined using the object list source of the operation oris copied from the selected Object Zone, except for the non-applicable

criteria.If the Object Zone contains even one QoS criteria, a warning appearsindicating that it is not possible to create a Sub Working Zone fromthat Object Zone.Once the Working Zone is created, it is automatically opened.

3BK 21216 AAAA PCZZA Ed.26 161 / 664

9 Working Zone

9.3.5 Create Sub Working Zone by Copy

To copy a Sub Working Zone:

1. Select a sub working zone which you want to copy, then click on .

The Working Zone ’Properties’ panel appears with the default name and theeditable properties panel.

2. Type a name and a title.

The format for the name is <old name>_Copy_n, where n is incremented tofind a unique name (n can be 1, 2, 3...). .

While copying the properties, the Operator list is added to the ’Properties’panel, in the case of a Sub Working Zone.

3. Click on .

The sub working zone is created at the same level as the copied subworking zone, and inheriting the filters of its parent.

9.4 Change Current Working ZoneChange the current Working Zone:

1. Select Analysis Desktop -> Change Working Zone...The ’Select Working Zone’ window appears.

2. Select the appropriate working zone, then click on [ Open ].

The selected working zone is displayed.

162 / 664 3BK 21216 AAAA PCZZA Ed.26

10 Counters and Indicators


This section describes how to manage counters and indicators.

3BK 21216 AAAA PCZZA Ed.26 163 / 664


10.1 Presentation

Note: The MUSE_QOS_<TECHNO>_LICENSE license must be installed, so thatthe administrator can declare QoS data sources for a given technology (GSM,W-CDMA,…).

The MUSE_QOS_INDICATOR_CREATION_LICENSE license must beinstalled to be able to create indicators.

If the MUSE_QOS_HISTORY_LICENSE license is not instaled, then the historyof the QoS Data is limited to one week.

10.1.1 Definition

Counters are retrieved from the NPO and used as building blocks in theformation of indicators.

An Indicator is an Optimization Application view of a network property.

The indicator is computed from performance measurements, counters values,other indicators, or any other available network parameter values, suchas radio parameters.

An indicator is defined on Availability Domains that consist of sets of NetworkObjects and period types. An indicator value can be calculated for the specifiedNetwork Objects and for the possible period types only. An indicator has nomeaning for Network Objects and / or period types that are not specifiedin its Availability Domain.

An indicator is consolidated. Consolidation consists of normalization, andoptionally, of aggregation (spatial or temporal).

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

Indicator Type Description

Basic Indicator Indicator calculated directly from the counters, or from the counters and theparameters, using a formula dependent on the release.

Calculated Indicator Indicator calculated on basic or other calculated indicators, or on parameters, usinga formula independent of the equipment release with the same topology level(network object type) and periodicity.

Telecom Indicator A basic or calculated indicator, with a telecom definition; i.e. related to a precisetelecom procedure (call drop…).

PresentationIndicator

Represents a value that can be displayed on the analysis desktop.

Several presentation indicators can be associated to a single telecom indicator. Inthis case, several entries are present in the functions list of the Analysis Desktop.This is typically the case when several temporal aggregations are defined.

TemporalAggregationIndicator

A presentation indicator based on telecom indicators. Its value is computed athigher temporal level: day, week, month.

Visible Indicator A presentation indicator that has the visible flag set to ’true’.

Reference Indicator Presentation indicator used to calculate the busy hour.

164 / 664 3BK 21216 AAAA PCZZA Ed.26


Indicator Type Description

Customer Indicator Indicator (basic or calculated) created by the customer.

System Indicator Indicator (basic or calculated) delivered by Alcatel-Lucent.

Temporary Indicator Customer calculated indicator whose lifetime is limited to the operator session (it isdeleted when exiting the Analysis Desktop).

When created, it can only be added interactively to view template, and cannotbe saved to a view template.

Reliability Indicator Indicator that provides information about loss of QoS data.

Topology Indicator Indicator that presents the number of topology objects from a given type per day.

3BK 21216 AAAA PCZZA Ed.26 165 / 664


10.1.2 Basic/Calculated Indicators

Note: The system proposes by default a calculated indicator, and the operator mustexplicitly override the default to create a basic indicator.

10.1.2.1 Basic IndicatorsA basic indicator is an indicator calculated directly from the counters or from thecounters and the parameters, using a formula dependent on the release.

The following indicators can be basic:

Basic indicator alone

Stored aggregation of a temporal aggregation indicator.

When creating / editing a basic indicator, the system shows the list of availablecounters / parameters and available functions. Once a counter has beenselected:

Only counters of same release, PM type, source and reporting elementsare available

Only parameters and counters of the same release and with the same

source element are available.

The availability domain for the basic indicator, if the indicator has a non-emptyaggregation function, is based on:

Counters only, as it is extended to a high level in the hierarchy (temporal

and spatial). It is done for all possible levels; it is not possible to selectseveral levels only.

Counters and parameters, as it is extended to a high level only in the

temporal hierarchy.

Basic indicators are always stored, but only a limited number of basic indicatorsis supported.For stored indicators, the storage duration can be configured.

166 / 664 3BK 21216 AAAA PCZZA Ed.26


10.1.2.2 Calculated IndicatorsA calculated indicator is an indicator calculated on basic or other calculatedindicators, or on parameters, using a formula independent of the equipmentrelease with the same topology level (network object type) and periodicity.

Calculated indicators can be:

Classical (without any particular aggregation)

With stored temporal aggregation function

With multiple spatial levels, also called complex indicator level 1, or changetopology levelThis is a calculated indicator using a formula that mixes indicators atdifferent topology levels, such as TRX, CELL, BSC, Network.Example: if an indicator formula is CALL_DROP_DIST_SUP = CALL_DROP/ sup(CALL_DROP), then to calculate this indicator at TRX level, the systemdoes: CALL_DROP_DIST_SUPTRX = CALL_DROPTRX / CALL_DROPCELL

Two functions may used:

ObjSup(Ind) - takes the value of the indicator ’Ind’ at the spatial level ’n+1’

ObjSupSel(Ind, ObjType) - takes the value of the indicator ’Ind’ at thespatial level defined by the ’ObjectType’.

With spatial aggregation function, also called complex indicator level 2.This is a calculated indicator with an aggregation function used over a zone,such as Cell Zone, TRX Zone, etc.Example: RTCH_TRAFFIC_OFFER_TOTAL = ErlangB(channelcell)A classical calculated indicator would be: RTCH_TRAFFIC_OFFER_TOTAL= ErlangB( channelcell)

Example An indicator defined as Call_drop = Call_success / Call_Attempt is calculateddifferently if it is classical, or if it has a stored temporal aggregation:

For classical calculated indicator:Call_drophourly = Call_successhourly / Call_AttempthourlyCall_dropdaily = Call_successdaily / Call_AttemptdailyCall_dropweekly = Call_successweekly / Call_AttemptweeklyCall_dropmonthly = Call_successmonthly / Call_Attemptmonthly.

For indicator with stored temporal aggregation, MAX for example:Call_drophourly = Call_successhourly / Call_AttempthourlyCall_dropdaily = MAXall hours(Call_successhourly / Call_Attempthourly)Call_dropweekly = MAXall days of the week(Call_successdaily / Call_Attemptdaily)Call_dropmonthly = MAXall days of the month(Call_successdaily /Call_Attemptdaily).

See also Aggregation (Section 10.1.7.2).

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

3BK 21216 AAAA PCZZA Ed.26 167 / 664


The availability domain for the calculated indicator, is based on:

Indicators, as it is the intersection of the availability domain of all the

referenced basic indicators, of the sampling indicator and the reliabilityindicator

Parameters, as it is the intersection of the availability domain of all

referenced basic indicators and the ’availability domain’ of the parameter.The availability domain of a parameter is the object on which the parameter

is based, extended to a high level in the temporal hierarchy. The ruleused to compute a parameter during a period is to return the last value of

the period (even if the value of the parameter has been modified during

the required period).

Figure 10: Example of Availability Domain

When using advanced operators such as OBJSUP, OBJINF in the formula ofcomplex indicators, the Availability Domain must be manually determined(manually uncheck the non supported periodicities).Example: For a complex indicator defined as Call_drop /

ObjSup(Call_drop) , the "CZ" and "Network" should not be part of theavailability domain.

10.1.3 Scalar/Vector/Matrix/Axis Indicators

The following indicator types are available:

Scalar, corresponding to all mono-valued (non vector or matrix) indicators

Vector, corresponding to an indicator defined in one dimension with an

associated axis indicator. It can be manipulated through the AnalysisDesktop or through dedicated QoS reports (distribution report)

Matrix, corresponding to an indicator defined in two dimensions, and each

dimension is associated with an axis indicator. It can be manipulated throughthe Analysis Desktop or through dedicated QoS reports (distribution report)In GSM, vector and matrix indicators are used to display RMS (RadioMeasurement Statistics).

Axis, associated with vector and matrix indicators. They cannot be

manipulated directly by the Analysis Desktop. They are manipulated by theindicator manager. The properties of an axis indicator can be displayed by

navigation through the properties of a vector indicator or a matrix indicator.

168 / 664 3BK 21216 AAAA PCZZA Ed.26


10.1.4 Indicator Group

The indicator group has only one source. A source is a unique combination ofPM type, that collects network elements and source network elements for adedicated release.

Each indicator group is stored in a different table in the database. In the datawarehouse, each indicator group corresponds to a different table.

All the indicators of the same group have the same spatial aggregation path.

For example, for a group it is possible to have:

for B9: Source = PMType 110, BSC, CELL2G

for B10: Source = PMType 200, BSC, TRX.

3BK 21216 AAAA PCZZA Ed.26 169 / 664


10.1.5 Counter Attributes

The following tables describe the content of a counter dictionary.

10.1.5.1 Header

Content Mandatory DisplayOnly

Comments

Name Y Y Dictionary name

Version Y Y Version

Date N Y Publishing date

Author N Y Publishing responsible name (team or person)

Description N Y Free comment (changes log or comments)

10.1.5.2 Domains


Comments

Name Y Y Name

For each domain, list of the sub-domains1 (optional)

Name Y Y Sub-domain name

For each sub-domain1, list of the sub-domains2(optional)





170 / 664 3BK 21216 AAAA PCZZA Ed.26


10.1.5.3 Releases


Comments

Technology Y N Standard name (GSM, W-CDMA… - ASCII)

Supplier Y N Supplier name (ASCII)

Name Y N Release name (ASCII)

Version Y Y Release version (ASCII)

Description N Y Free comment

3BK 21216 AAAA PCZZA Ed.26 171 / 664


10.1.5.4 Counters


Comments

Reference Y N Unique counter reference (ASCII)

Long name Y N Unique long counter name (mnemonic)

Description N Y Counter description

Source networkobject

Y Y Type of object (RNC, NB, BS…) supporting thecounter (ASCII)

Collecting networkobject

Y Y Type of object (RNC, NB, BS…) reporting thecounter (ASCII)

PM type N N If that information is not provided, it is set with thesame value that “Collecting network object”. In GSMcase, a particular data type (110, 180…) is provided.(ASCII)

Unit Y Y Unit of the counter (%, db…)

Precision Y Y Number of significant digit. The ’%’ may beconcatenated to the precision using the ’-’ asseparator, and in this case the value of indicator hasto be also * 100 for display.

Default RP N Y Default permanent reporting period

Algorithm type N Y Method used to compute the counter (asynchronouscumulative, synchronous cumulative, sampling…)

Algorithm info N Y Sampling period in case of “sampling” algorithm type. Previously called “Sampling period”.

Sampling Period N Y Value of the sampling period when the algorithmtype is sampling

LoadMap Formula N N Value of the factor when a factor is applied at loadingtime. Counter value = PM value * factor (by defaultnone).

Consolidation Method Y N Normalization method (Sum, Average, Max, Min…).Interpolation Method Y N Default interpolationmethod (No, Zero, linear…)

Domain name Y Y Refer to a (sub-)domain defined in “DomainsDefinition” section

172 / 664 3BK 21216 AAAA PCZZA Ed.26


10.1.5.5 Structure Type: Scalar


Comments

Value Type Y N Counter type (Boolean, Integer, float)

10.1.5.6 Structure Type: Vector



Comments

Value Type Y N Counter type (Integer, float)

Size Y N Max vector size (<= 50)

Axis counter N N Associated axis counter reference name

10.1.5.7 Structure Type: Matrix



Comments

ValueType Y N Counter type (Integer, float)

XSize Y N Max X matrix size (<= 50)

YSize Y N Max Y matrix size (<= 25)

XAxis counter N N Associated axis counter reference name

YAxis counter N N Associated axis counter reference name

3BK 21216 AAAA PCZZA Ed.26 173 / 664


10.1.5.8 Structure Type: Axis



Comments

ValueType Y N Counter type (Integer, float)

SizeMax Y N Max length (<= 50)

Choice between ’Dependent Columns’ or the three other fields

Dependent Columns N N Indicates whether the columns displayed in the HMImust be attached or not.

FirstColumnBoundaryIncluded

N N Inform the HMI whether the first column includes thefirst value of the axis indicator or not

LastColumnBoundaryIncluded

N N Inform the HMI whether the last column includes thelast value of the axis indicator or not

PreviousColumnBoundaryIncluded

N N Inform the HMI whether the last value of the previouscolumn is included or not.

174 / 664 3BK 21216 AAAA PCZZA Ed.26


10.1.5.9 Telecom Families


Comments

Name Y Y Family name

Order Y Y Number to order the families between themselves

List of telecom sub-Family1 Definition (optional).

Name N Y Sub-family name

Order N Y Ordering number










List of the counters, the same counter may be present in several (sub-) families.

Counter name Y Y Counter reference name (counter belonging to the(sub-) family)

3BK 21216 AAAA PCZZA Ed.26 175 / 664


10.1.6 Indicator Attributes

The following tables describe the content of an indicator dictionary.

10.1.6.1 Header

Content Mandatory Displayonly

Comments

Name Y Y Dictionary name

Type Y N System or Customer dictionary

Version Y Y Version

Date N Y Publishing date

Author N Y Publishing responsible name (team orperson)

Description N Y Free comment (changes log or comments)

10.1.6.2 Release


Comments

Technology Y N Standard name (GSM, W-CDMA… - ASCII)


Name Y N Release name (ASCII)

Version Y Y Release version (ASCII)

Description N Y Free comment

176 / 664 3BK 21216 AAAA PCZZA Ed.26


10.1.6.3 Indicator Group


Comments

Name Y N Name of the indicator group (QoS, HO,HOO…) (ASCII)

Spatial Aggregation Path Y N Describes the spatial aggregation path forthe indicator group.

Optional choice between nHourlyLevel and DailyLevel or nothing.

nHourlyLevel N N Value in minutes of the collecting period.

DailyLevel N N Flag indicating if the indicator of the groupare available on all temporal level (dailyLevel= false) or only on daily to monthly temporallevel (dailyLevel = true). The default isdailyLevel = false.

3BK 21216 AAAA PCZZA Ed.26 177 / 664


10.1.6.4 Telecom Indicators

Section Content Mandatory Displayonly

Comments

Long name Y N Unique telecom indicator long name(ASCII)

Reference Y N Unique telecom indicator reference(ASCII)

Description N Y Indicator description

Unit Y Y Unit of the indicator (%, db…)

Telecom IndicatorDefinition

Upper is fault Y N This flag indicates whether thequality is better when the indicatorvalue is higher or the opposite(quality is better when the value islower).

Structure Type:Scalar

ValueType Y N Indicator type (Integer, float,boolean)


Size Y N Max vector size (<= 50)

Structure Type:Vector

Axis indicator Y N Associated axis indicator long name


XSize Y N Max X matrix size (<= 50)

YSize Y N Max Y matrix size (<= 25)

XAxis indicator Y N Associated axis indicator long name

Structure Type:Matrix

YAxis indicator Y N Associated axis indicator long name

178 / 664 3BK 21216 AAAA PCZZA Ed.26



Comments


SizeMax Y N Max length (<= 50

Display N Y When set that attribute means thatthe axis value corresponds to aparticular object and that this valuemust be replaced at display levelby the object label (for example:“frequency” or “neighbor”).

FirstValue N N MEASURED (default), INFINITY,NONE or value

LastValue N N MEASURED (default), INFINITY,NONE or value

Choice between “Dependent columns” or the three other fields

Dependent Columns Y N Indicates whether the columnsdisplayed in the HMI must beattached or not.

FirstColumnBoundaryIncluded

Y N Inform the HMI whether the firstcolumn includes the first value of theaxis indicator or not. Not present ifFirstValue is INFINITY or NONE.

LastColumnBoundaryIncluded

Y N Inform the HMI whether the lastcolumn includes the last value of theaxis indicator or not. Not present ifLastValue is INFINITY or NONE.

Structure Type:Axis


Y N Inform the HMI whether the lastvalue of the previous column isincluded or not.

3BK 21216 AAAA PCZZA Ed.26 179 / 664



Comments

First InterpolationMethod

Y N Interpolation method (No, Zero,linear…)

First MethodParameter

N N Mandatory in case of Paddinginterpolation function as firstinterpolation method. Providethe padding value for the firstinterpolation method.

Second interpolationMethod

N N Second interpolation method (No,Zero, linear…).

Second MethodParameter

N N Mandatory in case of Paddinginterpolation function as secondinterpolation method. Providethe padding value for the secondinterpolation method.

Consolidation Method Y N Consolidation method (Sum, Count,Average, Min, Max). Note that incase of average counter, it may benecessary to provide also a counterrepresenting the weighting factor toperform indicator consolidations.

Interpol changeAllowed

Y N Boolean (if false then only thedefault interpolation method can beused)

Group Y N Refer to an indicator group definedin the section “indicator groups”

Basic indicator

Spatial Aggregation N N Method used to perform the spatialaggregation. Note that in caseof average counter, it may benecessary to provide also a counterrepresenting the weighting factor toperform indicator consolidations.

180 / 664 3BK 21216 AAAA PCZZA Ed.26



Comments

Technology Y N Standard name (GSM, W-CDMA…- ASCII)


Release Y N Release name (ASCII)

Spatial Aggregation onLoading

N N Method to be used to perform spatialaggregation to n+1 level at loadingtime (possible values: “sum”, “avg”,“count”, “min”, “max” and “none”(default)).

CounterFormula

Counters Formula Y N Reference counter reference namebased formula

Calculatedindicator

Formula Y N Telecom indicator long name basedformula.

3BK 21216 AAAA PCZZA Ed.26 181 / 664


10.1.6.5 Presentation Indicator


Comments

Availability domain Y Y Telecom indicator availability domain. It isthe list of object types (RNC, NB, BS…) ateach temporal level where the indicator isavailable.


Precision Y Y Number of significant digit. The ’%’ may beconcatenated to the precision using the ’-’as separator, and in this case the value ofindicator has to be also * 100 for display.

Sampling Indicator N N Sampling indicator long name

Threshold Values N N Threshold values for that telecom indicatorfor each sensitivity (Low, Medium, High)

Sampling Values N N Sampling values for that telecom indicator foreach sensitivity (Low, Medium, High)

Reliability indicator N N Reliability indicator long name

AccessRight N N Indicate the access right of the indicator(PUBLIC or PRIVATE).

isVisible N N Boolean: TRUE if the indicator is visible inthe Analysis Desktop. Default value: TRUE.Note that if the indicator is present in noneof the defined families, this flag is forced toFALSE (at the import time) whatever thedictionary value (a warning is logged in thatcase to point out the potential inconsistency).

182 / 664 3BK 21216 AAAA PCZZA Ed.26


10.1.6.6 Temporal Aggregation


Comments

Long name N Y Unique indicator long name (ASCII).Empty if it is the same as the telecomindicator one.

Reference Extension N N Reference extension of the temporalaggregation. This extension has tobe merged with the reference of thetelecom indicator (ASCII).

Description Extension N Y Description of the temporal aggregation.This description replaces the descriptionof the telecom indicator.

Availability domain Y Y Telecom indicator availability domain.It is the list of object types (RNC, NB,BS…) at each temporal level where theindicator is available.


Precision Y Y Number of significant digit. The ’%’ maybe concatenated to the precision usingthe ’-’ as separator, and in this case thevalue of indicator has to be also * 100for display.

Sampling Indicator N N Sampling indicator long name

Threshold Values N N Threshold values for that telecomindicator for each sensitivity (Low,Medium, High)

Sampling Values N N Sampling values for that telecomindicator for each sensitivity (Low,Medium, High)

Reliability indicator N N Reliability indicator long name

AccessRight N N Indicate the access right of the indicator(PUBLIC or PRIVATE).

isVisible N N Boolean: TRUE if the indicator is visiblein the Analysis Desktop. Default value:TRUE. Note that if the indicator ispresent in none of the defined families,this flag is forced to FALSE (at theimport time) whatever the dictionaryvalue (a warning is logged in that caseto point out the potential inconsistency).

3BK 21216 AAAA PCZZA Ed.26 183 / 664



Comments

StoredTemporalAggregation

Temporal aggregationmethod

Y Y Function used to perform temporalaggregation (from Normalized table toDaily, or weekly or Monthly).

Relevant hour N All hours or working hours. By defaultthe value is All hours. Allow computingconsolidation only for relevant hours.

Group Y N Refer to an indicator group defined inthe section “indicator groups”.

Busy hour indicator N N Long name of the indicator used asreference indicator to compute the busyhour. This field may be empty (ASCII).

CalculatedTemporalAggregation

Formula Y N Formula (of telecom indicators – basic,calculated, temporal aggregation – longnames) used to compute the temporalaggregation of a calculated indicator.

184 / 664 3BK 21216 AAAA PCZZA Ed.26


10.1.6.7 Telecom Family


Comments

Name Y Y Family name

Order Y Y Number to order the families betweenthemselves













List of the indicators, the same indicator may be present in several (sub-) families.

Indicator name Y Y Indicator long name (indicator belonging tothe (sub-) family)

3BK 21216 AAAA PCZZA Ed.26 185 / 664


10.1.7 Consolidation

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

Aggregation and normalization apply only on indicators.

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

The scheduler launches the consolidation scripts every night. If the previous dayconsolidation is not finished, the system waits for the completion of the ongoingloading of files, before launching the consolidation for the current day. If anyfiles are missing (not in exchange directory), the consolidation starts anyway.

The administrator can manually launch the consolidation if they find out thatthere is recovered data that has not been consolidated.

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 (static aggregation) andthen temporally (daily, weekly, and monthly aggregations). Daily aggregationis always performed; weekly and monthly are only performed on the firstday of the week or of the month.

To view the Consolidation Follow Up, refer to Consolidation Follow Up (Section2.18).

10.1.7.1 NormalizationNormalization consists of adapting basic indicator values to display purpose, forindicator formula calculation, or for aggregation.

It comprises the following process:

Interpolation , to automatically complete the missing values.

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

Extend - only the existing values are used and they are extended to the

wanted displayed period

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

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 afterare not known.

Padding - all the missing periods are set to a padding value. This is zero

by defaut, but can be configurable through the ’Padding’ parameter.

186 / 664 3BK 21216 AAAA PCZZA Ed.26


Period alignment (time shift) , to set the same measurement period for allmeasurement data involved in the aggregation or formula calculation (for

example 4H, 1H, 15mn).

Synchronization of measurement data , to set the same beginning / end

dates for aggregation or formula calculation.

The following figures present various combinations of cumulative counters.

3BK 21216 AAAA PCZZA Ed.26 187 / 664


10.1.7.2 AggregationIndicators can be aggregated whenever requested.

There are two types of aggregation:

Temporal Aggregation , containing summarizing data of one networkelement into one value that defines the parent in the period hierarchy .Example: aggregation of raw data to daily data.When the indicator is defined, it is possible to have several aggregationfunctions; in this case there are several linked indicators.

Two types of temporal aggregation can be defined:

Stored Aggregation

Calculated AggregationCalculated temporal aggregation can be used to avoid having too muchstored temporal aggregation when it is possible to calculate it usingother indicators.

Possible temporal aggregations are: SUM, MIN, MAX, BH, 3DAV, ...

Note: For Temporal Aggregation execution at hourly level the result is the value ofthe telecom indicator at hourly level.

Spatial Aggregation , containing the summarizing data of several networkelements into one value that defines the parent in the network hierarchy .Example: aggregation of cell data to BSC data.The spatial aggregation is always done on the normalized data, beforethe temporal aggregation.

Possible spatial aggregations are: MIN, MAX, SUM, AVG, ...

188 / 664 3BK 21216 AAAA PCZZA Ed.26


Example of Aggregation Consider that ’RTCH_CONG’ indicator has two aggregation functions: TOTand MAX.

MAX aggregation automatically produces an indicator called’RTCH_CONG_MAX’.

’RTCH_CONG_MAX’ has the same counter formula as ’RTCH_CONG’. It iscomputed each night based on ’RTCH_CONG’ as the raw level, and notduring PM loading. ’RTCH_CONG_MAX’ is potentially available at hourlylevel. In case the administrator removes this level from its availability domain,the following are produced:

A telecom indicator, called ’RTCH_CONG’

A temporal aggregation, called ’RTCH_CONG’

A temporal aggregation, called ’RTCH_CONG_MAX’.

When browsing the functions in the Analysis Desktop, you can see bothtemporal aggregations: ’RTCH_CONG’ and ’RTCH_CONG_MAX’, asthey are considered presentation indicators. When displaying the indicatordocumentation, there is a main entry for the telecom indicator ’RTCH_CONG’and two sub entries for the two temporal aggregations.

10.1.7.3 Busy HourUsing the hourly consolidated data:

Busy hour position is used to retrieve the per-day position (the hour of

the day) when a reference indicator reaches its maximum value (00:00 –

00:59 = 0, 01:00 – 01:59 = 1…).

Busy hour is used to return the value of an indicator, at the busy hour of a

reference indicator (usually not the same).This is not correlated to the maximum value of that indicator.

The example below tries to get the call drop rate when the call numberis maximum, and:

Reference indicator is call number

Indicator is call drop rate.

3BK 21216 AAAA PCZZA Ed.26 189 / 664


Depending on the value of the reference indicator upper_is_fault flag, itmay be needed to search for the minimum value instead of the maximum.

Upper_is_fault = true => BH_max

Upper_is_fault = false => BH_min.

In the "Execution Context" window, by putting the mouse over the Busy Hourperiodicity, a tooltip details the indicator name set as the busy hour indicator(see the example below).

Busy hour can either be computed dynamically by the system (when the busyhour option is checked in execution context), it can also be computed duringconsolidation and stored.

When computing a busy hour on an object zone, the reference indicator is firstcalculated on the object zone, the maximum value is taken, and then theindicator is computed as the busy hour value.

Example:Cell1 traffic: 16H => 10, 17H => 8, 18H=>0Cell2 traffic: 16H => 0, 17H => 8, 18H=>10

Related to this example, in case of:

Busy Hour/Object Zone execute view : If you calculate indicator call_drop

at the busy hour of this object zone, the maximum traffic of Cell1+Cell2 is at

17H, so the result will be call_drop( 17H,cell1)+call_drop(17H,cell2)

Busy Hour stored aggregation the busy hour is calculated for each cells

and stored. For Cell1, the system store call_drop(16H ), for cell2 it storecall_drop(18H) , this would correspond to an indicator call_drop_bh .

It is also possible to calculate object zone on call_drop_bh .

10.1.7.4 Daily Average ValueThe objective of Daily Average Value computation is to get an average busyhour value for a given period (several days).

The algorithm is called nDAV , n being the number of reference days for theaverage computation.

In NPO, nDAV is usually computed for a week or a month using the followingcriteria:

A number of reference days is selected (for instance n=3 or n=5).

The per day busy hour value is computed and the n days where the

reference indicator reaches its maximum values are selected.

The indicator value is the average of the indicator for those n busy hours.

3DAV Example

190 / 664 3BK 21216 AAAA PCZZA Ed.26


3BK 21216 AAAA PCZZA Ed.26 191 / 664


10.1.8 PM Data Purge

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

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

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

Table Type Storage Duration

Raw 30 days

Normalized 30 days

Daily From 3 to 14 months

Weekly From 3 to 36 months

Monthly From 3 to 36 months

See ’NPO Administration Guide’ to Configure Indicator Storage Duration,Configure Parameter Storage Duration, or to Configure Laser Data StorageDuration.

192 / 664 3BK 21216 AAAA PCZZA Ed.26


10.1.9 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 may be missing. Thereliability indicates if this displayed value is “reliable” (TRUE) or not (FALSE).

Therefore, the displayed value for an indicator can be:

Correct, whereby the reliability is TRUE

Partially correct (on a limited domain), whereby the reliability is FALSE

Wrong, whereby the reliability is FALSE.

The reliability indicator is associated to one or several indicators, through the’Reliability Indicator’ field (See Create Indicator (Section 10.7.2)).

The QoS loss of data may occur on:

Current Network exploitation operations (reset…)Some software problems or operator commands such as board resetmay reset the counter values on one or several boards. In this case, theequipment cannot provide the counter values associated with these boardsfor the entire PM period. The concerned counters are put to NULL. Whena problem occurs on some equipment (for example, on the MFS) and allthe counters are NULL, then a specific flag is set to active in the PM file toindicate that there are no available counters in the PM file.

QoS files transfer problems.Due to different problems (BSC/MFS or OMC-R failure), some PM files canbe lost. Also, PM files that arrive too late to be processed by the differentaggregation scripts performed once a night, are considered as lost.

The reliability indicator is not developed for the adjacency object

The Alcatel-Lucent reliability indicator is not developed for QoS indicators

based on RIM-NACC counters (RIM-NACC = RAN Information Management- Network Assisted Cell Change)

The displayed value for an indicator can be good and reliability false when

an object is added, removed or migrated.

3BK 21216 AAAA PCZZA Ed.26 193 / 664


10.1.10 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 aview or report, in order to quickly see which values are critical, major, etc. (seeHighlight in View (Section 18.5.2)).

The indicators for which thresholds are defined are also used when creatingwarning reports. In this way, the report results may be filtered according to theset thresholds (see Warning Reports (Section 19.1.5)).

Three alert thresholds corresponding to three QoS requirement levels can bedefined for each QoS indicator: red, orange, and yellow, each having threedefinable sensitivities. See Set QoS Requirement (Section 4) to changethe requirement level.

If the value of the reference indicator upper_is_fault is:

’true’, min color is green, and max color is red

’false’, min color is red and max color is green.

Figure 11: Threshold and Sampling for Call_Drop_Rate Indicator

Figure 12: Threshold and Sampling for Call_Success_Rate Indicator

If the sampling indicator is below the sampling value, then the threshold isnot taken into consideration.

For example, for call_drop_rate :

the red threshold is ’4%’ for the high sensitivity

the sampling indicator is ’RTCH_success_end’

the sampling value is ’100’.

194 / 664 3BK 21216 AAAA PCZZA Ed.26


If the value of ’RTCH_success_end’ is less than ’100’, the threshold is nevercomputed.

Therefore, the goal of the sampling is to avoid triggering the threshold whenthere are too few calls to have any meaningful statistics.

The following icons are attached to the indicators having or not threshold:

Indicators with thresholds:

Indicators without thresholds: .

The threshold and sampling of an indicator are customizable, in order toadapt their values to the operator’s expertise. See Edit Indicator Threshold /Sampling Values (Section 10.7.5)

10.1.11 Indicator Formula Operands

The following formula operands are allowed:

Basic Operators: +, -, *, /

Cross Type Operators: ++, –, **, //

Mathematical Functions: EXP, EXP10, LN, LOG, SQR, SQRT, INT, ROUND,

ABS, COS, SIN, TAN, FACT, MOD

Shortname

Name Scenarios

EXP Natural exponent If x = 1 EXP(1) = 2.7183

This function is valid for all real numbers.

EXP10 Decimal exponent If x = -3 EXP10(-3) = 0.001


LN Natural logarithm If x = 1, Ln(1) = 0

If x = 3, Ln(3) = 1.097

This function is not valid for x = 0 .

LOG Decimal logarithm If x = 2, LOG(2) = 0.3010

If x =10 , LOG(10) = 1

This function is not valid for x = 0 .

SQR Square If x = 5.5, SQR(5.5) = 30.25

If x =10 , SQR(x)= 100

This function is valid only if x > 0 .

SQRT Positive square root If x =225, SQRT(225) = 15

If x =60.84, SQRT(60.84)= 7.8


3BK 21216 AAAA PCZZA Ed.26 195 / 664


Shortname

Name Scenarios

INT Integer Value If x =4.57, INT(4.57) = 4

If x =4.89, INT(4.89) = 4


ROUND Round Integer Value If x =4.57, ROUND(4.57) = 4

If x =4.89, ROUND(4.89) = 5


ABS Absolute Value If x = -14.5, ABS( -14.5) = 14.5

If x =45.1, ABS(45.1) = 45


COS Cosine If x =13.5, COS(45) = 0.5949

If x =0, COS(0) = 1


SIN Sine If x =25, SIN(25) = -0.1323

If x =0, SIN(0) = 0


TAN Tangential If x =0.7853, TAN(0.7853) = 1

If x =0, TAN(0) = 0


FACT Factorial If x =8, FACT(8) = 40320


MOD Modulo If x =7, n = 2 MOD(7,2) = 1

If x =8.3, n = 3.4 MOD(8.3,3.4) = 1.5

This function is valid only if x,n > 0 .

196 / 664 3BK 21216 AAAA PCZZA Ed.26


Logical Functions: ISNULL, ISDIV0, NOT, AND, OR, =, >, <, >=, <=, <>,LIKE, TO_BOOLEAN

Shortname

Name Scenarios

AND Standard logical AND If X -> 5 , Y-> 5 X AND Y ->TRUE.

This function is only valid for same data types.

OR Standard logical OR If X-> 1 , Y->0 X OR Y -> TRUE. If X-> 0 , Y->0 X OR Y -> FALSE.


NOT Standard logical NOT If X-> 0, NOT X ->TRUE

= = This assigns the values to variables, X= 5

This function assigns value for variables with constants andvariables.

<> <> If X-> JDK , Y->JAVA X <> Y -> FALSE.


< < If X-> 5 , Y-> 7 X <> Y -> TRUE.


> > If X-> 9 , Y-> 7 X > Y -> TRUE.

This function is only valid for same data types

<= <= If X-> 5 , Y-> 7 X <= Y -> TRUE.


>= >= If X-> 3 , Y-> 7 X >= Y -> FALSE.


LIKE Like test If X-> Solaris , M-> Sol X LIKE M% -> TRUE.

Allows to perform a search based on a pattern, rather thanspecifying exactly what is desired or spell out a range.

This function is only valid for same data types. The used wildcardis ’%.’

IF If condition If t-> TRUE IF (t, v1, v2) returns v1

If t-> FALSE IF (t, v1, v2) returns v2

IsNUL Test NULL value If X-> 0 IsNUL X -> TRUE

This function is valid for Boolean Arguments.

IsDiv0 Test the dived by zero If X-> division by zero result IsDiv0 X -> TRUE

This function is only valid for real numbers.

3BK 21216 AAAA PCZZA Ed.26 197 / 664


Specific Functions: NZ, NV, TDIV0, TDIV, IF, TIME_MEASURED

Short name Name Scenarios

NZ Null to Zero If x -> scalar value(other than indicator) NZ ( x ) fails.

If x -> indicator (of null value)

NZ ( x ) returns zero.

NV Null to Value If x-> indicator (of null value),v->specific value NV ( x, v )returns v.

If x-> indicator (not null value),v->specific value NV ( x, v )returns x.

TDIV Divided with a test onDenominator

If d= 0, TDIV ( x, d, v ) returns v

If d<> 0, TDIV ( x, d, v ) returns x/d

Statistical Functions: OFFERED, OFFERED_ERLANGC,

OFFERED_POISSON, OFFERED_REQUIRED,OFFERED_REQ_ERLANGC, OFFERED_REQ_POISSON,

GOS, GOS_ERLANGC, GOS_POISSON’OFFERED’ functions indicate the offered traffic according to the Erlang Blaw. The used argument is the number of channels, GoS.

To Scalar Functions: V_INDEX, V_MAXIMUM, V_MINIMUM, V_TOTAL,

V_AVERAGE, V_MAX_INDEX, M_MAXIMUM, M_MINIMUM, M_TOTAL,M_AVERAGE

To Vector Functions: VECTOR, ARRAY, REVERSE, MAXIMUM_COL,MINIMUM_COL, TOTAL_COL, AVERAGE _COL, MAXIMUM_ROW,

MINIMUM_ROW, TOTAL_ROW,AVERAGE_ROW, CUMUL,

CUMUL_REVERSE, SUMPRODUCT_COL, SUMPRODUCT_ROW,INTERVAL, MIDDLE, MIDDLE_POS, MIDDLE_LEV, V_ROUND, V_IF,

M_ROW_INDEX, SUMPRODUCT_COLN, SUMPRODUCT_ROWN

198 / 664 3BK 21216 AAAA PCZZA Ed.26


To Matrix Functions: MATRIX, MATRIX_COL, MATRIX_ROW, ARRAY_COL,ARRAY_ROW, V_PRODUCT, M_PRODUCT, CUMUL_COLS,

CUMUL_ROWS, CUMUL_REVERSE_COLS, CUMUL_REVERSE_ROWS,REVERSE_COL, REVERSE_ROW, TRANSPOSE, M_ROUND, M_IF

Short name Name Type Scenarios

+

-

*

/

+

-

*

/

Vector, Matrix If Vector-> V ,Matrix ->M

V * NULL = NULL

V + NULL = NULL

V - NULL = NULL

V / V = V

M * NULL = NULL

M + NULL = NULL

M - NULL = NULL

M / M = M

Note: The mathematical operation onmatrix are possible on matrices of the samedimension. When the mathematical operationis applied on matrices of different dimensions,then the output is NULL.

AND

OR

NOT

AND

OR

NOT

Vector, Matrix If Vector-> V, Matrix ->M, Boolean->b

V AND NULL = NULL

V AND b = V

M AND NULL = NULL

M AND b = M

IF If Vector, Matrix If Vector-> V1,V2 ,Matrix ->M1,M2 , Boolean->b

IF (b,V1,V2) returns V1 if b=true else V2.

IF (b,M1,M2) returns M1 if b=true else M2.

Vector Create a vectorfrom a scalar

Vector If Vector-> V, Scalar ->b, Length of vector ->n Vector(b,n) -> V

Array Create a vectorfrom a scalar list

Vector If Array-> A ,Scalar ->b,No. of elements-> nArray (b,n) -> A

Matrix Create a matrixfrom a scalar

Matrix S->Scalar, m,n ->Matrix dimension

Matrix(S,m,n)->M

Matrix_Col Create a matrixfrom a vector

Vector, Matrix If Vector-> V ,n ->Matrix dimension

Matrix_Col(V,n)->M

Matrix_Row Create a matrixfrom a vector

Vector, Matrix If Vector-> V ,n ->Matrix dimension

Matrix_Row(V,n)->M

3BK 21216 AAAA PCZZA Ed.26 199 / 664



Array_Col Create a matrixfrom a vector list

Vector, Matrix If No. of Vector-> Vs

Array_Col(Vs)->M

Array_Row Create a matrixfrom a vector list

Vector, Matrix If No. of Vector-> Vs

Array_Row(Vs)->M

V_Index Returnsthe scalarcorrespondingto the index

Vector If Vector-> V, S->Scalar,I->index

V_Index(V,i)->S

Maximum Returns themaximum valueof the vector orthe matrix

Vector, Matrix Maximum(V) -> S

Maximum(M) -> S

Minimum Returns theminimum valueof the vector orthe matrix

Vector, Matrix Minimum(V) -> S

Minimum(M) -> S

Total Returns the sumof all value ofthe vector or thematrix

Vector, Matrix Total(V) -> S

Total(M) -> S

Average Returns theaverage of allvalues of thevector or thematrix

Vector, Matrix Average(V) -> S

Average(M) -> S

V_Max_Index Returns theindex of themaximum value

Vector V_Max_Index(v) -> i

Maximum_Col Returns themaximum rowvalue in a columnvector

Vector, Matrix Maximum_Col(M) -> V

Maximum_Row Returns themaximumcolumn valuein a row vector

Vector, Matrix Maximum_Row(M) -> V

Minimum_Col Returns theminimum rowvalue in a columnvector

Vector, Matrix Minimum_Col(M) -> V

200 / 664 3BK 21216 AAAA PCZZA Ed.26



Minimum_Row Returns theminimum columnvalue in a rowvector

Vector, Matrix Minimum_Row(M) -> V

Total_Col Returns the sumrow value in acolumn vector

Vector, Matrix Total_Col(M) -> V

Total_Row Returns the sumcolumn value ina row vector

Vector, Matrix Total_Row(M) -> V

Average_Col Returns theaverage rowvalue in a columnvector

Vector, Matrix Average_Col(M) -> V

Average_Row Returns theaverage columnvalue in a rowvector

Vector, Matrix Average_Row(M) -> V

V_Product Returns thevector product

Vector, Matrix V_Product(M) -> V

M_Product Returns thematrix product

Vector, Matrix M_Product(M) -> V

Cumul Cumul thevalues in thevector (increase)

Vector Cumul(V) -> V

Cumul_Cols Cumul the rowvalues in thematrix (increase)

Matrix Cumul_Cols(M) -> M

Cumul_Rows Cumul thecolumn valuesin the matrix(increase)

Matrix Cumul_Rows(M) -> M

Cumul_Reverse Cumul thevalues inthe vector(decrease)

Matrix Cumul_Reverse(V) -> V

Cumul_Reverse_ColsCumul therow valuesin the matrix(decrease)

Matrix Cumul_Reverse_Cols(M) -> M

3BK 21216 AAAA PCZZA Ed.26 201 / 664



Cumul_Reverse_RowsCumul thecolumn valuesin the matrix(decrease)

Matrix Cumul_Reverse_Rows(M) -> M

SumProduct_Col Sum of theproduct of amatrix with arow (column inresult)

Vector, Matrix SumProduct_Col(M,V) -> V

SumProduct_Row Sum of productof matrix row(column in result)

Vector, Matrix SumProduct_Row(M,V) -> V

SumProduct_ColN Sum of theproduct of amatrix with acolumn (row inresult)

Vector, Matrix SumProduct_ColN(M) -> V

SumProduct_RowN Sum of productof matrix column(row in result)

Vector, Matrix SumProduct_RowN(M) -> V

Interval Returns theinterval betweentwo continuesvalues

Vector Interval(V) -> V

Middle Returns themiddle of twocontinues values

Vector Middle(V) -> V

Middle_POS Returns the’positive’ middleof two continuesvalues

Vector Middle_POS(V) -> V

Middle_LEV Returns the’level’ middleof two continuesvalues

Vector Middle_LEV(V) -> V

Round Returns theround of value invector or matrix

Vector, Matrix Round(V) -> V

Round(M) -> M

Round_Sup Returns thesuperior roundof value in vectoror matrix

Vector, Matrix Round_Sup (V) -> V

Round_Sup (M) -> M

202 / 664 3BK 21216 AAAA PCZZA Ed.26



Round_Inf Returns theinferior roundof value in vectoror matrix

Vector, Matrix Round_Inf(V) -> V

Round_Inf (M) -> M

Reverse Returns thereverse vector

Vector Reverse(V) -> V

Reverse_Col Returns thereverse rowmatrix

Matrix Reverse_Col(M) -> M

Reverse_Row Returns thereverse columnmatrix

Matrix Reverse_Row(M) -> M

Transpose Returns thetranspose matrix

Matrix Transpose(M) -> M

Topology Functions: SUM, COUNT, AVG, MAX, MIN.

Short name Name Scenarios

COUNT Count COUNT() returns number of normalized values

SUM Sum If a,b,c -> normalized values

SUM(a,b,c) returns the sum

AVG Average If a,b,c -> normalized values

AVG(a,b,c) returns the average value

MAX Maximum If a,b,c -> normalized values

MAX(a,b,c) returns the maximum value

MIN Minimum If a,b,c -> normalized values

MIN(a,b,c) returns the minimum value

Topology counting indicators

Those indicators are composed of a single function call, any of the threefunctions below can be used:

OBJECT_COUNT(<object_type>)

CHILDREN_COUNT(<children_type>)

CHILDREN_COUNT()

The indicators defined using the OBJECT_COUNT function are by defaultavailable on every object type and daily levels because OBJECT_COUNTsimply returns the number of objects for a given type at a given date.

3BK 21216 AAAA PCZZA Ed.26 203 / 664


The indicators defined using the CHILDREN_COUNT functions are availableonly on every object type and daily levels because they return the numberof children for a given object on a given date.Their spatial aggregation method is SUM, interpolation method isPREVIOUS.

Log counting indicatorsA single function call is used: LOG_COUNT(‘<filtering expression>’).The indicators defined using the LOG_COUNT function are available onevery object type and daily levels because LOG_COUNT simply returns thenumber of logs matching a filter on a given date. Their spatial aggregationmethod is SUM, interpolation method is PADDING(0).

Alarm counting indicatorsA single function call is used: ALARM_COUNT(‘<filtering expression>’).The indicators - defined using the ALARM_COUNT function - are availableon every object type and daily levels because ALARM_COUNT simplyreturns the number of alarms matching a filter on a given date.Such an indicator returns information about the number of active alarms foreach period inside a time interval.

The filtering expression allows filtering on:

The oject type

The event type

The severity

The probable cause

The specific problem

And the friendly name.

Their spatial aggregation method is SUM, interpolation method isPADDING(0).

Alarm outage indicatorSimilar to alarm counting indicators but it sums the alarm outage time (cleartime – event time) instead of simply counting alarms.

Alarm Cut-off indicators.

Braces (“{”, “}”) are not supported for boolean expressions.

204 / 664 3BK 21216 AAAA PCZZA Ed.26


10.1.12 Propagate Counters and Indicators

You can propagate:

Counters to IndicatorsThis retrieves all indicators using, directly or indirectly, the selected countersin their formula.

Indicators to:

CounterThis retrieves all used counters, directly or indirectly, in the selectedindicators formula.

View TemplateThis retrieves all view templates using the selected indicators in theirtabular list.

DiagnosisThis retrieves all diagnosis for which the indicator is their trigger.

THLThis retrieves all Thematic Layers Templates referencing the selectedindicators.

Use the following procedure to propagate the selected item to thecorresponding function tree:

1. Click on the item you want to propagate.

If it is a leaf node, it is selected. If it is a non-leaf node, all items under thatnode are selected.


2. Drag the selected item and drop it to needed function tab. The mouse

pointer changes to .

3. Depending on how the parameter ’Display time before a tab is raised andmade active’ is set as a user preference, the target counter tree:


You have to switch to the target counter tree to view it.


3BK 21216 AAAA PCZZA Ed.26 205 / 664


10.1.13 Indicators Restrictions After B9 NPA Data Import into NPO


The following restrictions are applicable for indicators migrated from NPA toNPO:

Reliability indicatorsIn both NPA and NPO the reliability indicators follow the group structureof the stored indicators groups. When groups change (split/join), the oldreliability indicators are no longer relevant. The group structure is verydifferent in NPO compared to NPA, this is why the reliability indicators areignored during data import. So for the historical data, the reliability indicatorsdo not hold any values in NPO. Therefore you should not check the reliabilitywhen displaying the historical data - all this data appears as “unreliable”.

B8 specific indicatorsNPA B9 tables contain several columns for B8 specific indicators. WhenNPA data is imported to NPO the whole network is swapped to B9, howeverthere may still be some historical B8 values visible in NPA. As NPO supportsB9/B10 GSM releases, the B8 specific indicators are not present in NPO, sothe historical B8 data is not imported in NPO.

NPA B9 MR1 specific indicators, removed in B9 MR4As NPO dictionaries are aligned with B9 MR4, migration from NPA B9 MR1is possible but with some restrictions. The indicators present in MR1onlyand removed in MR4 are not imported in NPO.

Provisioned or unused indicatorsSeveral provisioned stored indicators present in the NPA database are notmigrated to NPO.

10.2 Display Counters and IndicatorsTo display the values of the counters and indicators, select them and theappropriate network object(s) and execute them in a view. Refer to ExecuteView (Section 18.4.1).

Indicators are classified as Basic/Calculated Indicators andScalar/Vector/Matrix/Axis Indicators.

10.3 Display Counter PropertiesSee Display and Edit Properties (Section 3.3).

206 / 664 3BK 21216 AAAA PCZZA Ed.26


3BK 21216 AAAA PCZZA Ed.26 207 / 664


ParameterName


Counter_Ref Unique reference of the counter Yes Yes

Long Name Long Name of the counter Yes Yes

Description Description of the counter Yes Yes

Source NetworkObject

Source network object associated with the counter. Yes Yes

SupportedReleaseInformation

Supported Release Technology - The release technology ofthe counter

Supported Release Supplier - The release supplier of thecounter

Supported Release Name - The release name of the counter

Supported Release Version - The supported release version

Supported Release Description - The supported releasedescription.

Yes Yes

Source NetworkObject

Source network object associated with the counter. Yes Yes

CollectionNetwork Object

Type of network object reporting the counter Yes Yes

PM Type Data Type (type 110, 180…) must match with indicator PM Type Yes Yes

Value Type Type of counter (integer, float…) Yes Yes

Unit Unit of the counter (%, db…) Yes Yes

Precision Precision of the value at the display. Must be power of 10 Yes Yes

Default RP Default permanent reporting period Yes Yes

Algorithm Type Algorithm type describes the method used to compute thecounter (asynchronous cumulative, synchronous cumulative,sampling…)

Yes Yes

SamplingPeriod

Value of the sampling period when the algorithm type issampling

Yes Yes

Load mapformula

CounterValue = PM value * constant

This field describes the value of the constant (by default theconstant is 1)

Yes Yes

Consolidationmethod

Type of normalization (Sum, Average, Max, Min…) Yes Yes

Interpolationmethod

Default type of interpolation (No, Zero, linear…) Yes Yes

208 / 664 3BK 21216 AAAA PCZZA Ed.26


ParameterName


Domain Name Domain name of the counter Yes Yes

AssociatedFamilies

Table of associated family and sub families of the counter.

Family - The family to which this counter belongs.

Sub-Family Depth 1 - The sub-family to which this counter

belongs

Sub-Family Depth 2 - The sub-sub-family to which this

counter belongs

Sub-Family Depth 3 - The sub-sub-sub-family to which thiscounter belongs


this counter belongs.

No Yes

DictionaryInformation

Dictionary Name - Name of the counter dictionary

Dictionary Version - Version of the counter dictionary

Dictionary Date - Publishing Date of the counter dictionary

Dictionary Auth - Author of the counter dictionary

Dictionary Desc - Description of the counter dictionary.

Yes Yes

For vector counters , the following additional parameters apply:

ParameterName


Size Max size of the vector. Yes Yes

Axis Counter The axis counter reference name. Yes Yes

For matrix counters , the following additional parameters apply:

ParameterName


Size (X) Max size of the X for the matrix. Yes Yes

Size (Y) Max size of the Y for the matrix. Yes Yes

X Axis Counter The X axis counter reference name Yes Yes

Y Axis Counter The Y axis counter reference name Yes Yes

For axis counters , the following additional parameters apply:

3BK 21216 AAAA PCZZA Ed.26 209 / 664


ParameterName


Size Max size of the axis No Yes

DependantColumns

Indicates whether the column displayed in HMI must beattached or not.

No Yes

First ColumnBoundaryIncluded

Inform the HMI whether the first column includes the first valueof the axis indicator or not.

No Yes

Last ColumnBoundaryIncluded

Inform the HMI whether the last column includes the last valueof the axis indicator or not.

No Yes


Inform the HMI whether the last value of the previous columnis included or not.

No Yes

210 / 664 3BK 21216 AAAA PCZZA Ed.26


10.4 Display Type 110 Counters


Select the appropriate cell and select Display type 110 counters... .

The Properties page of the PM 110 type counters related to the selectedcell is displayed.

ParameterName

Description Mandatory Read-only

ModeName

Name of the Mode Yes Yes

Cell Id The id of the cell provided in the URL(<MCC>-<MNC>-<LAC>-<CI>)

Yes Yes

Cell Label Label of the cell Yes Yes

Start Time Start time of the PM counter Yes Yes

3BK 21216 AAAA PCZZA Ed.26 211 / 664


ParameterName

Description Mandatory Read-only

End Time End time of the PM counter Yes Yes

ExecutionTable

This table contains the execution results for anexecute view of all the counters related to theselected cell and its corresponding mode networkobjects for which the execution is carried out.

The following parameters compose the ExecutionTable:

Counter Name - Name of the Counters for theSelected network object

Long Name - Long name of the counter

Network object - The network objects of theselected mode related to the selected cell.

212 / 664 3BK 21216 AAAA PCZZA Ed.26


10.5 Display Indicator PropertiesSee Display and Edit Properties (Section 3.3).

3BK 21216 AAAA PCZZA Ed.26 213 / 664


ParameterName


Name Name of the indicator Yes Yes

Indicator_Refor ReferenceName

Unique reference of the indicator Yes Yes

Description Description of the indicator Yes Yes

Owner Operator who created the indicator Yes Yes

Unit Unit of the indicator Yes Yes

Precision Precision of the value. Must be a power of 10. Yes Yes

214 / 664 3BK 21216 AAAA PCZZA Ed.26


ParameterName


ReliabilityIndicator

Name of the indicator used as reliability indicator SamplingIndicator Name of the indicator used as sampling indicator

Yes Yes

Families Table of associated family and sub families of the indicator.

Family - The family to which this counter belongs.

Sub-Family Depth 1 - The sub-family to which this counterbelongs


counter belongs


counter belongs

Sub-Family Depth 4 - The sub-sub-sub-sub-family to whichthis counter belongs.

No Yes

AvailabilityDomain

Availability Domain of the indicator, It is the list of object type ateach temporal level where the indicator is available.

Yes Yes

Threshold andseverity Graph

A graphic representing the threshold and severity Yes Yes

Upper is fault Flag for quality of indicator Yes Yes

Value Type Indicator type (integer, float, Boolean) Yes Yes

SpatialAggregation

Operation used to perform the spatial aggregation TemporaryWhether the indicator is a temporary indicator or not.

Yes Yes


Dictionary Name - Name of the indicator dictionary

Dictionary Version - Version of the indicator dictionary

Dictionary Date - Publishing Date of the indicator dictionary

Dictionary Auth - Author of the indicator dictionary

Dictionary Desc. - Description of the indicator dictionary

Yes Yes

IndicatorFormula

Formula to calculate the indicator. Yes Yes


Supported Release Technology - The release technology ofthe indicator

Supported Release Supplier - The release supplier of theindicator

Supported Release Name - The release name of the indicator


Supported Release Description - The supported releasedescription.

Yes Yes

3BK 21216 AAAA PCZZA Ed.26 215 / 664


For basic indicators , the following additional parameters apply:

ParameterName


ConsolidationMethod

Consolidation method (sum, Count, Average, Min, Max) Yes Yes

SupportsDynamicInterpolation

A flag specifying if interpolation change is allowed or not. Yes Yes

InterpolationMethod

Type of interpolation Yes Yes

Pad Value Value if interpolation method is Padding. Second InterpolationMethod Type of interpolation Pad Value Value if interpolationmethod is Padding. Group Name Name of the indicator group

No Yes

SecondInterpolationMethod

Type of interpolation No Yes

Pad Value Value if interpolation method is Padding. No Yes

Group Name Name of the indicator group Yes Yes

SupportedReleaseInformation(Multipleinformation incase of BasicIndicators)

Supported Release Technology - The release technology ofthe indicator

Supported Release Supplier - The release supplier of theindicator

Supported Release Name - The release name of the indicator


Supported Release Description -The supported releasedescription

Yes Yes

Aggregate onLoading

Method to be used to perform spatial aggregation to n+1 levelat loading time (possible values: “sum”, “avg”, “count”, “min”,“max” and “none” (default)). When loading time aggregationis used for an indicator, that indicator is placed in a derivedindicator group (same name + “_sal”.

No Yes

Formula Formula of the counter Yes Yes

For stored temporal aggregations , the following parameters apply:

216 / 664 3BK 21216 AAAA PCZZA Ed.26


ParameterName


ReferenceExtension

Reference extension of the temporal aggregation. Thisextension has to be merged with the reference of the telecomindicator

Yes Yes

Group Group to which the indicator belongs Yes Yes

TemporalAggregationMethod

Function used to perform temporal aggregation (fromNormalized table to Daily, or weekly or Monthly, busy hour).

Yes Yes

Relevant Hour All hours or working hours. By default the value is All hours.Allow computing consolidation only for relevant hours.

Yes Yes

Busy HourIndicator

Long name of the indicator used as reference indicator tocompute the busy hour.

No Yes

For calculated temporal aggregations , the following parameters apply:

ParameterName


Formula Formula (of telecom indicators – basic, calculated, temporalaggregation – long names) used to compute the temporalaggregation of a calculated indicator.

Yes Yes

For axis indicators , the following additional parameters apply:

ParameterName


Size Maximum size Yes Yes

Bound Min Minimum bound Yes Yes

Bound Max Maximum bound Yes Yes

Display Whether the axis indicator is to be displayed as label as it is Yes Yes

For vector indicators , the following additional parameters apply:

ParameterName


Size Maximum size Yes Yes

Axis X Axis Indicator for X Axis Yes Yes

3BK 21216 AAAA PCZZA Ed.26 217 / 664


For matrix indicators , the following additional parameters apply:

ParameterName


Size (x * y) Maximum x and y axis size Yes Yes

Axis X Axis Indicator for X Axis Yes Yes

Axis Y Axis Indicator for Y Axis Yes Yes

10.6 Find Indicator from CounterIndicator trees can be searched for the indicator referencing a specified counter.

1. In the indicator tree, right click and select Find Indicator from Counter .

The "Search Indicator by Counter Name" window opens.

2. Type the full reference name of the counter by which the indicator tree issearched, then click on [ Search ].

If any node is already selected in the indicator tree, the first indicatorafter the selected node which uses the counter whose reference name isspecified is selected in the tree.

If any node is not already selected in the indicator tree, the first indicatorreferencing the counter whose reference name is specified is selected inthe tree.

10.7 Indicator Template Editor

10.7.1 Open Indicator Editor

Open the Indicator Editor:


In the Alcatel-Lucent Analysis Desktop window, in the right frame, in the

’Indicator’ tab, right click on any displayed indicator and select Indicator , OR

218 / 664 3BK 21216 AAAA PCZZA Ed.26


In the Analysis Desktop main window, click on Data -> Indicators... , OR

Press Ctrl+N.

3BK 21216 AAAA PCZZA Ed.26 219 / 664


The Indicator Editor window opens.

220 / 664 3BK 21216 AAAA PCZZA Ed.26


10.7.2 Create Indicator

Alcatel-Lucent recommendation is to create only calculated indicators.The system proposes by default a calculated indicator, and the operator mustexplicitly override the default to create a basic indicator.

Create an Indicator:

1. In the ’Indicator Editor’ window, click on .

The ’Indicator Type’ window opens.On the right panel, the system shows:

Available indicators sorted by structure type and then by family, bothvisible and non-visible can be selected

Available parameters sorted by family / sub-family

Available functions.

2. Select the appropriate Indicator Type (Scalar, Vector, Matrix, Axis), then clickon [ OK ] OR double click on the appropriate Indicator Type.

The property editor appears with default values and editable fields.


FieldName


Reference Reference of the indicator to be created.

For Presentation Indicator, it is the reference of the telecomindicator

For Temporal Aggregation, it is Indicator.Reference +

TemporalAggregation.ReferenceExtension

Name Name of the indicator to be created.

Dictionary Dictionary name where the indicator is created.

The dictionary is identified by the name and the owner. System andcustomer dictionary may share the same name.


Owner User who is creating the indicator.

This field is read-only


Description Text box to be filled in with operator description for the currentindicator.

3BK 21216 AAAA PCZZA Ed.26 221 / 664


FieldName


Value Type Indicator value type:

Float - corresponding to 32 bit floating point number

Integer - the maximum number of digit is 12

Boolean - only for display, not calculation.

The conversion is done in the following way:

From Float to Integer: round to the nearest value

From Float to Boolean: 0 is converted to FALSE, and everything

else is converted to TRUE.

Float

AccessRights

Access rights for Public or Private Private.

Unit Indicator value measurement unit.

Select from the drop down list the appropriate unit, based on theunits of the already present indicators. The administrator can alsocreate their own units.

The indicator is multiplied by 100 if % unit is used.

Next you have to choose to create a Calculated Indicator, or Basic (Stored)Indicator.

4. For Calculated Indicator , perform the following steps:

Click on the [ Calculated ] radio button

In the ’Formula’ field, type the formula you want to use.For this drag from the right panel the appropriate indicators and thenecessary operators / functions (refer to Indicator Formula Operands(Section 10.1.11)), and drop them in the ’Formula’ field.

Click on [ Check Formula ] to verify the typed formula.If it is incorrect, an error message appears indicating the cause ofthe error: syntax error, unknown formula and/or indicators. Correctit until it is valid.

To make this calculated indicator a temporary one, select TemporaryIndicator .Temporary Indicators can only be private. They have a life-durationlimited to the current user session, and are automatically deleted whenthe Analysis Desktop is stopped.

222 / 664 3BK 21216 AAAA PCZZA Ed.26


5. For Basic (Stored) Indicator , perform the following steps:

Click on the [ Basic (Stored) ] radio buttonThe system checks if the maximum number of customer storedindicators has been reached. If yes, the operation is rejected; if no,you can continue.

Add the first and second interpolation methods. If ’Padding’ is selected,

add the padding number in the ’Pad Value’ field

Choose to have or not dynamic interpolation, using the ’Support Dynamic

Interpolation’ buttonUnselecting ’Support Dynamic Interpolation’ annuls the interpolationmethod(s).

Add the appropriate Consolidation Method, by choosing one of the

following: Sum, Count, Average, Maximum, Minimum

Add the appropriate Spatial Aggregation, by choosing one of the

following:: Sum, Count, Average, Maximum, Minimum, None

Add an indicator group.

You can either:

Select a predefined compatible group (with the same PM type, source,and collecting network element) from the drop down list group, or

Create your own group:Click on [ Add Group ]. The "Add Group" window opens.Type the appropriate indicator group name.Select the Spatial Aggregation Path from the drop down list.Click on [ OK ] to associate the spatial aggregation path with thenewly created indicator group.

At least one and a maximum of five Indicator Formulas must be added.

Choose the Technology, Supplier, Release, Spatial Aggregation, thenadd the indicator formula in the ’Formula’ field. See Basic Indicators

(Section 10.1.2.1) for the allowed elements in formula.To check the validity of a basic indicator formula, select the formularow, right click on it and select [ Check Formula ].If it is incorrect, an error message appears indicating the cause ofthe error: syntax error, unknown formula and/or indicators. Correctit until it is valid.

Basic Indicators can have multiple formulae associated per

technology. Depending on the number of available technologies,formulas can be added.Right click on the ’Formula’ field and select [ Add ]. This adds a rowat the end of the table for indicator formula.

To remove a row in the ’Formula’ field, right click on it and select[ Remove ]

3BK 21216 AAAA PCZZA Ed.26 223 / 664


6. If needed , add a Temporal Aggregation by clicking on [ New TemporalAggregation ] (this step can be done several times, and it is the defaultchoice for a basic indicator).

Type the Reference Extension and Name of the temporal aggregation.The ’Name’ field may be left empty; in this case the temporal aggregationis displayed with the same name as the indicator.

Type the Description Extension.

Choose the unit, and the precision to which the indicator be rounded up.When available, the unit and the precision of the indicator are proposedas default value. The unit needs to be entered by the operator only whendifferent from telecom indicator.

Choose whether you want ’Percentage’ display or not.

Choose whether the Temporal Aggregation is ’Visible’ or not.

Select between ’Stored’ and ’Calculated’ temporal aggregation. The

default choice is stored.

For stored temporal aggregation , the system checks whether the

maximum number of customer stored indicators has been reached (forstored aggregation only).

If yes, the operation is rejected; if no, perform the following:

Choose a temporal aggregation function.If the chosen temporal aggregation is ’BusyHour’, add also the’BusyHour Indicator’.

Choose the relevant hours for the aggregation: all hours or just

working hours.

If needed, add a reliability indicator.

Add an indicator group.

You can either :

select a predefined compatible group (with the same PM type, andcollecting network element) from the drop down list group, or

create your own group:Click on [ Add Group ]. The "Add Group" window opens.Type the appropriate indicator group name.Select the Spatial Aggregation Path from the drop down list.Click on [ OK ] to associate the spatial aggregation path with thenewly created indicator group.

For calculated temporal aggregation , perform the following:

224 / 664 3BK 21216 AAAA PCZZA Ed.26


Add a formula that calculates the indicator. The same possibilitiesexist as for the formula of calculated indicator.

If needed, add a reliability indicator.

The system computes the availability domain. If necessary, unselectsome parts of it, but make sure it is not empty.

7. If needed , add an associated presentation indicator (it is possible toperform this step only once, this is the default choice for a calculatedindicator).Presentation is:

in the case of basic indicators - set as unchecked and one stored

temporal indicator is added

in the case of calculated indicators - added with no temporal indicators.

Perform the following:

Choose the unit, and the precision to which the indicator be rounded up.

Choose whether you want ’Percentage’ display or not.

Choose whether the presentation indicator is ’Visible’ or not.

Add a reliability indicator.

The system computes and displays the availability domain. If necessary,unselect some part of it, but make sure it is not empty.

8. If needed , add the appropriate Families .

An indicator can belong to a family and sub-family hierarchy. Up to fourdepths of sub family are currently supported. An indicator can belong tomore than one family and it is also possible that the indicator does notbelong to any family. Such indicators are visible only to the administrator.

Select or type a family and subsequently the sub families of the family arelisted. The same behavior is followed for all four levels of sub families.

To add a new family, right click on an existing family, and select [ AddFamily ]. A new row is created and you can select from the list, or typethe appropriate new family.

To remove an existing family, right click on an existing family, and select[ Remove Family ]. The row is deleted from the Families table.

9. If needed , add Threshold and Sampling .The following configurations are possible:

Both threshold and sampling are available

Either threshold or sampling is available

Neither threshold nor sampling is available.

3BK 21216 AAAA PCZZA Ed.26 225 / 664


When thresholds are enabled:

The thresholds / sampling table is displayed with thresholds columns,

and you can enter the values for each severity

The threshold graph is displayed as per Severity vs Value fieldWhen changing the severity value, its associated image (Severity Graphand Threshold Graph) is also be changed.

When sampling is enabled:

The thresholds / sampling table is displayed with the sampling columnand you can enter the values for each severity

The Sampling Indicator field is displayed and you can add the sampling

indicator for sampling.Indicators can be dragged and dropped into the Sampling Indicator field.

10. Click on to save changes.

The Analysis Desktop verifies all mandatory parameters, checks the formulasyntax, and checks that the availability domain is not empty.

When all verified data is correct, a confirmation message asks whether theindicator is to be saved or not. Click on [ OK ].

The indicator is created.

226 / 664 3BK 21216 AAAA PCZZA Ed.26


10.7.3 Create Customer Indicator by Copy

Indicators that are referencing at least one "hidden" indicator (nopresentation/no temporal aggregation) cannot be coppied.Laser indicators cannot be created by copy.

To create a Customer Indicator:

1. In the Indicator Editor window, select the indicator from which you want tocreate a copy.

2. Click on .

The ’Indicator Properties’ panel appears with a default name and editableproperties panel.

The name of the copied indicator respects the format <oldname>_copy_n ,where n is a number.

3. Update all needed editable fields.

4. Click on to save the changes.

10.7.4 Edit Customer Indicator

To edit a Customer Indicator:

1. In the Indicator Editor window, select the indicator to modify.

2. Click on .

The ’Indicator Properties’ panel appears with editable fields except forthe name.

3. Modify the fields as required.If you want to update the Availability Domain:

Click first on [ Check Formula ]. This recomputes the Availability Domainand sets its default values.

Update the appropriate values by unselecting the unnecessary parts.


10.7.5 Edit Indicator Threshold / Sampling Values

The threshold / sampling values can be modified for system and customerindicators of scalar type.

To edit an Indicator Threshold / Sampling Value:

1. In the Indicator Editor window, select the indicator to modify.

2. Click on .

The current threshold and sampling values along with other indicatorproperties are displayed in the ’Threshold & Sampling’ panel.

3. Modify as needed the sensitivity of the threshold / sampling values.


The modified indicator threshold / sampling value parameters are updated.

3BK 21216 AAAA PCZZA Ed.26 227 / 664


The modified threshold / sampling values are stored in the customerindicator dictionary.

10.7.6 Delete Indicator

To delete an indicator, select the indicator, then:

In the "Indicator Editor" window, click on , OR



Click on [ OK ] to confirm the deletion.

The confirmation of deletion checks that the indicator is not referenced byanother indicator, such as in the formula of another indicator, or as a Sampling,Reliability, Axis, or Busy Hour Indicator for another indicator, or is a part ofan existing view template.

The indicator is deleted.

228 / 664 3BK 21216 AAAA PCZZA Ed.26

11 Parameters

11 Parameters

This section describes how to manage radio parameters.

3BK 21216 AAAA PCZZA Ed.26 229 / 664

11 Parameters

11.1 Presentation

Note: The MUSE_PARAM_<TECHNO>_LICENSE license must be installed sothat the administrator can create parameters for a given technology (GSM,W-CDMA,…).

If the MUSE_PARAM_HISTORY_LICENSE license is not instaled, then thehistory of the parameters is not kept.

Radio parameters are used for:

Tuning, i.e. changing parameters, for that NPO allows to:

Display parameters

Compare parameters between cells

Show the history, in particular to correlate it with Qos variation.

compare it with planned value

compare it with referenced value

tuning.

QoS interpretation and reportingParameters are taken into account when comparing cells, object zones, andclassifications between themselves.

Radio parameters are used for QoS interpretation and reporting. Parametersare taken into account when comparing cells, object zones, and classificationsbetween themselves.

Parameters are also taken into account (for example the number of TRX)when computing some indicators.

Two types of parameters are defined:

Design parameters, that define the radio network architecture in term ofcoverage and mobility capability

Design parameters can have the following values:

An operational value that is in use in the network. The value is retrieved

from the OMC-R

A planned value.

Design parameters can have four sub-levels in the family hierarchy.

Logical parameters, also called telecom algorithm parameters, used tooptimize the telecom behaviour.

Logical parameter can have the following values:

An operational value that is in use in the network. The value is retrieved

from the OMC-R

A historical value that results from the value of the operational parameter

in the past

A forecast value that results from a tuning session and is used to changevalues in the network

A reference value which is the default value of a parameter for a givennetwork object. This value depends on the network object configuration,

230 / 664 3BK 21216 AAAA PCZZA Ed.26

11 Parameters

i.e. values of other parameters (for example, for GSM cells, on the celltype and cell class: urban, rural, number of TRX…)

A planed value coming from the planning tool.

Logical parameters can have four sub-levels in the family hierarchy.

3BK 21216 AAAA PCZZA Ed.26 231 / 664

11 Parameters

11.2 Display Logical/Design Parameter PropertiesSee Display and Edit Properties (Section 3.3).

Figure 13: Example of Logical Parameters Properties

232 / 664 3BK 21216 AAAA PCZZA Ed.26

11 Parameters

Figure 14: Example of Design Parameters Properties

The properties Of Design and Logical Parameters are:

3BK 21216 AAAA PCZZA Ed.26 233 / 664

11 Parameters

ParameterName


Name Name of the parameter Yes Yes

ReferenceName

Unique reference of the parameter Yes Yes

Formula Parameter formulae No Yes

Type Type of the Parameter

Can be: True/ Computed/ Free Field.

Yes Yes

Description Description of the parameter Yes Yes

Default Value Default Value of the Parameter No Yes

Min Minimum value of the parameter No Yes

Max Maximum value of the parameter No Yes

Unit Unit of the parameter Yes Yes

AvailabilityDomain

Availability Domain of the parameter, It is the list of object typeat each temporal level where the parameter is available.

Yes Yes

Step Step of the parameter. No Yes

Planned Parameter is planned or not. No Yes

Cell Zonecriteria

criteria for Cell Zone No Yes

Outaged Parameter is outaged or not. No Yes

Visible Parameter is visible or not. No Yes

TechnologySpecificAttributes

Set of name value pairs for a parameter of a technology. No Yes


Supported Release Technology - The release technology ofthe parameter

Supported Release Supplier - The release supplier of theparameter

Supported Release Name - The release name of the parameter


Supported Release Description - The supported releasedescription

Yes Yes

234 / 664 3BK 21216 AAAA PCZZA Ed.26

11 Parameters

ParameterName



Dictionary Name - Name of the parameter dictionary

Dictionary Version - Version of the parameter dictionary

Dictionary Date - Publishing Date of the parameter dictionary

Dictionary Auth - Author of the parameter dictionary

Dictionary Desc - Description of the parameter dictionary

Yes Yes

Families Table of associated family and sub families of the indicator.

Family - The family to which this parameter belongs.

Sub-Family Depth 1 - The sub-family to which this parameterbelongs

Sub-Family Depth 2 - The sub-sub-family to which thisparameter belongs


parameter belongs

Sub-Family Depth 4 - The sub-sub-sub-sub-family to whichthis parameter belongs

No Yes

11.3 Display ParametersTo display the values of the parameters, select them and the appropriatenetwork object(s) and execute them in a view. Refer to Execute View (Section18.4.1).

You can customize the way parameters are displayed, by changing the userpreferences. Refer to Configure User Preferences (Section 27.2).

3BK 21216 AAAA PCZZA Ed.26 235 / 664

11 Parameters

11.4 Propagate ParametersYou can propagate both design and logical parameters to:

View TemplateThis retrieves all View Templates referencing the selected parametersin their tabular list.

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

THLThis retrieves all Thematic Layer Templates referencing the selectedparameters.

Use the following procedure to propagate the selected parameter:

1. Click on the item you want to propagate.



2. Drag the selected parameter and drop it to needed function tab. The mouse

pointer changes to .





11.5 Manage Parameters

11.5.1 Import Parameters Dictionary

Parameter dictionaries describe all the supported parameters for the managednetwork objects. They are specific for each managed technology and release.

For the procedure to import parameter dictionaries into the NPO datawarehouse, refer to NPO Administration Guide, Import Dictionary.

11.5.2 Load Parameters Data

The parameters data of the whole network is loaded each night, or each timethe administrator wants to take into account a new configuration of the network.

See NPO Administration Guide, Load Radio Parameters.

11.5.3 Parameters Historical Data Purge

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

The purge process is launched every night after the daily import of operationalvalues. It deletes every history records that contain a date older of a specifiednumber of days than the current date.

236 / 664 3BK 21216 AAAA PCZZA Ed.26

11 Parameters

See PM Data Purge (Section 10.1.8) .

3BK 21216 AAAA PCZZA Ed.26 237 / 664

11 Parameters

238 / 664 3BK 21216 AAAA PCZZA Ed.26

12 Reference Values

12 Reference Values

This section describes the use of reference values.

3BK 21216 AAAA PCZZA Ed.26 239 / 664

12 Reference Values

12.1 Presentation

Note: The MUSE_PARAM_HISTORY_LICENSE license must be installed, so thatthe history of parameters is kept.

12.1.1 Definition

Reference values are Excel files that express the default value that a parameterfor a given network object should have.

These values depend on the network object configuration, i.e. values of otherparameters (for example, for GSM cells, on the cell type and cell class: urban,rural, number of TRX…).

Alcatel-Lucent publishes reference values for the parameters of its equipment.Some operators directly use Alcatel-Lucent reference values, others changethem to better suit their needs.

Note: For W-CDMA, the customer can create some, but no reference values fromAlcatel-Lucent.

12.1.2 Characteristics

A parameter dictionary can contain only one reference values Excel files.

The file is mono-release, unlike rules files that are multi-releases.

The xls reference values file can contain several sheets: each sheet containsreference values for one type of object or relation.

Each sheet contains:

A list of a parameters for a given object typeFor one type of objects, several sheets can be created and parameterscan be grouped as wished by the operator, but one sheet contains onlyreference values for one object type.Each parameter can have a ’ParamVersionInfo’ for a given release and agiven object type. The Parameter Version Info describes the parameter andthe object on which the parameter is applied.

A list of criteria that defines the conditions when the reference value apply

The reference values themselves.

On the fields, some parameters may be changed for local optimization(“tuning”). That is why the reference value is composed of:

A minimum value - the tuning should not go below this value

A maximum value - the tuning should not go above this value

A reference value - this should be the value used when the cell wascreated.

Note: The layout used by Excel (font, bold, italic, cell colors, cell border, comments…)has no impact on NPO.

240 / 664 3BK 21216 AAAA PCZZA Ed.26

12 Reference Values

12.1.3 File Header

Each sheet of the xls reference values contains a header in the following form:

1 <Parameter name 1> <Parameter value 1>


3 <Comment>


n Start

The header is contained in the first two columns (A and B).

For each line, the header contains either:

a parameter name in column A and the parameter value in column B, or

a comment, that can be any string from column A, that is not a known

parameter.

Parameter names are case insensitive. If a parameter name is present severaltimes, only the first occurrence is taken into account.

Comments are ignored.

The header stops when column A contains the keyword "start" (caseinsensitive).

Figure 15: Example of Reference Values Header

Some parameters are only meaningfull on the first sheet; others are definedon each sheet.

Name Description Mandatory Scope

Dictionary Dictionary name or technology standard asdefined in the Parameters dictionary.

Yes Apply to the file.

Present only in first sheet.

Author Author’s name No Apply to the file.


3BK 21216 AAAA PCZZA Ed.26 241 / 664

12 Reference Values

Name Description Mandatory Scope

Date Document date No Apply to the file.


Supplier Supplier type:

Standard

Alcatel-Lucent

Customer.

The same supplier can be used in severalsheets.

Yes Apply to the sheet.

Type Type of the network object the rule is appliedon, as defined in the topology metadata.(e.g. CELL2G).

The same type can be used in severalsheets.


Table 5: Description of Parameters from the Reference Values Header

12.1.4 Columns Header

Below the rule file header, the first two lines contain the columns header.

In the two lines of the columns header, column A contains the header for thecolumn containing parameter names (e.g. the label ’Parameters’).

Columns B, C and D contain the header for the default values columns (e.g.label ’Default’ on the first line and labels ’min’ ’ref’ and ’max’ on the secondline). Theses headers are only for presentation purposes.

Starting at column E, cells are grouped three by three: for minimum, referenceand maximum value. For each group, the first line contains a criteriaexpression, that must match the grammar described in Expression Grammar(Section 12.1.7). The second line is only for presentation purpose (labels’min’ ’ref’ and ’max’).

Figure 16: Example of Columns Header for Reference Values File

242 / 664 3BK 21216 AAAA PCZZA Ed.26

12 Reference Values

12.1.5 Reference Values Data

After the columns header, the next lines contain the reference values data, oneset of reference values for a given parameter per line.

Columns A, B, C and D define the following:

Column Description Mandatory

A The parameter name (e.g. A_LEV_HO). Yes

B Default minimum value (only numerical values). No

C Default Reference value. No

D Default maximum value (only numerical values). No

All next columns are grouped three by three, and contain the following:

Column Description Mandatory

E Minimum Reference value for the correspondingcriteria (only numerical values).

No

F Reference value for the corresponding criteria. No

G Maximum Reference value for thecorresponding criteria (only numericalvalues).

No

The following rules apply:

If a minimum value is given then a maximum value must be given (and

vice-versa)

If minimum and maximum values are given, the reference value must

be given

If the reference value is given but the minimum and maximum are empty itmeans that, if the criteria matches, the parameter has no minimum and

maximum values.

If the three are empty it means that, even if the criteria matches, it is nottaken into account and the next criteria (on the left) is checked. The default

reference values (minimum, maximum or the three) can be empty, in thiscase, nothing is returned.

Figure 17: Example of Reference Values Data

3BK 21216 AAAA PCZZA Ed.26 243 / 664

12 Reference Values

12.1.6 Reference Values Evaluation

The evaluation of criteria starts with the rightmost one first, and then criteria isevaluated from right to left until one is matched. If none matches, the defaultvalues are used.

The criteria in the xls file is evaluated starting with the Reference value (min,max and reference value).

A next Reference value is linked to it, it contains the criteria to evaluate if thefirst one is false and the associated minimum, maximum and reference values.The default Reference value is the last one (not linked to a next Referencevalue) if the criteria expression is empty; otherwise it means that the parameterhas not default values.

12.1.7 Expression Grammar

The following grammar is used to check reference values and rules expressions:

Tokens

Whitespace <<[ \t\n\r]+>> %ignore%

Number <<[0-9]+>>

Identifier <<[a-zA-Z][a-zA-Z0-9$#_]*>>

RelationSel <<[SsTt]:>>

S for Source, T for Target

TopoSel <<[a-zA-Z][a-zA-Z0-9$#_]*:>>

Dot "."

Comma ","

Left Parenthesis "("

Attention: Round brackets are only supportedfor numerical expressions.

Right Parenthesis ")"

Attention: Round brackets are only supportedfor numerical expressions.

Colon ":"

Square brackets are not supported.

Basic operators

Plus "+"

Minus "-"

244 / 664 3BK 21216 AAAA PCZZA Ed.26

12 Reference Values

Multiply "*"

Divide "/"

Boolean/logical functions

NOT "NOT"

AND "AND"

AND is evaluated before OR condition.

OR "OR"

Do not use any kind of brackets (round or square) for the logical evaluation.

Expresion functions

EQ "="

NE "<>"

LT "<"

LE "<="

GE ">="

GT ">"

LIKE "LIKE"

BETWEEN "BETWEEN"

Productions

BooleanExpr [NOT] BooleanTerm [BooleanExprRest] ;

BooleanExprRest AND BooleanExpr | OR BooleanExpr ;

BooleanTerm "[" BooleanExpr "]" | Expression RelationalOperatorExpression | BETWEEN Expression AND Expression |StringComparator PTEXT;

RelationalOperator EQ | NE | LT | LE | GE | GT ;

StringComparator LIKE | EQ;

Expression Term [ExpressionRest] ;

3BK 21216 AAAA PCZZA Ed.26 245 / 664

12 Reference Values

ExpressionRest "+" Expression | "-" Expression ;

Term Factor [TermRest] ;

TermRest "*" Term | "/" Term ;

Factor Atom | "(" Expression ")";

Atom Numerical | Parameter ;

Parameter [TOPOSEL|RELATIONSEL]IDENTIFIER;

Numerical ["-"]NUMBER["."NUMBER] ;

Examples:(((IFBAND1+1)*2)-2)/(IFBAND2-IFBAND2+2) = IFBAND1(IFBAND1*2)/2 = IFBAND1 AND IFBAND1 <> IFBAND2

12.1.8 Compare Different Values of Reference Values

You can troubleshoot for parameter related problems by comparing their current’Operational’ values against their ’Reference’ values to see which values havebeen changed from the default values.

Note: For W-CDMA, it is possible only one reference value per parameter.

1. Select the appropriate network elements (e.g.: BSCells) and Designparameters, then:

Drag and drop them in the Tabular / Graphical Viewer, OR

Select from the menu bar View -> Execute View... , OR

Press Ctrl+Q.

The ’Execution Context’ window appears.

2. Enter the appropriate information, as presented in Execution Context(Section 3.7), selecting ’Hour’ periodicity, the appropriate ’Date’ and ’Time’.

3. Click on [ Execute ] to execute the view.

The values related to the dropped objects are displayed in the ExecutedTabular / Graphical Viewer.

4. Choose from the combo box the appropriate values to display (e.g. Date, orOperational Value).

5. Show Legend (Section 18.5.3).

6. In the "Legend" window, ’Parameter Comparison’ frame, choose to comparethe appropriate Source and Target values (e.g.: ’All’ values to ’Reference’,or values before and after a migration or upgrade).

246 / 664 3BK 21216 AAAA PCZZA Ed.26

12 Reference Values

7. Rotate / Inverse Axis of Graphical View (Section 18.4.3.8) to be able tofilter by parameters.

Parameter names are now positioned in the rows of the table, while thenetwok elements (cells) are in the columns.

8. In the "Legend" window, choose to hide the OK values by selecting the“Hide” checkbox for green color.

The remaining values are those for which at least one cell the value is notequal to the default value.

3BK 21216 AAAA PCZZA Ed.26 247 / 664

12 Reference Values

12.2 User Defined Reference ValuesTo create a new reference values file, you have to export an existing file, edit itas appropriate, then import it in NPO.

The import / export / delete of reference values is described in NPOAdministration Guide, the following chapters:

Import Reference Values

Export Reference Values

Delete Reference Values .

248 / 664 3BK 21216 AAAA PCZZA Ed.26

12 Reference Values

Figure 18: Example of Reference Values File

3BK 21216 AAAA PCZZA Ed.26 249 / 664

12 Reference Values


250 / 664 3BK 21216 AAAA PCZZA Ed.26

12 Reference Values


3BK 21216 AAAA PCZZA Ed.26 251 / 664

12 Reference Values

252 / 664 3BK 21216 AAAA PCZZA Ed.26

13 Rules

13 Rules

This section describes the use of rules.

3BK 21216 AAAA PCZZA Ed.26 253 / 664

13 Rules

13.1 Presentation

Note: The MUSE_CUSTOMER_RULES_LICENSE license must be installed, so thatthe rules where the supplier is “customer” can be imported and exported.

13.1.1 Definition

Rules are Excel files that express the dependency between two or moreparameters of a given object, and are stored in the Oracle database.

To indicate when a rule is applicable, conditions and expressions on otherparameters are defined inside it.

13.1.2 Classification

Depending on their supplier, three types of rules are defined:

Standard rules are provided by Alcatel-Lucent, and are related to thestandard itself, regardless of the firm producing the equipment (e.g. GSM

rules as defined by the standard)

Alcatel-Lucent rules are provided by Alcatel-Lucent, and are related toAlcatel-Lucent equipments

Customer rules are rules defined by the operator (Import/export of

customer rules are subject to the MUSE_CUSTOMER_RULES_LICENSE).

Depending on their type, rules can be:

System rules are the expression of a dependency between object

parameters, as they appear in standardization documents

Expert rules are rules that results from experience.

13.1.3 Characteristics

A parameter dictionary can contain several rule Excel files, but a file containsrules for only one dictionary.

The xls rule file can contain several sheets: each sheet contains rules for agiven dictionary, a given supplier, and a given object type.

A rule file can be:

multi-type, one type per sheet, but types can also be split into several files

multi-supplier (e.g. one sheet for Standard rules and one sheet for

Alcatel-Lucent rules), but rules from different supplier types can also besplit into several files

multi-release (unlike reference values files that are mono-release).

The name of a rule file is unique for a dictionary and object type.

Rules can be checked:

on objects in the Analysis Desktop

when applying a Tuning Session.

254 / 664 3BK 21216 AAAA PCZZA Ed.26

13 Rules

13.1.4 File Header

Each sheet of the xls rule contains a header in the following form:



3 <Comment>


n Start

The header is contained in the first two columns (A and B).

For each line, the header contains either:

a parameter name in column A and the parameter value in column B, or

a comment, that can be any string from column A, that is not a known

parameter.

Parameter names are case insensitive. If a parameter name is present severaltimes, only the first occurrence is taken into account.

Comments are ignored.

The header stops when column A contains the keyword "start" (caseinsensitive).

Figure 21: Example of Rule Header

Some parameters are only meaningfull on the first sheet; others are definedon each sheet.

Name Description MandatoryScope

DictionaryDictionary name or technologystandard as defined in theParameters dictionary.

Yes Apply to the file.

Present only in firstsheet.

Author Author’s name No Apply to the file.


3BK 21216 AAAA PCZZA Ed.26 255 / 664

13 Rules

Name Description MandatoryScope

Date Document date No Apply to the file.


SupplierSupplier type:

Standard

Alcatel-Lucent

Customer.

The same supplier can be usedin several sheets.


Type Type of the network object therule is applied on, as definedin the topology metadata. (e.g.CELL2G).

The same type can be used inseveral sheets.


Table 6: Description of Parameters from the Rules Header

256 / 664 3BK 21216 AAAA PCZZA Ed.26

13 Rules

13.1.5 Columns Header

Below the rule file header, the first two lines contain the columns header.

The first eight columns (from A to H) contain the names of the rule attributes .

The names contained in the header cells are not important themselves, it isonly the order of the columns that counts. The rules attributes are definedin the following order: Name, Rule Type, Severity, Visible, Function, RuleExpression, Description, and Rule Condition.

The next columns (starting with column I) define additional conditionalparameters for rules.

The first line contains a variable set of merged cells. Each set has avariable number of merged cells. It contains an object parameter name, e.g.CELL_CLASS. The number of sets itself is not limited.

On the second line, for each set of merged cells, i.e. for each object parameter,each individual cell contains a parameter value, e.g. URBAN, SUBURBAN, etc.

Each column represents a specific condition on an object parametervalue, of the form <parameter name>=’<parameter value>’, e.gCELL_TYPE=’CONCENTRIC’ .

Figure 22: Example of Columns Header for Rules File

3BK 21216 AAAA PCZZA Ed.26 257 / 664

13 Rules

13.1.6 Rules Data

After the columns header, the next lines contain the rule data, one rule per line.

The first eight columns (from A to H) contain the following rule attributes :

Description Mandatory

The name of the rule.

It must be unique among all rules.

Yes

The type of the rule (e.g. System or Expert), it can actually beany free text.

No

The rule severity. A value among (case insensitive):

ERROR

WARNING

Yes

The visibility: if any text is present, (e.g. X) it means true. No(defaultis false)

The function, i.e. the family and subfamilies in the form:<family>/<subfamily1><subfamily2><subfamily3><subfamily4> .The number of sub families can be from zero to four. The familyitself is optional.

No

The description of the rule. No

The rule expression. It must validate the grammar given in Annex. Yes

The rule condition that defines when the rule applies. It mustvalidate the grammar given in Annex.

No

Figure 23: Example of First Columns of Rules Data

The next columns (starting with column I) define additional conditionalparameters for rules.

Depending on the Columns Header, each cell corresponds to a specificcondition on a parameter value (e.g. CELL_CLASS = ’CONCENTRIC’). If thecell contains any text (e.g. X) it means that the condition must be appliedfor the rule.

258 / 664 3BK 21216 AAAA PCZZA Ed.26

13 Rules

Figure 24: Example of Last Columns of Rules Data

For each rule, a cross in a cell means that the conditional parameter must havethe corresponding value to make the rule applicable.

If some cells are checked for several values of the same parameter (e.g.RELEASE = B9 is checked and RELEASE = B10 is also checked) the ruleapplies if the conditional parameter have one of the checked values (i.e. ifRELEASE = B9 is checked and RELEASE = B10 is also checked, the rule isapplicable for objects where RELEASE = B9 OR RELEASE = B10).

If a condition (and specific conditional parameters) is false for an object, itmeans that the rule cannot be applied on that object, and the rule result is N/A(and not true or false, whatever the rule expression value for that object).

Rule expressions and conditions are formulas containing references toparameters of the network object. It can also contain selectors to useparameters of a child or a parent object, or to use parameters of the source ortarget objects in the case of relations (adjacencies).

Example:

BSC:Release = XYZ

S:CELL_CLASS = “URBAN” (S for Source)

T:CELL_CLASS = “URBAN” (T for Target)

In the same way, “Hard-coded” conditional parameters (e.g. CELL_CLASS,RELEASE) must match the parameter expressions defined in the grammar.They may also use selectors like S:CELL_CLASS, i.e. the parameterCELL_CLASS of the source cell.

3BK 21216 AAAA PCZZA Ed.26 259 / 664

13 Rules

13.1.7 Rules Evaluation

When executing a view that contains rules , the parameter values from therules conditions and expressions are evaluated with operational, historical,planned, or forecast values depending on the view execution context. Theexecution context is set in the same way as for views containing parameters.

The temporal part of the availability domain (list of periodicity) is fixed and iscommon to all rules; it is configurable in a configuration file.

The spatial part of the availability domain of a rule is the associated object typeof the rule (e.g. CELL2G).

The availability domain of a rule is not computed from availability domain ofparameters used in the rule. This means that if the user chooses an executioncontext that is not valid for one of the parameters, the result of the Ruleis N/A (see below).

When checking a tuning session, the parameter values from the rulesconditions and expressions are evaluated with operational or forecast values,depending on the given tuning session.

In both cases, the evaluation of the rule may involve getting parameter values ofother related objects (operational or forecast when checking a tuning session,operational or historical when executing a rules view, in the same executioncontext).

The criteria in the xls file is evaluated from right to left.

A rule cannot be checked on an object(the rule result is ’N/A’) if:

The rule condition (and specific conditional parameters) is false for thatobject

At least one parameter used in the rule expression has no value for thatobject in the given execution context.

The rule condition or rule expression cannot be evaluated (e.g. division

by zero or comparison between numeric and non-numeric values). In thiscase, a warning must be logged.

Depending on the ’Severity’ value, the following icons are defined:

Icon Description

The rule expression is true on that object.

The rule expression is false on that object, andthe rule type is Warning.

The rule expression is false on that object, and therule type is Error.

260 / 664 3BK 21216 AAAA PCZZA Ed.26

13 Rules

13.1.8 Highlighting

The operator can highlight the view based on rules results.

This case is an extension of the case Highlight in View (Section 18.5.2).

Criteria Color

Rule result is N/A Black

Rule result is true Green

Rule result is false and the rule is of type Warning Orange

Rule result is false and the rule is of type Error Red

13.1.9 Expression Grammar

The same grammar expressions are used for rules as for reference values.Refer to Expression Grammar (Section 12.1.7).

3BK 21216 AAAA PCZZA Ed.26 261 / 664

13 Rules

13.2 Display Rules PropertiesSee Display and Edit Properties (Section 3.3).

ParameterName


Name Name of the Rule Yes Yes

Rule Type Rule Type (Expert/System) Yes Yes

Severity Severity (Error/Warning) Yes Yes

Visible Visibility (Yes/No) No Yes

Description Description of rhe rule Yes Yes

262 / 664 3BK 21216 AAAA PCZZA Ed.26

13 Rules

ParameterName


Supplier Standard/Alcatel-Lucent/Customer Yes Yes

Type Object type (e.g. Cell2G) Yes Yes

Comments Free comment Yes Yes


Name of the file it has been imported from

Author

Date of creation

Yes Yes

Families Associated family and sub-families of the rule. No Yes

Rules Rule Expression Yes Yes

Condition Rule Condition (Boolean expression, it includes also thespecific conditional parameters hard coded in the imported file,like CELL_CLASS=’URBAN’)

No Yes

13.3 Execute RulesThe execution and representation of views containing rules is done in thesame way as for the views containing parameters, except that rules cannot beadded to a graphic.

Rules can be mixed with other data in views.

Execute a rule:

1. Select the network object(s), and the rules or view(s) containing the rule(s),then drag and drop them in the Tabular / Graphical Viewer.

2. The ’Execution Context’ window appears. Enter the appropriate information,as presented in Execution Context (Section 3.7).

Note: Note that rules can be applied only on operational values.


Rules are evaluated (see Rules Evaluation (Section 13.1.7)). The evaluationof the rules may involve getting parameters values of other related objects(with the same execution context).

The executed view with rules is displayed depending on the selected numberof network objects and rules, in a new tab of the tabular view.

3BK 21216 AAAA PCZZA Ed.26 263 / 664

13 Rules

Figure 25: Executed Rules

264 / 664 3BK 21216 AAAA PCZZA Ed.26

13 Rules

13.4 User Defined RulesTo create a new rule, you have to export an existing rule, edit it as appropriate,then import it in NPO.

The import / export / delete of rules is described in NPO Administration Guide,the following chapters:

Import Rules

Export Rules

Delete Rules .

Figure 26: Example of Rules File

3BK 21216 AAAA PCZZA Ed.26 265 / 664

13 Rules

266 / 664 3BK 21216 AAAA PCZZA Ed.26

14 Events

14 Events

This section describes the use of events.

3BK 21216 AAAA PCZZA Ed.26 267 / 664

14 Events

14.1 PresentationEvents are correlated to the QoS evolution of the network and show whenkey information of a cell is changed.

Events are defined per technology (GSM, W-CDMA, …). The events definitionscontain a unique name, an availability domain, and a family.

The family attribute represents the method that is used to compute theevent. Two families are defined: parameter (modification of current orplanned parameter, e.g identifier, BSC, frequency…) and topology (objectcreation/deletion, e.g Move BTS).

Internal events are defined on historicized network configuration data, suchas logical/design parameter modifications and/or topology modifications todetect significant changes.

Events may be displayed:

On a synthetic view like a dashboard where each event is represented by agraphical symbol

In reports or in a dedicated tabular view.

Note: Only the following events are available for W-CDMA:cell, adjacency, networkelement creation/deletion.

Only Events for which the ’Visible’ property is set to ’True’ are displayed for anyuser. ’Non-Visible’ events are displayed only for the Administrator.

A predefined set of events per technology is defined by Alcatel-Lucent. Theseare called system events and cannot be updated or deleted by the user.

268 / 664 3BK 21216 AAAA PCZZA Ed.26

14 Events

Icon Type Icon Description

Nature of event System

Adjacency changes

Adjacency Parameter Changes

BCCH/BSIC Changes

Cell Capacity Changes

Cell Type Changes

Frequency Changes

Logical Parameter Changes

Planned Logical ParameterChanges

Release Changes

Topology Changes

Cell Creation

Cell Deletion

Type of event

ALL_EVENTS

Events are displayed classified by technology.

Example:

3BK 21216 AAAA PCZZA Ed.26 269 / 664

14 Events

14.2 Display Event Properties


See Display and Edit Properties (Section 3.3).

270 / 664 3BK 21216 AAAA PCZZA Ed.26

14 Events

ParameterName

Description MandatoryRead-Only

Name Name of the Event Yes Yes

EventType

Event Type

Values: Topology/Parameter

Yes Yes

TopologyMap

Map of topology

Values: Current/Planned

Yes Yes

3BK 21216 AAAA PCZZA Ed.26 271 / 664

14 Events

ParameterName


Technology Technology for the event.

Values: GSM/W-CDMA etc.

Yes Yes

Version Version of the technology. Yes Yes

Date Date the event dictionary was loaded. No Yes

Author Author of the event dictionary. Yes Yes


Description Details about event dictionary. No Yes

Event Type Operation on the network object forwhich the event is fired.

Yes Yes

Event Parameter Name of the event parameter. Yes Yes

Release Release of the event parameter. Yes Yes

Display Difference Display difference for the event.

Values: NONE/NEW/REMOVED/NEW_AND_REMOVED

Yes Yes

EventInformation

Availability Domain Availability domain for the event, it isby default daily for all events.

No Yes

272 / 664 3BK 21216 AAAA PCZZA Ed.26

14 Events

14.3 Display Events


Events are displayed in executed views, tabular mode only . Graphical modeis not supported for executed views that contain only events.

An executed event in tabilar mode displays a synthesis of all occurrences ofevents for one or several objects, and one or several days. The resultingexecuted view contains a list of icons for each result cell.

When there is no data available for a table cell in such a view, nothing isdisplayed in that cell.

The execution and representation of views containing events is done in thesame way as for the views containing parameters, except that events cannot beadded to a graphic.

Events can be mixed with other data in views.

14.3.1 Execute Events

To execute an event:

1. Select the network object(s), and the event(s) or view(s) containing theevent(s), then drag and drop them in the Executed View Browser.


Note: For a multi-object comparison view, only ’Day’ periodicity is available.


The executed view with event(s) is displayed depending on the selectednumber of network objects and event(s), in a new tab of the tabular view.

The Cells display a synthesis of all event occurrences where each eventtype is represented by an icon. If no event occurs for any of the selectedobjects on a given date, then nothing is displayed.

Figure 27: Executed Events

3BK 21216 AAAA PCZZA Ed.26 273 / 664

14 Events

14.3.2 Open Events Details Window

To open the details window for an event:

1. Select the event in the executed view.

2. Select from the menu: View -> Event Details , OR

Right click and select Event Details .

The parameter name, previous value, new value, event name are displayed.

Figure 28: Events Details Window

14.3.3 Tabular Mode for Executed Event

Select the appropriate network objects and ’ALL_EVENTS’

The matrix representation of the view is:

The rows represent the network objectsThe event cells contain an icon representing the event if one or moreoccurrences of the event exist; they are empty otherwise.The Cells display a synthesis of all event occurrences where each eventtype is represented by an icon.

274 / 664 3BK 21216 AAAA PCZZA Ed.26

14 Events

The columns define the dates.

Note: For a multi-object comparison view, in the execution context window, theevolution must be chosen for only one date.

Figure 29: All Events Executed View

14.3.4 Tabular Mode for Standard View

14.3.4.1 Multi-Object Comparison - a Set of Indicators/Parameters/Events and a Setof Network Objects


The rows represent the network objectsThe event cells contain an icon representing the event if one or moreoccurrences of the event exist; they are empty otherwise.

The columns define indicators/parameters/events.

Note: For a multi-object comparison view, in the execution context window, theevolution must be chosen for only one date.

Figure 30: Multi-Object Comparison View

14.3.4.2 Mono-Object Evolution - one network object and a set ofindicators/parameters/events


The rows represent indicators/parameters/events

3BK 21216 AAAA PCZZA Ed.26 275 / 664

14 Events

The event cells contain an icon representing the event if one or moreoccurrences of the event exist, they are empty otherwise

The columns define dates.

Note: For a mono-object comparison view, in the execution context window, theevolution must be chosen between two selected dates.

Figure 31: Mono-Object Evolution View

14.3.4.3 Multi-Object Evolution – one eventThe matrix representation of the view is:

The rows represent the network objects

The columns define dates.

Note: For a multi-object evolution view, in the execution context window, the evolutionmust be chosen between two selected dates.

Figure 32: Multi-Object Evolution View

276 / 664 3BK 21216 AAAA PCZZA Ed.26

14 Events

14.4 Display Event Synthesis


In a Mono-Object Evolution View with ’Day’ periodicity that contains onlystandard indicators and/or parameters, the user can trigger the display of anevent synthesis for the given network object.

The Event Synthesis can be triggered in both tabular and graphical mode.

14.4.1 Event Synthesis in Tabular Mode

1. Open Executed View (Section 18.4.4.1)

2. Click on the ’Execution Context’ tab.

3. In the "Execution Context" window, click on the ’Options’ tab.

4. In the "Options" panel, select the ’Display Event Synthesis’ checkbox.

5. Click on [ Update View ].An additional row is added at the bottom of thetabular view.

The cells of this row contain an “x” if an event occurrence exists for thegiven day and the given network object.You can then view details about it by double clicking on “x”.This is applicable for any type of event that applies for the selectedtype of object.

If there is no event occurrence, the cell is empty.

Figure 33: Event Synthesis in Tabular Mode of Mono-Object Evolution View

14.4.2 Event Synthesis in Graphical Mode

1. Open Executed View (Section 18.4.4.1)

2. Click on the ’Execution Context’ tab.

3. In the "Execution Context" window, click on the ’Options’ tab.

4. In the "Options" panel, select the ’Display Event Synthesis’ checkbox.

5. Click on [ Update View ].

The event synthesis is displayed below the regular graph in the form of a bardivided in cells. This is also called one-line-event .

Each cell represents a day and is aligned on the day boundaries of theX-axis of the graph above it.

If an event occurred on the given day, the cell is colored in blue. Otherwise,the cell is not colored.

3BK 21216 AAAA PCZZA Ed.26 277 / 664

14 Events

Figure 34: Event Synthesis in Graphical Mode of Mono-Object Evolution View

278 / 664 3BK 21216 AAAA PCZZA Ed.26

15 Free Fields

15 Free Fields

This section presents an overview of free fields.

3BK 21216 AAAA PCZZA Ed.26 279 / 664

15 Free Fields

15.1 Presentation

15.1.1 Definition

For each customer object type, a set of additional free fields can be defined.Then, an object can be associated to a set of free fields values.

Free fields can be generalized for all network objects, but are basically usedwith the cells.

They can be displayed as design parameters, used in criteria for workingzone, object zone and in classification.

Free Fields are displayed in alphabetic order and no user-defined classificationcan be created for them.

Figure 35: Example of Free Fields Function Tab

280 / 664 3BK 21216 AAAA PCZZA Ed.26

15 Free Fields

15.1.2 Free Fields File Format

The free fields file can be either a comma-separated, or a semicolon-separatedvalues file.

The format is composed of three parts:

Header

Label

Value.

15.1.2.1 Free Fields File HeaderThe header part is the first line of the file.

For the specific case of GSM Cells , the header is composed as below:FREE FIELD;<optional comment>

For generic cases , the header is composed as below:FREE FIELD;<optional comment>;<TYPE>

where <TYPE> is the type of objects contained in the file.

Example: FREE FIELD;CELL3G

15.1.2.2 Free Fields File LabelFor the specific case of GSM Cells :

The second line defines the used external IDs and the names of free fields.

There are two ways of identifying cells with two different configurations ofexternal IDs:

MCC/MNC/CI configurationIn CI configuration, the label part is composed of keyword “CELL_MCC”,“CELL_MNC”, “CELL_ID” followed by free fields name, separated bysemicolons:CELL_MCC;CELL_MNC;CELL_ID;<name1>;<name2>; etcExample: CELL_MCC;CELL_MNC;CELL_ID;Address; ZIP_Code

MCC/MNC/LAC/CI configurationIn LACCI configuration, the label part is composed of keyword “CELL_MCC”,“CELL_MNC”, “LAC_ID”, “CELL_ID” followed by free fields name, separatedby semicolons:CELL_MCC;CELL_MNC;LAC_ID;CELL_ID;<name1>;<name2>; etcExample: CELL_MCC;CELL_MNC;LAC_ID;CELL_ID;Address;ZIP_Code

The external IDs of GSM cells is constructed from this information.

For generic cases , the header is composed as below:

The second line is composed of keyword “OEXID” followed by the names offree fields, separated by semicolons.

The label part is composed of the name of the type, followed by free fieldsname, separated by semicolons:OEXID;<name1>;<name2>; etc

Example: OEXID;Address;ZIP_Code

3BK 21216 AAAA PCZZA Ed.26 281 / 664

15 Free Fields

15.1.2.3 Free Fields File ValueThe other lines of the free fields file form the value part. Each line describesthe values of free fields for one cell.

For the specific case of GSM Cells :

The line is introduced by the cell identifiers followed by values of free fields,separated by semicolons:<MCC>;<MNC>;[<LAC_ID>];<CI>;<val1>;<val2>; etc

LAC_ID is contained depending if it is present or not in the label part.

Note that the number of values must be equal to the number of labels declaredin label part.

Empty lines are skipped with no warning. The last line is read even if it does notend with a carriage return.

Example:2;3;12450;4 Main Street;920005;3;13200;3 Downtown blvd;06000

For generic cases :

The line is introduced by the object external identifier followed by values offree fields, separated by semicolons:<OEXID>;<val1>;<val2>; etc

Note that the number of values must be equal to the number of labels declaredin label part.

Empty lines are skipped with no warning. The last line is read even if it does notend with a carriage return.

Example:000001/000005;4 Main Street;92000000001/000006;3 Downtown blvd;06000

282 / 664 3BK 21216 AAAA PCZZA Ed.26

15 Free Fields

15.2 Display Free Field PropertiesSee Display and Edit Properties (Section 3.3).

ParameterName


Name Name of the free field. Yes Yes

DescriptionDescription of Cell. Yes Yes

3BK 21216 AAAA PCZZA Ed.26 283 / 664

15 Free Fields

15.3 Free Fields ManagementThe management of free fields is described in NPO Administration Guide ,as follows:

The import of free fields via GUI in section Import Free Fields

The load of free fields via command line in section Load Free Fields

The delete of free fields via command line in section Delete Free Fields.

15.4 Execute Free FieldsTo execute free fields:

1. Select the appropriate cell(s) and the free field(s), then drag and dropthem in the Executed View Browser.



The executed view with free field(s) is displayed depending on the selectednumber of network objects and free field(s), in a new tab of the tabular view.

284 / 664 3BK 21216 AAAA PCZZA Ed.26

16 User Notes

16 User Notes

This section describes how to use user notes.

3BK 21216 AAAA PCZZA Ed.26 285 / 664

16 User Notes

16.1 PresentationUser Notes are user defined comments associated to topology objects (networkobjects or object zones) and functions.

User Notes are visible to all users and are clearly visible in topology or function

trees, a yellow icon being attached to them .

Only one (or none) user note can be associated per object.

All users can see the user notes, but only those having the corresponding FADcan modify or delete them.

286 / 664 3BK 21216 AAAA PCZZA Ed.26

16 User Notes

16.2 User Notes Management

16.2.1 Display User Note

If a topology object/function has a user note already assigned to it then theuser note icon is shown in the network object or function tree, marked witha yellow icon.

To display an existing user note attached to a cell, pass the mouse over the

user note icon corresponding to the object. The comment is displayed asa tool-tip.

Figure 36: User Note is Present

3BK 21216 AAAA PCZZA Ed.26 287 / 664

16 User Notes

16.2.2 Create User Note

To create a user note:

1. Right click on the appropriate topology object (network object or objectzone) or function, and select User Note -> Add... . You can also selectTopology/Data -> User Note -> Add... from the menu bar.

The "User Note" window opens.

The ’Owner’ and ’Date of Last Update’ properties are automatically addedby NPO in the User Note.

2. Type the comment (as free text) and click on [ OK ].

Note: The cell user note message is limited at 4096 characters. The textarea isscrollable in case the contents of the user note are large.

A notification of user note addition is sent to all connected users.

16.2.3 Edit User Note

To edit a user note:

1. Right click on the appropriate topology object (network object or object zone)or function that has a user note attached, and select User Note -> Edit..

The "Edit User Note" window opens with the previous user note contentselected.

2. Type the appropriate comment, then click on [ OK ].

The comment is refreshed.

16.2.4 Delete User Note

To delete a user note:

1. Right click on the appropriate network object or function, and select UserNote -> Remove .

2. Click on [ Yes ] at the deletion confirmation message: Do you want to

remove the selected user note(s)?

The user note is removed and a notification of user note deletion is sent toall connected users.

Note: Multiple user notes can be selected for removal.

288 / 664 3BK 21216 AAAA PCZZA Ed.26

17 Favorites

17 Favorites

This section describes how to use favorites.

3BK 21216 AAAA PCZZA Ed.26 289 / 664

17 Favorites

17.1 PresentationFor a friendlier and quicker navigation to the user preferred functions, they canbe added to favorite list of functions. Thus, when a function is defined as beinga favorite function, it can be quickly retrieved from the popup menu, instead ofhaving to search for it in the function tree.

Groups and sub-groups of favorites can be defined for a better customizing.There is one list of groups/sub-groups/favorite functions per Function Type perMode (i.e. Favorite Indicators for Cell 3G, Favorite Indicators for RNC, FavoritesLogical Parameter for Cell 3G, etc).

The favorites definition - including groups and sub-groups, is dedicated to oneuser (not shared between users).

The list of groups and sub-groups is unique for each mode and function type.The same Favorite function can be added to different groups and sub-groups.

17.2 Favorites Management

17.2.1 Select Favorite Function

To select a favorite function:

1. Right click on the function tree. A pop-up menu containing the Favoritesoption is displayed.

2. Navigate through the Favorites pop-ups list of favorites, and select thedesired favorite function to display.

When a favorite function is selected any prior selections on the function treeare maintained only if “Add favorite to current selection” is set as true inUser Preferences. Otherwise the selections are lost and the tree is scrolleddown to the selected favorite function.

“Whole Group ” selection contains all the favorites under the group.

290 / 664 3BK 21216 AAAA PCZZA Ed.26

17 Favorites

17.2.2 Add a Function to Favorite Functions

To add a function to Favorite Functions:

1. Select the needed function(s) from the function browser.

2. Perform one of the following operations:

Select from the menu bar: Data -> Favorites -> Add to... , OR

Right click and select Favorites -> Add to... .

The "Add to Favorites" window is displayed.

In case several functions are selected, the first selected function is displayedin the ’Favorite name’ field. By placing the mouse over the ’Favorite name’field, the names of the functions are displayed in a tool tip.

3. Classify the favorite function(s) in the appropriate hierarchy.You can:

Select one of the existing groups or sub-groups displayed in the

’Favorites hierarchy’ field, OR

Define and organize your own groups and sub-groups containing the

function(s).Refer to Create Group to Add Favorites (Section 17.2.3) and OrganizeFavorites (Section 17.2.6).

4. Click on [ OK ].

The function(s) is(are) added as favorite function(s), in the selected groupor sub-group of favorites.

3BK 21216 AAAA PCZZA Ed.26 291 / 664

17 Favorites

17.2.3 Create Group to Add Favorites

To create a group/sub-group of favorites:

1. In the "Add to Favorites" or "Organize Favorites" window, select a groupunder which you want the new group/sub-group to be created.

By default the root node (i.e. “Favorites”) is selected.

2. Click on [ Create Group ].

The "Create New Group" window is displayed.

In the case of sub-groups, this window only opens if the sub-group iswithin the maximum number of permitted sub-groups. Up to four levels ofsub-groups can be created (4 is a configurable value).

3. In the ’Group name’ field, type the name of the group/sub-group to becreated.

The group name must be unique, and the sub-group name must beunique within the group.

4. Click on [ OK ].

The Favorites tree is updated and the new group/sub-group is selected.

292 / 664 3BK 21216 AAAA PCZZA Ed.26

17 Favorites

17.2.4 Rename Group of Favorites

To rename a group/sub-group of favorites:

1. In the "Add to Favorites" or "Organize Favorites" window, select a group torename, then:

Click on [ Rename ], OR

Right click and select Rename , OR

Press F2.

2. The current name of the group is highlighted and becomes editable.

Type the new name of the group.

Press [ Enter ] or click outside the name tag. If unique, the new nameis saved.

3BK 21216 AAAA PCZZA Ed.26 293 / 664

17 Favorites

17.2.5 Delete Favorite/Group of Favorites

To delete a favorite/group/sub-group of favorites:

1. In the "Add to Favorites" or "Organize Favorites" window, select afavorite/group to delete, then click on [ Delete ].

2. Click on [ Yes ] at the confirmation message:

The favorite/group/sub-group of favorites is deleted. In case of a groupremoval, all the favorite functions it contained are also deleted.

The favorites tree is refreshed.

294 / 664 3BK 21216 AAAA PCZZA Ed.26

17 Favorites

17.2.6 Organize Favorites

To organize favorites:

1. Select the needed function(s) from the function browser.

2. Perform one of the following operations:

Select from the menu bar: Data -> Favorites -> Oganize... , OR

Right click and select Favorites -> Oganize... .

The "Oganize Favorites" window is displayed.

The displayed favorites are those of the current mode and Function Type(active function tree).

3BK 21216 AAAA PCZZA Ed.26 295 / 664

17 Favorites

The Mode field displays the mode for which the organize favorites isopened. On mode navigation, the first function tab of the mode is activated.You can change the mode by selecting a different mode from the list. Onlymodes of the active standard and only the visible modes are displayed.

The Function Tabs contains all the functions of the selected mode. Onlythe visible tabs on the function browser are displayed. By changing thefunction tab, the favorites of that function are loaded and the function tabfrom which organize favorites is called is displayed.

The Favorites Hierarchy tree displays favorites organized by group andsub-group. The tree is scrollable vertically and horizontally.

3. The following actions are available from this window:

Create Group to Add Favorites

Rename Group of Favorites

Delete Favorite/Group of Favorites

Move Favorite/Group of Favorites to Folder

Import Favorites

Export Favorites

296 / 664 3BK 21216 AAAA PCZZA Ed.26

17 Favorites

17.2.7 Move Favorite/Group of Favorites to Folder

To move favorites/group of favorites from one folder to another:

1. In the "Organize Favorites" window, select the favorite/group to move.

2. Drag and drop it to the appropriate group.

During the dragging process, if the favorite/group to move is incompatible

with the target group, the mouse pointer changes to . This may happenin case of a parent folder being dropped in a child folder, or if the source anddestination folders are the same.

Continue the dragging process to an appropriate group, where the mouse

pointer is .

The favorite/group is moved.

17.3 Import FavoritesFavorites can also be added in NPO by importing them from an xml file.

The exported file to be imported has no associated owner, so any user canimport favorites exported by another user.

If the active mode and the mode in the imported file are not the same, then theimport is only possible for the functions whose availability domain contains theactive modes object type.

Favorites defined for a Non Zone mode can be imported also for thecorresponding Zone mode (i.e. Favorite Indicators defined on 3G Cell can beimported in 3G Cell Zone mode).

Favorites defined for a Zone mode can be imported also for the correspondingNon Zone mode (i.e. Favorite Indicators defined on 3G Cell Zone can beimported in 3G Cell mode).

When importing favorites, the existing favorites are merged with the importedones.

To import favorites from an xml file:

1. In the "Organize Favorites" window, click on [ Import ].

The "Import Favorites" window opens.

3BK 21216 AAAA PCZZA Ed.26 297 / 664

17 Favorites

2. Browse for the favorites xml file to import, then click on [ Import ].

The file is imported.

17.4 Export FavoritesThe exported favorite must contain the mode and function type for whichthe xml is exported.

To export favorites to an xml file:

1. In the "Organize Favorites" window, select a favorite, then click on [ Export ].

The "Export Favorites" window opens.

298 / 664 3BK 21216 AAAA PCZZA Ed.26

17 Favorites

2. Browse for a location to export the selected favorite, then click on [ Export ].

The favorite is exported in xml format. Its corresponding mode and functiontypes are also saved in the xml file.

3BK 21216 AAAA PCZZA Ed.26 299 / 664

17 Favorites

300 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

18 Views

This section describes the management of view templates. It describes how tocreate, edit, display, and delete a view template.

3BK 21216 AAAA PCZZA Ed.26 301 / 664

18 Views

18.1 Presentation

18.1.1 Definition

View enables to display results coming from any analysis service (e.g.functions) in a tabular way or graphical way. A view contains the networkobjects, functions, and execution context (period, interval, sampling,interpolation, reliability options). The limit for the number of functions insidea view is 500.

A view template defines a set of indicators / parameters.

A view can be created:

By selecting network objects and view templates, then executing them on anExecution Context (period, interval, sampling, interpolation, reliability), OR

Interactively, by selecting network objects and

indicators/counters/parameters/events/rules/syntheticdiagnosis, then dragging and dropping them into a viewer browser.Only the Equipment view cannot be created interactively.

The default limit for the maximum objects in a view in the view browser is 5000.

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

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

If you want to change the following limits:

the limit of 5000 objects, you must modify the following parameters:

’analysis.desktop.objects.views.limit’ parameter from the following file:/alcatel/muse/MUSEADWEBSTART/webapps/AD/rsc/com/alcatel/

muse/usm/config/ad_param.cfg

’MAXSIZE’ parameter from the following file:

/alcatel/muse/MUSE_MAAT/qos/rsc/com/alcatel/muse/maat/

qos/QoSResource.cfg

the limit of 20 views in the view browser, you must modify the following

parameters:

’analysis.desktop.views.inside.report.limit’ parameter from the followingfile: /alcatel/muse/MUSEADWEBSTART/webapps/AD/rsc/com/alcatel/


’MAX_TABLE_GRAPH_TABS’ parameter from the following file:

/alcatel/muse/MUSEADWEBSTART/webapps/AD/rsc/com/alcatel/


’MAX_VIEW_TEMPLATE_SIZE ’ parameter from the following file:/alcatel/muse/MUSEADWEBSTART/webapps/AD/rsc/com/alcatel/


the limit of 500 functions inside a view, you must modify the followingparameters:

302 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

’analysis.desktop.functions.inside.view.limit’ parameter from the followingfile: /alcatel/muse/MUSEADWEBSTART/webapps/AD/rsc/com/alcatel/


’MAX_GRAPH_DATA_LIMIT’ parameter from the following file:/alcatel/muse/MUSEADWEBSTART/webapps/AD/rsc/com/alcatel/


In order for the updates to be taken into account in Analysis Desktop, theAnalysis Desktop must be closed, then re-opened.


18.1.2 Classification

The views can be displayed in one of the following modes:

Tabular mode - displays the exact values of analysis services outputsin a table

Graphical mode - displays analysis outputs with curves and histograms.

Four types of views are defined: standard, vector, and matrix and equipment.

Apart from the specific case of Equipment, views can also be grouped into fourtypes of evolution and comparison:

Mono-Object Evolution View

Multi-Object Evolution View

Multi-Object Comparison View

Mono-Object Distribution View.

Mono-Object Distribution Views are not available in WiMAX.

In the following table, the “Number of Objects” refers to the number of networkobjects used when creating the executed view. The “Period Covered” refers tothe date(s) entered in the execution context when creating the executed view.

3BK 21216 AAAA PCZZA Ed.26 303 / 664

18 Views

Type NumberofObjects

PeriodCovered

View Constraints

Mono-ObjectEvolution View

One Aninterval

Multiple standard indicators, counters, parameters, events, rules,synthetic diagnosis


The rows represent the parameters

The columns define Planned, Reference, historical evolution,Operational, and forecast values according to what the user

chose to display in the view template or user preferences.

Multi-ObjectEvolution View

Many Aninterval

One standard indicator, counter, parameter, rule, event, syntheticdiagnosis


The rows represent the network objects

The columns define Planned, Reference, historical evolution,

Operational, and forecast values according to what the user

chose to display in the view template or user preferences.

Multi-ObjectComparisonView

Many One date Multiple standard indicators, counters, parameters, events, rules,synthetic diagnosis

The view has three dimensions. The kind of values displayed inthe view is chosen through a selection in a dropdown list attachedto the left-top square of the view (Planned, Min Reference,Reference, Max Reference, Chosen Date (Historical, i.e. 2January 2006), Operational).


The rows represent the network objects,

The columns define parameters.

Mono-objectDistribution View

One One date Vector and/or matrix indicators

The vector view is like the standard indicator view except thata dimension is lost; the x-axis contains the values of the x-axisindicator. The view can only be executed on one date and networkobject.

The vector view contains matrix indicator values for both axis xand axis y indicators.

Table 7: View Types

304 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

18.1.3 Tabular and Graphical Modes

Two types of modes are defined for the views:

Table mode, with all attached indicators or parametersThe table mode displays values of analysis services outputs.Optional rows and columns (such as Total, Weight and Order) may bedisplayed in tabular views (depending on the choices made at view templatedefinition time).

Graphic mode, if the graphic representation is defined in the view template.The graphical mode is defined from a subset of indicators or parametersdefined in the tabular mode.The graphic mode displays analysis outputs with curves, histograms withscales and legend.

Only one mode is displayed at a time for each view. Indicators or Parametersmay have different graphical properties (legend) according to the mode used.

Figure 37: Differences of View Template Indicator Properties Dependingon Mode

Find below an example of the differences between table and graphic modesfor a view template:

3BK 21216 AAAA PCZZA Ed.26 305 / 664

18 Views

Graphical and Tabular

View Title Format

The following title format is automatically filled in at view execution:<Title as defined in view template> ’ <’Equipment (N=’TopN Value’) ’Equipment View Class’: ’Equipment View Type’’if Equipment view> <’-’ Alarm Sub-Type ’ ’ if Equipmentview of alarm> <object type> <’:’object tree label ifsingle object>’-’<’Trend from’ if Trend> <from date andtime depending on periodicity> <’to’ to date and timedepending on periodicity> <’(’periodicity if one ofspecified cases’)’> ’(’<Working Zone: Working Zone Name -QoS Requirement>’) ’<’ (Interpolation)’ if not default><’(Sampling)’ if true> <’(Reliability)’ if true> <’(’Typeof Result’)’ if Equipment view> <’(’Time Range Type’)’ ifEquipment view>

The used font style is bold, and the font size is “Default Size”.

18.1.4 Standard View Template

Standard view templates contain standard indicators and/or parameters.

The graphics for the standard view templates are 2D.

See also Display Standard View Properties (Section 18.2.1).

18.1.5 Vector View Template


Vector view templates contain vector indicators all of which have the sameaxis indicator.

The graphics for the vector view templates are 2D.

See also Display Vector View Properties (Section 18.2.2).

18.1.6 Matrix View Template


Matrix view templates contain one matrix indicator which has two axisindicators.

The graphics for the matrix view template are 3D.

See also Display Matrix View Properties (Section 18.2.3).

18.1.6.1 Matrix Distribution ImagesThe following matrix distribution images are available:

Figure 38: Matrix View Templates – With Grid Without Independent Columns

306 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

Figure 39: Matrix View Templates – Without Grid With Independent Columns

Figure 40: Matrix View Templates – Without Grid Without Independent Columns

Figure 41: Matrix View Templates – With Grid Without Independent Columns

Figure 42: Matrix View Templates – With Grid With Independent Columns

18.1.6.2 Interval ValuesThe interval values entered by the user are rounded according to the’nbAfterPoint’ attribute of the matrix indicator. This rounded value is the oneused and displayed for the interval bound, and not the input value.

Per default, min and max values are set to 0. If min or max changes, thecorresponding value is changed in the distribution scale, without changingcolors, and other interval values are updated according to the intervaldistribution function.

The update of min / max values is done:

in the distribution scale when modifying their values in static sections

in static sections when changing theirs values in the distribution scale.In static distributed QoS views, interval values are written in black in theview legend.

Switching from Dynamic distribution mode to Static distribution mode and viceversa does not change the number of steps or the colors of the distributionscale.

If the user changes the mode from custom distribution to linear / exponential/ logarithmic mode, a confirmation message appears to prevent the lost of

previous interval values

If the user changes any distribution value, the interval distribution becomesthe custom mode.

3BK 21216 AAAA PCZZA Ed.26 307 / 664

18 Views

18.1.7 Equipment View Template


Equipment view templates contain the top N of alarms, logs or basicunavailability.

The “top N” is generated according to a defined attribute of items. For instance,the top 1counts the highest number of items with the same value for thisattribute.

The graphics for the equipment view templates are 2D.

See also Display Equipment View Properties (Section 18.2.4).

18.1.8 Extension and Restriction of Availability Domain


The availablity domain can be managed by extending it or restricting it in viewsand reports, for the following cases:

Create / Create By Copy View Template

Edit View Template

Edit View Template From Executed View by Dialog Box

Execute View(s)

Create / Create By Copy Report Template

Edit Report Template

Edit Report Template From Executed Report by Dialog Box

Executed View Modification in Report by Dialog Box

Execute Report(s).

Click on the appropriate checkbox to extend/restrict the availability domain.

For a warning report, if the filtering/sorting indicator is not available, theavailability domain cannot be extended.

If you try to add a function to a view, or interactively a view to a report,whose availability domain is restricted, then the drop cursor indicates thatthe operation is not allowed.

If the final availability domain was restricted to no longer be available on anobject and period, for example “BSC” as object and “Day” as periodicity, thenthis view/report cannot be executed on BSC with Day periodicity.

308 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

By default all domains are restricted for a new equipment view.

3BK 21216 AAAA PCZZA Ed.26 309 / 664

18 Views

The following table gives the description of visibility of the Availability Domain:

Icon Object Visibility Description

Light Blue background withblack x.

Original availability domain (AND) where the user can makerestrictions.

Light Blue background withno x.

The user can make extensions (OR).

Light Blue background withblue x.

User made extensions.

Light Orange backgroundwith black x.

User made restrictions.

Blue x with no backgroundcolor.

Inactive Extensions.

Light Orange backgroundwith no x.

Inactive Restrictions.

White background with lightgray x.

User removed Inactive Extensions.

Light Gray background withno x.

User removed Inactive Restrictions.

No background color and nox.

User cannot extend or restrict.

310 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

18.2 Display View Properties

18.2.1 Display Standard View Properties


The figure below is an example of the properties window of a standard view.For the explanation of parameters, refer to Create View (Section 18.3.2).

3BK 21216 AAAA PCZZA Ed.26 311 / 664

18 Views

Figure 43: Example of Standard View Properties Window

312 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

18.2.2 Display Vector View Properties



The figure below is an example of the properties window of a vector view. Forthe explanation of parameters, refer to Create View (Section 18.3.2).

3BK 21216 AAAA PCZZA Ed.26 313 / 664

18 Views

Figure 44: Example of View View Properties Window

314 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

18.2.3 Display Matrix View Properties



The figure below is an example of the properties window of a matrix view. Forthe explanation of parameters, refer to Create View (Section 18.3.2).

3BK 21216 AAAA PCZZA Ed.26 315 / 664

18 Views

Figure 45: Example of Matrix View Properties Window

316 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

18.2.4 Display Equipment View Properties



The figure below is an example of the properties window of an equipment view.For the explanation of parameters, refer to Create View (Section 18.3.2).

3BK 21216 AAAA PCZZA Ed.26 317 / 664

18 Views

Figure 46: Example of Equipment View Properties Window

318 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

18.3 View Template Editor

18.3.1 Open View Template Editor

In the Alcatel-Lucent Analysis Desktop window:

Click on the icon, OR

In the right frame, in the ’View’ tab, right click on any displayed reportand select View Template , OR

In the Analisys Desktop window, click on Data -> View Templates... , OR

Press Ctrl+E.

The "View Template Editor" window opens.

18.3.2 Create View

To create the view:

1. In the ’View Template Editor’ window, click on .The ’View Template Type’ window opens, listing four view template types:

Standard

Vector

Matrix

Equipment.

2. Select the appropriate view template type and click on [ OK ] OR double clickon the appropriate view template type.

The ’View Template Editor’ appears with default values and editable fields.


FieldName


Name Name of the view template to be created. ViewTemplate_<owner>_n

where<owner> is theowner of the viewtemplate.

Owner User who is creating the view template.

This field is read-only


Created Date when the view template was created.


Modified Date when the view template was last modified, in case of a viewtemplate update.


3BK 21216 AAAA PCZZA Ed.26 319 / 664

18 Views

FieldName


System True, if this view template is a System view template - thus it cannotbe modified or deleted except certain fields (Visible) only by theAdministrator.

Grayed, otherwise.

AvailabilityDomain

Availability Domain is the view template availability both spatial andtemporal. It is derived from availability domain of the indicatorsused in the view template.

It is created dynamically.

AccessRights


Title Title of the view template. Same as ’Name’.

Families A table containing the families and sub families to which the viewtemplate can belong. There can be a maximum of four sub-levelsfor each family.

To add a new family, right click in the ’Families’ panel and select’Add Family’.The pre-defined family values are: Connection, DashBoard,DHT, GPRS, GSM, Handover, LCS, QoS, RAB, RadioMeasurement, RMS, SMS, Traffic,Select an existing ’User Family’, or edit your own ’Family’.In the next column, type the appropriate sub-family.

To remove an existing family, right click in the ’Families’ panel

and select ’Remove Family’. All its corresponding sub-familiesare automatically deleted.

Note: If no family is added, then the view is not visible in thefunction tree.

Description Text box to be filled in with operator description for the currentview template.

PreferredDisplayType

The display type to view the results: tabular, graphical, or as userpreference.

Graphical or Tabular,according to user’spreference settings.

Visible Checked: if you want the view template to be visible in the ViewTemplate Tree.

Unchecked: if you want the view template to be invisible in the ViewTemplate Tree, except for the Administrator.

Checked

FilteringIndicatorforWarning

The indicator to be used for filtering when executing this view ina warning report.

This is one of the indicators from the tabular view indicators thathas a threshold defined.

320 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

FieldName


SortingIndicatorforWarning

The indicator used for sorting when executing this view in a warningreport.

Grayed when there is no Filtering Indicator for warning.

SortingDirection

Indicates if the sorting indicator for warning is sorted in ascendingor descending order, taking into account the gravity sense(UpperIsFault).

Grayed when there is no sorting indicator for warning.

Descending

OptionalRows

This panel is only avaliable for standard and equipment viewtemplates.

Optional rows may be displayed in tabular views. Their values canbe:

Order, to display an addition row giving the order number ofevery data column

Total, to display an addition row giving the total number of every

data column

Weight, to display an addition row giving the weight inpercentage of every data column.

OptionalColumns

This panel is only avaliable for standard and equipment viewtemplates.

Optional columns may be displayed in tabular views. Their valuescan be:

Order, to display an addition column giving the order number

of every data row

Total, to display an addition column giving the total number ofevery data row

Weight, to display an addition column giving the weight in

percentage of every data row.

4. Depending on the type of view to create, perform:

Create Standard View (Section 18.3.2.1)

Create Vector View (Section 18.3.2.2)

Create Matrix View (Section 18.3.2.3)

Create Equipment View (Section 18.3.2.4).

5. Click on .

6. The following confirmation popup window appears:Are you sure you want to create view template

<view_template_name>?.

3BK 21216 AAAA PCZZA Ed.26 321 / 664

18 Views

Click on [ Yes ].

18.3.2.1 Create Standard ViewFor standard views , perform the following:

1. Drag and drop as appropriate, the following objects from the right frame inthe ’Tabular View’:

Indicators

The indicators are filtered when creating a view template dependingon their type:

For a standard view template, axis, vector and matrix indicators

are not allowed

For a vector view template, only vector indicators are allowed

For a matrix view template, only matrix indicators are allowed.

Regardless of the type of view template, temporary indicators can onlybe added when editing a view interactively.

CountersCounters can only be added when editing a view interactively. Theycannot be mixed with any other type of object.

Design Parameters

Logical Parameters

Rules

Events

Free Fields

Synthetic Diagnosis.

The availability domain is updated automatically depending on theavailability domain of the indicators, counters and parameters.

2. In the ’Primary Graphic’, in the ’Tabular View’, drag and drop the requiredobjects.

Select the appropriate graphic ’Type’.

For the ’Min’ and ’Max’ Y-Axis, leave ’Computed’, or type the required values.

The Primary Graphic is not mandatory. If used, the axis for this graphappears on the left side. The indicators / parameters chosen for this vieware a subset of those in the tabular view, without overlapping those in thesecondary view, and all having the same units.

Parameters can only be added to the graphic depending on their type. Onlynumber types can be added. Parameters with multiple values cannotbe added.

3. In the ’Secondary Graphic’, ’Tabular View’, drag and drop the neededobjects, other than the ones used for ’Primary Graphic’.

Select the appropriate graphic ’Type’.

For the ’Min’ and ’Max’ Y-Axis, leave ’Computed’, or type the needed values.

The Secondary Graphic is not mandatory though. If used, the axis for thisgraph is displayed on the right side. The indicators / parameters chosen forthis view are a subset of those in the tabular view, without overlapping thosein the primary view, and all having the same units.

322 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

Parameters can only be added to the graphic depending on their type. Onlynumber types can be added. Parameters with multiple values cannotbe added.

4. Drag and drop in the ’Filtering Indicator for warning’ the indicator to be usedfor filtering when executing this view in a warning report.

This is one of the indicators from the Tabular view indicators that has a

threshold defined ( or icons associated).

5. Drag and drop in the ’Sorting Indicator for warning’ the indicator to be usedfor sorting when executing this view in a warning report.

This is one of the indicators from the Tabular view indicators.

6. Choose from the ’Sorting Direction’ the sorting indicator for warning(ascending or descending order). This takes into account the gravity sense(UpperIsFault).

7. In the ’Parameter Attributes’ field, select the type of values you want todisplay for all the parameters in the view template (tabular and graphicalmodes):

’Display Choice’

Choose the type of values for parameters to display for all the parametersin the view template for tabular and graphical modes. These override thechoices in the user preferences. At least one type has to be chosen ifparameters are included in the view. The following values are available:

Operational - to display operational values

Planned - to display planned values

Min Reference - to display min reference values

Reference - to display reference values

Max Reference - to display max reference values

Forecast - to display forecast values of the tuning sessions that will be

selected in the Execution Context

Historical - to display historical values.

’Value Change’If ’Value Change’ option is checked, the source and target optionsare not valid.

’Source’This parameter is used as the default comparison type for highlightingin the view.

’Target’This parameter is used as the default comparison type for highlightingin the view.

3BK 21216 AAAA PCZZA Ed.26 323 / 664

18 Views

Figure 47: Example of Standard View Template, with “CHO_AMR_rate” Filtering Indicator for Warning and“CHO_AMR” Sorting Indicator for Warning

324 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

18.3.2.2 Create Vector View


For vector views , perform the following:

1. Perform steps (1) to (3) from Create Standard View (Section 18.3.2.1).

2. Drag and drop in the ’Axis Indicator’, the appropriate indicator.

There is just one axis indicator for a vector view template.Set the neededvalues for:

Axis Indicator Name - the axis indicator name of the vector indicatorsin the tabular section. All vector indicators must have the same axis

indicator.

Legend - the legend for the axis indicator

Units - the units for the axis indicator

Reverse - True or False. If True, then Reverse the display of the Axis

Indicator.

Figure 48: Example of Vector View Template

3BK 21216 AAAA PCZZA Ed.26 325 / 664

18 Views

18.3.2.3 Create Matrix View


For matrix views , perform the following:

1. Drag and drop in the ’Matrix Indicator’ the appropriate indicator. There isonly one Matrix indicator per view.

This automatically adds its two axis indicators. For the X and Y-AxisIndicators of the Matrix Indicator, set as appropriate the:

Axis Indicator - the axis indicator name as specified on the added

matrix indicator

Legend - the legend for each of the axis indicators

Units - the units for each of the axis indicators

Reverse - True or False. If True, then Reverse the display of the Axis

Indicator.

2. In the ’Distribution Scale’, add the following:

’Inclusion’ scale

Color - color for IntervalUser can change the color or can choose to automatically color allIntervals.

Min - minimum value for the range of this interval stepThe first Min value may be “none” to correspond to negative infinity.

Max - maximum value for the range of this interval stepThe last Max value may be “none” to correspond to positive infinity.

Min Inclusion - included or notThe inclusion of the Min value must be specified, for example, [2, 4] or]2, 4] showing that 2 is included in the first case and not included inthe second case.

Max Inclusion - included or not.The inclusion of the Max value must be specified, for example, [2, 4]or [2, 4[ showing that 4 is included in the first case and not included inthe second case.

3. For the ’Boundary Parameters’, choose either Dynamic or Static.

If Static is chosen, you may set Min and Max values. By default Min andMax are set to 0.

If you modify the Min value, then the Min of the first Interval Step is set tothis value and vice versa.

If you modify the Max value, then the Max of the last Interval Step is set tothis value and vice versa.

4. For ’Interval Distribution’, set the following:

’Interval Distribution’: Linear, Logarithmic, Exponential or CustomCustom is only possible with Static Bound Determination.

’Number of Intervals’ - the number of Interval steps needs to be listedand be editable.

326 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

If the number of Steps is modified in the table, this number must beupdated and vice versa.

’Show Grid’ - Yes or No.When set to Yes, draws a grid. Otherwise it does not.

Figure 49: Example of Matrix View Template

18.3.2.4 Create Equipment View


For equipment views , perform the following:

1. Optionally, in the “Alarm Filters” panel, add the appropriate:

Attribute, selecting it from the available drop-down list

Operator, selecting it from the available drop-down list

Value, by double clicking in the “Value” row and typing the needed

criterion value for the selected alarm.

2. In the “Graphics” panel, select the appropriate graphic ’Type’. The possiblevalues are: Bar Chart and Continuous Line.

For the ’Min’ and ’Max’ Y-Axis, leave ’Computed’, or type the required values.

3BK 21216 AAAA PCZZA Ed.26 327 / 664

18 Views

3. For “Equipment View Type”, select the appropriate type of equipment viewtemplate from the following value: Alarm, Log, Basic Unavailability.

4. In the “Time Range Type” field, select the target time range type for Top Ncomputation.

The possible values are: It must be taken among: Unavailability RelevantHours, Unavailability Non Relevant Hours, 24 Hours.

5. Choose the appropriate ”Preferred Date Display Type”.The possible valuesare:

“Visible”, for an Equipment view with the details made visible for allthe dates in the chosen periodThe intermediary totals for every date of the period is displayed.

“Hidden”, for an Equipment view with the details made hidden for allthe dates in the chosen period.Only the global Top N result for the considered period is displayed.

6. In the “Type of Result” field, select the type of information on which the TopN computation is based.

The possible values are: Number of Occurences, Time.

7. Select the appropriate “Alarm Criterion” from the avaliable drop-down list.

8. Select the “Top N Value” representing the number of items to be displayed inthe Equipment view.

9. Select the appropriate value for “Among Network Object”:

Yes, to get a Top N where the classification computation is based on the

pairs (Network Object instance, Top N item)In this case, the corresponding object instance label is used as a prefixfor every row header label (which basically corresponds to a top N iteminstance) of the resulting view.

No, otherwise (global Top N item classification, whatever the related

network object instance).

Example:

Object/Alarm Alarm 1 Alarm 2 Alarm 3

C1 1 9 8

C2 3 11 12

C3 7 35 4

Total 11 55 24

Considering the above input data, the result is:

If “Among Network Object” = No

55 and 24 are respectively the Top 1 and Top 2 values

“Alarm 2” and “Alarm 3” are respectively the Top 1 and Top 2 alarm

item instances.

328 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

If “Among Network Object” = Yes

35 and 12 are respectively the Top 1 and Top 2 values

“C3-Alarm 2” and “C2-Alarm 3” are respectively the Top 1 and Top 2

alarm item instances.

10. To have an additional graphic view, select the “Graphic Mode” checkbox.

If you only need a tabular view, unselect it.

Figure 50: Example of Equipment View Template

3BK 21216 AAAA PCZZA Ed.26 329 / 664

18 Views

18.3.3 Create View by Copy

To create a view by copy:

1. In the ’View Template Editor’ window, select the view to copy, then click

on .

2. The user can choose to either copy by duplicating only the view template(thus linking to the existing view templates) or by also duplicating therelated view templates.

The new view template is created with a default name: <oldname>_Copy_n ,where n is an incremental number to define a unique name.

The view template properties window is filled with the existing values,except for the name and owner.


The user becomes the owner of the view template.


The new view is created and the function tree is refreshed.

If the view is public, other users are notified and they have to manuallyrefresh the tree.

18.3.4 Edit View

The operator can edit the existing view by adding / removing one / more objects(indicators, counters, design / logical parameters, rules, events, free fields,synthetic diagnosis), or by changing the existing view data.

A view cannot be edited if the modification impacts its current use.

To edit a view:

1. Open the view you want to modify.

2. In the ’View Template Editor’ window, click on .

The property editor displays the ’View Template Properties Panel’ interface.The current attribute values of the selected view are displayed.


Only the owner of the view or the Administrator can update its values. Thename of the view can also be updated.

The operator is not allowed to modify the view template owner.

If the owner of the view is not the one viewing it, the [ Edit ] button is grayed.

4. To add new objects, drag them from the right frame in the ’Tabular View’panel.

5. To set existing object(s) in the graphical representation, select it (them) inthe ’Tabular View’ and drag and drop them to the ’Primary/SecondaryGraphic’ panels.


Click on [ OK ] in the confirmation window, then click on [ Close ] to closethe ’View Template Editor’ window.

7. To remove a view template or a comment zone, select it / them, right clickand select ’Remove’.

330 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

8. To reorder the view templates or comment zones in the report:

Use the Up / Down arrows, or

Right click and select as appropriate:

’Move to first position’

’Move to last position’

’Move up’

’Move down’.

9. To save the changes, click on [ OK ].

If the edited view is public then other users are notified that the viewtemplate is modified.

18.3.5 Delete View

A view cannot be deleted if it is part of a report.

To delete a view, select the view, then:

From the "View Template Editor" window, click on , OR



The following question appears: Are you sure you want to delete view

template <view_name>?

If only one view is selected to be deleted, click on [ Yes ].

If multiple views are selected to be deleted, click on [ Yes to All ].

The view/s is/are deleted from the operator function tree.

If the deleted view template is public, other users are notified about the deletionand they must manually refresh their function tree.

3BK 21216 AAAA PCZZA Ed.26 331 / 664

18 Views

18.4 Execute View

18.4.1 Execute View

The values of Network Objects / Indicators / Counters / Parameters / Rules /Events / Free Fields / Diagnosis / THL Templates can be viewed by executingthem in views.

The procedure to execute... is described...

Counters / indicators / parameters/ view templates

below.

Rules in Execute Rules (Section 13.3)

Events in Execute Events (Section 14.3.1)

Free Fields in Execute Free Fields (Section 15.4)

Diagnosis scenario in Execute Diagnosis (Section 21.5)

THL template in Execute THL (Section 23.6.5).

To execute a view:

1. Select the network elements and the counters / indicators / parameters/view templates, then:

Drag and drop them in the Tabular / Graphical Viewer, OR

Select from the menu bar View -> Execute View... , OR

Press Ctrl+Q.

Note: The QoS Counters / Diagnosis cannot be mixed with any other type of objectsthat can be put in a view template. Vector and Matrix View Templates cannotcontain anything else than Vector and Matrix Indicators.

The values related to the dropped objects are displayed in the Tabular /Graphical Viewer.



When executing a view with indicators, if “Nerr” value is displayed for a cell,this indicates a numeric error due to a miscalculation of an indicator (forexemple when dividing by zero).

If an entire view is empty, then a message is written in place of the viewarea explaining that there is no data available for the view: ”No data isavailable for the request”.

Depending on the selected number of network objects and indicators orcounters, you can have many types of executed views - refer to Examples ofExecuted Views (Section 18.4.2).

4. To schedule the view, refer to Schedule Reports (Section 19.3.4).

332 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

18.4.2 Examples of Executed Views


18.4.2.1 Examples of Executed Views in Tabular ModeFind below some examples of the possible resulting tables for the executedview in tabular mode.

Figure 51: Mono-Object Evolution View with Counters

Figure 52: Multi-Object Comparison with Indicators

Figure 53: Multi-Object Comparison View with Parameters

Figure 54: Multi-Object Evolution with Multiple Network Objects, Multiple Counters and One Date

Figure 55: Multi-Counters One Object Evolution with Raw Counters

3BK 21216 AAAA PCZZA Ed.26 333 / 664

18 Views

Figure 56: Indicator View - Multiple Network Objects - One Indicator - Several Dates

Figure 57: Indicator View - One Network Object - Multiple Indicators - Several Dates

Figure 58: Indicator View - Multiple Network Objects - Multiple Indicators - One Date

Figure 59: Vector View

Figure 60: Matrix View

Figure 61: Equipment View with Preferred Date Display Type=Hidden and Among Network Objects No withN=4 and Top N Item = Alarm – Event Type

334 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

Figure 62: Equipment View with Preferred Date Display Type=Visible and Among Network Objects No withN=4 and Top N Item = Alarm-Perceived Severity

18.4.2.2 Examples of Executed Views in Graphical ModeFind below some examples of the possible resulting tables for the executedview in graphical mode.

Figure 63: Mono-Object Evolution View

Figure 64: Multi-Object Evolution View

3BK 21216 AAAA PCZZA Ed.26 335 / 664

18 Views

Figure 65: Multi-Object Comparison View with Indicators

Figure 66: Vector View

Figure 67: Matrix View with Static bound Out-of Range Values

In the above figure min and max values in the legend panel with black colorfont indicate that Bound Distribution type is “Static” in the executed view.Also user can select individual colored cell that will be highlighted with invertcolor rectangle in the colored cell and the value of the cell is displayed inthe “Last Selected Value”.

336 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

Figure 68: Equipment View with Hidden Dates Example (N=4, Top NItem=Alarm-Event Type, Among Network Objects=No)

Figure 69: Equipment View with Visible Dates Example (N=4, Top NItem=Alarm – Perceived Severity, Among Network Objects=No)

Raw Counters Graphical Display

The user is allowed to display the graphical view for counters in raw periodicityof a maximum of 7 days.

The graphical view divides all the data by the smallest raw periodicity time(or the smallest difference between starting RP times) so that the data canbe equally compared. The following example shows how to divide the datausing raw periodicity:

Figure 70: Equipment View with Visible Dates Example (N=4, Top N Item=Alarm – Perceived Severity,Among Network Objects=No)

3BK 21216 AAAA PCZZA Ed.26 337 / 664

18 Views

Find below the data that is used to create the graphial mode. The values areadjusted to the smallest raw periodicity.

For example, in the table above the smallest raw periodicity is 15 min. Sothe value 100 of Cell A for the first counter RTCH_request (GTCAHRQN) isdivided such that its raw periodicity is 15 min – thus 100/4 = 25. Likewise,RTCH_request (GTCAHRQN) for Cell B is divided by 2 to go from an rawperiodicity of 30 min to an RP of 15 min.

Figure 71: Equipment View with Visible Dates Example (N=4, Top N Item=Alarm – Perceived Severity,Among Network Objects=No)

The graphs for raw counters are as follows:

Figure 72: Raw Graphical Display for One Counter / Multi-Object Evolution

Figure 73: Raw Graphical Display for Multi-Counter / One Object Evolution

The counters are displayed showing their adjusted raw periodicity value, but theduration of a value is displayed as in the original data.

338 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

18.4.3 Edit Executed View Interactively

The user can change the display properties that appear in the executed viewinteractively. The update appears directly on the displayed executed view.

18.4.3.1 Edit TitleThe title in the tabular and graphical view can be edited by double-clicking on it.This becomes editable and you can change only the real title part (as in the viewtemplate) and not the additional information (Ie. execution context information).

Press [ Enter ] or change the focus so that the new value is accepted.

If you press [ Esc ], the old value is displayed and the title field is grayed.

The following figure shows the behavior of editing a title in the executed view.

18.4.3.2 Add Network Objects / Indicators / Counters / Parameters / Rules / Events/ Free Fields / Diagnoses

Select the network objects / indicators / counters / parameters / rules / events /free fields / Diagnoses you want to add, then drag & drop them in the tabular /graphical viewer using Ctrl-Drag&Drop (depending on the user preferences).

Depending on the user preferences, the selected items are added to theexecuted view, or a new view is created. The same Execution Context is usedfor the new items.

If indicators / counters / parameters are added to a graphic view, they are addedto the primary or secondary one (and tabular) depending on their units. If theirunits are not those in the graphics, they are just added to the tabular.

If a vector indicator is added to a vector view template, it is added as thelast indicator.

If a matrix indicator is added to a matrix view, the current matrix indicator isreplaced by the new one since there is only one matrix indicator per view.The corresponding X and Y axis indicators are then updated based on thenew matrix indicator.

18.4.3.3 Remove Network Objects / Indicators / Counters / Parameters / Rules /Events / Free Fields / Diagnoses

Select from the topology tree the network objects / indicators / counters /parameters / rules / events / free fields / Diagnoses you want to remove, thenpress Ctrl-Shift Drag&Drop (depending on the user preferences).

Depending on the user preferences, the selected items are removed fromthe current view or in a new view. The same Execution Context is used forthe remaining items.

3BK 21216 AAAA PCZZA Ed.26 339 / 664

18 Views

18.4.3.4 Roll Up / Drill Down TemporallyThis sub use case allows the operator to Roll-up / Drill-down temporally inthe executed view.

As a prerequisite, the executed view must already exist in the tabular / graphicalviewer.

To Roll Up, select View -> Temporal Scope -> Roll Up from the toolbar, or

click on the icon from the view toolbar

To Drill Down, select View -> Temporal Scope -> Drill Down from the toolbar,

or click on the icon from the view toolbar.

The interval on the view changes depending on the temporal availability.Depending on the user preferences, the data is updated either in the executedview or in a new view.

Below day periodicities such as: 4Hr, 1/2Hr,1/4Hr, RAW, etc. are treated as“Hourly”. If the user rolls up from one of these periodicities, it is the same asrolling up from Hour. Drilling down from Day always goes to Hour, if it isavailable, and not to one of the other below day periodicities.

If any filter is active on the current view, the Roll-Up orDrill-Down is always performed on the actual data (invisibledata is also taken into account, filtering is ignored).

Example :

’Cells’ are displayed on a ’Day’ basis and the current availability domain ofthe executed view is:

Hour Day Week Month

Network X

RNC X

Cell X X

Adjacency X X

If the user Rolls-Up from ’Day’, the new period will be ’Month’ and not ’Week’,because ’Cells’ are not available on ’Week’ but are on ’Month’.

The user cannot Drill-Down because ’Cells’ are not available on ’Hour’.

Note: For Temporal Drill Down from daily value for stored/calculated temporalaggregation indicator (e.g. BH, MAX, MIN, AVG), the NPO will display the valueof the telecom indicator at hourly level.

340 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

18.4.3.5 Roll Up / Drill Down SpatiallyThis sub use case allows the operator to interactively Roll-up / Drill-downspatially in an executed view, and add or remove network objects.

For this, the executed view must already exist in the tabular / graphical viewer.

To Roll Up, select View -> Spatial Scope -> Roll Up from the toolbar, or click

on the icon from the view toolbar

To Drill Down, select View -> Spatial Scope -> Drill Down from the toolbar,

or click on the icon from the view toolbar.

The network objects in the view change depending on the spatial availability.

The interval on the view changes depending on the spatial availability. The datais updated in the executed view. The Execution Context remains the same.

When rolling-up or drilling-down to a relation, the relations that have the currentnetwork object as the source are used; i.e. if the current object is Cell1 and theuser drills-down to Adjacency, then all the Adjacencies that have Cell1 as thesource are displayed in the resulting view.

When triggering a Drill-Down for a mono-object evolution or a mono-objectdistribution view, then N views are generated as when executing them.

If any filter is active on the current view, the Roll-Up or Drill-Down is alwaysperformed on the actual data (invisible data is also taken into account, filteringis ignored.

Example :

’Cells’ are displayed on a ’Week’ basis and the current availability domain ofthe executed view is:

Hour Day Week Month

Network X

RNC X X

Cell X

Adjacency X X X

If the user Rolls-Up from ’Cell’, the new network object will be ’Network’ andnot ’RNC’, because there is no ’RNC’ on ’Week’ but ’Network’ is available on’Week’ periodicity.

If the user Drills-Down from ’Cell’, the new network objects will be all theoutgoing ’Adjacencies’ for all the ’Cells’ because ’Adjacencies’ are available on’Week’ periodicity.

3BK 21216 AAAA PCZZA Ed.26 341 / 664

18 Views

18.4.3.6 Cursor Facilities in Graphical View

To use the cursor facilities, select the cursor icon from the tool bar , orselect View -> Cursor Mode from the toolbar.

To display the values on the axis, move the cursor over the view area.

A vertical bar is always shown in the graphical display. By moving it, the mousecursor changes. The values for the cursor area are shown at the current cursorlocation, like on a tool tip. These values are also displayed in the legend.

To show grid lines:

Click on the icon from the view toolbar, then select Display Grid Lines ,

and click again on , OR

Select View -> Cursor Mode Choices -> Display Grid Lines from the

toolbar.

To show the values at cursor:

Click on the icon from the view toolbar, then select Display Value at

Cursor , and click again on , OR

Select View -> Cursor Mode Choices -> Display Value at Cursor fromthe toolbar.

In case of reports, the vertical bars on executed views are synchronized.Synchronizing the vertical bars causes the views to scroll when necessary ofthe value in one view is not visible in another view.

342 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

18.4.3.7 Zoom in Graphical ViewTo zoom in:

Click on the icon from the view toolbar, OR

Select View -> Zoom In (+) from the toolbar, OR

Press Ctrl+I.

This magnifies the view on the graph.

To zoom out:


Select View -> Zoom Out (-) from the toolbar, OR

Press Ctrl+O.

This reduces the size of the graph in the view.

The zoom is centered on where the user clicks.

For example, if the entire graph displays data from 0H to 24H, and the currentvisible area is only from 8H to 12H, if the user clicks on:

on 10H, the view displays data from 9H to 11H

on 10H, the view displays data from 6H to 14 H.

To reset to the original size:

Right click in the view and select Reset Graphic , OR

Select View -> Reset Graphic from the toolbar.

18.4.3.8 Rotate / Inverse Axis of Graphical ViewTo rotate / inverse the view axis:


Select View -> Inverse axis from the toolbar.

In a graphical view, the axis are inversed. In a tabular view, the rows areinversed with the columns.

For example, if the indicators are on the horizontal axis and the cells are onthe vertical axis, when the user chooses to inverse the axis, the indicators aredisplayed on the vertical axis and the cells are displayed on the horizontal axis.

3BK 21216 AAAA PCZZA Ed.26 343 / 664

18 Views

18.4.3.9 Propagate Selection to Network Object / Function Trees in ViewTo propagate network objects / functions from the view to the respective tree:


Click on icon from the view toolbar, OR

Right click in the view and select Propagate , OR

Select View -> Propagate Selection from the menu toolbar.


’Propagate All’

’Propagate All Network Objects’

’Propagate All Data’

’Propagation Selected Network Objects’, for tabular view only

’Propagate Selected Data’, for tabular view only.

344 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

18.4.4 Edit Executed View Using Dialog Box

18.4.4.1 Open Executed ViewTo open executed view:

Right click in the executed view from the executed view area, and selectExecuted View... , OR

Double click on one of the values from the executed view, OR

Select View -> Executed View... from the toolbar.

The "Executed View Properties" window is displayed.

The opened view contains three menu tabs: View Template Properties,Execution Context, and Spatial Scope. See the chapters below (18.4.4.2 -18.4.4.4) for information on how to edit them.

3BK 21216 AAAA PCZZA Ed.26 345 / 664

18 Views

The following table presents the buttons displayed in the ’Executed ViewProperties’ window.

Button Name Used to...

[ Edit ViewTemplate ]

Launch the view template editor.

You can change the view template properties. Refer toEdit View (Section 18.3.4).

After applying the changes in the view template editor,the view is refreshed.

[ Update View ] Update the performed changes to the current view.

[ Create View ] Create a new view with the performed changes.

[ Close ] Close the view.

18.4.4.2 Edit View Template Properties1. Select the ’View Template Properties’ tab.

The ’View Template Properties’ panel is displayed.

2. Click on [ Edit View Template ].

The ’View Template Editor’ window opens. Change as appropriate the viewtemplate properties. Refer to Edit View (Section 18.3.4).

3. You can:

Apply the changes made on the current view, by clicking on [ Update

View ], or

Create a new view with the performed changes, by clicking on [ Create

View ].

The executed view is refreshed.

18.4.4.3 Edit View Execution Context1. Select the ’Execution Context’ tab.

The ’Execution Context’ panel is displayed.

2. Update as appropriate the displayed fields. Refer to ’Execute View’,Execution Context (Section 3.7).

3. You can:

Apply the changes made on the current view, by clicking on [ UpdateView ], or


View ].

The tabular / graphical viewer displays the values with the new data.

346 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

18.4.4.4 Edit View Spatial Scope1. Select the ’Spatial Scope’ tab.

The ’Spatial Scope’ panel is displayed, with the list of included networkobjects.

2. To add network objects from the spatial scope, select them and drop themto the view panel.

To remove network objects from the spatial scope, right click on themand select Delete .

The modification of the network objects affects the availability domain. If theavailability domain is empty, an error message is displayed.

3. You can:


View ], or

Create a new view with the performed changes, by clicking on [ CreateView ].

The tabular / graphical viewer displays the values with the new data.

3BK 21216 AAAA PCZZA Ed.26 347 / 664

18 Views

18.5 Using Executed View

18.5.1 Toolbar

The following toolbar icons are available for the executed view:

The following table gives a brief description of the executed view toolbar icons:

Icon Description

Change View Display Type (Section 18.5.7)

Propagate Selection to Network Object / Function Trees in View (Section 18.4.3.9)

Save Executed View as Template (Section 18.5.13)


Roll Up Spatially

Drill Down Spatially

Roll Up Temporally

348 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

Icon Description

Drill Down Temporally

Show Legend (Section 18.5.3)

Highlight in View (Section 18.5.2)

Rotate / Inverse Axis of Graphical View (Section 18.4.3.8)

Remove Filter(s) (Section 18.5.5.2)

Filter Repeated Value(s) - Filter not yet applied

Filter Repeated Value(s) - Filter already applied

Show Filter List - Filter not yet applied

Show Filter List - Filter already applied

In case the executed view window is too small, up & down arraws are displayedto navigate among the executed view related icons - as seen in the figure below.

3BK 21216 AAAA PCZZA Ed.26 349 / 664

18 Views

18.5.2 Highlight in View

Highlighting is applicable on all functions except for counters and events.

To trigger the highlighting:


Select an item in the executed view, right click and select Select -> NoThreshold / Correct / Minor / Major / Critical / Sampling , OR

Select from the toolbar View -> Highlighting (On/Off) .

The QoS indicator values are colored according to their thresholds, to show themost significant information.

The following table presents highlighting criteria and description.

Function Criteria Color Description

Indicators Reliability Italic Reliability test is wrong.

Indicators Sampling Grey The associated sampling value is too low for a value test.

Indicators No threshold Black The indicator does not have a threshold.

Parameters Impossibleto testparametervalues

Black Impossible to test because:

Reference cannot be compared with Reference, forexample

There are inexistent values, for example the comparison

is done with Planned values, but the parameter has noplanned values.

Rules Rule result isN/A

Black Rule result is N/A

SyntheticDiagnosis

Unknownresult

Black Diagnosis result is unknown

Indicators Correct Green QoS is less (or greater) than the yellow threshold (dependingon UpperIsFault)

Parameters Equal values Green The parameter values are equal.

SyntheticDiagnosis

Resultnopbfound

Green Diagnosis result is nopbfound

Rules True Green Rule result is true.

Indicators Minorthresholdvalues

Yellow QoS is between the yellow and orange threshold

350 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

Function Criteria Color Description

Comparisonwith ReferenceParameters

Parametervalues inreferencebounds

Yellow The parameter values are in the reference bounds.

Comparison withOperational,Forecast,or PlannedParameters

Parametervalues in<target> list.

Yellow The parameter values are in the <target> list when theparameter contains a list.

Indicatos Major Orange QoS is between the orange and red threshold

Parameters ValueChange

Orange Value changes between current date and previous date, orbetween operational value and last date (i.e. the last beforeoperational value).

Rules False,warning rule

Orange Rule result is false and the rule is of type Warning

Indicators Critical Red QoS is greater (or less) than the red threshold (dependingon UpperIsFault)

Comparisonwith ReferenceParameters

Parametervalues outof referencebounds

Red The parameter values are out of reference bounds.

ComparisonagainstOperational,Forecast,or PlannedParameters

Parametervalues notequal

Red The parameter values are not e

SyntheticDiagnosis

Resultpbfound

Red Diagnosis result is pbfound

Rules False, Errorin rule.

Red Rule result is false and the rule is of type Error.

Table 8: Example of Highlighting Colors (UpperIsFault = true for Indicators)

The following criteria must be considered for highlighting:

When Sampling is set and the value of the sampling indicator is smaller thanthe sampling value defined in the indicator; or when Reliability is not set, or

set but not “wrong”, then the values are displayed in gray

If there is no value for the reliability indicator, or there is no reliabilityindicator, then it is as if reliability was not chosen

If any filter is active on the tabular view inducing invisible rows or columns,the highlighting synthesis is computed only on visible values basis

3BK 21216 AAAA PCZZA Ed.26 351 / 664

18 Views

The Standard View optional rows and columns (Total, Weight, Order)cannot be highlighted

The synthesis and operations on the synthesis can be performed on therows, columns or both

If any filter is active on the tabular view inclucing invisible rows or columns,

the highlighting synthesis is computed only on the visible values.

352 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

18.5.3 Show Legend

To show the legend for a view:


Right click in the view, then select Show Legend...

Select View -> Legend... from the toolbar.

The ’Legend’ window appears, displaying the list of colors and their meaning.This window is not modal and only one instance is opened.

3BK 21216 AAAA PCZZA Ed.26 353 / 664

18 Views

Parameter Description

Hide Hide/unhide rows in the tabular view, based on the selectedcriteria.

There is one checkbox per highlight criteria/color. The user canhide more than one color type.

Select When “Select” is chosen, then those rows/columns with thesynthesis color in the header are selected in the tabular view.

There is a checkbox per highlight criteria/color. The user canselect more than one color type.

Criteria Short description of the criteria for coloring the table cells.

Color Color (or font style) associated with the criteria of highlighting.

ValueChange

Select/deselect the Value Change option.

Source Choose the default comparison type for highlighting in the view.

Target Choose the default comparison type for highlighting in the view.

To set a color for the rows / columns in the view, select their header, then in the’Legend’ window, click on the ’Select’ button corresponding to the needed color.

In the user preferences, the default value for ’Select’ is the column. Therefore,when pressing ’Select’ in the ’Legend’ window, all the chosen columns (andonly columns), header included, are selected.

The selection from Legend changes automatically when you have items in theview highlighted, and then you select the critical values. See the examplein the following snapshots:

Figure 74: Selected values highlightled in view

354 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

Figure 75: Highlightling changes when critical values are selected in Legend

18.5.4 Sort

The sorting feature is implemented very similar to the sorting implemented inWindows Explorer.

To change the sorting direction inside the executed view:

Double click on a row / column header.

The sorted row / column is indicated with:

an up arrow - when sorted in ascending order (Example: ,

)

a down arrow - when sorted in desscending order (Example:

, ).If you double click on another column, then that column is sortedascendingly.

OR

Click on the row / column header, then right click and select Sort ->Ascending / Descending as appropriateOR

Select View -> Sort -> Row / Column -> Ascending / Descending as

appropriate, from the toolbar.

If a row / column is no longer sorted, the arrow is removed.

3BK 21216 AAAA PCZZA Ed.26 355 / 664

18 Views

18.5.5 Filter in View

The operator can choose what information to be or not to be displayed usingfilters.

Filtering does not impact though the graphical executed view.

18.5.5.1 Add FilterTo add a filter in the tabular view:

1. Select the row / column header, then:

Right click and select Filter , OR

Select as appropriate View -> Filter -> Filter Row / Filter Columnfrom the toolbar.

The ’Custom AutoFilter’ window opens.

2. Set the appropriate filtering criteria.The following criteria is used for filtering:

Equals =

Does not equal !=

Is greater than >

Is greater than or equal to >=

Is less than <

Is less than or equal to <=

Begins with

Does not begin with

Ends with

Does not end with

Contains

Does not contain

The ’*’ wildcard character is supported.Filtering can be done depending on:

Highlighting: based on the highlighted indicator values

Selected rows or columns: by filtering a date, a network object, or an

analysis function.

356 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

The filter is applied only to unhidden rows/columns. A row that is hiddenon or prior to applying the filter criterial remains hidden when the filter isapplied / removed.

The filtered row or column header is shown in italics.

When a filtering criteria is applied on a column and the operator tries toapply filtering on another column then the intersection of filtered valuesare displayed.

3. Click on [ OK ]

18.5.5.2 Remove Filter(s)To remove:

One filter, right click on the filtered column and select Clear Filter

All filters:

Select the Clear All Filters , OR


Select View -> Clear Filters from the toolbar.

18.5.5.3 Filter ListTo show all the applied filters in the executed view:

Right click in the executed view and select Filter List... , OR

Select View -> Filter List... from the toolbar, OR

Click as appropriate on or from the view toolbar.

The "Filter List" window appears, displaying the list of applied filters (differentfrom Repeated Values Filter) associated to the current tabular view.

1. Click on:

[ Remove ], to remove the selected applied filter(s)

[ Remove All ], to remove all applied filter(s)

[ Deactivate All ], to activate/deactivate all applied filter(s).

3BK 21216 AAAA PCZZA Ed.26 357 / 664

18 Views

When the filter list is globally deactivated, all the filtering actions whichcan be accessed from the menus, toolbar and pop-up menus are stillaccessible.

If a new filter is applied by the user, depending on the User Preference“Automatic Filter List Reactivation”, the following actions are applied.

If “Automatic Filter List Reactivation” user preference is set to YES,the global filter list is automatically reactivated before taking into

account the new filter.

If “Automatic Filter List Reactivation” user preference is set to NO, awarning message is displayed. Click on [ OK ] to reactivate the global

filter list, before taking into account the new filter.

2. Click on [ OK ].

18.5.5.4 Filter on Period

Note: Filtering on Periods can be applied only in case of evolution views/reportsand on date columns only.

To filter (hide) periods:

1. In the executed view, select the items below:

one or several days of the week, and/or

one or several hours of the day, and/or

one or several date and time periods (depending on the periodicity),and/or

one or several particular dates and/or times (depending on theperiodicity)

2. Select from the menu toolbar View -> Period Filter... , or right click andselect Period Filter... .

The "Filtering on Period" window appears.

358 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

The conditions applied for filtering depend on the periodicity. The periodgranularity can only be greater or equal to the current periodicity, as follows:

For Hourly periodicity, all options are available

For Daily periodicity, "Hours of Day" is disabled

For Weekly and Monthly periodicity, "Hours of Day" and "Days of Week"

are disabled.

3. To hide:

A single date: check the ‘Date’ radio button, then select the appropriate

start date and end date

Multiple dates: check the ‘Date’ radio button, then specify the neededrange of dates

A range of dates and times: check the ‘Date and Time’ radio button, then

specify the needed range of dates and times

One or more Days of Week: select the checkbox corresponding to ‘Days

of Week’, then select the appropriate days

One or more hours of the day: select the checkbox corresponding to‘Hours of Day’, then select the appropriate hours.

Make the appropriate selection, then click on [ Add ].

4. Click on [ OK ].

18.5.6 Hide/Unhide Rows/Columns/Repeated Values

Hide/Unhide Rows 1. Select the row header.

2. Perform as appropriate:

3BK 21216 AAAA PCZZA Ed.26 359 / 664

18 Views

Right click and select Hide -> Hide Row , OR select View -> Hide-> Hide Row

Right click and select Unhide -> Unhide all Rows , OR select View-> Unhide -> Unhide All Rows

Hide/Unhide Columns 1. Select the calumn header.

2. Perform as appropriate:

Right click and select Hide -> Hide Column , OR select View -> Hide-> Hide Column

Right click and select Unhide -> Unhide all Columns , OR select View-> Unhide -> Unhide All Columns .

Hide Repeated Values A date row or column can be hidden only if it contains exactly the same valuesas the previous one (except for the column header). The repeated values filterhas priority over the other filter types.

1. Select the date rows or columns for the repeated values displayed for aset of dates.

2. Perform one of the following actions:

Right click and select Hide -> Hide Repeated Values , OR

Select View -> Hide -> Hide Repeated Values , OR

Click on icon from the view toolbar.

When this filter is being applied, the current view filter list state is checked.If the filter list is not empty and is activated, then a warning message isdisplayed as shown in the following figure. Click on [ OK ].

When a “Non Repeated” values filter is being applied, no check is performedon the rest of the filter(s) applied.

Unhide Repeated Values 1. Perform one of the following actions:

Right click and select Unhide -> Unhide Repeated Values , OR

Select View -> Unhide -> Unhide Repeated Values , OR

Click on icon from the view toolbar.

2. The repeated values are shown.

18.5.7 Change View Display Type

To change the display type of view:

360 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

Select the toggle button from the view toolbar, OR

Select from the toolbar View -> Toggle Display Type (Tabular/Graphical) ,

then select Tabular or Graphical , as appropriate.

The mode changes from tabular to graphical and vice-versa.

18.5.8 Resize

To resize a row / column, select the line separating the row / column, then dragand drop the line to the appropriate size.

This only changes the selected row / column, and not all rows / columns.

Double clicking when in between the two columns resizes the left columnbased on the size of the data included within the column. Double clickingwhen in between two rows resizes the top row based on the size of the dataincluded within the rows.

3BK 21216 AAAA PCZZA Ed.26 361 / 664

18 Views

18.5.9 Copy to System Clipboard

1. An executed view must exist in the tabular/graphical viewer or in thereport viewer.

Copy the needed data from the table and/or graphical viewer. Selectionof only several rows and columns is possible.

The data is copied into system clipboard in the following formats:unformatted text, HTML, Picture (Enhanced Metafile), and internal viewtemplate format.

2. If necessary, paste it into a report or another application like Excel.

18.5.10 Copy Executed View

To copy an executed view:

Right click on the executed view, and select Copy , OR

Select View -> Copy from the toolbar, OR

Press Ctrl+Shift+C.

A new copy of the executed view is created. The default name of the new viewis <old name>_copy_n, where n is an incremental value to give uniqueness.

If the number of views in the view browser has reached the maximum limit, thena new copy cannot be created and the user is warned.

18.5.11 Duplicate Executed View

To duplicate an executed view:

Right click on the view name tab, and select Duplicate , OR

Right click in the view (can also be inside an executed report), and select

Duplicate , OR

Select View -> Duplicate from the from the toolbar.

A new executed view is created with:

a default name: <oldname>_Copy_n , where ’n’ is an incremental numberto define a unique name

the values of the duplicated executed view.

18.5.12 Rename Executed View

To rename an executed view:


Right click on the view name tab, and select Rename , OR

Right click in the view (can also be inside an executed report), and

select Rename , OR

Select View -> Rename from the toolbar.

The ’Rename View’ window opens.

362 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

2. Type the new name of the view, then click on [ OK ].

The executed view is saved taking into account the new name.

18.5.13 Save Executed View as Template

If the exeuted view is modified and not saved, it is marked with ’*’ as needing tobe saved.


Right click on the executed view and select Save as Template... , OR

Select View -> Save as Template... from the toolbar, OR


Press Ctrl+S.

The ’Save View Template’ window opens.

2. Type the view template name, then click on [ OK ].

The executed view is saved as template.

18.5.14 Close Executed View(s)

To close an executed view:

Right click on the view name tab, and select Close , OR

Right click on the view, and select Close , OR

Select View -> Close from the toolbar.

To close all executed views:

Right click on a view name tab, and select Close All , OR

Select View -> Close All from the toolbar.

3BK 21216 AAAA PCZZA Ed.26 363 / 664

18 Views

18.5.15 Export Views

There is a limitation when exporting views in Excel to worksheets containinga maximum of 65,536 rows and 256 columns.In case of a worksheet containing more than 256 columns, a workaroundis to use the “Transpose” function from Excel in the view from AnalysisDesktop, which will return a horizontal range of cells, then export it usingExport -> Display option.

To export a graphical view in Excel, the Excel security level must be set to

"low" or "medium".

For example, in Excel 2002/2003, set the following:

Select from the menu bar: Tools -> Macro -> Security...The "Security" window opens.

In the ’Security Level’ tab, check Medium or Low , then click on [ OK ].

To export views:

1. One or several files can be exported.

To export one view:

Select the view, then select from the toolbar View -> Export ->Full …, OR select an element in the view, right click and selectExport -> Full …The original full view is exported.

Select the view, then select from the toolbar View -> Export ->Display …, OR select an element in the view, right click and selectExport -> Display …The current displayed view (ie. with filter applied on executedview) is exported.

If the view is already in the Executed View browser, an alternative is

to click on the icon. This triggers an original full view export (FullExport and not Export Display).

To export several views, click on the icon, OR choose View ->Export All... from the toolbar.This triggers an original full view export (Full Export and not ExportDisplay).

The ’Export View’ window opens.

364 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

2. Browse for the location where you want to save the view, give the appropriate’File Name’, then select the appropriate export format: xls, csv, xml, html,pdf.

Click on [ Save ].

3. The following message appears:

Export is Successfull. Do you want to open the exported file?

Click on [ Yes ] if you want to open the exported file. The file opens in anew window.

Click on [ No ] if you do not want to open the exported view.

The view is exported to the selected format, keeping the same look asin the tabular / graphical modes.

For the tabular mode, the rows and columns are in the same positions.Highlighting is displayed and the same colors are used. The informationabout the spatial scope, Execution Context, and view template parametersis also displayed.

For the graphical mode, the X-axis and Y-axis have the same data. Thesame colors are used. The legend is displayed. Information about the spatialscope, Execution Context, view template parameters is also displayed.

The view toolbar is not included in the export.

3BK 21216 AAAA PCZZA Ed.26 365 / 664

18 Views

Examples of Exported

View

Exported View in Excel Format:

Exported View in xml Format:

Exported View in csv Format:

366 / 664 3BK 21216 AAAA PCZZA Ed.26

18 Views

3BK 21216 AAAA PCZZA Ed.26 367 / 664

18 Views

368 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

19 Reports

This section describes how to manage reports. It describes how to create, edit,display, delete and execute reports.

3BK 21216 AAAA PCZZA Ed.26 369 / 664

19 Reports

19.1 Presentation

Note: The MUSE_REPORT_TEMPLATE_CREATION_LICENSE license must beinstalled for the reports creation.

The MUSE_REPORT_LICENSE license must be installed to execute reports.

A report template is composed of a set of view templates. A Report, which iscomposed of Views, enables the user to display results coming from Indicators/ Parameters in View Templates.

A Report enables the user to display results coming from Indicators orParameters in View Templates in a tabular way or graphical way. A Reportcontains the network objects, view templates and comment zones, and anExecution Context (period, interval, sampling, interpolation, reliability options).As a report template is composed of view templates, a report is composedof views. A report is also known as an Executed Report and is displayed inthe Report Viewer.

A report template is a formal description of a sequence of graphicalrepresentations of QoS indicator or parameter values. A report template isthen used to build from its definition and for one or several objects (accordingto the type of report template) a report that displays indicator or parametervalues for the considered date(s). A report template is mainly composed ofone or more view templates and comment zones.

The user may customize the report (e.g. define a title, view templates, specifythe legend, etc.). The user can save the report as a report template so that thesame template can be used to display any other report generated dynamicallyfrom the output of analysis services.

The report template type is required during the creation of the report templateand cannot be changed afterwards. Depending on the type of the QoS reporttemplate, different information is requested to define the report template.

Two types of reports distinguish:

Observation Reports

There are four types of observation report types:

Mono-Object Evolution Report

Multi-Object Evolution Report

Multi-Object Comparison Report

Mono-Object Distribution Report.

Mono-Object Distribution Reports are not available in WiMAX.

The following table presents the types of observation reports. ’Number ofObjects’ refers to the number of network objects used when creating theexecuted report. You can select a maximum number of 250 objects.The ’Covered Period’ refers to the date(s) entered in the Execution Contextwhen creating the executed report.

Report Type Number of Objects Covered Period View Constraints

Mono-Object Evolution One An interval None

370 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

Report Type Number of Objects Covered Period View Constraints

Multi-Object Evolution Many An interval Only one standardindicator or parameterper view

Multi-Object Comparison Many One date None

Mono-Object Distribution One One date Vector and/or matrixviews

Warning Reports.

For both observation and warning reports, you can select a maximum numberof 250 objects.

If you want to change the limit of 250 objects, you must modify the’analysis.desktop.objects.reports.limit’ parameter from the following file:/alcatel/muse/MUSEADWEBSTART/webapps/AD/rsc/com/alcatel/


If you want to change the limit of 20 reports executed in the reports browser,you must modify the following parameters:

’analysis.desktop.views.inside.report.limit’ parameter from the following

file: /alcatel/muse/MUSEADWEBSTART/webapps/AD/rsc/com/alcatel/


’MAX_REPORTS_TAB’ parameter from the following file:

/alcatel/muse/MUSEADWEBSTART/webapps/AD/rsc/com/alcatel/


’MAX_EXECUTED_REPORTS’ parameter from the following

file: /alcatel/muse/MUSE_MAAT/reports/rsc/com/alcatel/

muse/maat/reports/ReportsResourceFile.cfg

In order for the updates to be taken into account in Analysis Desktop, theAnalysis Desktop must be closed, then re-opened.


19.1.1 Mono-Object Evolution Report

A mono-object evolution report enables the user to display the evolution ofstandard indicators or parameters for the selected object between two dates.

The results are displayed in views in 2D graphs. A trend evolution can berequested on this type of report.

One network object is selected, and an interval of time is specified. Theresult is the following:

3BK 21216 AAAA PCZZA Ed.26 371 / 664

19 Reports

Figure 76: Mono-object Evolution Table

Figure 77: Example of Mono-object Evolution Table

372 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

19.1.2 Multi-Object Evolution Report

A multi-object evolution report enables the user to display the evolution ofstandard indicators or parameters for the selected objects between two dates.

The results are displayed in views in 2D graphs (only one standard indicator orparameter per view). A trend evolution can be requested on this type of report.

A color and a pattern are automatically set to each network object of the wholereport (the color and pattern set of standard indicator or parameter is ignoredsince there is only one standard indicator or parameter per view). All networkobjects are displayed in the same order in all views.

Many network objects are selected, and an interval of time is specified. Theresult is the following:

Figure 78: Multi-object Evolution Table made with an Object List

Figure 79: Example of Multi-object Evolution Table Made with an Object List

19.1.3 Multi-Object Comparison Report

A multi-object comparison report enables to compare several standardindicators or parameters for several objects at a given date.

The results are displayed in views in 2D graphs. Many network objects areselected, and one date is specified. The result is the following:

Figure 80: Multi-object Comparison Table

Figure 81: Example of Multi-object Comparison Table

3BK 21216 AAAA PCZZA Ed.26 373 / 664

19 Reports

19.1.4 Mono-Object Distribution Report


A mono-object distribution report enables to display specific vector and/ormatrix indicators and associated axis indicators for one object and a given date.

The results are displayed in specific views, in 2D or 3D graphs depending onthe chosen indicator (vector or matrix).

Figure 82: Mono-Object Distribution Table – Vector View

Figure 83: Mono-Object Distribution Table – Matrix View

374 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

19.1.5 Warning Reports

A warning report is a specific report composed of many views in which eachview is filtered according to its filtering indicator and sorted according to itssorting indicator. Therefore, the objects may be different from one viewto another.

The filtering mode is defined at a report level: it is a property of the warningtemplate report. A warning report can contain only views with a filteringindicator.

You can set the warning parameters to filter the cells according to differentcriteria. The criteria may be selected individually or combined:

Best / Worst ’Best’ indicates the “Good” objects, and ’Worst’ indicates the “Bad” objects.

’Best’ is greater if ’UpperIsFault = false’ on the filtering indicator.

’Worst’ is greater if ’UpperIsFault = true’ on the filtering indicator.

Top N The selection is made by keeping the Top N Best or Top N Worst Values.

Top N Variation Value The selection is made by keeping the Top N Best or Top N Worst Values of theAbsolute or Relative Variation based on the Reference Period.

Filtering on ColorValue

The selection is made by comparing the values of the filtering indicator with itsassociated thresholds, depending on the color choice.

The thresholds are those defined on the filtering indicator.

Filtering on VariationValue

The selection is made by comparing the computed variation to the chosenvariation.

The computed variation is the difference between the value of the filteringindicator’s warning date and the value of the reference period for absolutevariation.

For relative variation the absolute variation is divided by the value on the warningdate.

When computing a QoS warning report, two fields Before and After are usedto retrieve the evolution of the filtering indicator for the returned objects aroundthe report date. ’Before’ and ’After’ are given in number of periods with respectto the periodicity chosen when computing the report. This is extra informationadded to the tabular view and does not affect the filtering of data chosen for thewarning report or the graphical view.

3BK 21216 AAAA PCZZA Ed.26 375 / 664

19 Reports

19.1.5.1 ExampleThe following example presents the input for threshold and top combinations:

376 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

The following tables present the threshold output after applying the filteringcriteria to the example above:

Figure 84: Warning Reports: Best Value Filtering on Color

Figure 85: Warning Reports: Worst Value Filtering on Color

Figure 86: Value Filtering on Variation Value

3BK 21216 AAAA PCZZA Ed.26 377 / 664

19 Reports

19.1.5.2 Specific Icons for Warning ReportThe following table contains the icons for all the warning report possibilities:

378 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

19.1.5.3 Warning TableThe warning table is made out of:

The left part - containing the values of standard indicators for the report date

The right part - containing the evolution of the filtering indicator for the period

around the report date, according to the number of periods before and afterthe report date specified in the Execution Context.

The values of the filtering indicator in the left and right part are coloredaccording to the thresholds defined on the standard indicator. Note that for a“Top N objects” report, it is possible that all values are black.

If variation is selected, the last column of the left part contains the variationvalue. The column is named ’Relative Variation’ or ’Absolute Variation’(depending on the report template definition).

For a relative variation, the value is displayed in percentage and the unit is %

For an absolute variation, the unit of the filtering indicator is the unit of the

variation column.

If Sampling checks are selected, only the left part is colored according to therules defined in Highlight in View (Section 18.5.2).

19.1.5.4 Warning GraphicVariation, Before, and After on the Reference Period are not displayed on thegraphic view.

Warning for Area Threshold

The following formula must be verified to consider an object in warning:I warningDate >= value

Figure 87: Warning Table for Area Threshold

The following example presents a warning table for area threshold for selectedobjects with a ’Call drop rate > 4%’ and where ’RTCH attempts > 1000’.

Figure 88: Example of Warning Table for Area Threshold

3BK 21216 AAAA PCZZA Ed.26 379 / 664

19 Reports

Warning for Area Variation

The following formulas must be verified to consider an object in alarm:

For of absolute variation:I warningDate - I referenceDate >= value

For of relative variation:(I warningDate - I referenceDate) / I referenceDate >= value

Figure 89: Warning Table for Area Variation

The following example presents a warning table for area variation for selectedobjects with relative variation of the ’Call drop rate > 4%’ between ’J’ and ’J-1’and where ’RTCH attempts > 1000’.

Figure 90: Example of Warning Table for Area Variation

19.1.6 Report Title/Subtitle Format

The following title format is automatically filled in at report execution:<report type>’-’<title as defined in report template>

For the report title, the used font style is bold, and the font size is “DefaultSize + 2”.

The report subtitle format is:<’Trend from’ if Trend> <from date and time dependingon periodicity> <’to’ to date and time depending onperiodicity>

For the report subtitle, the used font style is normal, and the font size is“Default Size”.

380 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

19.2 Report Template Editor

19.2.1 Open Report Template Editor

To open the report template editor:


In the Alcatel-Lucent Analysis Desktop window, the right frame, ’Report’ tab,right click on any displayed report and select Report Template , OR

Figure 91: Open Report Template Editor

In the Analysis Desktop main window, click on Data -> Report Templates... ,

OR.

Press Ctrl+R.

The Report Template Editor window opens.

3BK 21216 AAAA PCZZA Ed.26 381 / 664

19 Reports

19.2.2 Create Report

To create a report:

1. In the ’Report Template Editor’ window, click on .

The ’Report Types’ window appears, listing five report types:

Multi-Object Evolution

Mono-Object Evolution

Multi-Object Comparison

Mono-Object Distribution

Warning.

2. Select the appropriate report type and click on [ OK ] OR double click on theappropriate report type.

The report template editor appears with default values and editable fields.

3. Fill in the appropriate fields.

FieldName


Name Name of the Report template to be created. ReportTemplate_<owner>_n

where<owner> is the ownerof the report.

ShortName

Short name of the report. Same as ’Name’.

Title Title of the report. Same as ’Name’.

Owner User who is creating the Report Template. The username you logged inthe application.

Visible Checked: if you want this report template to be visible in theReport Tree.

Unchecked: if you want this report template not to be visiblein the Report Tree, except for the Administrator.

Checked.

AccessRights


Description Text box to be filled in with operator description for the currentreport template.

System True, if this report template is a System view template - thus itcannot be modified or deleted except certain fields (Visible)only by the Administrator.

Grayed, otherwise.

382 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

FieldName


Families A table containing the families and sub families to which theview template can belong. There can be a maximum of foursub-levels for each family.

To add a new family, right click in the ’Families’ panel and

select ’Add Family’.The pre-defined family values are: Mono-ObjectDistribution Report, Mono-Object Evolution Report,Multi-Object Comparison Report, Multi-Object EvolutionReport, Warning Report, but you can edit your own’Family’.Select an existing ’User Family’, or edit your own ’Family’.Depending on the chosen family, the list of sub-familyoptions is changed. Select or type the appropriate one.

To remove an existing family, right click in the ’Families’panel and select ’Remove Family’. All its corresponding

sub-families are automatically deleted.

Note: If no family is added, then the report is not visible inthe function tree.

User defined according touser’s preference settings.

ViewTemplates

Use to add and visualize templates and comments on thecurrent report.

To add a view template, drag the required view template fromthe right frame to the ’View Templates and Comment Zones’panel.

CommentZones

This area is an optional feature of the report template, used toadd and visualize comments on the current report.

To add a comment, in the ’View Templates and CommentZones’ panel, right click and select ’Add Comment Zone’. Inthe ’Add Comment Zone’ box, add your comment, then clickon [ OK ].

AvailabilityDomain

The spatial (Network, Cell2G, Cell3G, RNC, CellZone, BSC)and temporal (hourly, daily, weekly, monthly) availabilitydomain according to the type of objects and the period.

The availability domain of a warning report template iscomputed as the set intersection of availability domains ofall referenced view templates.

3BK 21216 AAAA PCZZA Ed.26 383 / 664

19 Reports

When creating a Warning report, you must take into account the followingparameters:

ParametersSpecific toWarning Report

Description DefaultValue

Warning ReportType

The type of warning report to be defined:

Top N

Top N Variation

Color Filtering

Variation Filtering.

Top N

Best / Worst Best meaning the ’Good’ objects and Worst meaning the ’Bad’ objects.

Best is greater if UpperIsFault = false on the filtering indicator.

Worst is greater if UpperIsFault = true on the filtering indicator.

Worst

Top Objects Number of Top Objects.

0 means to use all the objects.

The selection is made either by keeping the:

Top N Best or Top N Worst Values, or

Top N Best or Top N Worst Values of the Absolute or Relative Variation

based on the Reference Period.

0

Variation Absolute or Relative.

If the variation is used with Top, then the selection is made by keeping theTop N Best or Top N Worst Values of the Absolute or Relative Variationbased on the Reference Period.

If the filtering uses the Variation Value, the selection is made by comparingthe computed variation to the chosen variation. The computed variation isthe difference between the filtering indicator’s warning date value and theReference Period’s value for absolute variation.

For relative variation, the absolute variation is divided by the value onthe warning date.

Unused

Variation Value Variation value. 0

Value Filtering onColor

The selection is made by comparing the Filtering Indicator’s values with itsassociated thresholds depending on the color choice.

Red Only

Reference Period The number of periods (determined by the periodicity when executing thereport) before the report date is used as reference date.

Its value is used when computing the relative and absolute variation, andvaries between 1 and 31 included.

1

384 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

ParametersSpecific toWarning Report

Description DefaultValue

Before Number of periods before the warning date. This is only for the tabulardisplay and does not affect the filtering or graphic display.

4

After Number of periods after the warning date. This is only for the tabulardisplay and does not affect the filtering or graphic display.

0

4. Click on .

5. Click on [ OK ] in the confirmation window.

19.2.3 Create Report by Copy

To create a report by copy:

1. In the ’Report Template Editor’ window, select the report template to be

copied, then click on .

2. The user can choose either to copy by duplicating only the report template(thus linking to the existing view templates) or to copy by also duplicatingrelated view templates.

The new report template is created with a default name: <oldname>_Copy_n ,where n is an incremental number to define a unique name.

The report template properties window is filled with the existing values,except for the name and owner.


The user becomes the owner of the report template.


The new report template is created and the report template tree is refreshed.

3BK 21216 AAAA PCZZA Ed.26 385 / 664

19 Reports

19.2.4 Edit Report

The user can edit an existing report by changing the existing report templatedata, or by adding/removing one/more view templates and/or comment zones.

To edit a report:

1. Open the report you want to modify.

2. In the ’Report Template Editor’ window, click on .

The property editor displays the ’Report Template Properties Panel’interface. The current attribute values of the selected report templateare displayed.


Only the owner of the report can update its values. The name of the reportcan also be updated.

If the owner of the report is not the one viewing it, the [ Edit ] button is grayed.

4. To add a view, drag the required view from the right frame to the ’ViewTemplates and Comment Zones’ panel.

5. To set existing object(s) in the graphical representation, select it (them) inthe ’Tabular View’ and drag and drop them to the ’Primary/SecondaryGraphic’ panels.

6. To edit a view in the comment zone, right click on it, and select ’Edit ViewTemplate’.

The ’View Template Editor’ window opens.

Click on .

Edit the appropriate fields, then click on .

Click on [ OK ] at the confirmation window, then click on [ Close ] to closethe ’View Template Editor’ window.

7. To add a comment, in the ’View Templates and Comment Zones’ panel, rightclick and select ’Add Comment Zone’.

In the ’Add Comment Zone’ box, add your comment, then click on [ OK ].

8. To remove a view or a comment zone, select it / them, right click and select’Remove’.

9. To reorder the views or comment zones in the report:

Use the Up / Down arrows, or

Right click and select as appropriate.

Select:

’Move to first position’

’Move to last position’

’Move up’

’Move down’.

10. To save the changes, click on [ OK ].

386 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

19.2.5 Delete Report

Note: A report cannot be deleted if it is scheduled.

To delete a report, select the report, then:

From the "Report Template Editor" window, click on , OR



The following question appears: Are you sure you want to delete report

template <report_name>?

If only one report is selected to delete, click on [ Yes ].

If multiple reports are selected to delete, click on [ Yes to All ].

The report/s is/are deleted from the operator function tree.

3BK 21216 AAAA PCZZA Ed.26 387 / 664

19 Reports

19.3 Execute Report

19.3.1 Execute Report

1. Select the network element(s) and report template(s) of the same type, then:

Drag and drop them in the report viewer, OR

Select Report -> Execute Report... , OR

Press Ctrl+Shift+R.

The same can be done for network element(s) and:

View templates from the Functions Browser

Indicators from the Functions Browser.In this case, the result is a report with one view per indicator.For example, if 10 cells and 4 indicators are selected and dropped in theexecuted report, 4 views are created in the executed report.


3. Click on [ Execute ] to execute the report.

When executing a report containing a view with indicators, if “Nerr” value isdisplayed for a cell, this indicates a numeric error due to a miscalculation ofan indicator (for exemple when dividing by zero).

If an entire view is empty, then a message is written in place of the reportarea explaining that there is no data available for the report: ”No data isavailable for the request”.

The display of "No data is available for the request" can be avoided in the caseof a warning report definition when the operator has defined the Warning withthe default value, by replacing the “Top Objects” default value “0”, for examplewith the value “10”:

Warning Report Type: Top N

Worst

Top Objects: 0 -> change it here with value “10”

Variation Value: 0.0

Value Filtering on Color: Red Only

Reference Period: 1

Before: 4

After: 0

Depending on the number of network objects selected, the number and thetype of report templates, see the possibilities below:

388 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

Figure 92: Number of Reports Generated Based on Report Type, Number ofNetwork Objects, and Number of Report Templates Selected

The report viewer displays the executed report to the operator, containingthe following:

The QoS Requirement used when executing the report

The Working Zone used to execute the report

The sub-title for mono-object evolution or mono-object distribution report:the identifier of the selected object as displayed in tree gadget followed

by the begin date and the end date.The sub-title for multi-objects comparison and warning report: the objecttype of the requested objects followed by the requested date. Moreover ifone trend is selected for the report (only for object evolution report), thetype of the trend is displayed after the period.

The format of the date depends on the selected period (taking intoaccount user preferences):

For 1/4 Hour period, the date is displayed as: DD/MM/YYYY – HH:MM

For 1/2 Hour period, the date is displayed as: DD/MM/YYYY – HH:MM

For hour period, the date is displayed as: DD/MM/YYYY – HH

For Day period, the date is displayed as: DD/MM/YYYY

For Week period, the date is displayed as: YYYY-Week NN whereNN is the week number (01 to 53)

For Month period, the date is displayed as: NameOfTheMonth YYYY

To enlarge the executed report to window size, double click on its title tab, orclick on the arraw from the splitter.

3BK 21216 AAAA PCZZA Ed.26 389 / 664

19 Reports

4. To schedule the report, refer to Schedule Reports (Section 19.3.4).

Note: You can execute again a report template that has already been executed.

Each time a report is scheduled, a job is created.

In order to manage jobs, there are operations which can be performed from theAnalysis Desktop, from the Administration menu, or from both (see the followingtable). Refer also to NPO Administration Guide, section Manage Job Results.

Job Type ADMIN Analysis Desktop

Create job -

View job result

Delete job result

Note: Automatically done after the job isviewed.

Delete job -

390 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

19.3.2 Edit Executed Report Interactively

The user can change the display properties that appear in the executed reportinteractively. The update appears directly on the displayed executed report.

19.3.2.1 Edit TitleThe title of the executed report is the short name of the report templatename. Only in the case of an executed report from a view, the title is of thefollowing format: Report_<n> , where n is an incremental number, to define aunique name.

To edit the title of an executed report:

1. Right click on the title and select Rename , OR

Select the title tab, then select from the menu bar Report -> Rename .

The "Report View" window appears.

2. Type the appropriate title of the executed report, then click on [ OK ].

The executed report title is updated.

19.3.2.2 Add Network Objects to ReportSelect the network objects you want to add, then drag & drop them in the reportviewer using Ctrl-Drag&Drop (depending on the user preferences).

Depending on the user preferences, the selected network objects are added tothe executed report, or a new report is created. The same Execution Context isused for the new items. The new report is displayed.

19.3.2.3 Add Views to ReportTo add one or several new view(s) to the executed report:

1. Select the appropriate view template(s) from the View Template Tree.

2. Ctrl + drag & drop them into the executed report.

Depending on the value set in the “Drag & Drop modifier to add” field fromViews/Reports User Preferences, the key used for the adding proceduremay differ from “Ctrl”.

During this operation the cursor changes to if the view is compatiblewith the executed report.

The selected objects are added to the executed report, or a new reportis created if the “Open results in new report on editing” field is checked inthe Views/Reports User Preferences. The availability domain of the reportis checked. The view templates are executed and the resulting executingviews are added to the end of the report.

3BK 21216 AAAA PCZZA Ed.26 391 / 664

19 Reports

19.3.2.4 Paste View into ReportCopy the view from the clipboard and paste it into the report viewer using Ctrl +V buttons. The pasted view is executed.

Depending on the user preferences, the resulting executed view is added at theend of the report, or as a new report.

You can also copy and paste an unsaved view into the report. If the view type isnot valid for the executed report, an error message is displayed.

19.3.2.5 Remove Network Objects from ReportSelect the network objects you want to remove, then press Ctrl-Shift Drag&Drop(depending on the user preferences).

Depending on the user preferences, the selected items are removed from thecurrent executed report or in a new report. The same Execution Context isused for the remaining items.

19.3.2.6 Remove Views from ReportSelect the views you want to remove, then press Ctrl+Shift+Drag&Drop.

Depending on the value set in the “Drag & Drop modifier to remove” field fromViews/Reports User Preferences, the key used for the removing proceduremay differ from “Ctrl+Shift”.

Depending on the Views/Reports User Preferences, the selected views areremoved from the current executed report or in a new report. The sameExecution Context is used for the remaining items.

392 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

19.3.2.7 Roll Up / Drill Down TemporallyThis sub use case allows the operator to Roll-up / Drill-down temporally inthe executed report.

As a prerequisite, the executed report must already exist in the tabular /graphical report.

To Roll Up, select Report -> Temporal Scope -> Roll Up , or click on theicon from the report toolbar

To Drill Down, select Report -> Temporal Scope -> Drill Down , or click on the

icon from the report toolbar.

The interval on the report changes depending on the temporal availability.Depending on the user preferences, the data is updated either in the executedreport or in a new report.

Below day periodicities such as: 4Hr, 1/2Hr,1/4Hr, RAW, etc. are treated as“Hourly”. If the user rolls up from one of these periodicities, it is the same asrolling up from “Hour”. Drilling down from “Day” always goes to “Hour”, if it isavailable, and not to one of the other below day periodicities.

Example :

’Cells’ are displayed on a ’Day’ basis and the current availability domain of theexecuted report is:

Hour Day Week Month

Network X

RNC X

Cell X X

Adjacency X X

If the user Rolls-Up from ’Day’, the new period will be ’Month’ and not ’Week’,because ’Cells’ are not available on ’Week’ but are on ’Month’.

The user cannot Drill-Down because ’Cells’ are not available on ’Hour’.

3BK 21216 AAAA PCZZA Ed.26 393 / 664

19 Reports

19.3.2.8 Roll Up / Drill Down SpatiallyThis sub use case allows the operator to interactively Roll-up / Drill-downspatially in an executed report, and add or remove network objects.

For this, the executed report must already exist in the tabular / graphical report.

To Roll Up, select Report -> Spatial Scope -> Roll Up , or click on theicon from the report toolbar

To Drill Down, select Report -> Spatial Scope -> Drill Down , or click on the

icon from the report toolbar.

The network objects in the report change depending on the spatial availability.

The interval on the report changes depending on the spatial availability. Thedata is updated in the executed report. The Execution Context remains thesame.

When rolling-up or drilling-down to a relation, the relations that have the currentnetwork object as the source are used; i.e. if the current object is Cell1 andthe user drills-down to Adjacency, then all the Adjacencies have Cell1 as thesource are displayed in the resulting view.

When triggering a Drill-Down for a mono-object evolution or a mono-objectdistribution report, then N reports are generated as when executing them.

In the case of a warning report with Filtering Unavailable Objects option andconsistent criteria, the QoS Availability Indicator must be available in the targetavailability domain when rolling-up or drilling-down.

Example :

’Cells’ are displayed on a ’Week’ basis and the current availability domainof the executed report is:

Hour Day Week Month

Network X

RNC X X

Cell X

Adjacency X X X

If the user Rolls-Up from ’Cell’, the new network object will be ’Network’ andnot ’RNC’, because there is no ’RNC’ on ’Week’ but ’Network’ is available on’Week’ periodicity.

If the user Drills-Down from ’Cell’, the new network objects will be all theoutgoing ’Adjacencies’ for all the ’Cells’ because ’Adjacencies’ are available on’Week’ periodicity.

394 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

19.3.2.9 Propagate Report Contents to Network Object / Function TreesA view topology / function selection from report can be propagated to networkobjects / view template trees.

To propagate network objects / view templates from report to the respective tree:

Click on icon from the report toolbar, then select as appropriate:

’Propagate All’



OR

Select Report -> Propagate Selection from the toolbar, then select asappropriate::

’All’

’All Network Objects’

’All Data’

The network objects / view templates are selected in their respective treesdepending on the options.

19.3.2.10 Propagate View Selection to Network Object / Function Trees fromExecuted Report

To propagate a view selection from an executed report:

1. From the view inside an executed report, click on icon from the viewtoolbar, OR right click in the view and select Propagate .


’Propagate All’



’Propagation Selected Network Objects’, for tabular view only

’Propagate Selected Data’, for tabular view only.

3BK 21216 AAAA PCZZA Ed.26 395 / 664

19 Reports

19.3.3 Edit Executed Report Using Dialog Box

19.3.3.1 Open Executed ReportTo open an executed report:

Right click on the title of the executed report, and select ExecutedReport... , OR

Select View -> Executed Report... from the toolbar.

The ’Executed Report Properties’ window is displayed.

The opened window contains three menu tabs: Report Template Properties,Execution Context, and Spatial Scope. See the chapters below (19.3.3.2 -19.3.3.4) for information on how to edit them.

396 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

The following table presents the buttons displayed in the ’Executed ReportProperties’ window.

Button Name Used to...

[ Edit ReportTemplate ]

Launch the report template editor.

You can change the report template properties. Refer toEdit Report (Section 19.2.4).

After applying the changes in the report template editor,the report is refreshed.

[ Update Report ] Update the performed changes to the current report.

[ Create Report ] Create a new report with the performed changes.

[ Close ] Close the report.

19.3.3.2 Edit Report Template Properties1. Select the ’Report Template Properties’ tab.

The ’Report Template Properties’ panel is displayed.

2. Click on [ Edit Report Template ].

The ’Report Template Editor’ window opens. Change as appropriate thereport template properties. Refer to Edit Report (Section 19.2.4).

3. You can:

Apply the changes made on the current report, by clicking on [ Update

Report ], or

Create a new report with the performed changes, by clicking on [ Create

Report ].

The executed report is refreshed.

19.3.3.3 Edit Report Execution Context1. Select the ’Execution Context’ tab.


2. Update as appropriate the displayed fields. Refer to ’Execute Report’,step (2).

3. You can:

Apply the changes made on the current report, by clicking on [ UpdateReport ], or

Create a new report with the performed changes, by clicking on [ Create

Report ].

The report viewer displays the resulting executed report.

3BK 21216 AAAA PCZZA Ed.26 397 / 664

19 Reports

19.3.3.4 Edit Report Spatial Scope1. Select the ’Spatial Scope’ tab.


2. To add network objects from the spatial scope, select them and drop themto the report panel.



3. You can:

Apply the changes made on the current report, by clicking on [ Update

Report ], or

Create a new report with the performed changes, by clicking on [ CreateReport ].

The report viewer displays the values with the new data.

19.3.4 Schedule Reports

Note: The MUSE_SCHEDULING_LICENSE license must be installed for thescheduling of reports.

The user can schedule the execution of reports on a daily, weekly or monthlybasis.

To schedule reports:

1. In the ’Execution Context’ window, click on [ To Be Scheduled ] radio button.

A new panel with three tabs (’Date’, ’General’, ’Repeat’) appears, with inputto create a schedule for the report execution.

2. In the ’Date’ tab, fill in the appropriate fields as presented in the table below.


Completion Date The date at which the scheduled report is executed, i.e. the report result becomesavailable at the morning of this date.

The default date is the next day from the current date.

If the report repeats, then this is the first schedule date.

The date can be selected either by using the select bar, or by clicking on andchoosing it from the displayed calendar.

The supported date format is mm/dd/yyy.

From Start date of the observation period for execution, expressed relatively to theCompletion Date in a number of days/weeks/months (according to the selectedperiodicity).

Date from which the scheduled execution starts.

The default value is 1 day/week/month before the Completion Date.

At Start time of the observation period for execution.

398 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports


To End date of the observation period for execution, expressed relatively to theCompletion Date in a number of days/weeks/months (according to the selectedperiodicity).

The default value is 1 day/week/month before the Completion Date.

At End time of the observation period for execution.

The supported time format is hh (00 to 23) mm (00 to 59).

3. In the ’General’ tab, fill in the appropriate fields.


Job Title Defines the name of the job. This can be different from the report name.

Default values:

<Report short name>, if one report is selected

MultipleReport, if there are several reports selected

<Report short name>_Repeat or MultipleReport_Repeat, if one or severalreport(s) is/are selected and repeat option other than ’None’ is selected.

3BK 21216 AAAA PCZZA Ed.26 399 / 664

19 Reports


Owner Defines the owner of the job.

This parameter is read-only.

Working Zone Defines the current Working Zone being used by the current user.

This parameter is read-only.

Output Format Defines the output format for the scheduled report.

Possible values: Analysis Desktop (displayed in Report Viewer), XLS, XML, CSV,HTML, PDF.

For Detailed Diagnosis execution only HTML format is available.

4. To schedule the report on an entire working zone, select [ Entire WorkingZone ].

This may be particularly useful when executing a warning report.

If the report is executed on the entire working zone, then the spatial scopecontains all the network objects in the working zone of the same type asthe executed report.

For example, if the report was executed on Cell 3G’s in Working Zone A,then the spatial scope of the executed report are all the Cell 3G’s that werein Working Zone A at the time when the report was executed.

5. In the ’Repeat’ tab, set the appropriate frequency for the scheduled reportrepetition.

By default, the repeat option is ’None’, so the report is only scheduled once.

OptionName


None - No report repetition is scheduled.

If the repeat option is ’None’, then all the other fields for the rest offrequency radio buttons are not visible.

400 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

OptionName


Every Specifies the recurrence interval in days.

Default value: 1 Day.

Day

End On Specifies the final date of the repeating report.

Default value: the next possible date after the scheduled date.

If changing the ’End on’ date, ensure that it is not less than thescheduled start date.

Every Specifies the recurrence interval in weeks.

Default value: 1 Week.




Week

Repeat On Click on the preferred day(s) of the week when you want the reportto be repeated.

Every Specifies the recurrence interval in months.

Default value: 1 Month.




Month

By Select one of the two possible values:

’Day’, to set a repeating weekday, such as the last Friday of eachmonth

’Date’, to set a repeating date in the month, such as the 15th.

3BK 21216 AAAA PCZZA Ed.26 401 / 664

19 Reports

6. Click on [ Execute ].

The scheduled reports are executed during the night, after the loading ofconsolidation.

To view or delete scheduled reports, reffer to Manage Scheduled Jobs.

402 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

19.3.5 Display Pending Executed Reports

After a report is scheduled, it can be visualized in two ways:

From the Analysis Desktop:

Select Jobs -> Display Pending Executed Reports... from the menu

bar, OR


Press Ctrl+G.

The ’Pending Executed Reports’ window opens, displaying the list ofexecuted reports.

3BK 21216 AAAA PCZZA Ed.26 403 / 664

19 Reports

To view one or several pending executed reports, select them by checking

the checkbox , then click on [ OK ].All the reports are opened one by one in a sequential order. If the reportoutput is not Analysis Desktop, then the user is first prompted to save thereport and then to open it to view it.

Once a report has been saved or viewed in the Analysis Desktop, then it ismarked as viewed and it no longer appears in the list of pending executedreports. If the current Working Zone is not the Working Zone in which thereport was scheduled, then when displaying the executed report, anyobjects not belonging to the current Working Zone are shown as ’unknown’.

From the NPO, as described in the NPO Administration Guide, in Download

Job Results.

19.3.6 Show Second Report Browser

To create a second Report Browser, in order to better visualize/compareexecuted reports, select from the Analysis Desktop menu bar: Report ->Show Second Report Browser .

A second Report Browser appears to the right of the already existing one.

Reports can be executed in this browser by draging and dropping theappropriate network element(s) and report template(s) in this second reportbroswer.

404 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

19.4 Using Executed Report

19.4.1 Toolbar

The following toolbar icons are available for the executed report:

The following table gives a brief description of the executed report toolbar icons:

Icon Description

Save Executed Report as Template (Section 19.4.11)

Synchronize Zooming in Report (Section 19.4.3)

Synchronize Cursors in Report (Section 19.4.2)

Display Grid in All Report Views (Section 19.4.6)

Highlight in All Report Views (Section 19.4.5)


Roll Up Spatially

Drill Down Spatially

3BK 21216 AAAA PCZZA Ed.26 405 / 664

19 Reports

Icon Description

Roll Up Temporally

Drill Down Temporally

Propagate Report Contents to Network Object / Function Trees (Section 19.3.2.9)

In case the executed report window is too small, up & down arraws aredisplayed to navigate among the executed report related icons - as seenin the figure below.

19.4.2 Synchronize Cursors in Report

The vertical and / or horizontal cursor in a report can be synchronized. Whensynchronized, the bar cursors of all graphs belonging to the same report arelinked, and they move in unison. The scroll bar is also linked.

Synchronization is only available when at least two views have the same scale.

To activate cursors synchronization, click on the icon from the reporttoolbar.

SynchronizationChoice

Description

None When moving the view cursor either horizontally orvertically, the view cursor does not move in the otherviews in the report.

406 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

SynchronizationChoice

Description

Horizontal When moving the cursor horizontally, the vertical cursoron the view is synchronized with the vertical black barcursor on the other views.

Vertical When moving the cursor vertically, the horizontal cursoron the view is synchronized with the horizontal black barcursor on the other views.

The cursors are synchronized according to the user’s choice.

19.4.3 Synchronize Zooming in Report

The zoom fields in all the graphs belonging to the same report can besynchronized.

When zooming is synchronized, the scroll bar is also linked and you cantoggle it on and off.

Zooming synchronization is only available when at least two views have thesame scale.

To activate the zoom synchronization:

1. Click on the icon from the report toolbar.

2. Zoom in one of the views that shares the same scale as another one.

The current view and the other views sharing the same scale are zoomed.

19.4.4 Filter in Report

This sub use case allows the operator to choose what to be displayed and whatnot to be displayed through filters.

Filtering allows showing/hiding of:

Network Objects for a Multi-Object report

Functions, for example hide one indicator

Periods, for example filter Monday’s data between 10/10/2006 to 11/10/2006,

Filter 00h. This is available only on Mono/Multi Object Evolution reports.

This filtering applies to all the views in the report.

All types of filters which can be applied to views in the Viewer Browser can beapplied to views inside a report. To check Filters which can be applied to Viewsrefer to Filter in View (Section 18.5.5).

The filtering can be toggled on and off.

19.4.5 Highlight in All Report Views

Highlighting can be turned on or off in all the views of an executed report atonce.

To trigger the highlighting:

3BK 21216 AAAA PCZZA Ed.26 407 / 664

19 Reports

Select View -> Highlighting (On/Off)

Click on the icon from the report toolbar.

The highlighting turns on. Selecting the option again turns the highlighting off.

408 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

19.4.6 Display Grid in All Report Views

The grid display can be toggled on or off in all the views of the report at once.

To activate the grid display, click on the icon from the report toolbar.

Grids are displayed in the views of the report.

19.4.7 Edit View from Executed Report Template

A view can be modified within an executed report. Note that an exceptionapplies: you cannot modify the spatial scope or Execution Context of anindividual view, since these apply to the entire report.

1. Select the report template that contains one or several views you wantto update.

2. Right click on the appropriate view and select Executed View...The ’Executed View Properties’ window is displayed.

3. Perform as needed:

Edit View Template Properties (Section 18.4.4.2)

Edit View Execution Context (Section 18.4.4.3)

Edit View Spatial Scope (Section 18.4.4.4).

If the view template is modified and not saved, then the executed report ismarked as needing to be saved.

If the view template is modified and saved with the same name, then thereport is not marked as needing to be saved.

If the view template is modified and saved with a new name, then the reportis marked as needing to be saved.

19.4.8 Duplicate Executed Report

To duplicate an executed report:

Right click on the report name tab, and select Duplicate , OR

Select Report -> Duplicate from the toolbar.

A new executed report is created with:

A default name: <oldname>_Copy_n , where ’n’ is an incremental numberto define a unique name

The values of the duplicated executed report.The new report template contains copies of each view within the reporttemplate.For example, if you have ’Report A’ containing ’View B’ and ’View C’, whenyou duplicate the report, the result is ’Copy Report A’ containing ’Copy ViewB’ and ’Copy View C’. This is useful in the case when you are not the ownerof a report and its corresponding view templates.

3BK 21216 AAAA PCZZA Ed.26 409 / 664

19 Reports

19.4.9 Rename Executed Report

To rename an executed report:

1. Right click on the report name tab, and select Rename , or select Report ->Rename from the toolbar.

The ’Report View’ window opens.

2. Type the new name of the report, then click on [ OK ].

The executed report is saved taking into account the new name.

19.4.10 Automatic Views and Legends Resizing in Report

You can choose to automatically resize all views and legends of a report (usingthe report tool bar or if the Default resize of views inside report user preferencehas been selected for report execution).

The height of every view inside the report is adjusted such that for the viewsdisplayed in Tabular mode, the height of the view should be adjusted such thatall lines are visible and not more. This means that each view can have adifferent height depending on its content (i.e. a view displaying 10 indicatorsis bigger than a view displaying 3 indicators). If a view has been rotated, theheight must take care of the real dimension displayed vertically.

Views displayed in graphical mode are displayed using a default height. So ifthey have been resized earlier, they are resized back to the default height.

Every graphical view legend width is adjusted such that for views displayedin Graphical mode, the automatic resize updates the legend width up to themaximum requested width to make the complete legend visible (i.e. themaximum width among all views must be applied to all views). In other words,legend of all views must have the same width, this width being the maximumof all legend widths.

19.4.11 Save Executed Report as Template

If the exeuted report is modified and not saved, it is marked with ’*’ as needingto be saved.


Right click on the executed report and select Save as Template... , OR

Select Report -> Save as Template... from the toolbar, OR

Click on icon from the report toolbar, OR

Press Ctrl+Shift+S.

The ’Save Report Template’ window opens.

410 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

2. Type the report template name, then click on [ OK ].

The executed report is saved as template.

19.4.12 Close Executed Report(s)

To close an executed report:

Right click on the report name tab, and select Close , OR

Select Report -> Close .

To close all executed reports

Right click on a report name tab, and select Close All , OR

Select Report -> Close All .

3BK 21216 AAAA PCZZA Ed.26 411 / 664

19 Reports

19.4.13 Export Reports

There is a limitation when exporting reports in Excel to worksheetscontaining a maximum of 65,536 rows and 256 columns.In case of a worksheet containing more than 256 columns, a workaroundis to use the “Transpose” function from Excel in the report from AnalysisDesktop, which will return a horizontal range of cells, then export it usingExport -> Display option.

To export a report containing graphs in Excel, the Excel security level

must be set to "low" or "medium".

For example, in Excel 2002/2003, set the following:

Select from the menu bar: Tools -> Macro -> Security...The "Security" window opens.

In the ’Security Level’ tab, check Medium or Low , then click on [ OK ].

To export reports:

1. The user can export one or several files.

To export one report:

Select the report, then select from the toolbar Report -> Export ->Full …, OR select an element in the report, right click and selectExport -> Full …The original full report is exported.OR

Select the report, then select from the toolbar Report -> Export ->Display …, OR select an element in the report, right click and select

Export -> Display …The currently displayed report (ie. with filter applied on executedreport) is exported.

If the report is already in the Executed Report browser, an alternative is

to click on the icon from the Executed Report browser. This triggersan original full report export (Full Export and not Export Display).

To export several reports, click on the icon, OR choose Report ->Export All... from the toolbar.This triggers an original full report export (Full Export and not ExportDisplay).

The ’Export Report’ window opens.

2. Browse for the location where you want to save the report, give theappropriate ’File name’, then select the appropriate export format: xls,csv, xml, html, pdf.

Click on [ Save ].




412 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

Click on [ No ] if you do not want to open the exported file.

The report is exported to selected format, keeping the same look as inthe executed report. The information about the spatial scope, ExecutionContext, and report template parameters is also displayed.

The comment zones are exported as displayed. The reports and commentzones are exported in the same order as displayed in the executed report.

The report toolbar is not exported.

3BK 21216 AAAA PCZZA Ed.26 413 / 664

19 Reports

Examples of Exported

Report

Exported Report in Excel Format:

Exported Report in xml Format:

Exported Report in csv Format:

414 / 664 3BK 21216 AAAA PCZZA Ed.26

19 Reports

Exported Report in pdf Format:

3BK 21216 AAAA PCZZA Ed.26 415 / 664

19 Reports

19.4.14 Export Views from Executed Report

A view can be exported from an executed report.

From the view inside an executed report, perform the steps described inExport Views (Section 18.5.15).

416 / 664 3BK 21216 AAAA PCZZA Ed.26

20 Web Publishing

20 Web Publishing

This section describes how to publish executed views/reports on a web page.

3BK 21216 AAAA PCZZA Ed.26 417 / 664

20 Web Publishing

20.1 Presentation

The “Web Publishing” feature is not available for B10 GSM.It is only used for NPO W-CDMA UA6.

This feature enables the “light” client to display computed views and reports ina web browser, accessible from any PC with a web browser, without having toinstall the Analysis Desktop.

Each published view/report is stored in a web file repository in its existingXML format.

The following assumplitions apply:

Web publishing is applicable to views/reports/reports scheduling

For W-CDMA, no nodes are selected in the view/report tree

The date format of the executed view/report may not be the same inAnalysis Desktop and the published view/report

Views executed with temporary indicators can be publishedIn this case, if the view/report is published after one of the temporaryindicators has been deleted, an appropriate error message is displayed tothe user.

Views that do not request any execution context when executed cannotbe published

The views and reports can be re-executed with the modification of the

temporal or spatial scopeThe temporal scope is limited to the start and end date.The spatial scope is limited to a subset of the existing spatial scope.

If a view/report is executed with the publishing option selected, and inAnalysis Desktop, inside the executed view/report another operation like

spatial/temporal execution is performed, the view/report is no longerpublished. The publish option is implicitly unchecked from the executed

view properties.If you want to publish the view/report again, edit the executed viewproperties and select the web publish option from it. The same procedure isused to interactively add objects to an executed view or to re-execute a view.

If you execute a mono-object evolution report in Analysis Desktop with ’m’

network objects (m >1, e.g. m=4), the request consists of ’m’ objects. The

response is shown in Analysis Desktop in four tabs for this case.In such a scenario, if the you selected the "web publish" option and laterrequest for the published reports from the browser, four reports will belisted for publishing.

418 / 664 3BK 21216 AAAA PCZZA Ed.26

20 Web Publishing

20.2 Display Published Executed Views/ReportsBy performing an [ Execute and Publish ] from the "Execution Context" window,the executed view/report is exported in html.

To access it, type in an internet browser the following address:http://<IP>:8190/maat/report/npowebviewer

The list of published executed views/reports for the current user appears in theleft ’Available Reports/Views’ frame, as a tree structure.

The user login name is displayed, along with the dates of the executedviews/reports.

To view the executed views/reports for a displayed date, click on the left arrowto expand it.

The name of the view/report is displayed in the left tree in the following format:<view/report_name>_<published_date>_<published_time> .

The tree nodes are sorted based on the <published_date> ,<published_time> , and <view/report_name> .

To reload the page, click on icon in the ’Available Reports/Views’.

To display an executed view/report, click on its name in the ’AvailableReports/Views’ tree.

The corresponding view/report is displayed in the right frame.

3BK 21216 AAAA PCZZA Ed.26 419 / 664

20 Web Publishing

The tabular and graphical modes can be displayed, by choosing thecorresponding tab. If a view/report doesn’t have graphical data, then only

“Tabular” is shown.No user actions are allowed on graphical chart.

The highlighting is kept for the table data as in Analysis Desktop.

If the selected executed views type is “Multi Object Comparison forparameters” then, instead of a single tabbed pane to display the executed

view, continuous tabbed panes are displayed for each “display choice”

in the execution context.

Figure 93: Tabular Data of the Executed View

420 / 664 3BK 21216 AAAA PCZZA Ed.26

20 Web Publishing

Figure 94: Graphical Data of the Executed View

3BK 21216 AAAA PCZZA Ed.26 421 / 664

20 Web Publishing

Figure 95: Tabular Data of the Executed Report

422 / 664 3BK 21216 AAAA PCZZA Ed.26

20 Web Publishing

Figure 96: Graphical Data of the Executed Report

3BK 21216 AAAA PCZZA Ed.26 423 / 664

20 Web Publishing

Figure 97: Multi Object Comparison Executed View for Parameters

424 / 664 3BK 21216 AAAA PCZZA Ed.26

20 Web Publishing

20.3 Re-execute Published Executed Views/ReportsTo re-execute the selected view/report:

1. Display the appropriate published executed views/reports.

2. In the right frame, click on the [ Update ] button.

The "Re-Execution Context Page" appears.

Figure 98: Multi Object Comparison Executed View for Parameters

3. In the ’Spatial Scope’ panel, select the network objects you want to usefor the view/report re-execution.

By default, the list of all the network objects previously used for theview/report execution context are displayed in their friendly name.

To select all network objects, click on [ Select All ].

To deselect all network objects, click on [ Deselect All ].

4. In the ’Temporal Scope’ panel, set the ’Start Date’ of the execution context.

The date can be set either by typing it in the mm/dd/yyyy format, or by

clicking on and choosing it from the displayed calendar.

Select the appropriate execution start hour and minute from the drop-downlist.

5. In the ’Temporal Scope’ panel, set the ’End Date’ of the execution context.

The date can be set either by typing it in the mm/dd/yyyy format, or by

clicking on and choosing it from the displayed calendar.

Select the appropriate execution end hour and minute from the drop-downlist.

3BK 21216 AAAA PCZZA Ed.26 425 / 664

20 Web Publishing

6. Click on [ OK ] to submit the re-execution content.

The re-executed view/report with the set user preferences and the ’AvailableReports/Views’ tree are refreshed.

Note: When a view/report has been published then later deleted, the re-execution ofsuch a view/report results in an exception.

426 / 664 3BK 21216 AAAA PCZZA Ed.26

21 Diagnosis

21 Diagnosis

This section describes how to perform diagnosis of QoS problems.

3BK 21216 AAAA PCZZA Ed.26 427 / 664

21 Diagnosis

21.1 PresentationIn case of one of the following situations, the operator may want to triggerdiagnosis reports:

A QoS indicator crossed a threshold

A QoS indicator is suspected to be faulty, even if no threshold was crossed

(it is even possible that no threshold is associated to the indicator)

An alarm was received.

To retrieve the cause for an identified QoS problem, or to check the logicalconfiguration of any topology objects, particularly cells and adjacencies,diagnosis reports are executed.

The diagnosis execution results can be viewd as:

A synthetic summary, provided in the Views BrowserThe synthetic report of the standard diagnosis is displayed in icon format

( , , ).

A node per node detailed report, displayed on demand in the Reports

Browser.

Detailed diagnosis reports consist of test nodes grouped in a tree, based oncausality links. A detailed diagnosis tree is not limited in size.

The trees start with an observed QoS problem, an alarm or nothing is specified,and go from node to node to the possible reasons until a root problem causeis found.

See also Execute Diagnosis (Section 21.5).

There are system available dignosis scenarios, but the user can also createtheir own. This is done through the Diagnosis Editor, which is based on theEclipse platform concepts.

The Eclipse framework is structured around the concept of plug-ins, and usesPyDev Node Code Editor.

Diagnosis scenarios consist of test nodes grouped in a tree based oncausality links. A link is oriented from a consequence node to a causal node.A consequence node can have several causal nodes. The execution of adiagnosis scenario is the process of executing its causual nodes applied on anexecution context.

For detailed information on Diagnosis Editor, Scenario Creation, Node CodeUpdate, Introduction in Python, refer to NPO Diagnosis Development Guide.

428 / 664 3BK 21216 AAAA PCZZA Ed.26

21 Diagnosis

21.2 Display Diagnosis Scenario PropertiesSee Display and Edit Properties (Section 3.3).

You can also view the "Diagnosis Scenario Properties" window by clicking inthe Detailed Mode Diagnosis on the ’See node code’ hyperlink.

3BK 21216 AAAA PCZZA Ed.26 429 / 664

21 Diagnosis

ParameterName


Name Name of the Diagnosis Scenario Yes Yes

Description Description of the scenario No Yes

Owner Displays the name of the owner for the scenario Yes Yes

System True if this scenario is a System Scenario Yes Yes

Access Rights Access rights for Public or Private Yes Yes

430 / 664 3BK 21216 AAAA PCZZA Ed.26

21 Diagnosis

ParameterName


Visible Yes, if this scenario is visible in the Analysis Desktop.

No, if this scenario is not visible in AD.

No Yes

Validated Flag indicating if the user has considered that this scenario iscorrect and executable

No Yes

Type Scenario type (Diagnosis or Complex rule) Yes Yes

Severity Error or Warning Flag, used to discriminate complex rules (Tuningchecks)

Yes Yes

Name Name of the scenario dictionary No Yes

Version Version of the dictionary. Yes Yes

System Whether it is a system or customerdictionary.

Yes Yes

Date Date the scenario dictionary was loaded. Yes Yes

Author Author of the scenario dictionary. Yes Yes


Description Details about scenario dictionary. Yes Yes

Families Table of associated family and sub families of the scenario.

Family - The family to which this scenario belongs.

Sub-Family Depth 1 - The sub-family to which this scenario

belongs


scenario belongs

Sub-Family Depth 3 - The sub-sub-sub-family to which thisscenario belongs


this scenario belongs.

Yes Yes

AvailabilityDomain

Availability Domain of the indicator, It is the list of object type ateach temporal level where the indicator is available. Yes

No Yes

ScenarioTriggers

Indicators and parameters associated with the scenario. Yes Yes

Node Tree A tree displaying all the nodes associated with the scenario. Incase of an external scenario node then the scenario name.nodename is given.

Yes Yes

3BK 21216 AAAA PCZZA Ed.26 431 / 664

21 Diagnosis

ParameterName


Node Name Name of the Node Yes Yes

Node Description Description of the Node Yes Yes

Node (x,y) The X and Y positions of the node Yes Yes

Node Links Link Rank

Link Cut-Off

Iteration Variable

Iteration List Target Node

No Yes

NodeInformation

Node Code Node diagnosis code. No Yes

432 / 664 3BK 21216 AAAA PCZZA Ed.26

21 Diagnosis

21.3 Propagation

21.3.1 Propagate Diagnosis Scenario

Propagate the selected diagnosis scenario to indicator function tree:

1. Click on the diagnosis scenario you want to propagate.



2. Drag the selected diagnosis scenario and drop it to an indicator function tab.

The mouse pointer changes to .

If you drag it to an incompatible function tab, the mouse pointer changes to

.





21.3.2 Propagate Selection Between Synthetic and Detailed Report andTopology Classifications

Refer to Propagate Selection to Network Object / Function Trees in View(Section 18.4.3.9).

The detailed generated report has hyperlinks in the network objects of theexecution context.

21.4 Open Diagnosis EditorTo open the diagnosis editor, in the Alcatel-Lucent Analysis Desktop window,

click on the icon.

The "Alcatel-Lucent Diagnosis Editor" window opens.

See also Start Diagnosis Editor from the “NPO Diagnosis Development Guide”.

3BK 21216 AAAA PCZZA Ed.26 433 / 664

21 Diagnosis

21.5 Execute Diagnosis

21.5.1 Synthetic Mode

To create an executed diagnosis in synthetic mode:

1. Select the appropriate topology objects and diagnosis scenario(s), then:

Drag and drop them into the Executed View Browser, OR

Select Diagnosis -> Execute Diagnosis … from the menu bar.


3. Click on [ Execute ] to execute the diagnosis.

The diagnoses associated with the selected reference indicator aredisplayed in tabular view only. The default naming format for executeddiagnosis in tab is the same as for views (refer to Graphical and TabularView Title Format (in section 18.1.3)).

The executed diagnosis cannot be saved as template.

Figure 99: Example of View Tabular Mode - Multi-Object Comparison Containing Diagnosis

Depending on the ’Severity’ value, the following icons are defined:

Icon Description

Correct indicator value, no problem found.

Unkown.

Incorrect indicator value, problem found.

Diagnosis must be triggered.

434 / 664 3BK 21216 AAAA PCZZA Ed.26

21 Diagnosis

21.5.2 Detailed Mode

The execution of diagnosis in detailed mode can be done in two ways:

By drag&drop operation into Report Browser:

Select the appropriate topology objects and diagnosis scenario(s), then

drag and drop the objects into the Report Browser.

The ’Execution Context’ window appears. Enter the appropriate

information, as presented in Execution Context (Section 3.7).

Click on [ Execute ] to execute the diagnosis in detailed mode.If the availability domain is not empty, the diagnosis is executed in theReport Browser with the number of tabs equal to the number of networkobject multiplied by the number of scenarios.

OR

From an executed synthetic diagnosis view having a standard indicator with

the cell value in red color:

Select the red data.

Right click and select Trigger Diagnosis in Detailed Mode from the

pop-up menu, select View -> Trigger Diagnosis in Detailed Modefrom the menu bar.The diagnosis is executed from synthetic mode in the detailed mode.

The detailed generated report is an html page that contains hyperlinks tothe network objects of the execution context. The hyperlinks propagate tothe modes and functions.

The title of the detailed diagnosis report is the short name of the diagnosisscenario name.

The following details are presented:

Name of the executed diagnosis

Description and context of the triggering elements:

The target network object

The target date

The target period type.

The execution results of the nodes

Each node is detailed in a table containing the following information:

Name of the node

State of the executionThe nodes are colored depending on their status: test failed = red, testpassed = green, unkown = orange.For each identified cause, the observations and the conclusion aredetailed.

Context (iteration list values)If an iteration variable is used, the local context contains the identifier ofthe iterated object. This object identifier and its type permit to generate ahyperlink that propagates to the mode tree.

Description of the node

3BK 21216 AAAA PCZZA Ed.26 435 / 664

21 Diagnosis

Report of the execution

The conclusion contains:

The node report of the root cause node (Report true, Report false

and Report unknown)

The action associated to the root cause node.

Python code of the node (HTML link using external web interface).

Figure 100: Example of Detailed Diagnosis View

To enlarge the executed detailed diagnosis view to window size, double click onits title tab, or click on the arraw from the splitter.

436 / 664 3BK 21216 AAAA PCZZA Ed.26

21 Diagnosis

21.6 Display Execution LogsSelect Diagnosis -> Display Execution Logs... from the menu bar.

The "Diagnosis Execution Logs" window appears, displaying the diagnosisexecution logs with their size and last modified date.

3BK 21216 AAAA PCZZA Ed.26 437 / 664

21 Diagnosis

21.7 Edit Detailed Diagnosis

21.7.1 Procedure

1. Select a detailed diagnosis report.

2. Select from the menu bar: Diagnosis -> Executed Diagnosis …The execution context dialog with Spatial scope for the selected diagnosisreport is displayed.

The opened window contains two menu tabs: Execution Context, andSpatial Scope . See the chapters below (21.7.2 - 21.7.3) for information onhow to edit them.

438 / 664 3BK 21216 AAAA PCZZA Ed.26

21 Diagnosis

21.7.2 Edit Diagnosis Execution Context

1. Select the Execution Context tab.


2. Update as appropriate the displayed fields. Refer to ’Execute View’,Execution Context (Section 3.7).

3. You can:

Apply the changes made on the current view, by clicking on [ UpdateDiagnosis View ], or


Diagnosis View ].

The tabular/graphical viewer displays the values with the new data.

21.7.3 Edit Diagnosis Spatial Scope

1. Select the Spatial Scope tab.


2. To add network objects from the spatial scope, select them and drop themto the view panel.



3. You can:


Diagnosis View ], or

Create a new view with the performed changes, by clicking on [ CreateDiagnosis View ].

The tabular/graphical viewer displays the values with the new data.

21.8 Copy Diagnosis View to System ClipboardThis operation allows the user to select and copy the data from a diagnosisexecuted view in the tabular/graphical viewer, and then to paste it in anotherapplication like Excel.

Refer to Copy to System Clipboard (Section 18.5.9).

3BK 21216 AAAA PCZZA Ed.26 439 / 664

21 Diagnosis

21.9 Schedule Executed Diagnosis ReportsThe procedure to schedule executed diagnosis reports is the same as thescheduling of executed reports - see Schedule Reports (Section 19.3.4),except for the following points:

’Job Title’ default values are:

ScheduleDiagnosis, if one diagnosis scenario is selected

ScheduleMultipleDiagnosis, if there are several diagnosis scenarios

selected

ScheduleDiagnosis_Repeat or ScheduleMultipleDiagnosis_Repeat, ifone or several diagnosis scenario(s) is/are selected and repeat option

other than ’None’ is selected.

’Output Format’ options: only HTML.

21.10 Display Pending Executed DiagnosesAfter a diagnosis report is executed, it can be visualized in two ways:

From the Analysis Desktop:

Select Jobs -> Display Pending Executed Diagnoses... from the

menu bar, OR

Click on the icon.

The "Pending Executed Diagnoses" window opens, displaying the list ofexecuted Diagnosis reports.

To view one or several pending executed diagnosis reports, select them by

checking the checkbox , then click on [ OK ].

440 / 664 3BK 21216 AAAA PCZZA Ed.26

21 Diagnosis

All the diagnosis reports are opened one by one in a sequential order. Ifthe diagnosis report output is not Analysis Desktop, but HTML, then theuser is first prompted to save the executed diagnosis report and then toopen it to view it.Once a diagnosis report has been saved or viewed in the Analysis Desktop,then it is marked as viewed and it no longer appears in the list of pendingexecuted diagnosis reports. If the current Working Zone is not the WorkingZone in which the diagnosis report was scheduled, then when displayingthe executed diagnosis report, any objects not belonging to the currentWorking Zone are shown as ’unknown’.

From the NPO, as described in the NPO Administration Guide, in Download

Job Results.

21.11 Close Executed Detailed DiagnosisTo close an executed diagnosis report in detailed mode:

Right click on the diagnosis name tab, and select Close , OR

Select Diagnosis -> Close .

To close all executed diagnosis report in detailed mode:

Right click on a diagnosis name tab, and select Close All , OR

Select Diagnosis -> Close All .Click on [ Yes ] at the confirmation message.

3BK 21216 AAAA PCZZA Ed.26 441 / 664

21 Diagnosis

21.12 Export DiagnosisDiagnosis reports can be exported in html format, in order to be used with anexternal application such as Microsoft Word, Microsoft Excel, HTML browser,e-mail.

There is a limitation when exporting diagnosis reports in Excel to worksheetscontaining a maximum of 65,536 rows and 256 columns.

To export executed diagnosis reports:

1. The user can export one or several files.

To export one executed diagnosis report, select the report and select

Diagnosis -> Export... from the toolbar.

To export several reports, click on the icon, OR select Diagnosis ->Export All... from the toolbar.

The "Export Diagnosis" window opens.

2. Browse for the location where you want to save the html file, then give theappropriate ’File name’.

Click on [ Save ].




Click on [ No ] if you do not want to open the exported file.

The diagnosis report is exported to html format, keeping the same look asthe executed diagnosis.

The diagnosis toolbar is not exported.

442 / 664 3BK 21216 AAAA PCZZA Ed.26

21 Diagnosis

Example of Exported

Diagnosis Report

3BK 21216 AAAA PCZZA Ed.26 443 / 664

21 Diagnosis

444 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning

22 Tuning

This section describes how to perform tuning for the radio configuration.

3BK 21216 AAAA PCZZA Ed.26 445 / 664

22 Tuning

22.1 Presentation


Note: The MUSE_TUNING_LICENSE license must be installed, so that the Tuningmenu is displayed in Analysis Desktop.

The user must also have any one of the following FADs to seethe Tuning menu item: MUSE_NPO_TUNING_PREPARATION orMUSE_NPO_ADMINISTRATE_TUNING_SESSIONS .

22.1.1 Definitions

After a network optimization session is completed, its results (monitoring QoSindicators, checking rules on the parameters, executing diagnosis) are used totune the radio configuration, in order to correct the network misbehavior.

The optimizer can define radio resource configuration modifications, frequencychanges, neighborhood modifications, add adjacencies, change logical/designparameter values in a tuning session, which is then applied on the OMC-R.

NPO allows you to copy the parameters from a cell into another cells usingthe reference cell. Also you are allowed to set a cell as non-tunable cell oncethis cell is well tuned.

A Tuning Session can be considered as a template. It contains tuningoperations and can be applied to create a tuning job. The limit for the number ofobjects for tuning session is 6000.

A Tuning Job is a particular tuning session that has been applied at a givendate. It contains a copy of the tuning session used to create it. It is parsedby MAAT Tuning to be split into different tuning tasks (one per impactedOMC-R). Many tuning jobs can be created from a tuning session (one job perapplication of the tuning session).

A Tuning Task contains all tuning operations that are impacting one particularOMC-R.

22.1.2 Purge Completed Tuning Job(s)

Each night, NPO checks if there is any Tuning Job that is:

Completed / failed / partially failed in the last 15 days (pre-defined delay

with configurable value)

Applied but not yet completed / failed / partially failed for more then 15 days

(pre-defined delay with configurable value).These old not completed Tuning Jobs are then purged (deleted) fromthe database.

A notification is sent to all users when a job is purged. If the tuning session of ajob is opened and then this job is purged, an error message is displayed andthe Tuning Session Viewer tab (of the Job’s Tuning Session) is closed.

446 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning

22.1.3 Tuning Session Life Cycle

The common usage of tuning is:

Create a Tuning Session

Fill the Tuning Session with:

Parameter Tuning Operations

Topology Object Tuning Operations

Topology Relation Tuning Operations

Frequency Tuning Operations

Advice Tuning Operations.

Check the consistency of all the operations

Apply the Tuning Session

A new tuning job is instantiated, and can be applied or scheduled.After the tuning job is completed / failed / partially failed, it is purged.

On tuning job execution, tuning tasks are instantiated and transferred tothe OMC-R.The tuning tasks are applied, and a notification / result polling is sentto all NPO clients.After the tuning tasks are completed / failed, they are purged.

Follow the application of the Tuning Session on the concerned OMC-R.

The advanced usage of tuning is:

Select the appropriate network objects and define them as being Reference

Objects. These objects can now be used as ’templates’ when tuning othernetwork objects.

Select the appropriate network objects and inhibit all tuning operations for

them. These objects can no longer be tuned.

The available operations depend on ownership and/or status of the tuningsessions:

If a tuning session is scheduled or applied but not yet completed / failed /

partially failed, then it can only be copied

If a tuning session is not owned by the operator (and the operator is not

Administrator), then it can only be copied or opened in read only mode

If a tuning session is owned by the operator (or the operator is theAdministrator) and is created, or completed / failed / partially failed, then it

can be opened, copied, deleted

It is always possible to create a new tuning session

Deleting a working zone results in the automatic re-parenting of the tuning

sessions.

3BK 21216 AAAA PCZZA Ed.26 447 / 664

22 Tuning

22.2 Display Tuning Operation PropertiesSee Display and Edit Properties (Section 3.3).

The Tuning Session and Tuning Job Properties windows are identical for thesame tuning session, only their title is different.

ParameterName


Name Name of the Tuning Session Yes No

Temporary Flag indicating if the Tuning Session is a temporary copy or not.

This field is not visible for the user.

Yes N/A

Source TuningSession ID

Reference to the non temporary tuning session from which atemporary tuning session has been created.

This field is not visible for the user.

Yes N/A

Owner Owner of the Tuning Session Yes Yes

448 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning

ParameterName


Working Zone Working Zone to which the Tuning Session is linked (i.e.Working Zone in which the Tuning Session has been created).

Yes Yes

Purpose Description associated to the Tuning Session No No

Recommendeddate ofapplication

Date when the tuning operations contained in a Tuning Sessionshould be applied on the network

No No

Creation Date Date when the Tuning Session was created Yes Yes Y

Last Update Date when the Tuning Session was updated Yes es

Last Apply Date when the Tuning Session was applied for execution No Yes

Overview Gives an overview of the Tuning Session content.

This overview indicates:

Number of modified object(s) of each object type (nothing isdisplayed if no object of a particular type has been tuned)

Number of created object(s) of each object type (nothing is

displayed if no object of a particular type has been created)

Number of deleted object(s) of each object type (nothing isdisplayed if no object of a particular type has been deleted)

Number of each specific Tuning Operation (such asFrequency Tuning or GPRS Distribution tuning).

Yes Yes

3BK 21216 AAAA PCZZA Ed.26 449 / 664

22 Tuning

22.3 Tuning Session Manager

22.3.1 Open Tuning Sessions Window

To open Tuning Sessions window:

In the Analisys Desktop window, select from the menubar Tuning -> TuningSession... , OR

Press Ctrl+H.

The "Tuning Sessions" window appears.

Tuning sessions are classified by working zone and are displayed in a treeformat.

If the current opened working zone is the Global Working Zone, than all tuningsessions are displayed. In other words, a tuning session is linked to two workingzones: the one from which it has been created, and the Global Working Zone.

Temporary Tuning Sessions are not displayed.

The tuning sessions are classified by working zone and are displayed ina tree format.

Button Name Description

New Creates a new tuning session.

Open Opens the description of a tuning session in the tuning session viewer. This includesthe properties and tree view of operations.

Copy Opens a copy of the selected tuning session in the tuning session viewer.

Delete Deletes the current selected tuning session(s).

Close Closes the "Tuning Sessions" window. This is the default button.

Help Invoke the on-line help for the current window. See Access Online Help (Section 2.14).

450 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning

22.3.2 Display Tuning Session

Display the existing tuning sessions linked to the current Working Zone:

1. Open Tuning Sessions Window

2. Select the appropriate tuning session(s),and double click on it or click on [ Open ].

The selected tuning session is displayed in the right frame.

3. Click on [ Close ] to close the "Tuning Sessions" window.

More than one Tuning Session can be selected at a time to open. In thiscase, each of the selected Tuning Sessions is opened in a different tab. Themaximum number of tabs is 20.

The list of tuning operations contained in the tuning session, as well as theproperties of the tuning session are displayed.

Properties of the opened Tuning Session can now be edited (see Edit TuningSession Properties (Section 22.5.3)) and Tuning Operations can be added,deleted, or modified (see Tuning Session Editing (Section 22.5)).

To enlarge the tuning session to window size, double click on its title tab, orclick on the arraw from the splitter.

3BK 21216 AAAA PCZZA Ed.26 451 / 664

22 Tuning

22.3.3 Create Tuning Session

Create tuning session:

1. Start the Analysis Desktop, refer to NPO Getting Started.


3. Click on [ New ].

A new tab is created with the template of the new tuning session, displayingthe default values of the tuning session properties. The name of the tab isthe default name associated to the new Tuning Session.


5. The table below presents the properties of the tuning session. To modifythem, refer to Edit Tuning Session Properties (Section 22.5.3).


Tuning SessionName

Name of the Tuning Session. Tuning_Session_<owner>_<number>

where<owner> is the ownerof the tuning session.

Creation Date Date when the Tuning Session was created.

This field is read-only. It is automatically filled in whenthe tuning session is saved.

Current date.

Last Update Date when the Tuning Session was updated.


Current date, for new tuningsessions.

Last update date, formodified tuning sessions.

Recommendeddate of application

Indicates the date when the tuning operationscontained in a Tuning Session should be applied onthe network.

Next day.

Owner Owner of the Tuning Session.


The username you logged inthe application.

Working Zone Working Zone to which the Tuning Session is linked(i.e. Working Zone in which the Tuning Session hasbeen created).

Current Working Zone.

Last Apply Date Date when the Tuning Session was applied forexecution.


Empty for new tuningsessions.

Last appling date, for appliedtuning sessions.

452 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning


Overview Gives an overview of the Tuning Session content. Itindicates:

Number of modified object(s) of each object type

(nothing is displayed if no object of a particular typehas been tuned)

Number of created object(s) of each object type(nothing is displayed if no object of a particular type

has been created)

Number of deleted object(s) of each object type(nothing is displayed if no object of a particular type

has been deleted)

Number of each specific Tuning Operation (such asFrequency Tuning or GPRS Distribution tuning).


Purpose Description associated to the Tuning Session.

6. Perform as necessary the following steps:

Create Parameter Tuning Operation(s)

Create Topology Relation Tuning Operation(s)

Create Frequency Tuning Operation(s)

Create Advice Tuning Operation(s)

7. Save Tuning Session

3BK 21216 AAAA PCZZA Ed.26 453 / 664

22 Tuning

22.3.4 Create Tuning Session by Copy

Copy existing tuning session:

1. Start the Analysis Desktop, refer to NPO Getting Started.


3. Select the appropriate tuning session, and click on [ Copy ].

The new tuning session is created with a default name: <oldname>_Copy_n ,where n is an incremental number to define a unique name.

’Creation Date’ is set to the current date, ’Last update’ and ’Last ApplyDate’ are left empty.

All tuning operations contained in the source tuning session are alsoduplicated in this new tuning session

The user becomes the owner of the tuning session.


5. Edit the appropriate properties (refer to Edit Tuning Session Properties(Section 22.5.3)), add/modify/delete the needed tuning operations (refer toTuning Session Editing (Section 22.5)).

6. Save Tuning Session.

The new tuning session is created.

22.3.5 Check Tuning Session

This task allows the operator to check the consistency of a Tuning Session.

Checking a Tuning Session can be done:

From the Tuning Jobs window

Select the appropriate Tuning Session, then:

Click on , OR

Right click and select Check .

Click on [ Yes ] at the confirmation message.

From the opened Tuning Session

Click on , OR

Select from the menu bar Tuning -> Tuning Session-> Check .

The following checks are performed:

All tuned objects must be operational objects (except for created objects)

All tuned relations must be between operational objects

No tuned object or relation is inhibited for tuning

Tuned parameter values are contained in the range defined in the ParameterDictionary (min/max)

Tuned parameter values have a correct value (correct type, correct value

[step/enumeration])

454 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning

All mandatory rules involving at least one tuned parameter are executedand reported

All optional rules involving at least one tuned parameter are executedand reported

Tuned parameter values have a consistent value compared to Reference

values (min/max of the Reference value) and/or are set to the ReferenceValue itself.All checks are performed using forecast values defined in the currentTuning Session when available. If no forecast value is available then theoperational value must be used.

If the tuning session is correct, the following message is displayed: No

errors/warnings found in Tuning Session.

If one or several of the first six checks mentioned above fail, they are consideredas errors and are displayed.

If any of the last two checks mentioned above fail, they are considered aswarnings and are displayed.

Refer to NPO Diagnosis Development Guide for more explanations aboutcomplex checks.

22.3.6 Apply Tuning Session

1. Applying a Tuning Session can be done:

From the Tuning Jobs window

Select the appropriate Tuning Session, then:

Click on , OR

Right click and select Apply .


From the opened Tuning Session

Click on , OR

Select from the menu bar Tuning -> Tuning Session-> Apply .

2. Click on [ Yes ] at the confirmation message.

The Tuning Job Created: <Tuning_Job_name> message appears.

The tuning job name must be unique (Tuning Session name + scheduleddate + applier of Tuning Session + unique ID)

3. Click on [ OK ].


The field ’Last Apply’ of the Tuning Session is updated with current date.

Forecast parameters/topology associated to the job are created.

A notification is then sent to other users indicating that a new job has beencreated.

3BK 21216 AAAA PCZZA Ed.26 455 / 664

22 Tuning

The tuning session job is split into tuning session tasks (one task per impactedOMC-R). Each task contains the following information for a dedicated OMC-R:

Creation/deletion of forecast objects

Creation of relations:

Creation of external cells on the OMC-R when necessary, i.e. in case of

relation between OMC-Rs

Creation of relations:

Relation inside an OMC-R: Only one tuning session task is createdfor the dedicated OMC-R

Relation between OMC-Rs, with both OMC-Rs managed by NPO:two tuning session tasks are created

Relation between OMC-Rs, with one OMC-R not managed by NPO:

one tuning session task is created.

Deletion of relations

Update of parameters.

Note: The same tuning session can be updated and applied several times. For eachapplication, a different tuning job is instantiated.

22.3.7 Delete Tuning Session

Delete tuning session:


2. Select the tuning session(s) you want to remove, then click on [ Delete ].Thefollowing confirmation message appears: Are you sure you want to

delete Tuning Session <tuning_session_name>?

If only one tuning session is selected to be deleted, click on [ Yes ]

If multiple tuning sessions are selected to be deleted, click on [ Yes to All ].

If the tuning session(s) is/are opened, the following message appears:Tuning Session <tuning_session_name> is already open. Are

you sure you want to delete it? , click on [ Yes ].

The selected tuning session(s) is/are deleted and the Tuning SessionsWindow is refreshed.

The existing tuning jobs that have been created from that tuning sessionare not deleted.


456 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning

22.4 Tuning Jobs Management

22.4.1 Open Tuning Jobs Window

To open existing Tuning Job(s) in order to check their content, perform one ofthe following actions:

Select from the menu bar Tuning -> Tuning Jobs... , OR

Press Ctrl+J.

The "Tuning Jobs" window is displayed.

Two lists are displayed:

The first list shows all existing Tuning Sessions owned by the user.

It displays the following information grouped by Working Zone:

Working Zone - the working zone associated to the Tuning Session

Not editable: , or editable:

Tuning Session Name - name of the tuning session

Owner - owner of the tuning session.

The available operations are:

Apply Tuning Session (Section 22.3.6)

Check Tuning Session (Section 22.3.5).

The second list displays all Tuning Jobs grouped by the status of jobs. The

user can change the classification type as “Applier of the Tuning Session” or“Working Zone”. The last classification is stored as preference.

The following information is displayed:

Status - the status of the job

3BK 21216 AAAA PCZZA Ed.26 457 / 664

22 Tuning

Tuning Job Status Icon Color

Applied Yellow

Created Blue

Partially Failed Orange

Failed Red

Completed OK Green

Modified Tuning Session - highlights Tuning Jobs for which their TuningSession has been modified since the job was created

Tuning SessionStatus

Icon

Modified sincejob creation Orange Flag

Not Modifiedsince jobcreation

Green Flag

Tuning Job Name - the name of the tuning job

Owner - the owner of the tuning job.

The available operations are:

Display Tuning Job Follow Up (Section 22.4.4)

Open Tuning Job(s) (Section 22.4.5).

22.4.2 Change Classification in Tuning Jobs Tree

The current classification is disabled.

To change the classification in the Tuning Jobs Tree, right click on the tuning joband select as appropriate:

Classify by Applier of Tuning Session

Classify by Status

Classify by Working Zone

The tuning job tree is updated with the selected classification.

458 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning

22.4.3 Display Existing Tuning Jobs

Display the existing tuning jobs:

1. Open Tuning Jobs Window.

2. Select the appropriate tuning job(s), then:

Click on , OR

Right click and select Open Tuning Job .

The selected tuning job(s) is displayed in the right frame, in read only mode.

In case multiple tuning jobs are selected, each one is opened in one tab.The maximum number of tabs is 20.

22.4.4 Display Tuning Job Follow Up

To display Tuning Job Follow Up, select the tuning job and:

Click on , OR

Right click and select View Followup

The result of the tuning job is displayed based on the execution in the OMC-Rs.

22.4.5 Open Tuning Job(s)

To open existing Tuning Job(s) in order to check their content:

Right click and select Open Tuning Job

Click on .

The properties of the selected Tuning Job are opened in the Tuning SessionViewer in read only mode. For each selected Tuning Job(s), the correspondingTuning Session is opened in a different tab.

3BK 21216 AAAA PCZZA Ed.26 459 / 664

22 Tuning

22.5 Tuning Session Editing

22.5.1 Display Tuning Session Operation Tree

The operator can visualize the tuning session in tree format, grouped byobject type or by parameters.

The following example shows a tuning session grouped by object type.

Figure 101: Tuning Session Grouped by Object Type

Relation <serving object> <relation direction ->, <-, or <->> <target object> (’New’ or ’Deleted’)

Object Name <Object name as displayed in Modes & Functions Tree> <if New, ’(New)’>

Parameter <parameter name as displayed in Modes & Functions Tree> = <old value> -> <newvalue> [[’Planned’, ’Reference <reference object label>’, ’Historical <date>’ or’Reference Value’]

If the old value is equal to the new value, the entire tree label is in italics.

460 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning

The following example shows a tuning session grouped by parameters.

Figure 102: Tuning Session Grouped by Parameters

Relation <serving object> <relation direction ->, <-, or <->> <target object> (’New’ or ’Deleted’)

Parameter <Parameter name as displayed in Modes & Functions Tree>

Object Name <Object name as displayed in Modes & Functions Tree> <if New, ’(New)’> = <oldvalue> -> <new value> [[’Planned’, ’Reference <reference object label>’, ’Historical<date>’ or ’Reference Value’]

If the old value is equal to the new value, the entire tree label is in italics.

The last used display type (grouping by parameter, or grouping by object type)is saved as an implicit user preferences.

3BK 21216 AAAA PCZZA Ed.26 461 / 664

22 Tuning

22.5.2 Display Tuning Synthesis

This task allows the user to display a synthesis of tuning operations of aparticular type of tuning.

Select one or several tuning operations, then:

Right click and select Show Synthesis , OR

Select from the menu toolbar Tuning -> Tuning Operations -> ShowSynthesis .

The context of the tuning operation is displayed: one tab per Parameter orNetwork Object. In each tab, a table displays one line per Network Objector Parameter. Each line displays:

Network Object or Parameter label - the label of the Network Object (as

in Topology trees) or Parameter

Min reference value - the min value as defined in Reference values

configuration

Max reference value - the max value as defined in Reference valuesconfiguration

Reference value - the reference value as defined in Reference values

configuration

Operational value - the operational value

Planned value - the planned value if available, N/A if not available

Forecast value - the chosen forecast value if it has already been chosen,

empty if not.

The synthesis is displayed in one of the following two modes:

by Parameter / Object

by Object / Parameter.

To edit the displayed tuning synthesis, refer to Edit Tuning Operation(s)(Section 22.5.13)

462 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning

22.5.3 Edit Tuning Session Properties

If any modification is made on an opened tuning session, it is tagged asmodified, and the ’*’ character is added to the name of the tuning session tab.

Edit existing tuning session:

1. Right click in the properties part of the of the tuning session, and clickon [ Edit ], OR

Select Tuning -> Tuning Session -> Edit Properties from the toolbar.

2. The "Tuning Session Properties" window opens. Edit as needed one ofthe following fields:

Tuning Session Name

Recommended date of application

Purpose.

For details on their description, refer to step (5) of Create Tuning Session(Section 22.3.3).



The updated properties of the tuning session are saved.

Note: The same tuning session can be updated several times.

22.5.4 Show/Hide Tuning Session Properties

To show tuning session properties, click on .

To hide tuning session properties, click on .

3BK 21216 AAAA PCZZA Ed.26 463 / 664

22 Tuning

22.5.5 Save Tuning Session

Only a tuning session not opened in read-only mode can be saved. The savingcan only be done by the owner or administrator of that tuning session.

To save a tuning session:

Click on , OR

Select from the menu bar Tuning -> Tuning Session -> Save , OR

Press Ctrl+Shift+A.


save Tuning Session <tuning_session_name>?

The tuning session is saved and forecast parameters/topology associatedto the tuning session are created.

22.5.6 Clear Tuning Session

Clearing the content of a tuning session removes all tuning operations alreadyincluded in that Tuning Session.This operation is only possible on tuningsessions not opened in read-only mode.

To clear a tuning session:

Right click in the content of the tuning session, and select Clear , OR

Select from the menu bar Tuning -> Tuning Session -> Clear .


clear Tuning Session <tuning_session_name>?.

All tuning operations that are part of the tuning session are removed and thetuning session is now empty.

22.5.7 Toggle Display Type

To switch the display type in a tuning session:

Right click on the tuning session name tab, and select Toggle Display , OR

Select from the menu toolbar: Tuning -> Tuning Operations -> ToggleDisplay .

To switch the display type in a synthesis table:

Right click on the tuning session name tab, and select Toggle Display , OR

Select from the menu toolbar: Tuning -> Tuning Operations -> ToggleSynthesis Table .

The content of the tuning session / synthesis table changes to a differentclassification. The default is based on objects and can be changed toparameters classification.

464 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning

22.5.8 Close Tuning Session

To close one opened tuning session:

Right click on the tuning session name tab, and select Close , OR

Select Tuning -> Tuning Session -> Close from the toolbar.

To close all opened tuning sessions:

Right click on a tuning session name tab, and select Close All , OR

Select Tuning -> Tuning Session -> Close All from the toolbar.

If the closed tuning session contains not-saved modifications (tab namecontains ’*’), then the user is prompted and can either Save TuningSessionbefore closing it, or confirm closure and lose pending modifications.

If the closed Tuning Session was a temporary Tuning Session then thetemporary Tuning Session is deleted.

22.5.9 Create Parameter Tuning Operation(s)

This task allows the user to tune Parameter(s) (Logical or Design) of NetworkObject(s) and to store these settings in a Tuning Session.

Note: Only parameters for which the ’Visible’ property is set to ’True’ and that aretagged as being Tunable are displayed.

To add parameter information to a Tuning Session:

1. Select the appropriate:

Network objects from the topology browser, and

Logical or Design Parameters from the Functions window, Tuning tab.

2. Drag and drop the selections to the opened tuning session.

The "Parameter Tuning" window appears.

Figure 103: Tuning Session Window - Parameter Tuning

3BK 21216 AAAA PCZZA Ed.26 465 / 664

22 Tuning

The Parameter Tuning Table displays the tuning values of thecells being tuned. The tuning values include Ref. Min, Ref.Value, Ref. Max, Operational, Planned, and Forecast values.An arrow icon indicates which line is currently being processed.The Parameter Tuning Values are:

Reference value - the tuned parameter is set with the reference valueReference value may not be available for all types of network objects.When Reference Value is selected, the parameter is tuned using theReference Value corresponding to the other parameter values of theprocessed network object.The Forecast parameter values retrieved from the current Tuning Sessionmust be used when available. If no forecast value is available, then theOperational value must be used.If the parameter tuning operation is applied on more than one object andone parameter, there could then be different values for each combination(network object / parameter).

Planned value - the tuned parameter is set with the planned valuePlanned value may not be available for all types of network objects, norfor all network objects of a given type (for example, there is no plannedBSC and some operational Cell2G may not be planned). When Plannedvalue is selected, the parameter is tuned using the value coming from thelast imported planning project.If the parameter tuning operation is applied on more than one object andone parameter, there could then be different values for each combination(network object / parameter).

User Defined value - the user must enter the value manuallyWhen User Defined is selected, the parameter is tuned using the valueentered by the operator.If the parameter tuning operation is applied on more than one networkobject, all these objects are tuned with the same value (the one enteredby the operator).

Historical value - the tuned parameter is set with the value of theparameter for the current object at the selected dateWhen Historical value is selected, the parameter is tuned using the valueof the tuned object at the date selected by the operator.If the parameter tuning operation is applied on more than one networkobject and one parameter, there could then be different values for eachcombination (network object / parameter).

Reference object - the tuned parameter is set with the value of the

parameter for the selected reference object.When a Reference Object is selected, the parameter is tuned using thevalue of the parameter from the Reference Object. If the parametertuning operation is applied on more than one network object, allthese objects are tuned with the same value (the one coming fromthe Reference Object).

Note: The window location, splitter position and window size are stored as implicituser preferences. The parameters are displayed with OMC name or RNP nameor NPO name as per user preference.

3. Select the appropriate Parameter Tuning Value for the selected networkobject. Refer to step (2).

466 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning

If ’User Defined’ is chosen, the forecast value can be modified. In theother cases, the forecast value is just displayed without any possibilityof changing it.

To preview the value, click on [ Preview ].

4. Click as appropriate on:

Button Name Result Description

[ Apply to CurrentObject ]

The selected value (see step (3)) is set in the ’Forecast’ column only for the currentnetwork object.

The selection cursor is updated to point to the next network object. If the tunednetwork object was the last one in the table, then the next tab (i.e. next parameter) isautomatically selected, and the first network object of that new table is also selected.If it was the last network object and there is no other parameter to tune, then thewindow is closed.

[ Apply toAll Objectsfor CurrentParameter ]

The selected value (see step (3)) is set for all network object(s).

The next tab (i.e. next parameter) with the first network object in the table is selected.If it was the last parameter, then the window is closed.

[ Apply to AllObjects for AllParameters ]

The chosen value (see step (3)) is set for all network object(s) and all parameter(s).

The window is closed.

5. A new window is opened and you must select the checks to be performed onthe network objects.Select one of the following options:

’Mandatory Checks’ - All mandatory checks linked to the tunedparameter(s) are performed. This includes mandatory rules referencing

tuned parameter(s), check of system min/max bounds and check of theallowed steps when applicable

’Optional Checks’ - All optional checks linked to the tuned parameter(s)

are performed. This includes optional rules referencing tunedparameter(s) and check of reference min/max bounds

’All Checks’ - Both mandatory and optional checks are performed

’No Checks’ - No checks other than the system min/max are performed.

6. Click on [ OK ].

The selected checks (as described in step (5)) are triggered, the progressbar is displayed.

If at least one of the checks fails, then a window is opened displaying all theerrors and all the warnings returned by the checks.

The selected checks are applied only to the concerned operations (currentobject + current parameter, or all objects + current parameters, or all objects+ all parameters) and not on the whole tuning session.

The window is closed and the Tuning Session Viewer is refreshed,displaying all new created operations.

If the labels of the objects appear in italic, it means that the new value set fortuning is the same as the initial value.

3BK 21216 AAAA PCZZA Ed.26 467 / 664

22 Tuning


468 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning

22.5.10 Create Topology Relation Tuning Operation(s)


To add topology relation information to a Tuning Session:

1. Select:

The appropriate network object(s) from the topology browser, and

The Topology Relation Tuning Operation: ’Adjacencies Tuning’ from the

Functions window, Tuning tab.


The "Relation Tuning" window appears.

Figure 104: Tuning Session Window - Relation Tuning

3BK 21216 AAAA PCZZA Ed.26 469 / 664

22 Tuning

Figure 105: Tuning Session Window - Relation Tuning - New Object

The Direction Setting Panel permits to define the type of relation that iscreated. It can be:

Incoming

Outgoing

Bi-directional .

The Operational Relations Panel displays the list of existing relation(s) ofthe currently processed network object.

The Added Relations Panel displays the list of new relation(s) to becreated for the currently processed network object.

The Removed Relations Panel displays the list of relation(s) to be removedfor the currently processed network object.

The Preview of Changes Panel displays how the result is after thechanges are applied.

Note: The window location, size and the splitters’ position are stored as implicituser preferences.

3. Edit the appropriate information for the relation tuning.

The following Operations for Relations are available:

Operation Type Description

Add Relation 1. Select the appropriate Direction Setting.

2. Select the needed network objects from the right panel, then drag and drop themto the Added Relations Panel.

If the relation does not already exist, it is added according to the set direction.

470 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning

Operation Type Description

Remove Relation To remove:

An operational relation: right click on it and select Remove .The operational relation is added to the list of removed relations.

A relation from the Added / Removed Relations Panel: right click on it and selectRemove .The relation is removed from the list.

Change Relation To change the direction for operational, added or removed relations, right click onthe relation and select:

Change to <- , to change the direction to Incoming

Change to -> , to change the direction to Outgoing

Change to <- -> , to change the direction to Bidirectional.

Related Objecttabs

There can be more than one tab if the tuned relations can link objects of differenttypes or has to be managed as a single relation type.

For adjacencies (for example), there must be one tab for 2G Cells and another one for3G Cells as user can create adjacencies between both technologies.

A particular (optional) tab contains objects that can be linked using the tuned relationand that can be “unknown for NPO”. These are called External NPO Objects(External NPO Cell means a cell not managed by any of the integrated OMC’s). Notethat, in that particular External tab, there must be a way to create a new ExternalNPO Object (even if, most of the time, these external objects are imported using theCustomer Topology interface).

To create a new object for a relation tuning

Select the appropriate Direction Setting.

Select as appropriate ’New ECell2G’, or ’New ECell3G’.

Fill in the available fields with the cells’ properties.

3BK 21216 AAAA PCZZA Ed.26 471 / 664

22 Tuning

Click on [ Create ].The "Parameter Tuning" window opens on the new sub-object(s). Editthe parameters tuning information - refer to Create Parameter TuningOperation(s) (Section 22.5.9), steps (3) to (6).The "Parameter Tuning" window closes, and the "Relation Tuning"window comes on top. The new object is added in the Added RelationsPanel.

3. If several network objects were selected to be tuned, click on [ Next Object ].

Set the appropriate relations for each network object. Refer to step (3).

When you are in the last object, the label [ Next Object ] is changed to[ Apply ].


If relations are created (and not just removed), when the "RelationTuning" window closes, the "Parameter Tuning" window is opened on thenew sub-object(s), so that the operator can tune the parameters. Editthe parameters tuning information - refer to Create Parameter TuningOperation(s) (Section 22.5.9), steps (3) to (6).

The changes are applied and the window is closed.


472 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning

22.5.11 Create Frequency Tuning Operation(s)


RESTRICTION3BKA17FBR197501

Do not use the same frequency for different TRX of the same cell.

RESTRICTION3BKA17FBR197758

Do not set the BCCH frequency on two ARFCN of the same cell.

To add frequency information to a Tuning Session:

1. Select:

The appropriate cell(s) from the topology browser, and

’Frequency Tuning’ from the Functions window, Tuning tab.


The "Frequency Tuning" window appears.

Figure 106: Tuning Session Window - Frequency Tuning

The ’BSIC’ field displays the list of current forecast BSIC of the cell, or theoperational value if the BSIC has not been changed. This list proposes thepossible values that can be used.It is obtained using the following formula:BSIC = BCC + 8 x NCC, where:

BCC varies from 0 to 7

NCC can take all the values indicated by the NCC_Permitted parameter.

3BK 21216 AAAA PCZZA Ed.26 473 / 664

22 Tuning

The following cell types that display different frequency tuning detailsare available:

Cell Type Description

CellThere is only one set of values, labeled Normal .

Cell split There are two sets of values, Main and Secondary , corresponding respectively tomain and secondary BTS sectors.

Concentric cell There are two sets of values, Inner and Outer , each relating to one of the zones

covered by the cell .

Concentric cellsplit

There are four sets of values, each relating to the sectors and zones covered bythe cell.

The "Frequency Tuning" window contains one tab per traffic zone of theprocessed cell. Each tab contains:

A Cell Allocation PanelThis contains the list of frequencies used by the cell. Note that formulti-band cell objects, Cell Allocation can be different in traffic zone tabs.

A Frequency Configuration Panel , that can be:

TRX Configuration - when no TRX uses FHS (i.e. Hopping Group)The values of the TRX mode are: Preference Mark, Planned,Operational, and Forecast.

FHS Configuration - when all TRX use FHSThe values of the FHS mode are: Planned, Operational, and Forecast.

RH/NH Configuration - when some TRX use FHS and others don’t.If the selected type is TRX, the values are as for the TRX mode, butyou can only tune the BCCH frequency on the non hopping TRX.If the selected type is FHS, the values are as for the FHS mode, butyou can only tune the frequencies on the hopping TRX.The user can change from TRX to FHS, or from FHS to TRX (whenthis is available).

For TRX/FHS mode:

When a value is not available for a configuration, a N/A value

is displayed

474 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning

When a value is not defined, for instance if there are more plannedTRX than operational TRX, a N/D value is displayed

Only the Forecast value column is editableThe forecast value is the operational value by default if there is nocurrent forecast value.

A cell which displays the BCCH value is highlighted using bluecolor background.

For RH/NH mode, depending on the type selected in the combo box,the cells are displayed.

Note: The window location and size are stored as implicit user preferences.

3. Edit the new forecast values.This can be done as follows:

ManuallyForecast frequencies can be entered manually and, in that case, the CellAllocation list is updated accordingly (adding the new entered value ifneeded, removing the old value if not used anywhere else).Whenever there is an N/D in forecast (respectively operational) and notin operational (respectively forecast) columns, then only the Restoreoperation is allowed to fix the inconsistency.

Using drag and dropForecast frequencies can be dragged and dropped in order to switchthem between two TRX.This is applicable only in case of TRX configuration mode.

Setting planned values.Forecast frequencies can be set to planned frequencies if available withthe help of the popup menu in the Tuning Table.

Restrictions: It is not possible to copy planned values into forecast valuesin the following cases:

When one of the planned values is either N/A or N/D

When the number of planned TRX is different from number offorecast TRX

When there is an N/D value in the Forecast value.

To set the forecast values back to the operational values, click on [ Restore ].

4. If several cells were selected to be tuned, click on [ Next Object ].

The details of frequency tuning for the next cell are displayed.

Update the forecast values as appropriate. Refer to step (3).





3BK 21216 AAAA PCZZA Ed.26 475 / 664

22 Tuning

22.5.12 Create Advice Tuning Operation(s)


Advices may be added to network object(s) in a tuning task, to send a messageto the OMC-R user. They are only available in the tuning session. A networkobject may have several advices.

To add advice information to a Tuning Session:

1. Select:

The appropriate network objects from the topology browser, and

’Advice Tuning’ from the Functions window, Tuning tab.


The "Create Advice" window appears.

Figure 107: Tuning Session Window - Advice Tuning

Note: The window location and size are stored as implicit user preferences.

3. Type the appropriate advice for the selected cell.

Click on [ Apply to Current Object ], to save the current advice and stepto the next available network object tab.When the user is in the last object, the label [ Apply to Current Object ]is changed to [ Apply ]. Click on [ Apply ] to save the changes andclose the window.

Click on [ Apply to All Objects ], to save the current advice to all theremaining objects and close the window.



476 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning

22.5.13 Edit Tuning Operation(s)

Tuning operations can be updated.

1. Select the appropriate tuning operation(s), then:

Right click and select Edit , OR

Select from the menu bar Tuning -> Tuning Operation-> Edit .

2. The same window that was used to create the selected tuning operation(s) isdisplayed. Perform the needed updates. Refer as appropriate to:

Create Parameter Tuning Operation(s), steps (3) to (6)

Create Topology Relation Tuning Operation(s), steps (3) to (4)

Create Frequency Tuning Operation(s), steps (3) to (5)

Create Advice Tuning Operation(s), step (3).

The changes are updated in the tuning session.


22.5.14 Copy Tuning Operation(s) to System Clipboard

Tuning operations from a tuning session can be copied and pasted in anothertuning session or in other applications such as Word or Excel.

Select the appropriate tuning operation(s), then:

Right click and select Copy , OR

Select from the menu bar Tuning -> Tuning Operation-> Copy , OR

Press Ctrl+Shift+H.

The data corresponding to the selected tuning operation(s) is copied intosystem clipboard in the following format:

internal Tuning Operation format - for pasting into another tuning session

unformatted text - for pasting into .doc or .xls format.

Note: The data displayed in the synthesis tables can also be copied.

22.5.15 Delete Tuning Operation(s)

Tuning operation(s) can be deleted from a tuning session.

1. Select the appropriate tuning operation(s), then:

Right click and select Delete , OR

Select from the menu bar Tuning -> Tuning Operation-> Delete , OR

Press Ctrl+Shift+D.


delete <tuning_operation_name>?

The tuning operation(s) is deleted from the tuning session.

3BK 21216 AAAA PCZZA Ed.26 477 / 664

22 Tuning

22.6 Propagate from Tuning Session

22.6.1 Propagate Tuning Session Content

The content of a tuning session (tuned network objects and tuned parameters)can be propagated to network objects / function tree.

To propagate the tuning session content:

1. Select the tuned network objects / tuned parameters you want to propagate.




Click on the icon from the tuning session toolbar, then select

Propagate Tuning Session , OR

Select from the menu toolbar: Tuning -> Propagate -> Tuning Session .

The network objects and/or parameters are selected in the appropriatetrees/modes/standards.

The selection is also made in non-active modes. So, if you switch to anothermode containing tuned network objects (for example), they are displayedas selected.

If there is an active filter on any active topology or function classification andsome of the propagated network object(s) / function(s) are not visible due tothis filter, you are informed and can choose to automatically remove thecurrent filter (i.e. switch to ’No Filter’), or to propagate anyway.

If any propagated network object(s) and/or parameter(s) is not found, noerror message is displayed.

22.6.2 Propagate Tuned Parameters of Network Object(s)

The tuned logical/design parameters of a tuning session can be propagated tothe corresponding logical/design function trees.

To propagate the parameters of a tuning session:

1. Click on the parameter(s) from the tuning session.

2. Perform one of the following actions::


Propagate Tuned Parameters , OR

Select from the menu toolbar Tuning -> Propagate -> Parameters

The tuned logical/design parameters contained in the tuning session areselected in their respective trees/modes/standards.

The selection is also made in non-active modes. So, if you switch to anothermode containing tuned parameters, they are displayed as selected.

If there is an active filter on any active function classification and some of thepropagated parameter(s) are not visible due to this filter, you are informedand can choose to automatically remove the current filter (i.e. switch to ’NoFilter’), or to propagate anyway.

If any propagated parameter(s) is not found, no error message is displayed.

478 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning

22.6.3 Propagate Tuned Network Objects of Parameter(s)

The tuned network object(s) of a tuning session can be propagated to thecorresponding topology trees.

To propagate the network object(s) of a tuning session:

1. Click on the tuned network objects you want to propagate.

2. Perform one of the following actions::


Propagate Tuned Network Objects , OR

Select from the menu toolbar Tuning -> Propagate -> Tunable Objects .

The network objects are selected in the appropriate trees/modes/standards.

The selection is also made in non-active modes. So, if you switch to anothermode containing tuned network objects, they are displayed as selected.

If there is an active filter on any active topology or function classification andsome of the propagated network object(s) are not visible due to this filter,you are informed and can choose to automatically remove the current filter(i.e. switch to ’No Filter’), or to propagate anyway.

If any propagated network object(s) is not found, no error message isdisplayed.

3BK 21216 AAAA PCZZA Ed.26 479 / 664

22 Tuning

22.7 Manage Reference Object(s) for Tuning

Note: The MUSE_TUNING_LICENSE license andMUSE_NPO_ADMINISTRATE_REFERENCE_OBJECT FAD must be installedto manage reference objects for tuning.

22.7.1 Declare Network Object(s) as Reference Object(s) for Tuning

Network object(s) can be declared as reference object(s). When tuning someparameters, the values to be used can be retrieved from any existing referenceobject (i.e. reference object can be used as a template). The values retrievedfrom the reference object are the operational values.

To declare netwok object(s) as reference object(s):

1. Select the appropriate network object(s), then:

Right click and select Set Reference Object... , OR

Select Topology -> Set Reference Object... from the menu toolbar.

The "Declare/Undeclare Reference Object" window appears.

2. Select ’Declare Reference Object’.

3. If needed, edit the reason of the operation in the ’Reason’ panel.

If several network object(s) are selected, the same comment can be appliedto all selected objects, or you can enter a different message for each of them.

By default, the same message is applied to all selected netwok objects.

4. Click on [ OK ].

Click on [ Yes ] at the Are you sure to save the changes? question.

The network object is set as reference object and highlighted in blue color. Theparameter is tuned using the value of the parameter from the reference object.

If the parameter tuning operation is applied on more than one network object,all these objects are tuned with the same value (the one coming from thereference object).

A notification is sent to all clients about the new status of the concernednetwork object(s).

480 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning

22.7.2 Undeclare Network Object(s) as Reference Object(s) for Tuning

Network object(s) can be undeclared as no longer being reference object(s).

To undeclare netwok object(s) as reference object(s):

1. Right click on the network object and select Set Reference Object .

The "Declare/Undeclare Reference Object" window appears.

2. Unselect ’Declare Reference Object’.


4. Click on [ OK ].


The selected network object(s) are no longer defined as reference object(s)and their label(s) appear in standard format.


3BK 21216 AAAA PCZZA Ed.26 481 / 664

22 Tuning

22.8 Manage Tuning Inhibition of Network Object(s)

Note: The MUSE_TUNING_LICENSE license andMUSE_NPO_ADMINISTRATE_TUNABLE_OBJECT FAD must be installed tomanage tunable objects.

22.8.1 Inhibit Tuning of Network Object(s)

By default, all network objects are admitted for tuning, but the tuning operationcan be forbiden on some network objects.

To inhibit tuning of netwok object(s):

1. Select the appropriate network object, then:

Right click and select Set Tunable Object... , OR

Select Topology -> Set Tunable Object... from the menu toolbar.

The "Allow/Inhibit Tuning" window appears.

2. Unselect ’Allow Tuning’.


If several network object(s) are selected, the same comment can be appliedto all selected objects, or you can enter a different message for each of them.

By default, the same message is applied to all selected netwok objects.

4. Click on [ OK ].

The selected network object(s) are no longer accepted for tuning, and theirlabel(s) appear in italic format.


482 / 664 3BK 21216 AAAA PCZZA Ed.26

22 Tuning

22.8.2 Allow Tuning of Network Object(s)

In case some network objects were declared as non-tunable, the tuningoperation can be allowed.

To allow tuning of netwok object(s):

1. Right click on the network object and select Set Tunable Object .

The "Allow/Inhibit Tuning" window appears.

2. Select ’Allow Tuning’.

3. The ’Reason’ panel displays the comment associated to the network objectwhen it was disabled for tuning. If needed, update it.

If several network objects are selected, the window displays the commentassociated to the first selected network object.

4. Click on [ OK ].


The network object(s) is now defined as tunable and its label appears instandard format.


3BK 21216 AAAA PCZZA Ed.26 483 / 664

22 Tuning

484 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

23 Cartography

This section describes the management of network objects and layers in ageographical representation.

3BK 21216 AAAA PCZZA Ed.26 485 / 664

23 Cartography

23.1 Presentation

23.1.1 Overview

Note: The MUSE_CARTOGRAPHY_LICENSE license must be installed for thecartography viewer to be available.

The cartography module offers the user the following possibilities:

Correlate the design view and the operational view

Access the topology of operational elements

Focus on faulty objects

Highlight network objects

Perform adjacency analysis and tuning

Manage background maps, as well as strongest server maps

Manage multiple map layers

Network objects filtering

Customizable rendering properties: overlaid raster and vector maps

Levels of details based on network object density, controlable by the

operator.

View multi-technology objects for the same map.

The following table gives the definitions of the main cartography terms:

Term Definition

Raster A bitmap image consisting of a matrix of pixels. The accepted formats for raster files are:.jpg. .jpeg, .bmp, .tif, .tiff, .png.

Vector A file that contains objects and shapes using mathematical coordinate systems andformulas. The accepted formats for vector files are: mif/mid.

BackgroundMaps

Used to display a set of raster and vector maps in the background, while all the otherlayers are put in front of this one by default. This is mainly the place where satellite/aerialmaps, roads, rivers, elevation maps are displayed.

NPO imports all the available background maps for:

Vectors , in MIF format (MapInfo Interchange File Format) and in the long/lat

geographical WGS84 co-ordinate systemThis procedure is explained in “NPO Administration Guide”, chapter Import Vector File.

Rasters , in BMP, JPG, JPEG, TIF, TIFF, PNG format and in the long/lat geographical

WGS84 co-ordinate system using .txt georeference files (two georeference pointsneeded).This procedure is explained in “NPO Administration Guide”, chapter Import Raster File.

Example: map of a country, RNP imported files like power map.

486 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

Term Definition

CCA

(Cell CoverageArea)

It is a data file containing polygons (layers of geo-referenced vectors) representingsurfaces associated with a network object reference, coming from RNP files that areprocessed at the import.

Each polygon of the files is referenced with a network Object ID. CCA Layers contain alist of polygons with rendering properties (line colour, fill colour/pattern, transparencycoefficient).

The Cell Coverage Area files can be of two types:

MIF/MID files (containing polygons data), or

Computed Voronoi.

CCA layers show Voronoi cells, best server files coming from RNP, or any kind of polygonlinked with a topology object reference.

CCA objects are not movable and zoomable.

The user can define which CCA is associated to the cell, by configuring the cartographyconfiguration file. If only one CCA is available, the Cartography module makes this choiceautomatically. When at least two CCA are available, you should define which CCA is usedfor this association. All CCA can be simultaneously displayed.

NetworkObjects

The network objects from the topology classification (cell, BTS, Node B) that are droppedinto the cartography viewport.

This layer is further sub layered based on the object type (e.g. Cell3G, RNC).

All the Cell3G objects are grouped into the Cell3G sub layer.

Network Objects are not displayed in this sub layer.

Relations Layer, another sub-layer, constitutes the adjacencies present in the viewport.Its sub layers are grouped based on the technology.

Icon A bitmap image used to render a network object in the cartography.

Main ObjectType

The network object type that is the focus of a technology. Example: CELL3G for W-CDMA, CELL2G for GSM.

Voronoi Voronoi maps are computed polygons per object, that represent a zone where a functionis maximized for the object.

A Voronoi map displays the Voronoi contours of an area covered by a cell. Each of theseareas is called a Best Server. If you want to use a Voronoi map for Adjacency Analysis,you must load it before you carry out the analysis.

The used algorithm for Voronoi computing is the distance, and this function is tuned bythe network object parameters.

3BK 21216 AAAA PCZZA Ed.26 487 / 664

23 Cartography

Term Definition

Best Server The Best Server is a computed raster or vector file coming from RNP software. The BestServer computes polygons for cells showing the geographic zone that is the best telecomservice. Several polygons can be set for a network object. The Best server file comes ina MAP info of MIF/MID format describing the polygon list, the rendering attributes, andadditional information on each polygon (Network object reference).

ThematicLayer

A thematic layer displays graphically the value of parameters. It contains sub-layers bysorting criteria, containing all selected objects that match the criteria.

An executed thematic layer is a set of network objects sorted by criteria in sub layers anddisplayed in various shapes and colours (user defined rendering).

Thematics are computed using thematic layers template and a set of network objectsfor a consolidated period.

Example: a selection of cells drawn in colour depending on the call drop.

488 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

23.1.2 Cartography Browser

The Cartography browser is displayed as a tab in the Report browser. Therecan be multiple report tabs and multiple tuning tabs, but there is only onetab for cartography.

The Cartography browser consists of five regions:

Cartography Toolbar

Cartography ViewportThe rendering Viewport is the main window of the cartography module;it is a drawing area showing the visible layers at their right position in thecurrent world coordinates system.Here background maps, CCA polygons, network objects, and thematicobjects are displayed. This area can be zoomed and panned.

MinimapThe mininmap defines the overview of the actual viewport. At any point intime the entire map is visible in the mini map with a small rectangle.

Layer ManagerThe layer manager contains a list of layers and sub-layers that are arrangedin the hierarchical tree structure. A layer is a graphical component containingthe description of the graphical content and not the graphical content itself.The layers can be moved up and down in the hierarchy, depending on thetype of the layers. The sub-layer within the main layer can be moved up anddown, except for the relation type and thematic layers.The root nodes and the leaf nodes, as well as their corresponding icons aredefined in the configuration file.

Information BarThe information bar shows the latitude and longitude of the cursor positionin the map. It also contains a scale displaying the information regardingthe distance of the line when the user is in compute distance mode. Thenumber displayed in the scale changes dynamically when the viewportis zoomed or unzoomed.

The user can choose to hide both the layer manager and the minimap; in thiscase most of the screen space is filled with the cartography viewport. TheDensity Level is recalculated and the objects are adjusted according to thenew density factor.

3BK 21216 AAAA PCZZA Ed.26 489 / 664

23 Cartography

Figure 108: Cartography Browser

490 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

23.1.3 Display Network Objects in Viewport

For W-CDMA only 3G cells are available (RNC and NodeB are planned later).

A site is a logical object, where one or more network objects are located. Allthe objects that have the same geographical position (latitude/ longitude) areusually grouped together as a site.

The site is usually represented as a filled circle. It has the samelatitude/longitude as that of the objects it contains.

The site name is a parameter:

of the Cell, for W-CDMA

retrieved from the RNP cell id, for GSM.

When no names are available, the site name is the latitude/longitudeinformation.

A sector is a line joining the site to the network objects. A line is displayedusing the cartography configuration file attributes (thickness, color, length). Thesector usually gives the information about the Azimuth of the cell.

The Azimuth is the angle of the antenna of the cells in the network. Its valueis taken from the OMC-R or RNP.

The following figure presents the site elements as displayed in the viewport.

Cells are considered as the main object types in the viewport. They are alwaysdisplayed as hexagons. To differentiate cells of different standards, a smallhexagon containing the technology letter (G for GSM, U for W-CDMA, W forWiMAX) is displayed on the lower right corner of the hexagon, as shownin the figure below.

3BK 21216 AAAA PCZZA Ed.26 491 / 664

23 Cartography

You can use the user preferences to show the standards or not:

The figure below shows the layout of a cell along with its rendering attributes:

ObjectType giving the shape

Technology represented by a symbol

Two parameters:

cellClass - background

cellType - sub icon.

Size of the sector line : the azimuth line has a fixed graphical size, but when itis zoomed, so when the Density Levelis increased, the line is also thickened.This allows showing expanded views of collapsed cells.

492 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

23.1.4 Density Level

The viewport can contain thousands of objects, making the rendering of allobjects along with all their properties practically impossible. This is why thedensity level notion is introduced. The density level is the level of details towhich the network objects are displayed in the viewport.

The table below explains the density level depending on the number of objectsin the viewport.

RenderingDensityLevel

Number ofNetworkObjects inViewport

Main Object Type Site Other NodesChildren

Other NodesParents

1 >2000 None None None Point

2 [501;2000] None Point None Icon

3 [101-500] None Point

Azimuth

None Icon

4 [51-100] Collapsed Iconssize(1/2)

Point

Azimuths

None Icon

5 [26-50] Collapsed Iconssize(1)

Point

Azimuths

Icon size(1/2) Icon

Size(1)

6 [11-25] Expanded Iconssize(1) sub-Iconlabels

Point

Azimuths

Icon size(1) Icon

Size(1)

7 [1-10] Full Expanded Iconssize(1) sub-Iconlabels

Point

Azimuths

Icon size(1) Icon

Size(1)

1/2 : half the original size

1 : full size

To set the density level of the network objects, choose the appropriatevalue from the ’Density Level’ drop down list in the Cartography toolbar:

. To lock it to the chosenvalue, select the ’Density Lock’ checkbox.

3BK 21216 AAAA PCZZA Ed.26 493 / 664

23 Cartography

23.1.5 Graphic Modes

Depending on the Density Level of the viewport, two modes of graphicdisplay are automatically selected for the main object type: collapsed andfull-expanded mode.

Collapsed Mode

Since the viewport may contain thousands of objects, some of them which areof similar type or located in the same site can be grouped together. In this casethey are also called co-localized cells or collapsed cells.

Three cells of different standards(GSM, W-CDMA, WiMAX) can be co-localized. The maximum number of cellsco-localization for a given azimuth (or a sector) is:

2G: two co-localized cells

3G: four co-localized cells.

An example of graphical representation of the collapsed cells is given below.

Figure 109: Example of Collapsed Cells

The meaning of the graphical object presented above is:

The double hexagon indicates that there are multiple cells situated at

the same location (co-localized)

“U-3” means that there are three W-CDMA cells grouped together

“G-2” means that there are two GSM cells grouped together

“W-1” means that there is one WiMAX cell in the collapsed cell.

494 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

Figure 110: Collapsed Cells with Highlight Selection

The meaning of the above graphical object is:

The double hexagon indicates that there are multiple cells situated atthe same location

“U-3” means that there are 3 W-CDMA cells grouped together

“G-2” means that there are 2 GSM cells grouped together

“W-1” means that there is 1 WiMAX cell in the collapsed cell.

3BK 21216 AAAA PCZZA Ed.26 495 / 664

23 Cartography

Full-expanded Mode

The “full expanded co-localized cells” are rendered on the border of the circlerepresenting the sector, by technology, with a larger space between co-localizedobjects. This allows rendering of adjacencies between co-localized objects.

The sub-icon and background pattern drawing rule is defined in theconfiguration file.

Figure 111: Full-expanded Cells

Figure 112: Full-expanded Cells with Highlight Selection

496 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

23.1.6 Compute Voronoi Maps

Voronoi Maps are used:

at the CCA files import.

for THL template shapes.

Every night, the Voronoi cells computing is triggered. CCAs are thusautomatically created.

For each target Voronoi layer, a Voronoi polygon is computed and stored inthe database as a couple (MuseId, polygon data and rendering). Voronoicomputation is based on cell localization.

The following process is used:

1. The list of cells is retrieved using the filter defined in the Voronoi layer.

2. The barycenter of all the cells is calculated. A UTM (Universal TransverseMercator) projection centered on this point is then created.

3. If several cells are co-located, the same polygon is assigned.

A list of sites is then built. A site is identified by a number (from 0 to thenumber of cells) and has a position.

4. Voronoi diagram computation is performed.

The goal of the Voronoi algorithm is to divide the plane in polygons (there isone polygon per cell) so that each point inside a polygon is closer to theattached cell than to any other cell.

5. A post processing is made in order to find all the segments of a cell and toorder them so that the last point of a segment is equal to the first point ofthe next segment.

The polygon sizes are though adjusted to telecom constraints (umbrella,micro, macro cells..).

6. Best Server contour is created.

The polygons are adjusted to represent more accurately a best servercontour. To do that the edges of the polygons are moved to the nearestcircle defining the maximum distance for a cell.

7. Cell coverage limitation takes place.

The cell coverage is limited to a maximum distance. In the cartographyconfiguration file, in each Voronoi layer definition, the radius of the circleis associated to the values of a single criterion.

For example in GSM standard, the cell type of the GSM cell determinesthe circle size.

To check the Voronoi Maps computation, view the traces in the following file:/alcatel/muse/data/trace/MUSE_VORONOI_JOB_MUSE_0.traces .

To view the Voronoi maps inside the Cartography viewport, refer to Show/HideLayer (Section 23.3.2).

3BK 21216 AAAA PCZZA Ed.26 497 / 664

23 Cartography

23.1.7 Common Cartography Usage

The basic common usage of cartography module in NPO is:

Administrator Tasks 1. Import rasters, vectors and THL Template files in the database via webadministration tools.

2. Import RNP planned data files in the Muse database.

Operator Tasks 3. Start the Analysis Desktop, choose a working zone, and open theCartography browser.

4. Add new graphical layers from the database to display in the cartographyviewer.

5. Add a set of Network Objects to display, by dragging and dropping themfrom the topology classification into the cartography viewport.

6. Select a set of Network Objects and a thematic layer template in the functionbrowser. Drag and drop this double selection into the cartography viewer andenter additional execution context such as: periodicity, start and end time.

The Analysis Desktop retrieves data from MUSE and generates the result(called an Executed thematic layer).

The Analysis Desktop renders the executed thematic View as a new layerwith sub layers for each sorting criterion.

7. Perform the needed operations with the displayed result: selecting, panning,zooming, centering, computing distances, display properties, hiding layers,modifying rendering properties.

8. Edit the executed thematic layer properties in order, for example, to definehow to display these network objects or change the execution context.

9. If needed, save the modified executed thematic layer as a thematic layertemplate in order to be able to execute it again later without redefiningall graphical properties.

10. Select a cell and display incoming and outgoing adjacencies.

11. Launch a wizard to manage the cells adjacencies and choose to add orremove adjacencies based on the geographical criterion.

12. Use the Highlight facility to find the set of network objects.

13. Propagate this subset of network objects to the topology manager.

14. Export the graphical results into several raster or vector formats.

498 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

23.2 Open CartographyTo open the cartography browser:

Select from the menu bar: Cartography -> Launch Cartography , OR

Click on from the menubar.

A set of predefined layers is displayed in the cartographic viewer correspondingto the current working zone if no layers were loaded in the previous session ofthis working zone.

The last saved layer display configuration is retrieved from the user preferencesif the working zone has not changed. Layers are downloaded and displayed.

To enlarge the cartography window to window size, double click on its title tab,or click on the arraw from the splitter.

23.3 Layer Manager

23.3.1 Display Layer/Layer List

During the Cartography start up, the Cartography module fetches the layersassociated with the working zone and depending on the user rights. The layersmust be first imported by the administrator (see “NPO Administration Guide”,chapters Import Vector File and Import Raster File).

A layer represents a set of sub layers, which are grouped in categories.Basically, layers and sub layers offer the same features. A sub-layer can be araster or a group of vector objects.

The layers and sub-layers are displayed in the layer manager. The user hasno direct access to do this operation, this is only part of the Cartographymodule startup.

For example: if the user starts the Cartography module for the first time,since the user does not have any last user layers in the working zone, thedefault layers associated with the working zone are loaded. Supposing thatthe user adds or removes the layer from the layer manager and closes theCartography module. When they reopen the cartography module, the layersthat were last saved in the user preferences are fetched and loaded. But whenrestarting the AD, if the user changes the working zone, the last saved layersin the user preferences are ignored and the layers associated with the newworking zone are loaded.

3BK 21216 AAAA PCZZA Ed.26 499 / 664

23 Cartography

23.3.2 Show/Hide Layer

For the defined layers, the layer manager tree disposes of a V checkbox,representing the visibility option.

To show a layer in the viewport, select its corresponding “Visible” checkbox.

To hide a layer from the viewport, unselect its corresponding “Visible”

checkbox.

The following figures present the Voronoi maps display in case of CCA Layer’GSM900_Macro’ set and unset to ’Visible’.

Figure 113: CCA Layer ’GSM900_Macro’ Not Visible

500 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

Figure 114: CCA Layer ’GSM900_Macro’ Visible

A table with all the objects in the “Cartography Layers” and the availability oftheir visiblity checkboxes is presented in Filter Network Objects in a Layer(Section 23.5.8).

23.3.3 Display Layer Legend

Select a cartography layer and:

Right click and select from the pop menu Show Legend... , OR

Select from the menu bar Cartography -> Show Legend...

The legend window is displayed. The following information is displayed:

Background Layer - the MID information for vectors and rasters

CCA Layer - the MID information

Network Object Layer - the list of possible representations of the ObjectType extracted from cartography configuration file

Thematic Layer - Thematic layer legend

Relations Layer - the state of the adjacencies.

3BK 21216 AAAA PCZZA Ed.26 501 / 664

23 Cartography

Figure 115: Background Layer Legend Dialog

Figure 116: Network Object Layer Legend Dialog

502 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

23.3.4 Modify Display Properties of a Layer

This case allows the operator to modify a background layer appearance bychanging its contrast, brightness and transparency.

1. Select a cartography layer and:

Right click and select from the pop menu Modify Layer Properties... , OR

Select from the menu bar: Cartography -> Modify Layer Properties...

The "Display Properties" window appears.

If multiple layers of same layer type are selected, the "Display Properties"window is opened for the most top selected layer.

Figure 117: Display Properties of Background Layer

Figure 118: Display Properties of THL Layer

If all layers have the same value, then all their labels are displayed in black.

If the layers have different values for an attribute, then the label for thatattribute is displayed in blue color, to indicate that the values are not samefor all the selected layers.

2. Set the appropriate parameters.

3BK 21216 AAAA PCZZA Ed.26 503 / 664

23 Cartography

ParameterName


Contrast Contrast of the layer 0.5

Brightness Brightness of the layer 0.6

Transparency Transparency level of the layer 0.5 for raster files

1 for others

Note: The “Contrast” and “Brightness” can only be applied to raster files. For allother types of layers, it is greyed.

3. Click on [ OK ].

All the modifications done for the layer are saved as the implicit userpreference.

504 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

23.3.5 Modify Order of a Layer

To modify the order of a layer in the same group, drag and drop it tothe wanted position.

The order of sub layers belonging to the thematic layers cannot be changed.

All the modifications done for the layer order are saved as implicit userpreference.

23.3.6 Add Layer in Layer Manager

Add Layer in the CCA &

Background Layer

1. Select a cartography layer and:

Right click and select from the pop menu Add Layer... , OR

Select from the menu bar: Cartography -> Add Layer...

The "Add Layer to Layer Manager" window appears, showing the list ofimported CCA files (including computed Voronoi) and background maps.

2. Select the appropriate imported layer, choose the background or the CCAtype, then click on [ OK ].

The layer is downloaded in the cartography and is added in the layermanager tree, at the top of the layer type sub tree.

Add Layer in the

Network Object Layer

1. Drag and drop the appropriate Network objects from the Modes andFunctions tree in the layer manager.

A new layer is created for each newly dropped object type. For examplewhen dropping Cell3G objects, if Cell3G sub layer is not present in thenetwork object layer, then a new sub layer is created for Cell3G and theobjects are added in the Cell3G layer.

2. Drag and drop the appropriate adjacencies from the Modes and Functionstree in the layer manager.

The adjacencies and their corresponding network objects are added tothe viewport.

To view the adjacencies in the viewport, right click on a network object andchoose to Display Adjacencies, or choose to Run Adjacency AnalysisWizard to Create/Delete Adjacencies.

3. The network objects are not visible in the layer manager, but the cell objectsare rendered in the viewport.

Whenever a new sub layer is added in the Network object layer, theparameters (only those that have enumerations) for the object type isfetched and displayed as the children of the sub layer node in the tree.

For each parameter, all the enumeration values are added in the tree as subnode of the parameters. All these have checkboxes in the tree table, so youcan shown/hide them in the viewport. Refer to Filter Network Objects ina Layer (Section 23.5.8).

3BK 21216 AAAA PCZZA Ed.26 505 / 664

23 Cartography

Add Layer in the

Thematic Layer

Thematic layer can be added in the layer manager by executing thematictemplates.

1. Drag and drop the appropriate network objects and a thematic template inthe Layer Manager.

2. If a layer is not already there for the thematic template, a new layer is createdin the layer manager and Network objects are sorted in the thematic layerbased on the criterion defined in the THL template.

Figure 119: Example of “Add Layer in Layer Manager” Window

506 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

23.3.7 Remove Layer from Layer Manager

1. Select the cartography layer(s) you want to remove, and:

Right click and select from the pop menu Remove Layer... , OR

Select from the menu bar: Cartography -> Remove Layer...

Note: If you select a node in the tree that cannot be removed, then the menu itemsare disabled.

The following must be taken into account:

In the thematic layer, you can select only the thematic template node

to remove the layer. You cannot remove the main thematic layer node,criterions or the steps in the criterion.

In network object layer, you can select only the sub-layers like Cell3G,

RNC for example, for removing from layer manager.You cannot remove the main network object layer and the main relationslayer, under the Network Object layer node.You can only select the immediate sub-layer of the Relations layer,Adjacencies for example for that layer.

In CCA layer, you can select only the leaf nodes for removing. User

cannot remove the main CCA layer node.

In background layer, you can select only the leaf nodes for removing.

User cannot remove the main background layer node.


remove the following layer(s)? < list of layer(s)>

The selected layer(s) is removed from the layer manager tree and thememory is freed. The layer is also removed from the Cartography viewport.

The layer is not removed though from the database. The new layer list isstored in the implicit user preference so that when Cartography module isrestarted only the new list is reloaded.

3BK 21216 AAAA PCZZA Ed.26 507 / 664

23 Cartography

23.3.8 Export Displayed Layers/Viewport

1. Select the appropriate cartography layer(s) and:

Right click and select Export... , OR

Select from the menu bar: Cartography -> Export...

The "Export" window appears.

2. Select the appropriate export format, then click on [ OK ].

The following table presents the available export formats for different typesof cartography files:

Layer Type Export Description

Raster layer This layer can be exported only as PNG format. This layer can be exported as fulllayer and viewport.

The export can be done as a viewport only in the case when all the layers in layermanager are selected.

Vector layer This layer can be exported in:

MID/MIF format, as a full layer only

PNG format, as a viewport only.When it is exported as PNG only, all the other layers in the Layer Manager that areseen in the viewport are considered as part of the PNG file.

508 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

Layer Type Export Description

Network objectlayer

This layer can be exported as PNG and KMZ formats using Viewport and All NetworkObjects and Thematic export.

When it is exported in:

PNG format, all the layers that are seen in the current viewport are also exported

KMZ format, all the network objects, their corresponding THL objects, sites andsectors present in the viewport are also exported.

Thematic layer This layer can be exported as PNG and KMZ formats using Viewport and All NetworkObjects and Thematic export.

When it is exported as:

PNG format, all the layers that are seen in the current viewport are also exported

KMZ format, all the network objects, their corresponding THL objects, sites andsectors present in the viewport are also exported.

Export possibilities:

Full Layer Export Viewport Export All Network Objects andThematic Export

Layer type

PNG KMZ MID/MIF PNG(*)

KMZ MID/MIF PNG KMZ MID/MIF

Raster Yes No No Yes No No No No No

Vector No No Yes Yes No No No No No

Network Objects No No No Yes Yes No No Yes No

Executed THL No No No Yes Yes No No Yes No

(*) : Since PNG export is an image grab of the cartography viewport, when one layer is captured as PNG, all otherlayers that are visible in the viewport are also captured. So a PNG viewport export on one layer cannot be done.It is always on multiple layers.

3. In the "Save" window, choose the location where you want to save theexported file, then click on [ Save ].

The following message appears:Export is Successful. Do you want to open the exportedfile?

Depending on your preferance, select as appropriate [ Yes ] or [ No ].

3BK 21216 AAAA PCZZA Ed.26 509 / 664

23 Cartography

23.3.9 Google Earth Export

23.3.9.1 PresentationThe cartography information can be exported in order to be displayed in GoogleEarth through the KML interface. The KML (Keyhole Markup Language) is anXML grammar and file format for modeling and storing geographic featuressuch as points, lines, images and polygons for display in Google Earth.

For the Google Earth export cartography module, KMZ files (zipped KMLfiles) are used. The KMZ files (.kmz extension is used) contain the KMLexported cartography file and an “/images” directory containing a list of rastersfor each exported sector.

The supported version of XML schema for creating KMZ format file is KML 2.1.

Google Earth KML 2.1 permits to:

Specify icons and labels to identify locations on the earth

Create different camera positions

Use image overlays attached to the ground or screen

Define styles to specify feature appearance

Write HTML descriptions of features, including hyperlinks and images

Use folders for hierarchical grouping of features

Set level of details for each placemark.

For more information, refer to the following links:

http://earth.google.com

http://earth.google.com/downloads.html

http://earth.google.com/kml/kml_tut.html

http://earth.google.com/kml/kml_tags_21.html

23.3.9.2 Export Cartography in KMZ Format1. Export Displayed Layers/Viewport (Section 23.3.8) in KMZ format.

2. Double click on the saved KMZ file.

Google Earth opens zooming to the region where the network objects andassociated thematics of the KMZ file are.The following are exported inGoogle Earth:

The site - exported as an icon at the correct geographical position with

with the latitude-longitude coordinates

The sectors - exported with the correct Azimuth angle displayA line is displayed using the cartography configuration file attributes(thickness, color, length).The length is static, being configurable only in the cartographyconfiguration file. A multiplier factor is used with the configuration filesector length.

The main object type of the technology is exported as rasters (oneraster per sector)The Azimuth is used as name of the cell group.

510 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

The raster is generated per sector and put in the images repositoryof the export.

Depending on the level of detail defined in the KMZ file, two levelsof details are rasterized:

The expanded mode

The collapsed mode.

The cell background is also exported.Only the visible objects are exported, filtered objects are ignored.Transparency/contrast/brightness is ignored for Network Objects.Special thematic rendering modes (mobile, standard deviation andvoronoi) are not exported.

Note: Adjacencies are not exported.

If all the objects in the cell group are not visible (because the checkboxes offiltering or main layer visibility feature are on), their corresponding site, sectorand thematics are not exported.

Figure 120: Example of Site Exported in Google Earth at Level of Detail Expanded

3BK 21216 AAAA PCZZA Ed.26 511 / 664

23 Cartography

Figure 121: Example of Site Exported in Google Earth at Level of DetailCollapsed

Figure 122: Example of Site Exported in Google Earth at Level of DetailWhere Cells Are Not Shown

The left panel - "Places", presents the exported KMZ file, with associatedAzimuths.

512 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

Figure 123: Google Earth Places Window

To view information concerning the main object type:

Click on the appropriate Azimuth hyperlink from the "Places" left panel, OR

Click on the appropriate cell from the exported site window.

A tool tip window opens, displaying information about:

The sector azimuth value

The site it belongs to

The list of cells friendly names for each technology, with the corresponding

thematics criteria values.

3BK 21216 AAAA PCZZA Ed.26 513 / 664

23 Cartography

Figure 124: Sector Tool Tip

514 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

23.4 Cartography Navigation

23.4.1 Toolbar

The following toolbar icons are available for the cartography operations:

23.4.2 Single/Circular Selection

Single selection:

To select an object, click on , then select the appropriate object.If you click on a collapsed object, all the objects inside the collapsed graphicobjects are selected.

To deselect the object or append to the current selection, press the [ Ctrl ]

key. The selection list is updated.

To use the circular selection mode, click on , then draw a circle in theviewport. All the objects in the drawn circle are selected.

The objects in the viewport are selected only if their selectability field in thelayer manager is enabled (Refer to Filter Network Objects in a Layer (Section23.5.8)).

When there is a high density of objects, some of the objects are not displayed,or they are shown as points, in which case no selection is shown.

The selection color of the network objects can be configured in the userpreference. Refer to User Preferences (Section 27).

3BK 21216 AAAA PCZZA Ed.26 515 / 664

23 Cartography

23.4.3 Pan Rendering Viewport

The panning operation describes how you can move up, down, left, or right inthe current viewport.

1. Select from the menu bar Cartography -> Panning... , or click on .

2. In the minimap, click and hold the left mouse button, then drag to the wanteddirection. Both the minimap and viewport are moved.

23.4.4 Zoom In/Out/Rectangular

To zoom in in a viewport:

Select from the menu bar Cartography -> Zoom Plus... , OR

Right click in the viewport and select Cartography -> Zoom Plus... , OR

Click on , OR

Press [ Ctrl ] key and move the wheel of the mouse down.

To zoom out in a viewport:

Select from the menu bar Cartography -> Zoom Minus... , OR

Right click in the viewport and select Cartography -> Zoom Minus... , OR

Click on , OR

Press [ Ctrl ] key and move the wheel of the mouse up.

The zooming procentage is set in the User Preferences window.

To zoom in rectangular mode , click on the icon, then holding theleft mouse button, drag it to create a rectangle. This defines the amount ofviewport pixels in both axis of the displacement. The viewport is zoomed in

only for the drawn area. You can then move , enlarge/decreasethe rectangular zone.

The following figure shows successive zoom actions. The first two views showfixed sized sectors and icons. The last zoom displays the cells grouped ina sector.

516 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

The following figures summarize a display with real cells:

3BK 21216 AAAA PCZZA Ed.26 517 / 664

23 Cartography

Figure 125: Example of site exported in Google Earth at level of detail expanded

Figure 126: Example of site exported in Google Earth at level of detail collapsed

518 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

Figure 127: Example of site exported in Google Earth at level of detail wherecells are not shown

23.4.5 Center Viewport

To center a viewport so that you can easily see the location of the selected layer:

Select from the menu bar: Cartography -> Center Viewport... , OR

Right click in the viewport and select: Center in Viewport , OR

Click on icon from the Cartography toolbar.

If the selection is a set of network objects, the viewport is computed to displayall network objects plus a 10% zone around.

If there is no network object selected, the centre is done on the current layerselection in the layer manager. The zone to display is the whole layer.

3BK 21216 AAAA PCZZA Ed.26 519 / 664

23 Cartography

23.4.6 Compute Distance Between Points/ Network Objects


Select from the menu bar: Cartography -> Compute distance... , OR

Right click in the viewport and select: Navigate Backward/Forward , OR


The distance between two points can be computed either by drawing a line,or choosing two network objects.

2. To compute the distance between two points:

Select one point in the viewport. A line is drawn interactively followingthe mouse from the first point.

Select a second point up to which you want the distance to be calculated.

The distance is shown on the line that unites the two points.

3. To compute the distance between two network objects:

Select one network object in the viewport. A line is drawn from thenetwork object real position (latitude longitude) interactively following the

mouse from the first network object.

Select a second network object up to which you want the distance to becalculated. The distance is shown on the line that unites the two points.

Note: You cannot select a combination of one point and one network object tocompute distance.

520 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

To stop the computing of distance, exit the compute distance mode.

23.4.7 Navigate in Viewport Records

To go back and forward in the viewport history:

Select from the menu bar: Cartography -> Navigate Backward/Forward ,OR

Right click in the viewport and select: Navigate Backward/Forward , OR

Click on or icon from the Cartography toolbar.

The previous or next viewport record is loaded. The layer manager is updated:only the layer order and properties are changed. The viewport is moved andzoomed into the new viewport position/zoom.

Only 20 records are registered.

3BK 21216 AAAA PCZZA Ed.26 521 / 664

23 Cartography

23.4.8 Save Viewport

To save a viewport:

Select from the menu bar: Cartography -> Save Viewport... , OR

Right click in the viewport and select: Save Viewport , OR


The viewport properties: position/zoom/layer configuration are saved intothe viewport history.

A maximum of 20 records can be saved (circular record).

The current view can be later recalled via back and forward navigation.

23.4.9 Display Information Interactively

The current position of the mouse in the viewport is displayed in the statusbar of the cartographic viewer. The coordinates can be expressed in twocoordinate systems:

Longitude/Latitude (WGS84)

UTM (Universal Transverse Mercator).

If the mouse stops over a graphical object that is associated with a muse object(e.g. network object, executed thematic layer), a tool tip popup opens in thecartographic viewer (rectangular area) showing the related information.

23.4.10 Minimap

The Minimap displays in a limited graphical zone the whole displayed area witha rectangular area representing the current viewport zone. The backgroundcontent is a global view of the background layer currently drawn.

The minimap window displays the main viewport area of the main renderingwindow by a white rectangular zone not filled.

The size of the minimap window follows the AD size but is set as a percentageof the current cartographic viewport.

The minimap shows the background layers in the world coordinates and thezoom level of the minimap is always set to display all visible backgroundlayers within the minimap

Whenever the operator changes the viewport co-ordinates or the zoom on theviewport, it is reflected in the mini map

522 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

23.4.10.1 Show/Hide MinimapTo show/hide the minimap:

Select from the menu bar: Cartography -> Show/Hide Mini map , OR


The minimap window is shown/removed from the cartography browser.

Whenever the minimap is shown, the minimap rectangle is updated to show thecurrent viewport coordinates. The density factor is recalculated and the objectsare adjusted according to the new density factor. The level of details is changedaccording to the new density level.

23.4.10.2 Navigate to Position Through MinimapSelect a point in the minimap window by clicking on it. The rendering viewportis updated (panned) so that the new center of the viewport is the selectedpoint in the minimap.

3BK 21216 AAAA PCZZA Ed.26 523 / 664

23 Cartography

23.5 Network Objects

23.5.1 Select Network Objects

You can select a network object by clicking on it.

To add/remove an object in the current selection, press [ Ctrl ] and click on it.

You can add/remove objects in the selection also by creating an interactiverectangular surface over the objects to be selected, by pressing the left

button of the mouse.

To remove objects from the selection, right click on them and select:UnSelect All .

If you click on collapsed objects, all the objects of the collapsed graphic

are selected.

A set of objects can be selected by clicking on the network object layer.

The selection color is configurable from the user preferences menu (Refer to”NO Selection Color” in Configure User Preferences (Section 27.2)) or inthe cartography configuration file .

To convert one (or several) highlighted object(s) into selected one(s), rightclick on them and select:

Convert to Selection -> Append to Selection , to add the selected

object(s) to the selected list

Convert to Selection -> Replace Selection , to make the previously

selected object(s) lose the selection and the new object(s) to be selected.

23.5.2 Display Network Objects Properties

Select the appropriate network object from the viewport, then:

Right click and select View Properties... , OR

Select from the menu bar: Cartography -> Object Properties... .

The Properties window is displayed.

See also Display and Edit Properties (Section 3.3).

524 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

23.5.3 Add Network Objects in Viewport

To add network objects in the viewport, select them from the topology tree anddrop them in the rendering viewport or layer manager.

Only the network objects whose co-ordinates can be computed (exceptadjacencies) are added in the viewport and are highlighted.

Only the cells with defined geographical coordinates can be displayed. If thedragged BTS or BSC have no coordinates, their coordinates can be calculateddepending on the coordinates of the cells declared to them.

The network objects themselves are not displayed in the network object layer.Only the parameters of the object with all its enumerations are displayed inthe layer manager. Network objects are sorted by Object Type and a layeris created per ObjectType.

For each network object, the corresponding site is computed:

The distance of the network object with the existing sites is computed; if thedistance is zero, the network object is added in the site

If the network object has not found an existing site, the distance between all

others network objects is computed

When two objects are in the same location (distance is zero), a site iscreated and the objects are added in this site. The coordinates of the site

are computed from the first object put in the site

All new sites are added in the site layer (not displayed in the layer manager).

For each adjacency, the packed link is computed if needed:

The source object density level rendering mode and target density level

graphic object are determined

If there is already a packed link between the source and target graphicobject, the adjacency is added in the list and the number of links is updated

on the packed link

If there is already a single link in the same direction between the source andtarget graphic object, the current single link is destroyed and a packed link is

created with the two adjacencies in it

If there is already a single link between the source graphic object and target

graphic object, the single link is replaced by a bi-directional link.

3BK 21216 AAAA PCZZA Ed.26 525 / 664

23 Cartography

For the network objects that do not have coordinates or they cannot becalculated, an error dialog appears, displaying the uncomputed object ids.

526 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

Adjacencies do not have any co-ordinates, but they have the source and targetobjects, therefore they can still be displayed in the viewport.

In case the filtering is applied in the layer manager for the dragged & droppednetwork objects, they are not shown in the viewport.

Depending on the user preferences, whenever new objects are added tothe viewport, their operational value or planned value are displayed first

.

Their density level is also updated based on the current density level selection.

3BK 21216 AAAA PCZZA Ed.26 527 / 664

23 Cartography

23.5.4 Remove Network Objects from Viewport

Select one or several network objects in the viewport, right click and selectRemove .

The selected objects are removed from the viewport and from the THL Layer (ifany) in the layer manager.

For network objects:

If there are no more network objects in the site, the site is removed from the

rendering viewport

If there are no more network objects in the layer manager, the layer is

removed from the layer manager

If there are no more network objects on an Azimuth line, the Azimuthline is removed

If the removed network object was co-localized, the co-localized group is

updated and the viewport is refreshed. If the collapsed group has only oneobject in it, the collapsed object is replaced by the expanded object

Incoming relations and outgoing relations of the removed network objectsare also removed from the adjacency layer and from the rendering viewport.

For adjacencies:

If there are no more adjacencies in a packed link, the packed link is

destroyed

If there are only two adjacencies in opposite direction in a packed link, thepacked link is replaced by a bi-directional link

If there is only one adjacency in a bi-directional link or in a packed link, the

link is replaced by a single link.

When a network object is removed from the viewport, the THL objects remain inthe viewport.

528 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

23.5.5 Propagate Network Objects Selection from Cartographic Viewerinto Mode

Select one or several network objects in the viewport, then:

Right click and select Propagate -> All/Selection , OR

Select from the menu bar: Cartography -> Propagate to M&F->All/Selection .

All or the selected network objects are propagated to the topology tree browser.The tree is auto-scrolled so that the first selected object is visible.

23.5.6 Propagate Executed View to Highlight Network Objects inCartography

1. Select the objects in the executed view.

2. Right click and select Propagate -> Propagate Highlighted NetworkObjects to Cartography .

The network objects and the most severe color are propagated to thecartography viewport.

Note: Only views that contain indicators, rules and parameters can be propagatedfrom viewers to cartography.

3BK 21216 AAAA PCZZA Ed.26 529 / 664

23 Cartography

23.5.7 Highlight Network Objects

1. Select one or several network objects in the viewport, then right click andselect Highlight , or select from the menu bar: Cartography -> Highlight .

2. Select as appropriate one of the following options:

All Parent Objects

All Children Objects

All Incoming Adjacencies

All Outgoing Adjacencies

All Adjacencies

Interfered -> Co-channel Probability , to highlight all cells that are

interfered by the current selected cell with co-channel probability *

Interfered -> Adjacent Channel Probability , to highlight all cells that areinterfered by the current selected cell with adjacent channel probability *

Interfering -> Co-channel Probability , to highlight all cells that can

interfere with the current selected cell with co-channel probability *

Interfering -> Adjacent Channel Probability , to highlight all cellsthat can interfere with the current selected cell with Adjacent channel

probability *

* An interference matrix provided by RNP is used in order to analyzepotential interference problems.

Frequency Reusing Objects , to highlight all cells that are reusingfrequency in a specified radius around the corresponding network object

Highlight CCA .

The network objects are coloured semi transparently with the current highlightcolour.

You can select one network object and choose to highlight the CCA of theobject, if it is loaded in the Analysis Desktop.

For the collapsed objects, you can open the contents of the collapsed objectdialog and can see the details of highlighting.

When there is a high density of objects, some of the objects are not displayed,or they are shown as points, in which case no highlight is shown.

530 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

Figure 128: Example of Highlight Interfered with Co-channel Probability

The highlight color of the network objects can be configured in the userpreference. Refer to User Preferences (Section 27).

All the highlighted network objects except for CCA objects can be convertedinto selection. You can append to the current selection list or choose to reset alland select on the highlighted objects. Refer to User Preferences (Section 27).

To convert one (or several) highlighted object(s) into selected one(s), rightclick on them and select:

Convert to Selection -> Append to Selection , to add the selectedobject(s) to the selected list

Convert to Selection -> Replace Selection , to make the previouslyselected object(s) lose the selection and the new object(s) to be selected.

To unhighlight objects, right click on them and select: UnHighlight All .

3BK 21216 AAAA PCZZA Ed.26 531 / 664

23 Cartography

23.5.8 Filter Network Objects in a Layer

For the network objects, the layer manager tree contains two checkboxes:

S, which stands for SelectWhen checking the “Select” checkbox in the “Select” column, all thenetwork objects that are the children of the selected node in the tree arealso selected.If the selected node is the leaf node, then that particular category of networkobjects are shown in the viewport immediately.

V, which stands for Visible.When selecting the “Visible” checkbox in the “Visible” column, all thenetwork objects that are the children of the selected node in the tree areshown in the viewport immediately.If the selected node is the leaf node, then that particular category of networkobjects are shown in the viewport immediately.When all the objects on the sector line become invisible, then the sector lineitself becomes invisible.

The following checkbox selection rules apply:

If all sub-values of the same leaf node are selected, the leaf node remainsselected

If all sub-values of the same leaf node are unselected, the leaf node

is also unselected

If only some of the sub-values of the same leaf node are selected, the leaf

node remains selected.

The following logical functions apply:

OR: between the sub-values of the same parameter

AND: between the values of the different parameters.

The network objects are displayed in the viewport only if they satisfy the filteringcriteria in the layer manager. The selectability and visibility filter is applied to allthe objects that are added to the viewport.

The selectable and visiblity checkboxes are not available for some of the treenodes. In this case, the component is not present in the layer manager. Findmore information in the table below:

532 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

Object in the Tree SelectCheckboxAvailable

VisibleCheckboxAvailable

Thematic main layer node No Yes

Executed thematic node No Yes

Criterion node No No

Steps node No No

Network objects under the steps No No

Network objects main layer Yes Yes

Network objects sub layer (object type& relations layer)

Yes Yes

Adjacency layers (Immediatesub-layers of Relations layer)

Yes Yes

Parameters of Network objects andadjacencies

No No

Enumerations of parameters Yes Yes

CCA main layer node No Yes

CCA leaf layer No Yes

Background main layer node No Yes

Background leaf layer No Yes

The following figures present the cells display in case of ’NH Hopping Mode’ forcell set and unset to ’Visible’.

3BK 21216 AAAA PCZZA Ed.26 533 / 664

23 Cartography

Figure 129: NH Hopping Mode Not Visible

534 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

Figure 130: NH Hopping Mode Visible

3BK 21216 AAAA PCZZA Ed.26 535 / 664

23 Cartography

23.6 Thematic Layer Template (THL)

23.6.1 Presentation

The thematic layer is the equivalent of an executed view in cartography. Itallows to display graphically the values of logical/design parameters, QoSindicators, diagnosis, rules, geographic (ex: distance from the POI) andcustomer data (free fields).

This visual analysis can help you determine the best configuration andoptimization characteristics to apply to the group. NPO offers a defaultThematic Layer when installed, but you can create, modify and delete your ownthematic layers using the Thematic Layer Manager.

Thematic layers are available only when you are working with one of fourtypes of network objects listed below:

Cells

Adjacencies

BTS

BSC.

Thematics are computed using thematic layers template and a set of networkobjects for a consolidated period. It contains sorted objects given criteriawith a specific rendering.

Example: a selection of cells whose colour depends on the call drop.

The criteria of the THL is configurable in the cartography configuration file.

23.6.2 Display THL Properties

Select a THL template from the function tree, right click and select Display THLProperties . The THL Properties page is opened in a HTML Browser.


The following properties pages can be displayed:

Generic Thematic Layer Template definition

Attributes of rendering mode

Graphical properties of a THL

Attributes of interval distribution (steps and colors)

Graphical properties of adjacency.

536 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

23.6.3 Propagate THL to Function Tree

Select one or more THL Templates from a function tree, then drag and dropthem to another target function of the same mode.

A THL can be propagated to:

Indicator - to retrieve all indicators referenced in the selected ThematicLayer Templates

Design Parameter - to retrieve all design parameters referenced in the

selected Thematic Layer Templates

Logical Parameter - to retrieve all logical parameters referenced in the

selected Thematic Layer Templates.

3BK 21216 AAAA PCZZA Ed.26 537 / 664

23 Cartography

23.6.4 THL Editor

23.6.4.1 Open THL EditorTo open the THL Editor, in the Alcatel-Lucent Analysis Desktop window:


Select Data -> THL... from the menu toolbar OR

Press Ctrl+K.

The "Thematic Template Editor" window opens.

538 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

23.6.4.2 Create THL TemplateTo create a THL template:

1. Open THL Editor.

2. In the "Thematic Template Editor" window, click on .On the rightpanel, the system shows:

Available indicators sorted by structure type and then by family, bothvisible and non-visible can be selected

Available design/logical parameters sorted by family/sub-family

Available rules.

On the left panel, the existing THL templates are displayed.


FieldName


Name Name of the thematic template. THLTemplate_<owner>_n

where<owner> is theowner of the THLtemplate, and n is anincremented number tofind a unique name (ncan be 1, 2, 3...).

Owner User who is creating the thematic template.



Created Date when the thematic template was created.


Modified Date when the thematic template was last modified, in case of athematic template update.


AccessRights


Title Title of the thematic template.

This title is displayed in the layer manager of the cartography.

Visible A flag that indicates if the THL template is visible in the functionbrowser.

If the visible flag is false, then only the administrator can see thetemplate in the function browser.

Checked.

3BK 21216 AAAA PCZZA Ed.26 539 / 664

23 Cartography

FieldName


System True, if this THL template is a System view template, so it cannotbe modified or deleted.

False, otherwise.


Type The type of the thematic template.

The supported values are Standard and Specific

Standard.

Families Each row in the table is a family.

The first column is always the family name and each sub sequentcolumns are the sub-families. One family can have maximum offour sub-families.

One thematic template can belong to multiple families.

Description Text box to be filled in with operator description for the currentthematic template.

TemplateFor

Spatial domain for the THL template.

The supported object types are all the supported object types inAnalysis Desktop.

The THL template is created for the object type. For example, theTHL template created for Cell3G cannot be executed on the objectsother than Cell3G.

Cell3G

540 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

FieldName


AvailabilityDomain

The availability domain for the THL template is for the selectedobject type, so the THL template is only available for the object typefor which the THL template has been created.

The temporal availability is that of the function used in the THLtemplate. If density is selected, then it is available for all thetemporal periodicity.

Specialrenderingmode

Used in the graphical properties window, the following can beselected:

Positioning algorithm - to specify which algorithm is used to

calculate the position of the mobile icon or the rectangular box.The following options are available: “All”, “Timing Advance”,

“Conventional GPS”, “MS-Based A-GPS”, “MS Assisted

A-GPS”.

Shapes: “Mobile” and “Standard deviation” are available in the

graphical properties, if this mode is selected.

“Mobile” rendering mode is used so that a mobile symbol isdisplayed in the executed THL. The position of the mobile

symbol is calculated using the selected positioning algorithm.

“Standard deviation” rendering mode is used so that arectangular box is displayed in the executed THL. The

position of the box is calculated using the selectedpositioning algorithm.

Show line.This option is enabled only when the “Mobile” or “Standarddeviation” rendering mode is selected. This option specifieswhether to draw a line from the network object to the mobileicon or the rectangular box.

4. A minimum of one criterion and a maximum of two criteria can be defined.To add a new criterion to the thematic template, click on [ Add Criterion ].

When there are two criteria in the THL template, then the [ Add criterion ]button is disabled.

Whenever a user adds or removes a criterion, all the graphical properties ofthe criterion level and the step level properties are reset.The criterion can bea function selected from the available functions of the:

ObjectType

Parent of the ObjectType. In this case the parent ObjectType is chosenfrom the available parents ObjectType.

5. Fill in the parameter criterion properties, as described below.

3BK 21216 AAAA PCZZA Ed.26 541 / 664

23 Cartography

ParameterName


Name Name of the criterion. Criterion_<number>

Function id Function to be applied while executing the thematic template.

Drag and drop a function (indicator, logical/design parameter,rule) in this field.

This field is greyed if “Density” is selected.

Use Planned In case a design/logical parameter is added in the “Functionid” field, you can choose whether to display its Planned valueor not.

Applied To The target object on which the thematic should be executed.

The supported values are: SELF, PARENT, CHILD, SOURCE,TARGET.

SOURCE and TARGET are not available when the TemplateFor is a relation type.

In case ”Use Planned” is selected, “Applied To” is grayed.

This field is greyed if “Density” is selected.

SELF

Target policy The computation policy to be applied during the executionof the template.

The supported target policy are: MIN, MAX, AVG.

AVG

Evaluate Density Indicates whether to use the distance factor or to use thefunctions for executing the template.

If the density is on, then the user is not able to specify anyfunction in the function id field (it is greyed).

False

6. Click on to open the "Criterion Graphical Properties" window.

The fields in the dialog box are arranged in the form of a tree structure.The child nodes are enabled only when the parent field is checked. Seethe table below.

Take notice of the Rules for Graphical Properties of THL Editor (in section23.6.4.2).

542 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

Panel Name ParameterName


Label on the executed thematic.

Font properties are enabled only if [ Label ] checkbox is selected.

False

Font Color The color of the font when displaying labels. This isa RGB value.

Black

Font Size The size of the font to be displayed in the viewportwhen a label is displayed. The values are from 8to 15.

9

Font Style The style of the font to be used when drawing thelabel.

Plain

Label

FontTransparency

The transparency of the font. The values are from0 to 1

The transparency is used as a help for visualization(when shapes are superposed).

0.5

3BK 21216 AAAA PCZZA Ed.26 543 / 664

23 Cartography

Panel Name ParameterName


Graphics properties on the executed thematic.

The graphic properties are enabled only when the [ Graphic ]checkbox is selected.

False

Shape The shape to be displayed for the criterion.

The supported shapes are: circle, rectangle,square, triangle, Voronoi, Mobile, Standarddeviation.

Square

Layer Name When “Voronoi” is selected in the “Shape” field, youhave to mention from which layer file the Voronoishape is picked.

To select a layer name, click on [ Browse ] andchoose a layer from the opened layer browser.

NA

ShapeBackgroundColor

The background color of the shape. Black

Shape Pattern The pattern used to display the shape. None

Shape LineColor

The color of the line to draw the shape. Black

Shape LineStyle

The style of the line to be applied while drawing theshape in the viewport.

Continues

Shape LineThickness

This thickness of the line when drawing the shape. 1pt

ShapeTransparency

The transparency of the shape. 0.5

Shape Scale The scaling of the shape when displaying in theviewport.

The values are from 1 to 5.

1

Icon The icon to be displayed instead of the shape.

To select an icon, click on [ Browse ] and choosethe needed one.

When “Icon” is selected, none of the graphicalproperties are applied.

None

Transparency The transparency of the icon. 0.5

Graphics

Scale The scaling of the icon when displaying in theviewport. The values are from 1 to 5.

1

If “Special rendering mode” is selected, then in the graphical propertiestwo more shapes are displayed: “Mobile” and “Standard deviation”. Youmust select the positioning algorithm and check/uncheck the “Show link”

544 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

checkbox. Whenever special rendering mode is checked or unchecked, allthe criterion of the graphical properties and step level properties are reset.

The preview of graphical properties is displayed in the "Rendering Preview"area. It contains two images representing different graphical propertiesselected in the Criteria and steps.

If the template contains only one criterion, the first image on the preview

represents the consolidated graphical property of the first criterion andthe first step of the first criterion. The second imagell represents the

consolidated graphical property of the first criterion and the last step ofthe first criterion.

If the template contains two criterions, the first image on the preview

represents the consolidated graphical property of the first criterion, firststep of the first criterion, second criterion and the first step of the second

criterion. The second image represents the consolidated graphicalproperty of the first criterion, the last step of the first criterion, second

criterion and the last step of the second criterion.

3BK 21216 AAAA PCZZA Ed.26 545 / 664

23 Cartography

7. For the “Boundary Parameters”:

If “Static” bound determination is selected, you must also enter the

values for min & max interval distribution

If “Dynamic” bound determination is selected, then min & max valuesare disabled. In this case, the values are dynamically calculated

at execution time.

8. The “Interval Distribution” is used to create automatic step values and colors.

Select one of the possible values: Linear, Logarithmic, Exponential.

Select also the “Number of Intervals” if you want to compute stepsautomatically.

If the selected function id is a parameter and if the parameter hasenumerations, then the steps are automatically adjusted to have samenumber as the number of enumerations in the parameter. In this case, youare not allowed to enter “Interval Distribution”, or the number of steps, orthe boundary parameters.

Example:

If you enter the number of steps as 4, and the type of distribution as“Linear”, then click on [ Auto Background ], a total of four steps are addedin the distribution steps. If you enter min & max values, those values aredistributed for each step based on the selected type of distribution (linear inthis case). [ Auto Background ] is disabled if you selected the backgroundin criterion graphical properties.


When all verified data is correct, a confirmation message asks whether theTHL template is to be saved or not. Click on [ OK ].

The THL template is created in the MUSE database and the Thematic LayerTemplate is added in the function trees.

546 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

Rules for Graphical

Properties of THL Editor

There are certain rules for editing the graphical properties of the steps and ofthe criterion property.

For the case when only one criterion is defined in the THL:

It is mandatory to choose first the label and/or graphic (shape or icon) in anypart, either at criterion level or at the step level

If you selected a graphic property at the criterion level, then the same

graphic property cannot be selected in the steps

If you selected a graphic property at the step level, then the same graphicproperty cannot be selected in the criterion graphic property

Shape and icon cannot be simultaneously selected for any step or inside thecriterion

If shape is selected in steps or criterion properties, then icon cannot be

selected in steps

The same shape and color can be selected for multiple steps

If shape is selected in the criterion properties, then icon cannot be selected

in steps

If Voronoi is selected and a layer name is given in one step, in another stepVoronoi can be selected with a different layer name

If one property in one step is selected, that property should also be selected

in all the other steps.

For the case when two criteria are defined in the THL:

It is mandatory to choose first the label and/or graphic (shape or icon) in any

part, either at criterion level or at the step level

If you selected a graphic property at the criterion level, then the samegraphic property cannot be selected in the steps of first criterion, or in the

second criterion, or in the steps of second criterion

If you selected the graphic property at the step level, then the same graphicproperty cannot be selected in the criterion graphic property

Shape and icon cannot be simultaneously selected for any step or inside the

criterion

Shape in one step and icon in another step cannot be selected. If shape is

selected in one step, the icon is disabled in all the other steps

If shape is selected in criterion properties, then icon cannot be selectedin steps

If Voronoi is selected and a layer name is given in one step, in another step

Voronoi can be selected with different layer name

If one property in one step is selected, that property should be selected in

all other steps of that particular criterion.

3BK 21216 AAAA PCZZA Ed.26 547 / 664

23 Cartography

23.6.4.3 Create THL Template by CopyTo create a THL template by copy:

1. In the ’Thematic Template Editor’ window, select the THL to copy, then

click on .

2. The new THL template is created with a default name: <oldname>_Copy_n ,where n is an incremental number to define a unique name.

The THL template properties window is filled with the with the currentproperties of the template, except for the name and owner.


The user becomes the owner of the THL template.


The new THL template is created and the function tree is refreshed.

23.6.4.4 Edit THL TemplateA THL template cannot be edited if the modification impacts its current use.

To edit a THL template:


In the ’Thematic Template Editor’ window, select the THL you want to

update, then click on , OR

In the function tree, select the THL template you want to update, right

click and select THL....

If the operator is the owner or the administrator of the THL, the "ThematicTemplate Editor" window opens and the current attribute values of theselected THL are displayed.

If the owner of the THL is not the one viewing it, the button is grayed.



Click on [ OK ] in the confirmation window, then click on [ Close ] to close the’Thematic Template Editor’ window.

23.6.4.5 Delete THL TemplateTo delete a THL template:


In the ’Thematic Template Editor’ window, select the THL you want to

delete, then click on , OR

In the function tree, select the THL template you want to delete, right

click and select Delete .

The delete option is only available if the user is the owner or theadministrator of the THL template.

2. The following question appears: Are you sure you want to delete

the THL template <THL_name>?

548 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

If only one THL is selected to be deleted, click on [ Yes ]

If multiple THLs are selected to be deleted, click on [ Yes to All ].

The THL template is deleted.

23.6.5 Execute THL

23.6.5.1 Execute THL TemplateTo execute a THL template:

1. Select the appropriate network object(s) from the topology tree and oneTHL template from the function tree, then drag and drop them in thecartography viewport.


Using the availability domain of each criterion, the possible temporal valuesare proposed for the criteria. The date for each criterion can be different.

3. Click on [ Execute ] to execute the THL template.

The executed thematic layer is computed and all the network objects thatwere dropped along with the THL template are added to the viewport.Theexecuted thematic layer is displayed as a new thematic layer in thecartographic viewer containing:

The THL template reference ID

The execution context if available

The executed layer containing the rendering information

The legend explaining each rendering criterion.

Extentions:

If the object type node for the network object does not exist in the layermanager, the object type node is created and added as a sub-layer in

the network object layer in the layer manager. The parameters thathave enumerations are fetched from the server and added as a node

in the TableTree.

If any of the network objects does not satisfy the filtering criterion, thenthat object is not shown in the viewport, and no thematic object is

displayed in the viewport for that network object.

The thematic object is rendered on top of all the network objects thatsatisfy the step definition. If the user selected a Mobile deviation or

Standard deviation, then those objects are rendered on top of networkobjects.

The THL template is added as a sub node under THL layer in the layer

manager. This new sub-node is added on top of all executed layernodes. The structure of the layer in layer manager is given under section

Structure of executed THL layer in the layer manager.

When density is selected in the THL template and if you select only onenetwork object, the execution is not allowed.

3BK 21216 AAAA PCZZA Ed.26 549 / 664

23 Cartography

Figure 131: Example of Executed THL Template

Figure 132: Example of Executed THL Template

550 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

23.6.5.2 Edit Executed THL Template by Dialog Box1. Right click on a THL layer in the layer manager and select Executed THL... .

The ’Executed THL Properties’ window opens.

Figure 133: Example of ’Executed THL Properties’ Window

2. Click on [ Edit THL Template ].

The "Thematic Template Editor" window opens, displaying the selectedTHL data.

Edit the appropriate properties of the THL template. Some of the fields arenot available for editing.

Click on to save changes, then on to close the THLEditor.

3. You can choose to either:

Create a new THL layer with the new changes, by clicking on [ Create

THL ]A new THL layer is created in the layer manager and the thematicobjects are rendered in the viewport.

Apply the changes to the current executed layer, by clicking on [ UpdateTHL ].All thematic objects of the previous template are updated with thenew properties of the template.

The THL template is re-executed with the new properties.

3BK 21216 AAAA PCZZA Ed.26 551 / 664

23 Cartography

23.6.5.3 Execute Specific THL TemplateThe specific THL templates are un-modifiable and are supplied by the venders.These templates can only be executed.

1. Select the appropriate network objects and one specific THL template, thenand drag and drop them to the cartography viewer.

2. The ’Specific Execution Context’ window appears. This is built dynamicallybased on the specific THL template.

Enter the values for the Specific Execution Context.

3. Click on [ Execute ] to execute the specific THL template.

4. The selected objects along with the specific template are executed. Theexecution and rendering are same as that of the normal execution.

23.6.6 Display Thematics for Adjacencies

1. Create THL Template (Section 23.6.4.2).Take into account the following:

In the ’Template For’ field, select “ADJ”

From the right panel, select the appropriate logical parameter from the“Logical” tab, then drag & drop it in the ’Function id’ field.

2. Select the appropriate adjacencies and the newly created THL, then dragand drop them in the cartography viewport, to execute the THL.

Refer to Execute THL Template (Section 23.6.5.1).

The thematics are displayed for the dropped adjacencies.

The executed THL adjacencies will be shown under the THL layer and allthe NO Adjacencies dropped along with THL template will be displayedunder the Relations layer of the NO layer grouped by otype of the adjacency.

23.6.7 Frequency Reuse


Presentation This feature is used to make a graphical analysis regarding the re-use of oneof the frequencies of the selected cell by comparing the other cells inside ageographical area.

The geographical area is a circle centred on the selected cell. The radius of thiscircle is defined by the min and max values of the U_TIMEADVANCE parameterof the cell multiplied by a scaling factor (from 0.5 to 2.0). The minimum andmaximum values of the scale are stored in the cartography configuration file

The radius of the area, on which the frequency reuse check is performed, canbe set inside these bounds in the execution context.

The frequency reuse analysis is performed on all frequencies of the selectedcell except in the case where RH or NH/RH is used (i.e. only BCCH frequencyis checked).

For every non RH hopping frequency of the studied cell, the same check isperformed on all cells Ncell that satisfy the geographical criterion, i.e. cellsinside the circle defined above:

If Ncell is using RH or NH/RH, only BCCH of Ncell is checked

552 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

If Ncell is using NH or BBH, all frequencies of Ncell are checked.

According to the following legend, Ncell is displayed with the highest colourcode (red > orange > yellow > green):

Red = Ncell BCCH is a co-channel frequency with at least one frequency

of studied cell

Orange = Ncell TCH is a co-channel frequency with at least one frequency

of studied cell

Yellow = Ncell BCCH is an adjacent channel frequency with at least onefrequency of studied cell

Green = Ncell TCH is an adjacent channel frequency with at least one

frequency of studied cell.

Co-channel frequencies are those with identical ARFCN.

Adjacent channel frequencies are those for which : ABS(ARFCN1 – ARFCN2)= 1.

Procedure 1. Select a network object in the viewport, then right click and select Highlight-> Frequency Reusing Objects .

The "Input" window appears.

2. Type the appropriate radius of the circle that forms the geographic areaunder which you want to have the frequency reuse.

Figure 134: Example of "Input" for Radius Window

3. Click on [ OK ].

The request is sent to the server to get the frequency reused objects.The viewport is then updated and the network object is highlighted in theappropriate colour code (see the Presentation above).

3BK 21216 AAAA PCZZA Ed.26 553 / 664

23 Cartography

23.6.8 Show THL Legend

Select a THL and:



The legend of the executed thematic layer contains information about the splitand the rendering properties. It is a graphical representation of the criteriadefinition in the THL template.

Figure 135: THL Template with One Criterion Legend

554 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

Figure 136: THL Template with Two Criteria Legend

The “Thematic symbol” represents a label giving information about the thematicsymbol.

Criterion 1 step value column gives information about the graphical propertiesused in the criterion 1 step value.

Criterion 2 step value column gives information about the graphical propertiesused in the criterion 2 step value.

See Display Layer Legend (Section 23.3.3).

23.6.9 Export THL

See Export Displayed Layers/Viewport (Section 23.3.8).

3BK 21216 AAAA PCZZA Ed.26 555 / 664

23 Cartography

23.7 AdjacenciesThis chapter describes how to manage adjacencies and run adjacency analysis.

23.7.1 Presentation

The Cartography Module offers the adjacencies analysis functionality. Graphictools enable you to view existing and forecasted adjacency additions anddeletions for a cell, and decide whether you want to add the forecast to a tuningsession. Once this forecast is added to a tuning session, it can be exported tothe OMC-R (Refer to Create Topology Relation Tuning Operation(s) (Section22.5.10), Apply Tuning Session (Section 22.3.6), and GSM document: TuningBrowser User Guide).

The following actions are applicablewithin the adjacencies analysis tool:

Propose a choice of geographical discrimination: Circle, CCA buffer,

U-Time-Advance for 2G

Analysis: primitive returning adjacencies list (refer to Diagnosis (Section 21))

Find all target cells corresponding to the discrimination criteria

Show some statistics about candidate selection

Display a specific caption

Automatically suggest adjacencies to be added or removed

Allow the user to change the default proposal (by removing or adding

any other adjacencies,…).

556 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

Figure 137: Example of Adjacencies

3BK 21216 AAAA PCZZA Ed.26 557 / 664

23 Cartography

23.7.2 Adjacency Representation

23.7.2.1 Stand-alone LinksThis link is a Bezier Curve with an arrow at its center to give the direction.

When there is the same link in the opposite direction (Adj1 source = Adj2 targetand Adj2 source = Adj1 target), only one link is displayed and two arrows aredisplayed in the opposite direction.

When displaying object properties for bi-directional links, the objects propertiesare shown for both adjacencies objects.

The colour of the link is set in the cartography configuration file (Refer to”Adjacency Color” in Configure User Preferences (Section 27.2)).

Figure 138: Single Adjacency Representation

Figure 139: Bi-directional Adjacencies Representation

558 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

Figure 140: Non Co-localized Cells in Full-expanded/Expanded RenderingMode

Figure 141: Co-localized Cells in Full-expanded Rendering Mode

3BK 21216 AAAA PCZZA Ed.26 559 / 664

23 Cartography

23.7.2.2 Packed Links for Collapsed Source/Target ObjectsDue to the amount of links to display (up to 32 outgoing adjacencies perW-CDMA cell for example), when more than one link have the same graphicsource and same graphic target, the links are drawn in a packed mode showinga double link, the direction and the number of packed links.

The list of links in the packed link can be displayed in a pop up window (Referto Open Packed Link Content (Section 23.7.6)).

The graphic source/target is the rendering mode of an object:

Full Expanded co localized objects

Expanded co localized objects

Collapsed objects

Object icon.

Figure 142: Packed Links for Co-localized Cells in Collapsed Rendering Mode

Figure 143: Packed Links for Co-localized Cells in Expanded Rendering Mode

560 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

The packed links are used to render also the adjacencies between sectors orbetween sites. In this case, packed links can be bi-directional.

Figure 144: Packed Links Between Sectors and Sites

3BK 21216 AAAA PCZZA Ed.26 561 / 664

23 Cartography

23.7.3 Select Adjacencies

You can select an adjacency by clicking on it.

For a single direction adjacency, click on the line or on the arrow to select it.

For a bi-directional adjacency, if you click on the arrow of the adjacency, onedirection adjacency (source or target) is selected.If you select the right line from a cell, the outgoing adjacency is selected.If you select the left line from a cell, the incoming adjacency is selected.

For packed links, the all the links in one direction are selected, like

bidirectional links.To select one or more links inside the packed links objects, Open PackedLink Content window and select one or more links inside the list.If you select the right line from a site, the outgoing adjacencies are selected.If you select the left line from a site, the incoming adjacencies are selected.

You can choose to select multiple adjacencies in the rendering viewport.

The selection color is configurable from the user preferences menu (Referto ”Adjacency Color” in Configure User Preferences (Section 27.2)) or inthe cartography configuration file .

23.7.4 Display Adjacencies

Select the cell whose adjacencies you want to display, then:

Select Cartography -> Display Adjacencies from the menu toolbar, OR

Right click and select Show Adjacencies -> Incoming/Outgoing/Both .

The incoming, outgoing, and/or both adjacencies of the selected cell arerendered in Bezier curves.

Note: You can also display adjacencies using the procedure described in AddNetwork Objects in Viewport (Section 23.5.3).

23.7.5 Display Adjacency Properties

1. Select an adjacency in the cartography viewport.

2. Right click and select Properties... from the popup menu (Refer also toDisplay and Edit Properties (Section 3.3)).

The object properties window opens with the properties of the selectedadjacency.

If you change the selection, the object properties window is updated with thenew selection properties.

562 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

Figure 145: Example of Adjacency Properties

The parameters of Adjacencies properties window are:

ParameterName


Relation Type The type of the displayed relation: ADJ Yes Yes

RELATION ID The Relation ID of the displayed relation. Yes Yes

EXTERNAL ID The External ID of the displayed relation. Yes Yes

SOURCE TYPE The type of the displayed source relation. Yes Yes

SOURCEEXTERNAL ID

The External ID of the displayed source relation. Yes Yes

TARGET TYPE The type of the displayed target relation. Yes Yes

3BK 21216 AAAA PCZZA Ed.26 563 / 664

23 Cartography

ParameterName


TARGETEXTERNAL ID

The External ID of the displayed target relation. Yes Yes

FRIENDLYNAME

Friendly name of the relation. Yes Yes

23.7.6 Open Packed Link Content

Select the packed adjacency link you want to detail, then right click and selectOpen Packed Content .

The "Packed Link Contents" window opens displaying the friendly name of theadjacency and the adjacency type.

If the packed link contains more than one type of adjacency (combination ofplanned and operational), then that adjacency is displayed in a pre-definedcolor, which is configurable.

Each link in this window can be selected or highlighted, by checking thecorresponding checkbox (“Highlight” or “Select”). If the packed link is partiallyselected or highlighted, it is shown in a pre-defined color that is configurable.

Figure 146: Packed Link Contents Window

564 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

23.7.7 Run Adjacency Analysis Wizard to Create/Delete Adjacencies

The objective of this task is to make a proposal for the creation/deletion ofadjacencies based on the topological distance between the cells. Based on thisproposal, a tuning session can then be created and exported to the OMC-R.

1. To open the "Adjacency Analysis Wizard" window, select the cell with thepacked adjacencies you want to display, then:

Select Cartography -> Adjacency Wizard... from the menu toolbar, OR

Right click and select Adjacency Wizard... , OR


The "Adjacency Analysis Wizard" window opens.

All the incoming and outgoing adjacencies for the selected cell are displayedin the cartography viewport with the default adjacency color. The plannedadjacencies are displayed in the proposed for addition color. All the otheradjacencies are removed from the viewport.

2. Update the appropriate parameters, as explained in the table below.


U_TIMEADVANCE:Operational

Operational value of the U_TIMEADVANCE of the selected cell (in unity,and in parentheses the equivalent values in meters).

The operational value is multiplied by the radius, and is considered as theradius for the Adjacency wizard calculations.

U_TIMEADVANCE: Planned Planned value of U_TIMEADVANCE of the selected cell (in unity, and inparentheses the equivalent values in meters).

Circle: Center The circle center is either the site location or the Voronoi barycentre. Ifthere is no Voronoi map, the choice is the site location (by default the site isproposed).

Circle: Radius The default value (of radius) associated to the cell class of the selected cell.

The Radius of the circle can be defined as:

U_TIMEADVANCE - writes the distance in meters associated to theoperational U_TIMEADVANCE valueThe operational value is multiplied by the radius, and is considered asthe radius for the Adjacency wizard calculations.

“Cell Class Radius” - writes the distance associated to the cell class.

An edit area allows to enter the value in meters for the circle radius.By default, this edit box contains the value in meters associated to theoperational U_TIMEADVANCE value.

This value is then considered as the radius for Adjacency wizardcalculations.

3BK 21216 AAAA PCZZA Ed.26 565 / 664

23 Cartography


HO traffic filter When the “With HO filter” checkbox is activated, the type of traffic densitybecomes editable.

If the default traffic density “Low Usage” is checked, you can choose amongone of the two possibilities proposed on the left of this checkbox. The OFFposition resets the filter.

HO traffic is grayed for W-CDMA.

Adjacency Analysis This area summarises the information concerning the last analysis applied,with the number of adjacencies removed, added, and the total of forecastones.

All planned only adjacencies are candidates for addition.

All operational cells that are below the mentioned radius are candidates foraddition.

All other cells that are not candidates for addition are proposed ascandidates for deletion.

All adjacencies that are candidates for addition are changed to green colorand all adjacencies that are candidates for deletion are changed to red color.

3. Click on [ Update ] to save the new values.

The results are seen in the cartography viewport.

If you change the radius in the text box, press the [ Update ] button again tosee the new result.

If there were no adjacencies between two network objects, and you

clicked on [ Update ], and the network object lies inside the circle,adjacencies proposed for addition are drawn on both directions between

these cells. If there already is only one adjacency between the cells,then only one adjacency, which is proposed for addition, is drawn in the

reverse direction.

The Operational cells are represented by a continuous line, and thenon-operational cells by a dotted line.All planned adjacencies are represented by thick lines, and thenot-planned adjacencies are represented by thin lines.

A circle is drawn with the specified radius, centered as the user has

specified (on Site location or on the Voronoi Barycenter).

The incoming and outgoing adjacencies that are already displayed in theviewport are changed to green and red colored lines. Green lines are all

candidates for addition and red lines are all candidates for deletion.

You can select either green or red line and choose to remove theproposal (either addition or deletion) from the list. The list below explains

the details of the contextual menu that appears on the objects.

To create a new proposed adjacency : select the cell for whichyou want to create the new adjacency, then right click and

select Adjacency Management -> Add to Addition List ->Incoming/Outgoing .

566 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

Up to 25 adjacencies can be defined per sector.

To delete a proposed adjacency : select the cell whose adjacencyyou want to delete, then right click and select AdjacencyManagement -> Add to Deletion List -> Incoming/Outgoing .

To delete an existing adjacency : select it, then right click and select

Adjacency Management -> Add to Deletion List .

To remove a proposed adjacency creation/deletion :

Select the cell whose adjacencies you proposed forcreation/deletion, then right click and select AdjacencyManagement -> Remove from the Proposal ->Incoming/Outgoing , OR

Select the adjacency you proposed for creation/deletion, then right

click and select Adjacency Management -> Remove fromthe Proposal .

If the graphic object is a packed link or the collapsed objects, open first

the dialog to select the individual objects inside the group and then do

the operation on the selected object.In the Packed link dialog, for the adjacencies that are proposed foraddition and deletion, the Highlight and Select columns have the samebackground color as the adjacency color.

4. To add the new values and proposals of creation/deletion of adjacenciesto a tuning session, select it from the available drop-down list in ’ChooseTuning Session’, then click on [ Send to tuning ].

The "Relation Tuning" window opens and you can apply the tuning session(Reffer to Create Topology Relation Tuning Operation(s) (Section 22.5.10)and Apply Tuning Session (Section 22.3.6)).

3BK 21216 AAAA PCZZA Ed.26 567 / 664

23 Cartography

Figure 147: Adjacency Analysis Wizard

Figure 148: Adjacency Analysis Wizard

568 / 664 3BK 21216 AAAA PCZZA Ed.26

23 Cartography

23.7.8 Show Legend

See Export Displayed Layers/Viewport (Section 23.3.8).

Select an adjacency and:



Figure 149: Relations Layer Legend Dialog

The “State of Adjacency Symbol” column gives information about theAdjacency symbol.

The “Operational” column identifies whether the adjacency is Operational.

The “Planned” column identifies whether the adjacency is Planned.

See also Display Layer Legend (Section 23.3.3).

3BK 21216 AAAA PCZZA Ed.26 569 / 664

23 Cartography

570 / 664 3BK 21216 AAAA PCZZA Ed.26

24 Alerters

24 Alerters

This section describes how to display and manage alerters in NPO.

3BK 21216 AAAA PCZZA Ed.26 571 / 664

24 Alerters

24.1 Presentation

The “Alerters” feature is not available for B10 GSM.

Note: The MUSE_ALERTER_LICENSE must be installed for the Alerter relatedfeatures to be available.

Read more information about QoS Alerters in Quality of Service Alerters UserGuide - 3BK 21263 AAAA PCZZA.

24.1.1 Definition

Alerters are defined to detect QoS problems and generate QoS alarms inthe OMC-R, on the basis of reported Performance Measurement data, thenautomatically loaded inside the NPO. They are calculated from indicators.

Alerters have some attributes associated: name, alarm id, predicates,validity and stability conditions. At the end of each PM reporting period, theloader processes algorithms on these alerters, using thresholds and validityconditions, to detect the appearance or suppression of an alarm.

NPO alerters are not evaluated in real time, as the OMC-R alerters. Theminimum supported evaluation period is 1 hour to evaluate hourly indicatorvalues.

Alerters can be:

System defined, when they are delivered with the system and only some

parameters may be customized by the operator

Operator defined, these can be created from any Perfomance Indicator andare fully managed by the operator.

24.1.2 Types, Severities and States

The following alerter types are available:

Standard alerters : generate alerts if the value of the indicators crossesthe pre-defined thresholdsThe used threshold value is defined by the selected threshold color orby providing a user entered value.The stability parameter permits to decide when an alert is to be generated:for example if the given value is 3, an alert is generated only if the thresholdis crossed during the 3 last GPs. If the sampling is used, the alert is notgenerated if the sampling conditions are not fulfilled (enabled only when theindicator has an associated sampling indicator).

Variation alerters : generate alerts if the variation of the indicators valuecompared to a pre-defined “base line” exceeds the pre-defined thresholds

Four parameters are needed to implement variation alerters:

The number of observation periods P

The number of smoothing periods QQ is always less than P. It represents the number of periods needed tocompute the first (F) and the last value (L) of the curve.

572 / 664 3BK 21216 AAAA PCZZA Ed.26

24 Alerters

The delta in percentage that is used to determine if the alespirt mustbe generated

The algorithm (Average, Max, Min, Sum).

One period is equal to the alerter evaluation periodicity (e.g. if evaluationperiodicity is 1 hour and P=4, observation period is equal to 4 hours)Example of variation computation with P=12 and Q=3:

Points value for F: 12, 14 16. For each algorithm F is:

Average: F = (12+14+16)/Q = 14

Min: F = 12

Max: F = 16

Sum: F = 42.

Points value for L: 8, 7 and 9. For each algorithm L is:

Average: L = (8+7+9)/Q = 8

Min: L = 7

Max: L = 9

Sum: L =24.

The variation coefficient is S = (L-F)/FAverage: (8-14)/14 = -0.42Min: (7-12)/12 = - 0.42Max: (9-16)/16 = - 0.44Sum: (24-42)/42 = - 0.43S is displayed in percentage (S multiplied by 100). It can be then comparedto the given delta percentage. If the absolute value of S is greater than thecomputed delta, then an alert is generated.

Complex alerters : generate alerts in case a formula predicate is evaluatedto true.This predicate is constructed with a formula using multiple indicators. Theformula can use simple arithmetical and logical operators.For example, an alert is generated if ((I1 + I2 +I3)==0) && ((I1 + I2 + I4 +I5) > 5).The stability parameter is used as for standard alerters.

3BK 21216 AAAA PCZZA Ed.26 573 / 664

24 Alerters

Multiple severities can be defined for an alerter with different criteria. Thesupported severities are: Critical, Major, Warning. It is not mandatory to defineall of the severities, only one among these three is mandatory.

Three alerter states are used to manage the QoS Alerter:

Activated: the alerter is enabled and may raise or clear alarms

Deactivated: the alerter is disabled. There is no alarm on this alerter. The

alerter is created in deactivated state. It can be deleted only in this state.

Idle: the alerter is activated but disabled. It occurs when the current time isout of the alerter’s time scope. The alerter is still considered as “activated”.

24.1.3 Attributes

A QoS alerter is defined by the following attributes:

Name Description

Alerter Name The unique and user friendly name of the alerter.

Alerter ID Identifier used for the alerter unicity.

It is defined by the OMC-R, and not visible through the GUI.

Owner User name of the alerter creator.

“System” is used for system-defined alerters.

Technology Attribute that defines the kind of radio technology: GSM, W-CDMA, or WIMAX.

Category Defines the alerter origin: ‘system’, ‘operator’ or ‘3GPP’.

Alerter Type Can be either: Standard (default and for 3GPP), Range, Variation.

Alerter Family Telecom domain to be monitored, e.g. Traffic load, QoS, Handover, etc.

Famillies are defined through a configuration file.

SpecificInformation

Comment that describes the alerter and the generated alarm.

ManagedObject Class

Objects present in the PM File.

For instance, in W-CDMA it may be BB, Node B, RNC, CP, Cell, Ocell, Ecell, Dcell, Ccell,Interface, VC, VPCI_NB, VPCI_CN, VPCI_RNC.

ReportingElement

Type of Network Element that does the measurement (e.g. RNC or NodeB).

Spatial Scope Defines if the formula is computed on the pre-defined MOC or on the object container(e.g. RNS, RNC or NodeB for W-CDMA). By default, the scope is the defined MOC.

574 / 664 3BK 21216 AAAA PCZZA Ed.26

24 Alerters

Name Description

ManagedObjectInstance List(Object Scope)

If empty, all objects related to the MOC are selected for the threshold checking.

If not empty, the instance selection is a:

Subset of network objects (optional): network element (e.g. objects under RNS,

Node B or Iub), OR

List of Managed objects instance: a list of instances (cf. 3GPP PM IRP“createThresholdMonitor”).

QoS Alarm ID Identifies the alarm related to this alerter with the following configurable ranges:

System alerter: 200000 to 200099

Operator defined alerter: 200100 to 201999

3GPP Threshold monitor: 202000 to 203999.

PreventiveAction

Explanation text, used in the “Proposed Repair Action” alarm field.

Activation Flag Contains the current alerter status: activated/deactivated.

It may be “idle” when the current time is out of the time scope.

Direction Can be:

“Increasing”, the severity is higher when the threshold value increasesIf the measured value is equal or greater than the threshold, the threshold isconsidered as crossed.

“Decreasing” (the severity is lower when the threshold value increases)If the measured value is equal or lesser than the threshold, the threshold is consideredas crossed. It’s value may be set to “range” or empty for range alerter types.

Measurementtype (Formula)

Can contain:

Mathematical counter formula. All the counters are related to the same object andthe same PM file.The formula may contain the following symbols: “+”, “-”, “*”, “/”, “(“, “)”, integer, orfloat constants.Example: (CDR221b+CDR221bc )/(RBR030a+RBR030b)The counter formula is release dependent, which implies that such alerters are alsorelease dependent.

Indicator, which needs an NPO synchronisation.This type of alerter is release independent.

Thresholds 1 to 4 threshold values, one per severity level: Warning, Minor, Major, Critical.

Hysteresis 0 to 4.

Each threshold can have a hysteresis. A threshold with a hysteresis has threshold-highand threshold-low values that are different from the threshold value.

Within these two threshold levels, the indicator value is allowed to oscillate withouttriggering alarm raising or recovery conditions.

3BK 21216 AAAA PCZZA Ed.26 575 / 664

24 Alerters

Name Description

ContextValidation

Boolean formula on other counters (another counter > another threshold).

Empty by default.

Stability Period where formula and context should be verified to alert (equivalent to occurrence ofthe threshold crossing before rising the alert).

It should be a multiple of GP period. Only the current GP by default (1).

There are two stability parameters: one before raising the alarm, and the other beforeclearing the alarm.

If stability is 1, only the last value of the indicator is evaluated.

If stability is 2, the last two values of the indicator are evaluated.

For example, if stability=2 and color=red, the last two values of the indicators must crossthe threshold so that the red color be shown.

Time Scope Period when the alerter is active during the week (e.g. working hours).

The operator may select the same period for each day, or a specific period for each daysof the week. There is no time scope by default (always active).

GranularityPeriod

Should be set to the GP related to the counters used in the formula

Time Shift Laps of time between the beginning of the reporting period and the PM analysis.

The default value is 1 minute. This means that when the GP is 15 min, the PM analysis isdone at xx:01:00, xx:16:00, xx:31:00 and xx:46:00.

There is one global configuration parameter per GP put in the QoS Alerter IMconfiguration file.

Constraint The 3GPP alerters are not visible through the Alerter GUI. OnlySystem and OMC-R operator defined alerters are visible. Same for 3GPP:System and OMC-R operator alerters are not visible through 3GPP.

576 / 664 3BK 21216 AAAA PCZZA Ed.26

24 Alerters

24.1.4 Examples of Alerter Validity Period

24.1.4.1 Scenario 1Alerter Type: Standard

Periodicity: Day

Validity period: Monday, Wednesday, Saturday

Repetition: 1

Alerter activation: Monday (30-July-2007)

AlerterEvaluation day

Consolidated day dataconsidered for Alertgeneration (stability =1)

Consolidated day dataconsidered for Alertgeneration (stability = 2)

Comments

1st Evaluation Tuesday(31-July-2007)

Monday (30-July-2007) Monday

Sunday

2nd Evaluation Thursday(02-Aug-2007)

Wednesday(01-Aug-2007)

Wednesday

Tuesday

3rd Evaluation Sunday(05-Aug-2007)

Saturday (04-Aug-2007) Saturday

Friday

4th Evaluation Tuesday(07-Aug-2007)

Monday (06-Aug-2007) Monday

Sunday


Periodicity: Day

Validity period: Tuesday, Friday

Repetition: 2





Comments

1st Evaluation Saturday(04-Aug-2007)

Friday (03-Aug-2007) Friday

Thursday

2nd Evaluation Wednesday(08-Aug-2007)

Tuesday (07-Aug-2007) Tuesday

Monday

3rd Evaluation Saturday(18-Aug-2007)

Friday (17-Aug-2007) Friday

Thursday

3BK 21216 AAAA PCZZA Ed.26 577 / 664

24 Alerters


Periodicity: Hour

Validity period: 10.00 to 12.00

Repetition: 1

Alerter activation: 09.45 (30-July-2007)




Comments

1st Evaluation 11.00(30-July-2007)

10.00 – 10.59(30-July-2007)

10.00 – 10.59

09.00 – 09.59

2nd Evaluation 12.00(30-July-2007)

11.00 – 11.59(30-July-2007)

11.00 – 11.59

10.00 – 10.59

3rd Evaluation 13.00(30-July-2007)

12.00 – 12.59(30-July-2007)

12.00 – 12.59

11.00 – 11.59

4th Evaluation 11.00(31-July-2007)

10.00 – 10.59(31-July-2007)

10.00 – 10.59

09.00 – 09.59


Periodicity: Hour

Validity period: 09.00 to 12.00

Repetition: 2

Alerter activation: 09.45 (30-July-2007)




Comments

1st Evaluation 10.00(30-July-2007)

09.00 – 09.59(30-July-2007)

09.00 – 09.59

08.00 – 08.59

2nd Evaluation 12.00(30-July-2007)

11.00 – 11.59(30-July-2007)

11.00 – 11.59

10.00 – 10.59

3rd Evaluation 10.00(31-July-2007)

09.00 – 09.59(31-July-2007)

09.00 – 09.59

08.00 – 08.59

578 / 664 3BK 21216 AAAA PCZZA Ed.26

24 Alerters


Periodicity: Week

Repetition: 1





Comments

1st Evaluation Monday(06-Aug-2007)

Monday - Sunday(30-Jul-2007 –05-Aug-2007)

(30-July-2007 –05-Aug-2007)

(23-July-2007 – 29- July-2007)

2nd Evaluation Monday(13-Aug-2007)

Monday - Sunday(06-Aug-2007 –12-Aug-2007)

(06-Aug-2007 –12-Aug-2007)

(30-July-2007 –05-Aug-2007)


Periodicity: Week

Repetition: 2





Comments

1st Evaluation Monday(06-Aug-2007)

Monday - Sunday(30-Jul-2007 –05-Aug-2007)

(30-July-2007 -05-Aug-2007)

(23-July-2007 – 29- July-2007)

2nd Evaluation Monday(20-Aug-2007)

Monday - Sunday(13-Aug-2007 –19-Aug-2007)

(13-Aug-2007 –19-Aug-2007)

(06-Aug-2007 –12-Aug-2007)

3BK 21216 AAAA PCZZA Ed.26 579 / 664

24 Alerters


Periodicity: Month

Repetition: 1





Comments

1st Evaluation 01-Aug-2007 (01-July-2007 –31-July-2007)

(01-July-2007 –31-July-2007)

(01-June-2007 – 30-June-2007)

2nd Evaluation 01-Sep-2007 (01-Aug-2007 –31-Aug-2007)

(01-Aug-2007 –31-Aug-2007)

(01-July-2007 –31-July-2007)


Periodicity: Month

Repetition: 2





Comments

1st Evaluation 01-Aug-2007 (01-July-2007 –31-July-2007)

(01-July-2007 –31-July-2007)

(01-June-2007 – 30-June-2007)

2nd Evaluation 01-Oct-2007 (01-Sep-2007 –30-Sep-2007)

(01-Sep-2007 –30-Sep-2007)

(01-Aug-2007–31-Aug-2007)

580 / 664 3BK 21216 AAAA PCZZA Ed.26

24 Alerters

24.2 Alerter Editor

24.2.1 Open Alerter Editor

To open the Alerter Editor, in the Alcatel-Lucent Analysis Desktop window:


Select Alerter -> Alerter... .

The ’Alerter Editor’ window opens.

3BK 21216 AAAA PCZZA Ed.26 581 / 664

24 Alerters

24.2.2 Create Alerter

To create an alerter:

1. In the ’Alerter Editor’ window, click on .

The ’Alerter Type’ window appears.

2. Select the appropriate alerter type you want to create, then click on [ OK ].

The ’Alerter Editor’ window appears with default values and editable fields.



Name Name of the alerter to be created.

A maximum of 64 characters are allowed.

Alerter_<owner>_n

where<owner> isthe owner of thealerter, and "n" is anincremental number todefine a unique name

Owner User who is creating the alerter.


The usernameyou logged in theapplication

Created Date when the alerter was created.


Creation date

Modified Date when the alerter was last modified, in case of an alerterupdate.


Modification date

Alerter Type Defines the selected alerter type in the editor.The possible typesare: Standard, Variation, and Complex.


User selected type

582 / 664 3BK 21216 AAAA PCZZA Ed.26

24 Alerters


Indicator Drag the appropriate indicator from the ”Indicators” tab in theright frame, and drop it in the “Indicator” field.

This field must be filled in only in the case of Standard andVariation alerters.

Note: Only indicators with a defined threshold are droppablein the “Indicator” field.

Periodicity Periodicity for alerter evaluation.

It can be:

Indicator supported periodicity, for Standard or Variation

alerterThe possibilities for the periodicity depend on the availabilitydomain of the chosen indicator.

Formula supported, for Complex alerter.

The possible types are: Hour, Day, Week, Month.

If the periodicity is not supported by the indicator or formula forcomplex alerters, then “Periodicity” is grayed.

First supportedperiodicity

QoSRequirement

Describes the alerter QoS requirement.

The possible types are: Low, Medium, High.

Retrieved from UserPreference / WorkingZone QoS requirementvalue

Description Text box to be filled in with operator description for the currentalerter.

4. In the alerter severity panel, select the needed tab(s): Critical, Major,Warning, Cleared. The displayed fields to update vary depending on theAlerter Type.

At least one severity must be chosen for the created alerter.

For Standard Alerter

Select the “Color” criteria of the alerter from the drop-down list. Thepossible colors are Red, Orange, Yellow, and Green.The default values are: Red for Critical, Orange for Major, Yellow forWarning, Green for Cleared.For variation alerters, value “Free” also appears in the list. This is used ifyou want to choose your own threshold value.

Select the appropriate “Stability”.

3BK 21216 AAAA PCZZA Ed.26 583 / 664

24 Alerters

The periodicity unit is automatically updated whenever the “Periodicity”field value changes.

If the alerter will use sampling, check the “Use Sampling” checkbox.If the sampling is not supported by the selected indicator, the checkbox isgrayed.

For Variation Alerter

Select the “Direction” for threshold: “Raise” or “Fall”.

Select the appropriate “Observation period” of the selected alerterwith respect to periodicity.

Select the appropriate “Smoothing Period”. This represents the number

of periods needed to compute the first and last value of the curve. Itshould always be lesser than the observation period.The value of “Smoothing Period” must be lesser than the “Observationperiod” value.

Select the “Delta in percentage”. This defines the delta that is used to

determine if an alert needs to be generated. The value can be positiveor negative.

Select the appropriate “Algorithm” from the drop-down box, needed

for the computation of the variation alerter. The possible values are:Avarage, Max, Min, Sum.

The following table shows how all the parameters for the variation alerterevaluation are handled:

S is the result of algorithm calculation

X is the delta value given in alerter creation.

Direction Upper/Lower isfault

Evaluation Result Alert

S > XRaise Lower

S < X Alert generation

S > X Alert generationRaise Upper

S < X

S < XFall Lower

S > X Alert generation

584 / 664 3BK 21216 AAAA PCZZA Ed.26

24 Alerters

S < X Alert generationFall Upper

S > X

For Complex Alerter

In the “Formula” field, drag and drop the approriate indicators and

mathematical/logical/compharison operators from the right frame, tocreate the appropriate formula. This must be done for each severity.

Click on [ Check Formula ] to validate the formula. If errors occur,re-attempt to create a correct formula.

Select the appropriate “Stability”.The periodicity unit is automatically updated whenever the periodicitychanges.

5. Select the appropriate “Repetition” time for the selected alerter.

The periodicity unit is automatically updated whenever the periodicitychanges.

6. In case of “Hour” or “Day” periodicity, select the appropriate “Data ValidityPeriod”.

The period of validity is a time interval during the day or a list of days, inwhich the alerter can be evaluated.

7. Check [ Activate on apply ] if you want the alerter to be automaticallyactivated after its creation.

8. Check [ Automatic Clear ] if you want all the alerts to be cleared when thealerter state is changed to inactive.

9. The “Object Type” is automatically filled in when selecting the indicator, or incase of Complex alerters, from formula.

In case several options are available in a drop-down box, select theneeded one.

This does not display the zone object types.

10. Drag the appropriate network objects from the topology tab tree (in the rightframe) and drop them in the “Network Objects” panel.

The selected objects will be evaluated in the alerter.

11. If you want the alerter to be evaluated for the whole Working Zone, check[ Entire Working Zone: Global ].

When this is selected, the “Topology” tab from the right frame is disabled.

12. Click on .

13. Click on [ Yes ] at the confirmation message.

3BK 21216 AAAA PCZZA Ed.26 585 / 664

24 Alerters

The alerter is created and the tree in the Alerter mode is refreshed.

Note: All the created alerters are only available on the Analysis Desktop client, andnot on the NPO server. To send all the created alerts to the NPO server, makesure the “GENERATE_ALARAM” variable is set to “true” value (this is thedefault value), in the AlerterResourceFile.cfg file located in the/alcatel/muse/MUSE_MAAT/alerter/rsc/com/alcatel/muse/maat/alerter

directory.

586 / 664 3BK 21216 AAAA PCZZA Ed.26

24 Alerters

24.2.3 Create Alerter by Copy

To copy an alerter:

1. In the Alerter Editor, select the alerter you want to copy from the left frame,

then click on .

The ’Alerter Properties’ panel appears with the default name and propertiesof the selected alerter.

2. Define a name for the copied alerter, using the following format:<oldname_Copy_n> , where n is a incremental unique number.

3. Perform the appropriate modifications for the new alerter.


5. In the confirmation window, click on [ Yes ].

24.2.4 Edit Alerter

To edit an alerter:

1. In the Alerter Editor, select the alerter you want to edit from the left frame,

then click on .

The ’Alerter Properties’ panel appears.

2. Edit the appropriate values.

The ’Name’ field is read-only.


24.2.5 Delete Alerter

Only the owner or the administrator can delete alerters.

To delete an alerter:

1. In the Alerter Editor, select the alerter(s) to be deleted.

2. Click on .

3. In the deletion confirmation window, click on [ Yes ].

All the alerts associated to the deleted alerter are removed.

All the removed alerters and alerts are logged.

3BK 21216 AAAA PCZZA Ed.26 587 / 664

24 Alerters

24.3 Display Alerter List

24.3.1 Display Alerter List

To open the Alerter List, in the Alcatel-Lucent Analysis Desktop window:


Select Alerter -> Alerter List... .

The "Alerter List" window opens, listing all available alerters.

Column Name Description

Alerter Name Name of the alerter.

Owner Owner of the alerter.

Alerter Type Type of the alerter.

The possible types are: Standard, Variation, Complex.

Object Type Network objects type of the faulty object of an alert.

Object Nb Object number or name of the alerter, taken from the working zone.

State Current state of the alerter.

The possible states of the alerter are: Active, Inactive, Failed (when a problemoccured in the database).

Alerters are displayed taking into account the following:

The alerter is evaluated for each object of the alerter

The evaluation starts from the highest severity to the smallest. As soon asan alert is generated for a severity, the others (lower) are not evaluated

588 / 664 3BK 21216 AAAA PCZZA Ed.26

24 Alerters

Soft deleted objects are not evaluated. They are simply ignored

For each faulty object an alert is generated

If an alert with the same severity already exists, the last raise date value

is updated. If the severity is lower (or higher) than the existing alert, thecurrent alert is cleared and a new one generated with the new severity

The alerts are kept until they are cleared by the system or the user

If a GP is missing on the requested stability, the alerter is not evaluated andalerts are not generated

For variation alerters, if a GP is missing for the observation period, the

missing GP will not be taken into account in the algorithm calculation.

24.3.2 Actions in "Alerter List" Window

You can select the needed alerter(s), then click on:

[ Refresh ] , to update the alerter list

[ Edit ] , to edit the current selected alerterThe "Alerter Editor" window opens, Perform the actions decribed in EditAlerter (Section 24.2.4) .

[ Activate ] , to activate the selected alerter after checking the owner statusIn the confirmation window, click on [ Yes ] .The first evaluation of the alerter will occur at the next deadline of thegranularity period in the validity period.If the user is not the owner or the administrator, or if the alerter is alreadyactive, the [ Activate ] button is grayed.

[ Deactivate ] , to deactivate the selected alerter after checking the owner

statusIn the confirmation window, click on [ Yes ] .If the user is not the owner or the administrator, or if the alerter is alreadyinactive or failed, the [ Deactivate ] button is grayed.If Automatic Clear is checked in the Alerter Editor, all the alerts of thisalerter are suppressed.

[ Close ] , to close the alerter window.

You can also right click on the needed alerter(s), then select from the popupmenu:

Edit , to edit the current selected alerter

Activate , to activate the selected alerter

Deactivate , to deactivate the selected alerter.

3BK 21216 AAAA PCZZA Ed.26 589 / 664

24 Alerters

24.4 Display Alerts ListWhen you open the Analysis Desktop, if an alerts list with unacknowledgedalerts is present in the system, the alert window is automatically displayed.

Also, the toolbar Alerts icon is highlighted until all alerts present in thesystem are acknowledged.

To open the Alerter List, in the Alcatel-Lucent Analysis Desktop window:


Select Alerter -> Alerts List... .

The "Alerts View" window opens, listing all the alerts present in the AnalysisDesktop.


Ack Displays if the alert is acknowledged or not.

This column is not editable.

Severity Alerter severity.

The possible values are: Critical, Major, Warning, Cleared.

Alerter Name Name of the alerter.

Owner Owner of the alerter.

First Raise Date First raise date of the alert.

The date format is taken from Analysis Desktop user preference.

Last Raise Date Last raise date of the alert.

The date format is taken from Analysis Desktop user preference.

Object The faulty object of an alert.

If this is not in the current working zone, “unknown” is displayed instead of the objectidentifier.

590 / 664 3BK 21216 AAAA PCZZA Ed.26

24 Alerters


Reason The reason of the alert.

Depending on the alerter type, the column displays different data:

For standard type, indicator and color criteria are displayed

For variation type, indicator and delta values are displayed

For complex type, indicator and formula are displayed.

Alerter Type Type of the alerter.

The possible types are: Standard, Variation, Complex.

You can select the needed alerter(s), then click on:

[ Select All ], to select all the alert(s)

[ UnSelect All ], to unselect all alert(s)

[ Acknowledge ], to acknowledge all the selected alert(s)If any of the selected alerts is already acknowledged, the [ Acknowledge ]button is grayed.

[ Clear ], to clear all the selected alert(s)

An alert should be cleared if:

No alert is to be generated

The “Cleared” criterion is satisfied

There is currently an alert present on the current object.

The alerts are not cleared when the alerter definition is modified.

[ Edit Alerter ], to edit the alerter for which the alert is generatedPerform the actions decribed in Edit Alerter (Section 24.2.4).

[ Close ], to close the alerter window.

You can also right click on the needed alerter(s), then select from the pop-upmenu:

Edit Alerter , to edit the alerter for which the alert is generated

Copy , to create a new alerter by copyFollow the procedure steps described in Create Alerter by Copy (Section24.2.3).

Propagate -> Network Object(s)/Indicator(s) , to propagate the alert(s) tothe corresponding network object(s)/indicator(s)

Acknowledge , to acknowledge all the selected alert(s)

Clear , to clear all the selected alert(s)

Hide Acknowledged Alerts , to hide all the acknowledged alerts.

3BK 21216 AAAA PCZZA Ed.26 591 / 664

24 Alerters

592 / 664 3BK 21216 AAAA PCZZA Ed.26

25 Network Unavailability and Alarm Reporting Tool (NUART)

25 Network Unavailability and Alarm Reporting Tool(NUART)

This section describes how to manage network basic unavailability, alarms,and logs in NPO.

3BK 21216 AAAA PCZZA Ed.26 593 / 664


25.1 Presentation

This feature is not applicable for W-CDMA.

NUART (Network Unavailability and Alarm Reporting Tool) enables the user toanalyze and report network stability and availability.

Each day, NUART imports from each declared OMC-R the most recent archivefile containing:

Network topology

BSS/MFS alarms

OMC-R operator commands

Resource state changes

Resource current state.

The archive file is located on the OMC-R in the/alcatel/var/share/AFTR/LASER directory and has a specificname like ”<A1353RAInstnce>_day<n>.tgz ”, where:

<A1353RAInstnce> uniquely identifies a specific OMC-R

<n> identifies the day number.

Examples: A1353RA_838bc90d_day01.tgz , A1353RA_838bc90d_day02.tgz ,A1353RA_838bc90d_day03.tgz , . . . A1353RA_838bc90d_day31.tgz .

Two types of NUART metadata are defined in the LASER simplified dictionary:

Basic unavailabilities definition, used to generate QoS dictionaries that are

imported in the NPO data warehouseBasic unavailabilities definition does not include alarms and logs indicators.

Unavailability origins list definition, which is loaded into the NPO data

warehouse.

Unavailability indicators are a ratio based on the time during which theresources are down based on operational state.

Unavailability can be:

Planned: if it is scheduled for preventive maintenance on a resource for

example

Unplanned: if it is not scheduled, and results from a resource outagefor example.

They have boolean values: true/false.

Unavailability indicators correct the split between planned and unplanned, asthe automatic classification may not always be right.

LASER files are defined in XML format.

The LASER simplified dictionary file contains the following sections:

Header, that describes the dictionary (name, version, technology, supplier)

594 / 664 3BK 21216 AAAA PCZZA Ed.26


Release definition, that lists all supported releases used in the dictionary(name)

Unavailability origins definition, that list all Unavailability origins properties(type, filters, enable for a list of supported releases)

Basic Unavailability definition, that list all Basic Unavailabilities properties

(object type, spatial aggregation for a list of supported releases).

The content of a LASER simplified dictionary is presented below:

Section Content Description

Name Dictionary name

Version Dictionary version

Technology Standard name such as GSM,W-CDMA, or Wimax

Supplier Supplier name

Header

Description Free comments

Releases (foreach release)

Release Definition/Name Release name

Object type Object type name

Unavailability Type Unavailability type such asGPRS

Spatial aggregation path Describes the spatialaggregation path for the objecttype and the unavailability type

Planned flag Flag to manageplanned/unplanned (defaultvalue = true)

BasicUnavailabilities(for each basicunavailability)

Release name Identification of the release

3BK 21216 AAAA PCZZA Ed.26 595 / 664


Section Content Description

Name Unavailability origin name

Type Alarm or Log

Object type filter (optional) Like filter on object type forAlarms and Logs

Event/Log type filter (optional) Like filter on: Event type forAlarms Log type for Logs

Probable cause filter (optional) Like filter on Probable causefor Alarms

Specific problem cause filter (optional) Like filter on Specific problemfor Alarms

Managed Object Instance (MOI) filter optional Like filter on MOI for Alarms

Managed Object Class (MOC) filter optional Like filter on MOC for Alarms

Enable Indicates if the unavailabilityorigin is enabled or not (defaultvalue = true)

Unavailabilityorigins (for eachunavailabilityorigin)

Release name:8190/NUART/common/login.jsp Identification of the release

The import/deletion of LASER, Basic Unavailabilities, alarms, logs is describedin NPO Administration Guide.

Using NUART services, the operators can produce statistics on the mostfrequent alarms/logs/unavailability, filter and sort them to detect the mainimpacts on stability and unavailability.

596 / 664 3BK 21216 AAAA PCZZA Ed.26


25.2 Open NUART Web InterfaceTo open the Network Unavailability and Alarm Reporting Tool (NUART):


Type the URL of the NUART Web page in the address bar in an internet

browser: http://<NPOServer_IP_address>

OR

Select from the NPO iconbox: MUSE Applications -> Optimization-> Unavailability

The "NUART" web interface opens.OR

If you select network objects from the Topology Browser, then select

NUART -> Display Basic Unavailability / Display Alarms and Logsfrom the Analysis Desktop menu, the "NUART" page opens with the

selected network objects as checked.This is a quicker procedure to use the needed network objects in"NUART".

Pay attention to the number of selected network objects, as there is a limitationin the URL of NUART to 2,048 characters.

2. Enter the login and password.

If you use Mozilla web browser and a new page is opened for the first time,after you enter the login and password, the following message appears :Do

you want the Firefox to remeber your password? . Click on [ Neveron this site ].

The "Select Working Zone" window opens.

When the NUART window is opened for the first time, the “Global” workingzone is selected by default.

3BK 21216 AAAA PCZZA Ed.26 597 / 664


The list of all working zones are displayed. Clicking on one opens itsproperties: Working Zone Name/Owner/QoS Requirement/Description.

3. Select the appropriate working zone from the listed ones, then click on [ OK ].

The "NUART" window opens.

598 / 664 3BK 21216 AAAA PCZZA Ed.26


25.3 Close NUART Web InterfaceTo close the Network Unavailability and Alarm Reporting Tool, from the"NUART" window click on [ Exit ] button.

You must not click on the icon from the right corner.

25.4 Change Working Zone in NUART Page1. Open NUART Web Interface (Section 25.2)

2. Select Working Zone -> Change Working Zone .



3. Select the checkbox corresponding to the working zone you want to changeto, then click on [ OK ].

4. Click on the top buttons:

[ Exit ], to exit the NUART window page.

[ Help ], to open the help page.

3BK 21216 AAAA PCZZA Ed.26 599 / 664


25.5 Display Basic Unavailability (BU)1. Perform one of the following options:

Select from the Analysis Desktop menu bar NUART -> Display BasicUnavailability , OR

Open NUART Web Interface (Section 25.2), then select BasicUnavailability -> Display Basic Unavailability .

The "Display Basic Unavailability" window opens. The left panel displaysthe chosen working zone with associated network topology, while the rightpanel lists selectable options for displaying the BU.

2. Type the BU period to be displayed in the “From Date”, ”To Date” fields,in mm/dd/yyyy format, or click on the calendar icon and choose theappropriate dates.

The “To Date” field is by default filled in with the current date.

”From“ and “To” Date fields represent the start time of the last value tobe displayed.

3. If needed, select to filter after the appropriate Unavailability Type.

This drop-down list contains all basic unavailability types imported as part ofthe laser dictionary. The supported types are GSM and GPRS.

If no option is selected, both GSM and GPRS values are taken into account.

4. Select the appropriate Relevant Hours. The following options are available:All, Yes, No.

5. Select the type of Basic Unavailability. The following options are available:All, Planned, Unplanned.

6. Optionally, select the Origin for which to display the BU. For this, click on“Origin”.

A pop-up window appears, displaying all available origins in the system.

Select the needed origin(s), then click on [ OK ].

The selected origins are displayed in the “Origin” listbox.

600 / 664 3BK 21216 AAAA PCZZA Ed.26


7. Select from the left panel the network object(s) for which the BU to bedisplayed. If a parent object is selected, all its children are selected.

Pay attention to the number of selected network objects, as there is alimitation in the URL of NUART to 2,048 characters.

8. Click on [ OK ].

A table with the required data is displayed.

If the number of BU to be displayed is greater than the configurable size thatfits the opened window, the data is displayed on several pages. Click on

the navigation arrows or type the number of the desired page,then click on [ Go ].

From the NUART, the BU are displayed using the tables with raw data and thesetables have a storage duration of 32 days, while in the Analysis Desktop the BUare displayed using the tables with normalized data.

9. To change the Basic Unavailability (planned/unplanned) for a certainnetwork object and date, choose the appropriate value from the drop-downlist, then click on [ Save ].

Click on [ OK ] to confirm the operation.

If the value of Basic Unavailability is changed, it is recommanded to triggeran On-Demand Consolidation of Unavailability (refer to “NPO AdministrationGuide”).

10. To view a certain Suspect Origin, refer to Display Suspect Origin of BasicUnavailability (Section 25.6).



[ Home ], to go to the Welcome page

3BK 21216 AAAA PCZZA Ed.26 601 / 664



602 / 664 3BK 21216 AAAA PCZZA Ed.26


25.6 Display Suspect Origin of Basic Unavailability1. Display Basic Unavailability (BU) (Section 25.5).

2. To view suspect BU data for a particular object in the table with BU, click onits link in the “Origin” column of the table.

The "Display Suspect Origin" window for that object opens.

3. Select the ’appropriate values in the Window Before’ and ’Window After’drop-down lists.

4. Optionally, select the appropriate ’Origin’, by clicking on the “Origin” anchor.

A pop-up window appears with the list checkboxes and Origin Nameavailable in the datawarehouse.

Select the appropriate Origin(s), then click on [ OK ].

The pop-up window is closed, and the selected origins are displayed in thelistbox present in the parent window.

5. Click on [ OK ].


3BK 21216 AAAA PCZZA Ed.26 603 / 664



[ Back ], to go to the Display Basic Unavailability (BU) screen




604 / 664 3BK 21216 AAAA PCZZA Ed.26


25.7 Display Alarms and Logs1. Perform one of the following options:

Select from the Analysis Desktop menu bar NUART -> Display Alarmsand Logs , OR

Open NUART Web Interface (Section 25.2), then select Alarms & Logs-> Display Alarms and Logs .

The "Display Alarms and Logs" window opens. The left panel displays thechosen working zone with associated network topology, while the right panellists selectable options for displaying Alarms and Logs.

2. Type the Alarms and Logs period to be displayed in the “From Date”, ”ToDate” fields, in mm/dd/yyyy format, or click on the calendar icon and choosethe appropriate dates.



3. If you want to apply a filter, select it from the ’”Filter List” field.

By default, the user default filter is selected, if this exists.

To create a new filter, refer to Manage Filter for Alarms and Logs.

4. If you want to sort the alarms and logs data:

By default, the user default filter with sorting criterias is selected, if this exists.

To create a new sorting criteria, refer to Define Sort Criteria for Alarmsand Logs.

5. Select the Relevant Hours from drop-down list. The possible values are:All, Yes, No.

6. Select from the left panel the network object(s) for which the alarms andlogs data to be displayed. If a parent object is selected, all its childrenare selected.

Pay attention to the number of selected network objects, as there is alimitation in the URL of NUART to 2,048 characters.

7. Click on [ OK ].

A table with the required data is displayed. Alarms are displayed with a rowcolor corresponding to their severity, as follows:

Critical - Red

Major - Orange

Minor - Yellow

Warning - Blue

Indeterminate - White.

3BK 21216 AAAA PCZZA Ed.26 605 / 664


If the number of alarms and logs to be displayed is greater than theconfigurable size that fits the opened window, the data is displayed on

several pages. Click on the navigation arrows or type the numberof the desired page, then click on [ Go ].





606 / 664 3BK 21216 AAAA PCZZA Ed.26


25.8 Manage Filter for Alarms and Logs1. Open NUART Web Interface (Section 25.2)

2. Select Alarms & Logs -> Manage Filter .

The "Manage Filter" window opens, with the user default filter selected. Ifthere is no default filter, then no filter appears as selected.

3. Select a filter from the available ’Filter List’. The selected filter name isdisplayed in the ’Filter Name’ text field, and the corresponding filter criteriasare displayed in the table below.

4. To create a new filter , perform the following steps:

4.1 If any filter details appear in the bottom table, click on [ Clear ]. Theexisting filter details are removed.

4.2 Type the new filter name in the “Filter Name“ text field.

4.3 Select the appropriate “View Type” from the drop-down list.

The view type contains three options:

Alarm OnlyThe following attributes appear in the “Field” list from the bottomtable: Event type, Probable cause, Specific problem, Perceivedseverity, Friendly name.

Log OnlyThe following attributes appear in the “Field” drop-down from thebottom table: Log type and Operator name.

Mixed Filter.All the attributes defined in” Alarms Only” and “Log Only” casesappear in the “Field” drop-down from the bottom table.

4.4 In the second table, select the appropriate attribute from the “Field”column.

4.5 Select the appropriate relational operators (equals, different, or like).

4.6 Select an attribute from the “Value” list, or type its value in the

displayed textfield. The ’*’ wildcard can be used.

4.7 Apply the Logical conditions “AND”, “OR” which are present in the

“Logic” dropdown.

4.8 Click on [ Insert ].The first table in the Filter Criteria panel is updated with the newlycreated filter criteria.

4.9 To add more filter criterias, perform steps 4.4 - 4.8 for each newfilter criteria.

4.10 To update the filter with a new view type and filter criteria, select the

filter criteria, perform the modifications, then click on [ Update ].

4.11 To remove a row in the table, select its anchor number and click

on to [ Remove ].

4.12 Click on [ Save ] to save the filter, then on [ Yes ] at the confirmationquestion.

3BK 21216 AAAA PCZZA Ed.26 607 / 664


5. To make a filter the default one, select it, then check the ’Make this filter asdefault’ checkbox.

6. To update the filter, select it, perform the needed modifications (refer to theappropriate steps 4.3 - 4.11), then click on [ Update ].

The filter criterion is updated in the data warehouse.

7. To delete the filter, select it and click on [ Delete ].

The filter criterion is deleted from the data warehouse.





608 / 664 3BK 21216 AAAA PCZZA Ed.26


25.9 Define Sort Criteria for Alarms and Logs1. Open NUART Web Interface (Section 25.2)

2. Select Alarms & Logs -> Define Sort Criteria .

The "Define Sort Criteria" window opens, with the user default sort criteriaselected. If there is no default sort criteria, then no sort criteria appearsas selected.

3. Select a sorting criteria from the available ’Sort List’. The selected sort nameis displayed in the ’Sort Criteria Name’ text field, and the correspondingsort criterias are displayed in the table below.

4. To create a new sorting criteria , perform the following:

4.1 If any sorting criteria details appear in the bottom table, click on[ Clear ]. The existing sorting criteria details are removed.

4.2 Type the new sorting criteria name in the “Sort Criteria Name“

text field.

4.3 Select the appropriate “View Type” from the drop-down list.

The view type contains three options:

Alarm OnlyThe following attributes appear in the “Field” list of the bottomtable: Object Identifier, Friendly Name, MOC, MOI, Event type,Probable Cause, Specific Problem, Perceived Severity, Event time,and Clear time.

Log OnlyThe following attributes appear in the “Field” drop-down of the bottomtable: Object Identifier, Log type, Object type, Execution time, andOperator name.

Mixed Filter.All the attributes defined in” Alarms Only” and “Log Only” casesappear in the “Field” drop-down of the bottom table.

4.4 Add one or several attributes from the “Available” listbox to the“Selected” listbox by selecting them, then clicking on [ Add ].To remove them from the ”Selected” listbox, select them, then click on[ Remove ].The “Field” column from the bottom table fills in with the selected sortingcriteria.

4.5 Select each sorting criteria from the dropdown list in the “Field”

column, and define for each the appropriate sorting order: “Asc” (for

ascending) or “Desc” (for descending).

4.6 After defining each sorting criteria order, click on [ Insert ].The first table in the “Define Sort Criteria” panel is updated with thenewly created sorting criteria.

4.7 To add more sorting criteria, perform steps 4.4 - 4.7 for each new

filter criteria.

4.8 To update the sorting criteria with a new view type and soring criteria,select it and perform the modifications, then click on [ Update ].

3BK 21216 AAAA PCZZA Ed.26 609 / 664


4.9 To remove a row in the table, select its anchor number and click on[ Remove ]. Multiple deletion can be done by selecting several rows.

4.10 Click on [ Save ] to save the sorting criteria, then on [ Yes ] at theconfirmation question.

5. To make a sorting criteria the default one, select it, then check the ’Make thissort criteria as default’ checkbox.

6. To update the sorting criteria, select it, perform the needed modifications(refer to the appropriate steps 4.3 - 4.10), then click on [ Update ].

The sorting criteria is updated in the data warehouse.

7. To delete the sorting criteria, select it and click on [ Delete ].

The sorting criteria is deleted from the data warehouse.





610 / 664 3BK 21216 AAAA PCZZA Ed.26


25.10 LASER ReportsYou can execute NUART releated reports, by draging the appropriate networkelement(s) and report template(s) and droping them in the report viewer.Refer to Execute Report section from NPO User Guide for more informationon how to execute a report.

There are two reports called "STABILITY" and "AVAILABILITY" that provide aglobal view of BSC and MFS availability and stability.

The following NUART related report template(s) are available in the Report tabfrom the function browser:

ALARM_EVOLUTIONThe Alarm Evolution Reports display the daily evolution of the basic alarmson a selected sub-network, and over a specified observation period.

This report contains the following views:

Global Network, displaying the topology elements count: BSC, MFS,OMC, BTS, N7, TRX, CELL

Evolution, that counts per day, on the defined period and from the alarms

related to defined area, the number of alarms matched with the user text.

ALARM_SYNTHESISThe Alarm Synthesis Reports display the number of predefined alarmssorted by BTS, BSC, TRX and MFS.


Global Network, displaying the topology elements count: BSC, MFS,

OMC, BTS, N7, TRX, CELL

Number of alarms per BTS belonging to the selected observation area

and split by BSC

Number of alarms per BSC belonging to the selected observation area

Number of alarms per MFS belonging to the selected observation area

Number of alarms per BSC belonging to the selected observation area.

DAILY_SUMMARY_TRANSMISION_OCCURENCEThe Daily Summary Transmission report displays predefined alarms thatoccur in a defined area for the specified day. These predefined alarms havea direct impact on transmission link availability.

DAILY_SUMMARY_TRANSMISION_TIMEThe Daily Summary Transmission report displays predefined alarms thatoccur in a defined area for the specified day. These predefined alarms havea direct impact on transmission link availability.

GLOBAL_TRANSMISION_EVOLUTIONIt provides a global view of Transmission alarms. It displays in a cross-tablethe number of alarms and duration per day (in second).

OPERATIONALThe Operational Reports provide statistics on alarms split in several groups.


Global Network, displaying the topology elements count: BSC, MFS,

OMC, BTS, N7, TRX, CELL

3BK 21216 AAAA PCZZA Ed.26 611 / 664


Alarms split per severity: critical, major, minor, warning, events

Alarms split per event type: communication, environment, equipment,processing error, quality of service

BSC alarms, split per event type, and split per event type and probablecause

BTS alarms, split per event type, and split per event type and probable

cause

MFS alarms, split per event type, and split per event type and probable

cause

Transcoder alarms, split per event type, and split per event type andprobable cause

Top N occurrences on same specific problem.

STABILITYStability report displays the Total number of alarms per TRE and per day,total number of predefined alarms, Cut-off on Air interface per TRE andper day.

TOP_N_OCCURENCE_ALARMSTop N Alarms Reports display the Top N Alarms according to item typeover a specified period.The number of occurrences is classified by: event type, friendly name,perceived severity, probable cause, specific problem.The considered period is classified by: days, minutes, seconds.

TOP_N_TIME_ALARMSThis function allows displaying top N of alarms. This top N is generatedaccording to a defined attribute of items: the top 1 counts the highestnumber of items with the same value for this defined attribute (if type ofresult is based on the time).

TOTAL_DURATION_PER_ALARMThe report will display in a cross table for all the selected Network Elementsthe overall duration in seconds of their alarms for each day of a selectedperiod.

TRANSMISSION_TROUBLESHOOTINGThe report display transmission alarms for A/Abis/Ater Trailing TerminationPoint. The filter will be done according to the FriendlyName.

AVAILABILITYThe Availability Report displays the average planned and unplanned , in busyand non-busy hours, unavailability notifications per resource and per day.

TOP_N_BASIC_UNAVAILABILITYThe Top N Basic Unavailability Reports display Top N basic unavailabilityindicators over a specified period.

This report displays the number (count) of basic unavailabilities matching aninterval of time on each topology object, grouped by dependency of:

Time/Day

Time/Hour

Time/Minute

Time/Seconds.

612 / 664 3BK 21216 AAAA PCZZA Ed.26


TOP_N_OPERATOR_COMMANDTop N Operator Commands Reports display Top N operator commandsover a specified period.This report displays all operator commands grouped by LOGTYPE.

TopN_UNAVAILABILITYTop N Unavailability Reports display Top N unavailability indicators overa specified period.This report displays the number (count) of basic unavailability matching aninterval of time and selected topology object (day, week, month) orderedby friendly name.

25.11 Delete Failed LASER File ProcedureThe script cleanFailed.sh removes the failed entries for a particular dateand for a particular Domain.

You have to run the script manually if you want to load again the particularfailed domain [QOS/LASER] for a date.

Launch as root the following commands:cd /alcatel/muse/MUSE_QOS/bin./cleanFailed.sh LASER DD-MM-YYYY

You can see the log of which domain is cleaned on what date in/alcatel/temp/data/trace/cleanedFiles.log file.

3BK 21216 AAAA PCZZA Ed.26 613 / 664


614 / 664 3BK 21216 AAAA PCZZA Ed.26

26 Remote Inventory Data Management


This section describes how to manage hardware remote inventory in NPO.

3BK 21216 AAAA PCZZA Ed.26 615 / 664


26.1 Presentation

This feature is not applicable for W-CDMA.

The Hardware Inventory module of Muse is a set of applications that canbe accessed from the iconbox. It consists of Remote Hardware Inventorymanagement and Customer Acceptance List management.

26.1.1 Remote Hardware Inventory

The HW inventory data of all network elements is necessary for the operatorsto prepare interventions on sites (such as HW retrofits).

Using Remote HW Inventory, data is collected for the entire equipment veryquickly and precisely, without the need to go on site. The operator has thenthe information allowing them to determine the exact number and locations ofboards to be replaced (for example before introduction of a new release) or thedetailed characteristics (especially the functional variant and ICS (correctionstatus)) of a faulty board needing interventions.

The inventory data is collected from the OMC-R, which in the case of W-CDMAmay directly forward the request to the relevant network elements.

By default the data is imported every night, but it is possible to change theperiodicity, or to explicitly trigger an update for a part of the network (a BSS orRNS) - for this, refer to Load Inventory from “NPO Administration Guide”.

The main formats of the HW Inventory files (both being supported by MUSE)are:

INVENTAR, a text based format used by Alcatel-Lucent. Depending on

the production of the file (the factory, the equipment itself) and on thetype of equipment (not all equipment produce the same information), not

all fields may be filled in

616 / 664 3BK 21216 AAAA PCZZA Ed.26


3GPP inventory, coming from the the W-CDMA OMC-R, which produces3GPP inventory, and also adds the field coming from INVENTAR.

26.1.2 Customer Acceptance List

A Customer Acceptance List (CAL) is a file which contains the part number ofall equipments which should be in the customer field.

The content of a CAL is compared with the data coming from the field tocheck any discrepancies, in particular hardware modules in the field whichare not covered by the CAL.

There are two types of CAL files:

Generic CALsGeneric CALs are produced by Alcatel-Lucent and sent to the customer.

Customer Specific CALsFrom the Generic CAL, the customer may remove the reference toequipment types not used in their network (for example: reference to G2 BTSfor a customer having only 9100 BTS) and thus create their specific CAL.The Customer Mnemonic field is used to differentiate the two types ofCAL files.

The CAL file (generic file for Alcatel-Lucent, or customer specific CAL) isimported into MUSE after an Administrator request. This procedure is explainedin “NPO Administration Guide”, section Import Customer Acceptance List.

The administrator manipulates Hardware Inventory CAL files.

3BK 21216 AAAA PCZZA Ed.26 617 / 664


26.2 Start Remote Inventory Data ManagementTo open the NPO Remote Inventory Data Management (RIDM) page:

1. From the iconbox, select MUSE Applications -> Optimization -> RemoteInventory .

A login window opens.

2. Type the username and password.

If you use Mozilla web browser and a new page is opened for the first time,after you enter the login and password, the following message appears :Do

you want the Firefox to remeber your password? . Click on [ Neveron this site ].


When the RIDM window is opened for the first time, the “Global” workingzone is selected by default.


3. Select the appropriate working zone from the listed ones, then click on [ OK ].

The "RIDM" window opens.

618 / 664 3BK 21216 AAAA PCZZA Ed.26


3BK 21216 AAAA PCZZA Ed.26 619 / 664


26.3 Change Working Zone in RIDM Page1. Start Remote Inventory Data Management (Section 26.2)

2. Select Working Zone -> Change Working Zone .



3. Select the checkbox corresponding to the working zone you want to changeto, then click on [ OK ].


[ Exit ], to exit the RIDM window page.


620 / 664 3BK 21216 AAAA PCZZA Ed.26


26.4 Display End of WarrantyTo display the list of elements whose end of warranty is in a given period oftime (or from a given date):

1. Start Remote Inventory Data Management (Section 26.2)

2. Select Boards -> Display End of Warranty .

3. Type the appropriate period to be displayed in the “From Date” and ”To Date”fields, in mm/dd/yyyy format, or click on the calendar icon and choose theappropriate dates.



4. Click on [ OK ].


3BK 21216 AAAA PCZZA Ed.26 621 / 664


You can sort all the columns of the table in ascending or descending orderby clicking the column headers.

If the number of data to be displayed is greater than the configurablesize that fits the opened window, the data is displayed on several pages.

Click on the navigation arrows or type the number of the desiredpage, then click on [ Go ].

5. To export the data of table in CSV file format:

Browse for the file path where to save the file, then click on [ Open ]

Click on [ OK ] to start the exportA progress bar displays the progress and eventual completion of theoperation. Wait for the end of the export.When the export is done, another window opens displaying theproperties and status of the exported data.

Click on [ End ] to return to the "Display End of Warranty" window.


[ Exit ], to exit the RIDM window page



622 / 664 3BK 21216 AAAA PCZZA Ed.26


26.5 Search for BoardsTo display the list of equipments that match a given criteria:


2. Select Boards -> Search for Boards .

3. Select the appropriate filter from the ’”Filter List” field.

By default, the user default filter is selected, if this exists.

To create a new filter, refer to Manage Filter.

4. Click on [ OK ].

The boards that match the filter are displayed in a table.


If the number of boards to be displayed is greater than the configurablesize that fits the opened window, the data is displayed on several pages.

3BK 21216 AAAA PCZZA Ed.26 623 / 664






Click on [ End ] to return to the "Search for Boards" window.





624 / 664 3BK 21216 AAAA PCZZA Ed.26


26.6 Display Board Type StatisticsTo display the boards based on their PartnumberAndICS field:


2. Select Boards -> Display Board Type Statistics .

The board type statistics are displayed in a table. Each row displays a’PartNumberandICS’ field and the count of the boards that have thisPartNumberandICS .


If the number of boards to be displayed is greater than the configurablesize that fits the opened window, the data is displayed on several pages.




3BK 21216 AAAA PCZZA Ed.26 625 / 664



Click on [ End ] to return to the "Display Board Type Statistics" window.





626 / 664 3BK 21216 AAAA PCZZA Ed.26


26.7 Display Board HistoricTo display the boards that have been added or removed during a given periodfor a certain board criteria:


2. Select Boards -> Display Board Historic .

3. Type the appropriate period to be displayed in the “From Date” and ”To Date”fields, in mm/dd/yyyy format, or click on the calendar icon and choose theappropriate dates.



4. Select the ’Board Type’ to be displayed: added boards only, removedboards only, or all.

5. Click on [ OK ].


3BK 21216 AAAA PCZZA Ed.26 627 / 664








Click on [ End ] to return to the "Display Board Historic" window.

628 / 664 3BK 21216 AAAA PCZZA Ed.26






3BK 21216 AAAA PCZZA Ed.26 629 / 664


26.8 Display Customer Acceptance ListTo display the boards which are referenced in the Customer AcceptanceList (CAL):

1. Start Remote Inventory Data Management (Section 26.2).

2. Select CAL -> Display Boards in CAL .

3. Select the appropriate filter from the ’”Filter List” field.

By default, the user default filter is selected, if this exists. These filtersshould be created taking into consideration the data displayed in the"Search for Boards" page.

To create a new filter, refer to Manage Filter.

4. Click on [ OK ].

A table with the list of boards referenced in the Customer Acceptance Listis displayed.







630 / 664 3BK 21216 AAAA PCZZA Ed.26


Click on [ End ] to return to the "Display Customer Acceptance List"window.





3BK 21216 AAAA PCZZA Ed.26 631 / 664


26.9 Display Boards Not in Customer Acceptance ListTo display the list of boards and their location which are not referenced in thecustomer acceptance list:

1. Start Remote Inventory Data Management (Section 26.2).

2. Select CAL -> Display Boards Not in CAL .

A table with the list of boards and their location which are not present inCAL is displayed.






Click on [ OK ] to start the exportA progress bar displays the progress and eventual completion of theoperation. Wait for the end of the export.

632 / 664 3BK 21216 AAAA PCZZA Ed.26


When the export is done, another window opens displaying theproperties and status of the exported data.

Click on [ End ] to return to the "Display Boards Not In Customer

Acceptance List" window.





3BK 21216 AAAA PCZZA Ed.26 633 / 664


26.10 Manage Filter1. Start Remote Inventory Data Management (Section 26.2)

2. Select Filter -> Manage Filter .

The "Manage Filter" window opens, with the user default filter selected. Ifthere is no default filter, then no filter appears as selected.

3. Select a filter from the available ’Filter List’. The selected filter name isdisplayed in the ’Filter Name’ text field, and the corresponding filter criteriasare displayed in the table below.

4. To create a new filter , perform the following steps:

4.1 If any filter details appear in the bottom table, click on [ Clear ]. Theexisting filter details are removed.

4.2 Type the new filter name in the “Filter Name“ text field.

4.3 In the second table, select the appropriate attribute from the “Field”

column.

4.4 Select the appropriate relational operators (equals, different, or like).

4.5 Select an attribute from the “Value” list, or type its value in the

displayed textfield. The ’*’ wildcard can be used.

4.7 Click on [ Insert ].The first table in the Filter Criteria panel is updated with the newlycreated filter criteria.

4.8 To add more filter criterias, perform steps 4.3 - 4.7 for each new

filter criteria.

4.9 To update the filter with a new view type and filter criteria, select thefilter criteria, perform the modifications, then click on [ Update ].

4.10 To remove a row in the table, select its anchor number and click

on to [ Remove ].

4.11 Click on [ Save ] to save the filter, then on [ Yes ] at the confirmationquestion.

634 / 664 3BK 21216 AAAA PCZZA Ed.26


5. To make a filter the default one, select it, then check the ’Make this filter asdefault’ checkbox.

6. To update the filter, select it, perform the needed modifications (refer to theappropriate steps 4.3 - 4.10), then click on [ Update ].

The filter criterion is updated in the data warehouse.

7. To delete the filter, select it and click on [ Delete ].

The filter criterion is deleted from the data warehouse.


3BK 21216 AAAA PCZZA Ed.26 635 / 664





636 / 664 3BK 21216 AAAA PCZZA Ed.26

27 User Preferences

27 User Preferences

3BK 21216 AAAA PCZZA Ed.26 637 / 664

27 User Preferences

27.1 PresentationAnalysis Desktop can be configured to suit the individual preferences of eachuser. This allows you to choose for example a preferred layout, or what keysto use for different actions, default directory for export etc. Depending on theuser’s FADs, some user preferences may be activated or not - to view thelist of FADs, refer to section FAD Overview from 9953 MP / NPO PlatformAdministration Guide.

These settings apply only to the user currently logged on Analysis Desktop.They do not affect settings made by any other user when that user is logged.These settings can be changed by regular users, as well as administrator user.

Once these settings are saved, each time the operator re-opens AnalysisDesktop, the chosen preferences are used.

27.2 Configure User PreferencesTo configure user preferences to customize the behavior of Analysis Desktop:

1. In the Alcatel-Lucent Analysis Desktop window, select Edit -> Preferences... .

The ’User Preferences’ window appears.

2. Select and modify the appropriate:

General User Preferences (Section 27.2.1)

Views/Reports User Preferences (Section 27.2.2)

Cartography User Preferences (Section 27.2.3).

To reset the default values, click on [ Default Settings ].

To launch the online help, click on [ Help ].

3. Click on [ OK ].

4. The following message appears, followed by the list of modified userpreferences.Following user preference(s) will take effect onlyafter restarting AD or changing working zone.

Click on [ OK ].

638 / 664 3BK 21216 AAAA PCZZA Ed.26

27 User Preferences

27.2.1 General User Preferences

Preference Name for“General” tab

Description

Prompt to confirm on exit Gives the following confirmation before exiting:Do you want to exit AD?

Possible values: Yes, No.

Add favorite to currentselection

Enables prior selections in favorites selections tree.

Possible values: Yes, No.

Save layout on exit Saves the customized Analysis Desktop layout (windows, position, and size)after exiting the Analysis Desktop.

Possible values: Yes, No, Ask.

Data format Sets date with one of the following formats: dd/mm/yyyy, mm/dd/yyyy, oryyyy/mm/dd.

Default behavior forhyperlinks

Opens the target page in a new window or the same window.

Possible values: New window, Same window.

Mode tabs text Changes the mode for tab text in the Analysis Desktop main window.

Possible values: horizontal, vertical.

3BK 21216 AAAA PCZZA Ed.26 639 / 664

27 User Preferences

Preference Name for“General” tab

Description

Display time before a tab israised and made active

Indicates the time for triggering the auto-raise after the mouse selects a tab.

Possible values: between 1 to 5 seconds.

Show soft-deleted objects If “Yes” is selected, then soft-deleted topology objects are visible in all trees

(with the red cross icon ).

If “No” is selected then the soft-deleted topology objects are not displayedin Analysis Desktop.

Display tips on startup If true, displays "Tip of the Day" window at Analysis Desktop start up.

If false, the window is not displayed.

Font Changes the default font.

Size Changes the default font size.

640 / 664 3BK 21216 AAAA PCZZA Ed.26

27 User Preferences

27.2.2 Views/Reports User Preferences

Preference Name for“Views/Reports” tab

Description

Prompt to save modifiedview template

Asks the user to save the view template.

Prompt to save modifiedreport template

Asks the user to save the report template.

Always set highlight intabular view

Allows the user to keep highlighting in the tabular view.

Allow Dynamic Interpolation Indicates interpolation to be allowed for change while executing or not.

The MUSE_NPO_ALLOW_DYNAMIC_INTERPOLATION FAD must beadded to the user’s profile in order to allow this setting.

Text synthetic output Allows the display of values in text for diagnosis execution

Open results in new vieweron editing

Allows the user to edit the results in a new view window.

Open results in new reporton editing

Allows the user to edit the results in a new report window.

3BK 21216 AAAA PCZZA Ed.26 641 / 664

27 User Preferences


Description

Display Grid in View Allows to display or not the grid.

Automatic Filter ListReactivation

When checked, automatically activates the filter list when a new filter isadded.

Default resize of viewsinside report

Automatically resizes the views inside an executed report.

Highlighting synthesis,legend selecting and legendfiltering

Defines mode of highlighting synthesis, legend selecting and legend filtering.

Possible values: Row, Columns.

Drag & Drop modifier to add Sets a key for the add specific action in the executed views.

Needed to change the modifier keys used for adding elements to an existingview/report using drag and drop.

Possible values: Ctrl, Alt, Shift, Ctrl-Shift, Alt-Shift, Ctrl-Alt.

Drag & Drop modifier toremove

Sets a key for the remove specific action in the executed views.

Needed to change the modifier keys used for removing elements to anexisting view/report using drag and drop.

Possible values: Ctrl-Shift, Alt, Shift, Ctrl, Alt-Shift, Ctrl-Alt.

Its value must be different from the ’Drag & Drop modifier to add’ value.

Preferred Display Type Sets a tabular or graphical view, when not specified in the view template.

Possible values: Tabular, Graphical.

Default graph type Sets the type of the graph.

Possible values: Bar chart, Continuous Line, Stacked column, 100%Stacked column.

No value display Specifies the string to be displayed when no values are present in the table.

Possible values: Empty, N/A

View copy policy whenduplicating a report template

Allows the user to change the view copy policy on a report.

Possible values: Links to Existing View Templates, Duplicated ViewTemplates.

Display operational value Display the operational value when executing the view in tabular mode.

Display reference value Display the reference value of parameter when executing the view in tabularmode.

Display forecast value Display the forecast value of parameter when executing the view in tabularmode.

Display planned value Display the planned value when executing the view in tabular mode.

Display max reference Display the max reference values when executing the view in tabular mode.

642 / 664 3BK 21216 AAAA PCZZA Ed.26

27 User Preferences


Description

Display historical value Display the Historical value of parameter when executing the view in tabularmode.

Display min reference Display the min reference values when executing the view in tabular mode.

Default directory for viewexport

Allows the user to select a directory for export.

The default value is C:\WINNT\Temp

Default directory for reportexport

Allows the user to select a different directory for exporting a report.

The default value is C:\WINNT\Temp

Width of exported graphs(PDF/HTML)

Allows to set the width of exported PDF/HTML in pixels.

The incremental/decremental value change is in multiples of 100 pixels.

3BK 21216 AAAA PCZZA Ed.26 643 / 664

27 User Preferences

27.2.3 Cartography User Preferences

Preference Name for“Cartography” tab

Description

Zoom/unzoom Sets the percentage of zoom or unzoom to be done in the cartography.

Adjacency Color Select the color of the adjacency lines.

NO Selection Color Sets the color of the selected Network Objects.

NO Highlighting Color Sets the color of the highlighted Network Objects.

Highlighting Mode This option is used to keep the old highlighting or to reset the highlighting.

Use First Sets as first value the planned values or the operational value.

Show Standards User can use this option to show or hide the standards in the viewport.

644 / 664 3BK 21216 AAAA PCZZA Ed.26

27 User Preferences

Preference Name for“Cartography” tab

Description

Planned UtimeadvancedFactor

Sets the value of planned U_TIMEADVANCE parameter when definingadjacencies.

For W-CDMA, there is no U_TIMEADVANCE.

Operational UtimeadvancedFactor

Sets the value of operational U_TIMEADVANCE parameter when definingadjacencies.

For W-CDMA, there is no U_TIMEADVANCE.

27.3 Layout User PreferencesThe Analysis Desktop layout can be customized by resizing or changingthe position of the main window, the position of the dividers, or the size andposition of all sub-windows.

From the menu bar, select Window -> Save Layout to save current layoutwith your customized preferences.

To use pre-defined Analysis Desktop window layouts, select as appropriatefrom the menu bar: Window -> Layouts , then:

Default Layout , to keep the Analysis Desktop pre-defined default layout

Maximize Report , to maximize the executed reports browser area

Maximize Trees , to maximize the topology and functions trees area

Maximize View , to maximize the executed views browser area

User-Defined Layout , to display the layout as it was when last saved

by user.

27.4 Save User Preferences ImplicitlyThe values entered by the user in any Analysis Desktop dialog box are implicitlysaved as user preferences.

The next time the same dialog box is opened, the fields are automaticallyfilled in with these pre-saved values.

These parameters are associated with an identifier, which defines a user and/ora profile, so that each user and/or profile can have its own set of preferences.

If the user did not enter any values in a dialog box earlier, then the defaultvalues are displayed.

The list of

The following parameters are also stored as implicit user preferences:

Displayed and hidden modes

Order of modes

Topology classifications

Topology trees

3BK 21216 AAAA PCZZA Ed.26 645 / 664

27 User Preferences

Function classifications

Function trees.

646 / 664 3BK 21216 AAAA PCZZA Ed.26

28 Icons

28 Icons

3BK 21216 AAAA PCZZA Ed.26 647 / 664

28 Icons

28.1 Toolbar Icons

Icon Description Grayed

Report Template Editor If a report template is selected when triggering the toolbar button,then it is displayed in the report template editor, if not, an emptyproperties panel with no values is displayed. Grayed when userdoes not have

View Template Editor Never grayed. If a view template is selected when triggering thetoolbar button, then it is displayed in the view template editor, ifnot, an empty properties panel with no values is displayed.

Object Zone Editor Never grayed. If an object zone is selected when triggering thetoolbar button, then it is displayed in the object zone editor, if not,an empty properties panel with no values is displayed.

Indicator Editor Never grayed. If an indicator is selected when triggering thetoolbar button, then it is displayed in the indicator editor, if not, anempty properties panel with no values is displayed.

THL Template Editor Never grayed. If THL is selected when triggering the toolbarbutton, then it is displayed in the THL template editor, if not, anempty properties panel with no values is displayed.

Diagnosis Editor Never grayed. It launches the diagnosis editor.

Alerter Editor Never grayed. It launches the alerter editor.

Cartography Never grayed. It launches the Cartography module.

Refreshes Tree having thefocus

N/A

Consolidation Follow Up

Alerter List

Alerts List with acknowledgedalerts

Alerts List withunacknowledged alerts

Launches the NotificationWindow

Grayed when no notification messages are pending to beacknowledged

648 / 664 3BK 21216 AAAA PCZZA Ed.26

28 Icons

Icon Description Grayed

Displays the analysis desktopdefault layout.

N/A

Displays the analysis desktopwith executed reports browserarea maximized.

N/A

Displays the analysis desktopwith topology and functionstrees area maximized.

N/A

Displays the analysis desktopwith executed views browserarea maximized.

N/A

Displays the user-definedanalysis desktop layout.

N/A

Display Pending DiagnosisExecuted Reports

Never grayed.

Display Pending ExecutedReports

Never grayed.

Export All Views Grayed when no executed view to export.

Export All Reports Grayed when no executed report to export.

Table 9: Toolbar Icons Description

3BK 21216 AAAA PCZZA Ed.26 649 / 664

28 Icons

28.2 Topology IconsThe following table presents the GSM and W-CDMA List of Object Icon Types:

NetworkObject

Icon1 Icon2 Icon3 Icon4 Icon5 DisplayedString

GSMCell

Supplier:

Alcatel-Lucent

Other

Frequencyband:

PCS

1900

band

DCS1800

band

Multi-band

Unknown

frequencyband

Cell type:

Extended Outer

Mini

Concentric

Extended_Inner

Indoor

Micro concentric

Umbrella

Indoor concentric

Mini concentric

Micro

Umbrella

concentric

Single

Unknown cell

type

User Note

Theicon isdisplayedonly whena usernoteexists.

Deleted

This iconis onlydisplayedwhen theobject isdeleted.

Cell name (Id= [number])

W-CDMACell

Supplier:

Alcatel-Lucent

Other

Cell Class

Rural

Suburban

Urban

DenseUrban

User Note

The icon is displayedonly when a user noteexists.

Deleted



650 / 664 3BK 21216 AAAA PCZZA Ed.26

28 Icons

NetworkObject


GSMExternalCell

Frequencyband:

PCS 1900

band

DCS 1800

band

Multi-band

Unknownfrequency

band

User Note

The icon isdisplayedonly whena user noteexists.

Deleted

This icon is onlydisplayed when theobject is deleted.

If operationalname exists:[Cell Name]/ LAC=xxCI=yy Ifname doesnot exist:/ LAC=xxCI=yy

W-CDMAExternalCell

W-CDMA

User Note


Deleted



GSM_2GEXT

Supplier User Note


Deleted


GSM_2GEXTname

GSM_3GEXT

Supplier User Note


Deleted


GSM_3GEXTname

3BK 21216 AAAA PCZZA Ed.26 651 / 664

28 Icons

NetworkObject


CellZone,TRXZone,2GObjectZone &OtherObjectZones

System ,Customer

public ,Customer

private

Editable

Non

Editable

Not Computed,Computed and empty

, Computed and

not empty

User Note


[Cell Zonename] if thecell zone iscomputedandnon-empty(except forthe Network):[Cell Zonename][number ofcell]

RNC SupplierUser Note


Deleted


[RNC name]

ADJ

Technology

FrequencyMode

Inter-freq

Intra-freq

Inter-system

PLMN Mode

Inter PLMN

Intra PLMN

User Note


Deleted


[Servingcell label] –[Target celllabel]

ADJ2G3G

Technology

FrequencyMode

Inter-freq

Intra-freq

Inter-system

PLMN Mode

Inter PLMN

Intra PLMN

User Note


Deleted


[Servingcell label] –[Target celllabel]

652 / 664 3BK 21216 AAAA PCZZA Ed.26

28 Icons

NetworkObject


Node B SupplierUser Note


Deleted


[Node Bname]

Network SupplierUser Note


Deleted


Network

BB SupplierUser Note


Deleted


BB_<id>

VC SupplierUser Note


Deleted


VC_<id>

PhysLink

SupplierUser Note


Deleted


PhysLink_<ID>

3BK 21216 AAAA PCZZA Ed.26 653 / 664

28 Icons

NetworkObject


VPCI_NB SupplierUser Note


Deleted


VPCI_NB_<ID>

VPCI_CN SupplierUser Note


Deleted


VPCI_CN_<ID>

VPCI_RNCSupplierUser Note


Deleted


VPCI_RNC_<ID>

VP SupplierUser Note


Deleted


VP_<ID>

BTS Supplier User Note


Deleted


BTS name(Id =[number])

654 / 664 3BK 21216 AAAA PCZZA Ed.26

28 Icons

NetworkObject


BTS_BSC_LAPD

Supplier User Note


Deleted


LAPD_<id>

BSC_MFS_LAPD

Supplier User Note


Deleted


BSS name/sub-rack/appliqueposition/port

for Mx MFS:BSS name/logical_GPU/port

wherelogical_GPU=16*(sub-rack-1)+position

BSSSupplier

User Note


Deleted


BSS name(Id =[number])

TRX Zone Type:

Normal

Inner

Outer

User Note


Deleted


[Related Celllabel] #[TRXindex][Preferenceorder]

TRXTS Supplier User Note


Deleted


For SDCCH :[Related Celllabel] #[TRXindex]#S#[Id]

For TCH :[Related Celllabel] #[TRXindex]#T#[Id]

3BK 21216 AAAA PCZZA Ed.26 655 / 664

28 Icons

NetworkObject


TrafficZone

Zone Type:

Normal

Inner

Outer

Generic

Sector Type:

Main

Secondary

Frequency Band:

GSM850-GSM1900

MULTIBAND

GSM850-GSM1800

GSM850

EGSM900

GSM900

GSM1900

GSM1800

EMULTIBAND

User Note


Deleted


[Related Celllabel] ([Zonetype];[SectorType];[FrequencyBand])

X25 Supplier User Note


Deleted


X25_<id>

N7SL Supplier User Note


Deleted


N7LS_<id>

N7LS Supplier User Note


Deleted


N7LS_<id>

656 / 664 3BK 21216 AAAA PCZZA Ed.26

28 Icons

NetworkObject


AIC Supplier User Note


Deleted


AIC_<id>

GPU Supplier User Note


Deleted


BSS name/sub-rack/appliqueposition

for Mx:BSS name/logical_GPU


3BK 21216 AAAA PCZZA Ed.26 657 / 664

28 Icons

NetworkObject


PVC Supplier User Note


Deleted


BSS name/sub-rack/appliqueposition/port/bearer

for Mx MFS:BSS name/logical_GPU/port/bearer


BearerChannel

Supplier User Note


Deleted


BSS name/sub-rack/appliqueposition/port/bearer

for Mx MFS:BSS name/logical_GPU/port/bearer


Table 10: GSM and W-CDMA Network Objects in a Topology Tree

Note: Depending on the status of the “Show Soft-Deleted Objects” user preference,objects that are soft-deleted are either visible or not in all topology trees.Thisuser preference does not affect the Tuning Operations tree rendering (i.e. evenif the user preference asks to hide soft-deleted objects, the new object createdin the Tuning Session remain visible).

658 / 664 3BK 21216 AAAA PCZZA Ed.26

28 Icons

The following table presents the WiMAX List of Object Icon Types:

Network Object Icon1 Icon2

NetworkSupplier

WACSupplier

BSCell (BSID)Supplier

WADJACENCY

WPROCESSOR

WPHYSLNK

WDISKP

AAA_CNXSupplier

AAASupplier

BS

MAC

PHY

MAC_MR

MAC_SC

Table 11: WiMAX Network Objects in a Topology Tree

3BK 21216 AAAA PCZZA Ed.26 659 / 664

28 Icons

28.3 Functions IconsThe following table presents the GSM and W-CDMA List of Functions IconTypes:

Function Icon1 Icon2 Icon3 Icon4 DisplayedString

CounterScalar

Vector

Matrix

Axis

<Countername>(<eferencename>)

Indicator Supplier

Customer

Temporary

Scalar

Vector

Matrix

Axis

WithThreshold

and/orSampling and

associated

diagnosis

WithThreshold

and/orSampling and

no associated

diagnosis

Withoutthreshold

and/orSampling(icon

is blank)

<Indicatorname>(<referencename>)

Design Supplier

GSM

W-CDMA

<DesignParameterDisplayed name>

Logical Supplier

GSM

<LogicalParameterDisplayedName>

660 / 664 3BK 21216 AAAA PCZZA Ed.26

28 Icons


Rule Supplier

Customer

GSM

W-CDMA

Error

Warning

<Rule Name>

Diagnosis Supplier

CustomerPublic

Private

Indicatortrigger

associated to

the diagnosis

Indicatortrigger not

associated to

the diagnosis

<DiagnosisName>

THL Supplier

CustomerPublic

Private

Editable

Non Editable

<THL Name>

3BK 21216 AAAA PCZZA Ed.26 661 / 664

28 Icons


Event Supplier

Customer

Adjacency

changes

Adjacency

Parameter

Changes

BCCH/BSIC

Changes

Cell Capacity

Changes

Cell Type

Changes

Frequency

Changes

Logical

Parameter

Changes

Planned

LogicalParameter

Changes

Release

Changes

Topology

Changes

All

<Event Name>

Tuning Supplier

GSM

W-CDMA

<TuningParameterDisplayedName> or<TuningOperationDisplayedName>

Free Field <Free Fieldname>

662 / 664 3BK 21216 AAAA PCZZA Ed.26

28 Icons


ViewTemplate Public

Private

Editable

Non Editable

Scalar

Vector

Matrix

Equipment

Top N

AssociatedFiltering indicator

<View templatename>

ReportTemplate Public

Private

Editable

Non Editable

Mono-Object

Evolution

Multi-Object

Evolution

Multi-ObjectComparison

Mono-ObjectDistribution

Warning -

Worst

Warning -

Best

Top N

Top NAbsolute

Variation

Top N Relative

Variation

Red Only

Red & Orange

Red, Orange

& Yellow

Orange Only

Orange &

Yellow

Yellow Only

Green, Yellow

& Orange

Green &

Yellow

Green Only

Absolute

Variation

Relative

Variation

<Report templatename>

Table 12: Functions Icons

3BK 21216 AAAA PCZZA Ed.26 663 / 664

28 Icons

BLANK PAGE BREAK

664 / 664 3BK 21216 AAAA PCZZA Ed.26

NPO Manual

Documents

Transcript of NPO Manual