ADVANTAGE User Reference Guide PDF

ADVANTAGE
User Reference Guide
Software Version 7.0

Reference Guide Edition 1
© Copyright 2010 AIRCOM International
All rights reserved
ADVANTAGE, ARRAYWIZARD, ASSET, CONNECT, DATASAFE, DIRECT,
ENTERPRISE, MYRIAD, AIRCOM OPTIMA, RANOPT and WEBWIZARD are
recognised trademarks of AIRCOM International. Other product names are
trademarks of their respective companies.
Microsoft Excel , .NET™, Microsoft Office, Outlook , Visual Basic Windows®,
Windows XP™, Windows Vista and Word are trademarks of the Microsoft
Corporation.
This documentation is protected by copyright and contains proprietary and
confidential information. No part of the contents of this documentation may be
disclosed, used or reproduced in any form, or by any means, without the prior
written consent of AIRCOM International.
Although AIRCOM International has collated this documentation to reflect the
features and capabilities supported in the software products, the company makes no
warranty or representation, either expressed or implied, about this documentation, its
quality or fitness for particular customer purpose. Users are solely responsible for the
proper use of ENTERPRISE software and the application of the results obtained.
An electronic version of this document exists.
This User Reference Guide finalised on 16 September 2010.
Refer to the Online Help for more information.
This User Reference Guide prepared by:
AIRCOM International Ltd
Cassini Court
Randalls Research Park
Randalls Way
Leatherhead
Surrey
KT22 7TW
Telephone: +44 (0) 1932 442000
Support Hotline: +44 (0) 1932 442345
Fax: +44 (0) 1932 442005
Web: www.aircominternational.com
About This Manual
Change History
This table shows the change history (if any) of this guide:
Edition Date Reason
1 16 September 2010 Commercial Release
Explanation of Symbols
Throughout this guide, where appropriate, some symbols are used to highlight
particular pieces of text. Three different symbols are in use, and are explained as
follows:
Symbol Brief Description Full Description
Note Signifies text that should be noted or carefully considered.
Tip Signifies text that may help you do something in an easier or quicker
way.
Warning or Important Signifies text that is intended as a warning or something important.
Contents
Chapter 1 Introduction 11
About ADVANTAGE 12
About the ADVANTAGE Operational Environment 13
About the ADVANTAGE Optimisation Framework 14
What are the Benefits of Using ADVANTAGE? 15
Obtaining User Assistance 15
Who is This User Reference Guide For? 16
About the ENTERPRISE User Reference Guides 17
Can You Improve Our User Assistance? 18
Obtaining Support 18
Obtaining Further Information and Services 20
Chapter 2 Overview of ADVANTAGE 21

About the Main Features of ADVANTAGE 21
About Network Optimisation 22
About Network Analysis 23
About Measurement Data 24
About the ADVANTAGE User Interface 25
About the File Menu 25
About the Configuration Menu 26
About the Arrays Menu 27
About the Tools Menu 28
About the Reports Menu 28
About the Optimiser Menu 29
The ADVANTAGE Process Flow 30
About the Optimiser Workflow 32
Recommendations and Guidelines 34
Automatically Generating Sites 35
Chapter 3 Setting Action-Constraints in ADVANTAGE 37

About Action-Constraints 38
Action-Constraints Exclusive to the Site Database 39
About the Action-Constraints Available 39
Configuring Property Grid Constraints 40
Configuring Property Antenna Constraints 42
Configuring Equipment Constraints 44
Configuring GSM Site Installation Constraints 46
Configuring GSM Site Grid Constraints 46
Configuring GSM Cell Antenna Constraints 48
Configuring GSM Subcell Power Constraints 49
Configuring UMTS, CDMA/EV-DO, WiMAX or LTE Grid Constraints 50
Configuring UMTS, CDMA/EV-DO, WiMAX or LTE Antenna Constraints 52
ADVANTAGE 7.0 User Reference Guide Page 7

Contents
Configuring UMTS Node Resource Constraints 53
Configuring UMTS Cell Power Constraints 54
Configuring UMTS Cell Power Control Constraints 54
Configuring WiMAX Cell Power Constraints 55
Configuring LTE Cell Power Constraints 55
Configuring Constraints in the Site Database Global Editor 55
Chapter 4 Setting Up Thresholds, Targets and Parameters 59

Setting RF Array Thresholds 60
Specifying RF Array Thresholds for Clutter 60
Specifying RF Array Thresholds for Vectors 64
Setting RF Metric Targets 67
About the Targets for Array-based Metrics 67
About the Targets for Service-based Metrics 70
Specifying Costs/Limits 74
Setting Maximum Limits for Objects or Actions 75
Defining Combinations of Actions 76
Defining Costs for Objects and Actions 77
Specifying a Maximum Cost 81
Setting the Strategy 82
Selecting the Metrics and Weights 82
Rejecting Plans Based on Metric Degradation 84
Defining the Metrics Synthesis 86
Setting Traffic Options 88
Selecting the Terminal Types 88
Loading Cached Traffic Arrays 89
Specifying the Settings 90
Configuring General Options and Settings 90
Configuring Array Settings 93
Configuring the Settings for Auto Plan Setup 98
Specifying a Field to Differentiate New/Existing Elements 100
Globally Committing All Your Changes 103
Selecting Report Formats 104
Chapter 5 Using and Managing Plans 107

About the Concept of Plans in ADVANTAGE 108
Viewing and Using Plans in the Plan Manager 109
Creating Plans for Optimisation or Analysis 110
Using the Plan Setup Method to Create a Plan 111
Creating a Quick Plan from a Map View 114
Using the Auto Plan Setup Method to Create a Plan 115
Differentiating New/Existing Elements 118
Using the Context Menu 119
Viewing Plans in the Map View Window 121
About Plan Viewing Options 122
About the Sampling Option 123
About the Action-Constraints Dialog Box 124
About the Fixed Columns for the Action-Constraints 126
Using the Action-Constraints Dialog Box 127
Page 8 ADVANTAGE 7.0 User Reference Guide

Contents
About the Viewing Options for Action-Constraints 128
About the Methods of Editing the Action-Constraints 129
About the Action-Constraints on the Antenna Tab 131
About the Action-Constraints on the Power Tab 132
About the Action-Constraints on the Grid Tab 132
About Action-Constraints Templates 134
Creating and Editing Action-Constraints Templates 135
Configuring Action-Constraints Templates for Antenna Planning 136
Configuring Action-Constraints Templates for Power Planning 139
Configuring Action-Constraints Templates for Grid Planning 144
Assigning Action-Constraints Templates to Objects 147
Modifying Templates after Assigning them to Objects 149
Applying a Plan to the Database 150
Applying a Plan Temporarily to the Database 151
Key Differences between Temp Apply and Apply to Database 152
Deleting a Plan 153
Chapter 6 Optimising a Network 155

Prerequisites for an Optimisation 156
Running an Optimisation 157
Monitoring an Optimisation 158
About the Cost Graph 159
About the Statistics Graph(s) 160
About the Cost Details 161
About the Statistics Details 162
About the Optimisation Reports 162
Alternative Optimisation Scenarios 164
Applying a Plan to the Database 164
Chapter 7 Analysing and Evaluating Plans 165

Information Generated by the Analysis 166
Prerequisites for Running an Analysis 167
Performing an Analysis for a Single Plan 168
Performing an Analysis to Compare Plans 170
Displaying Plan Comparison Results in the Map View 171
About Rollout Planning and Partial Plans 173
Using the Rollout Planning Dialog Box 175
Creating a Partial Plan 177

Contents
Chapter 8 Identifying Problems in a Network 179
About Problematic Areas and Cells 180
Configuring Problem Area Thresholds 181
Configuring Problem Cell Thresholds 183
Identifying Problem Areas and Cells 185
About the Information Shown in a Problem Area Report 186
About the Information Shown in a Problem Cell Report 189
Configuring Problem Cell Weights 190
Chapter 9 Using Measurement Data 193

About Intelligent Spreading of Network Data 194
How ADVANTAGE Spreads Traffic Data 196
About the Spreading Mechanisms in ADVANTAGE 197
Configuring the Format for Importing Network Data 199
About Spreading Network Data 201
Spreading Network Data 202
Displaying Spread Data on the Map View 204
Displaying Spread Data in the Data Values Pixel Analyser 205
Re-Spreading Network Data 206
About Cached Traffic Arrays 207
Performing Network Data Array Operations 207
Scaling Network Data Arrays 207
Combining Network Data Arrays 208
Managing Network Data Arrays 208
Using Measurement Data for Analysis and Tuning 209
Using Measurement-Based Pathloss Files 210
Appendix Technical Reference 213

About the Optimisation-Based Spreading Algorithms 213
About the Network Optimisation Domain 214
About the Network Optimisation Cost Function 214
About Efficient Network Optimisation 216
About the Voronoi Diagrams 217
About Optimisation Problem Definitions 218
About Adaptive Simulated Annealing 219
Index 221

Contents
CHAPTER 1
Introduction
ADVANTAGE is an automatic network planning and optimisation tool. It provides
an advanced, integrated framework that is composed of:
Automatic cell planning and optimisation
Consideration of design issues and constraints
Network analysis and evaluation
Problem identification
Network modelling and fine tuning
ADVANTAGE is part of AIRCOM International's ENTERPRISE suite. ENTERPRISE
is the fully integrated, PC-based, network engineering solution for network operators,
cellular equipment manufacturers and system integrators.
The technologies explicitly supported by ADVANTAGE are:
GSM
UMTS FDD
Fixed WiMAX
Mobile WiMAX
CDMA2000
EV-DO
LTE
Occasionally in this guide, for simplicity, the term WiMAX is used to represent
Fixed or Mobile WiMAX, and the term CDMA/EV-DO is used to represent
CDMA2000 or EV-DO.
To optimise any of these networks, you need to have the appropriate licence.
If required, multiple technologies can be used within the same project.

Introduction
About ADVANTAGE
ADVANTAGE is an automatic planning/optimisation platform that:
Enables the automatic optimisation of:
 The number of sites required to meet the coverage and service objectives
during regional network rollout
 The physical network configuration to maximise capacity for the desired range
of services and traffic demands
 Various design parameter settings (antenna, power, site
location/configuration) to meet the network performance objectives
 ARFCN allocation and associated parameters, including baseband and RF
hopping
Provides a more efficient and economic solution to network planning and
optimisation than the manual 'trial and error' approach that usually involves
significant drive testing and re-rigging activity
Offers high level of integration between interacting optimisation mechanisms
Utilises a wide range of survey measurement and network statistics data to tune
the modelled network and facilitate area performance optimisation
Improves the efficiency of the cyclical process of ongoing planning and
optimisation, and frees up time for planning/optimisation engineers to focus on
other tasks
Supports ‘real-world’ performance targets and network configuration constraints
Facilitates the joint consideration of a wide range of data (such as pathloss
predictions, OSS performance statistics and drive test measurements) to make the
modelled network as realistic as possible
Supports multi-technology network planning and optimisation
Uses a series of intelligent analysis algorithms to identify and alleviate areas/cells
of poor performance
Integrates efficiently with planning and optimisation tools to avoid data
integration and interfacing issues
Benefits from the ENTERPRISE graphical interface and database architecture
There is a Technical Reference appendix at the back of the ADVANTAGE User

Reference Guide.

Introduction
About the ADVANTAGE Operational Environment
ADVANTAGE is designed to interact seamlessly with the other products of the
ENTERPRISE tool suite, so that you can make full use of the ENTERPRISE modelling
and analysis functionality, and apply the identified optimisation solutions into the
planning and operational network environment.
ADVANTAGE is:
Based on the same user interface as the rest of the ENTERPRISE products
Built to operate on top of the ENTERPRISE planning database, which uses a
robust Oracle platform to achieve both speed and data consistency
Alternatively, you can use ADVANTAGE in a standalone capacity, based on a series
of interfaces through which information can be exchanged between ADVANTAGE
and any third party or operator tools.
This picture shows the optimisation life cycle using ADVANTAGE:
The optimisation life cycle using ADVANTAGE

Introduction
About the ADVANTAGE Optimisation Framework
The ADVANTAGE framework enables you to optimise an extensive range of physical
design and network parameter settings, according to your specific requirements.
The optimisation process offers:
A choice of three planning mechanisms:
 Antenna
 Power
 Grid
A choice of two cost mechanisms, each with its own set of metrics:
 Array-based
 Service-based
For more information on these two sets of mechanisms, see About Network
Optimisation on page 22.
The changes considered in the optimisation can be evaluated in terms of various
metric categories:
Metric Category Represents
Budget The monetary cost of a network plan.
Financial The financial value of the network plan, such as revenue or net income.
(Licence-dependent.)
RF The network plan performance in terms of the targets specified by the user.
An overall optimisation cost value can be generated from all these components, based
on scenario-specific relative degrees of importance.
In summary, the optimisation depends on:
A series of actions that can be considered in order to improve a network, including
the monetary cost associated with each of these actions.
A set of constraints that restrict which/how specific network parameters can be
altered during optimisation.
A set of radio parameters and targets that characterise the expected performance
for the metrics that can be affected by the optimisation.
A set of financial parameters and associated targets that characterise the financial
value of a plan and can be affected by the optimisation.
(This is licence-dependent. For more information see the Financial Analysis User
Reference Guide.)
An analysis engine that estimates the cost values for the metrics used in the
optimisation every time a network plan is evaluated.
A sophisticated, proprietary algorithm that can identify the best solution in an
efficient manner.

Introduction
What are the Benefits of Using ADVANTAGE?
A large number of customer and trial optimisation scenarios have confirmed that
ADVANTAGE can enhance the efficiency of the network planning/optimisation
process, and thus provide significant commercial benefits:
Reduce CAPEX (Capital Expenditure), by decreasing the site count required to
achieve the prescribed performance levels during the nominal planning phase.
Reduce OPEX (Operational Expenditure), by enabling engineers to focus on other
tasks while it produces the best network plans, and by ultimately minimising the
need for drive testing or antenna re-rigging.
Increase traffic revenue, by leading to significant capacity gains, even in mature 2g
networks where it has been possible to improve the Quality of Service and
maximise the generated revenue from the same or higher bit rate services.
Obtaining User Assistance

Using Online Help
ENTERPRISE products come with a complete system of online Help which you can
access in three ways:
From the Help menu, click Help Contents. Scroll through the table of contents and
choose a relevant topic to display.
To search for something particular, from the Help menu, click Help Contents and
using the Index tab or Search tab, type in a letter or word to start searching for
relevant topics.
Press F1 in a dialog box to view context-sensitive help (available for most dialog
boxes).
If you are using ENTERPRISE within a CITRIX environment, to ensure that the
Help graphics are displayed, set your display settings to support more than 256
colours.

Introduction
Using ENTERPRISE User Reference Guides
If you prefer to read printed content, we also provide User Reference Guides. To view
or print these as PDFs (Adobe Acrobat portable document format):
1 Make sure you have Adobe Acrobat Reader installed on your PC. If you do not
have this, you can install it from the ENTERPRISE CD, or get it from the Adobe
website.
Adobe and Acrobat are trademarks of Adobe Systems, Incorporated.

2 Click Start on the taskbar, point to Programs, then AIRCOM International, then
ENTERPRISE, then Docs.
- or -
Navigate to the Docs folder in the location where you installed the product.
If neither of these exists, please contact your administrator.

3 Double-click the PDF file that you want to view.
If you have a customer web account, you can also download the latest User
Reference Guides from our website.
Checking Release Notes

Each release of the ENTERPRISE software is accompanied by Release Notes, giving
important information on system requirements, installation, known issues, upgrades
and so on. You can download these notes from our website.
For any further documentation, such as application notes and extra reference
information, please email the support team at the address described in Obtaining
Support on page 18.
Who is This User Reference Guide For?

The ENTERPRISE User Reference Guides are intended for different audiences,
depending on the particular product. Typical prerequisites include a good
understanding of the following:
The appropriate telecoms technologies and the associated network planning
methods (for planning software)
Relational database management, and in particular Oracle database creation and
administration procedures (for administrative software)
The various parameters utilised for monitoring and optimising networks (for OSS
software)
Irrespective of the particular product, the following basic knowledge is required:
Microsoft Windows concepts
The functions of the Microsoft Office suite of tools, in particular Excel

Introduction
About the ENTERPRISE User Reference Guides
This table describes our range of User Reference Guides:
This Guide Contains Information On
What's New The main difference between the latest versions of the ENTERPRISE
suite.
ENTERPRISE Installation and Administration Installing and configuring ENTERPRISE, your network, and Oracle
databases. Using Administrator to create users and groups, and set
permissions.
Also contains information on software licensing.
ENTERPRISE Database Reference The relationships between tables in the database and the contents of each
table.
ENTERPRISE User Reference Functionality that is common to most of the products in the ENTERPRISE
suite, including how to access, view, edit and store data.
ENTERPRISE Technical Reference File formats, as well as antenna and diffraction calculations.
ADVANTAGE User Reference Using ADVANTAGE to plan and optimise networks automatically, consider
measured data in analysis/optimisation, analyse network performance,
identify problematic areas/cells, and related tasks.
ARRAYWIZARD User Reference Using ARRAYWIZARD to automatically generate pathloss predictions and
best server arrays, which gives you instantaneous display of coverage and
interference information for pre-selected filters when loaded into ASSET.
ASSET User Reference Using ASSET, the network planning and analysis tool, to design a range of
cellular networks.
Includes information on hierarchical network planning, propagation
modelling, service and bearer definition, coverage analysis, traffic planning,
neighbour planning, measurement data analysis, detailed reporting,
analysis arrays and simulation of network performance.
ASSET Technical Reference Array descriptions and information on some of the algorithms used in
ASSET.
ADVANTAGE User Reference Guide Using ADVANTAGE to plan and optimise networks automatically, designed
as an aid for day-to-day planning.
(Optional add-on to ASSET.)
CONNECT User Reference Using CONNECT, the network transmission and microwave link planning
software for full network physical link design and logical link design.
Also contains CONNECT-specific reference information.
DATASAFE User Reference Using DATASAFE, our network configuration tool to implement both small
and large scale changes to networks
DIRECT User Reference Using DIRECT to design telecommunications networks of different network
layers. Explains how to plan cellular, PSTN and data networks at a both
general and strategic level.
Also contains DIRECT-specific reference information.
Financial Analysis User Reference Guide Using the Financial Analysis module to evaluate and plan for the revenue
potential of your network.
(Optional add-on to ASSET and ADVANTAGE.)
ILSA User Reference Guide Using ILSA, ASSET's automatic 2g frequency planning tool.
AIRCOM OPTIMA User Reference Using AIRCOM OPTIMA to view performance data and statistics both with
ENTERPRISE and standalone.
RANOPT User Reference Using RANOPT to efficiently find faults in your network, optimise and
validate its performance prior to commercial launch.

Introduction
This Guide Contains Information On
WEBWIZARD User Reference Using WEBWIZARD to display GIS and report information of network data,
including creating layers, regions, nodes, layer types, administering and
configuring the system and using the GIS view, explorer and report
viewers.
Can You Improve Our User Assistance?

We are always trying to improve the online Help and User Reference Guides.
If you cannot find the Help you were looking for, need more information, or have any
suggestions for improvements, we would be grateful for your feedback.
Also, if you are generally satisfied with these resources, we would appreciate any
positive feedback.
Online Questionnaire
You can help us by completing our brief online questionnaire
(http://www.surveymonkey.com/s.aspx?sm=RIRKLcrdvaCzRnUBNx5tcQ_3d_3d).
Alternatively, you can contact us directly at docs@aircominternational.com.
Obtaining Support
If you have a difficulty you cannot resolve yourself using the online Help or
Reference Guides, or you have found a possible fault in the software, you can log a
support request. You may also wish to contact us if you want to:
Register for a customer web account to access the Support area
Obtain further documentation, such as application notes and extra reference
information
Logging Support Requests Online

To log a support request online:
1 Go to the AIRCOM website, at www.aircominternational.com.
2 Click the link for Product Support Login.
3 Log in, using your customer web account username and password.
4 In the Technical Support pane, click Online Helpdesk.
5 Click Log New UTS Call.
6 Type the details of your request, and then click Submit.

Introduction
Contacting us via Telephone or Email
If you wish to contact us directly, here are the contact details of our regional offices:
Location Regional Office Contact Details
Europe United Kingdom Tel : +44 1932 442000

Fax :+44 1932 442005
support@aircominternational.com
Belgium support@aircominternational.be
France support@aircominternational.fr
Germany support@aircominternational.de
Italy support@aircominternational.it
Sweden support@aircominternational.se
Middle East, Africa and Central Asia United Arab Emirates Tel : +971 4 391 2642
Fax :+971 4 391 8141
support@aircominternational.ae
South Africa Tel : +27 11 745 1475
Fax : +27 11 465 1517
support@aircominternational.com
Americas Mexico support@aircominternational.com.mx
USA Tel : +1 214 576 2700
Fax : +1 214 576 2794
support@aircominternational.us
Brazil support@aircominternational.com.br
Asia and Oceania Singapore Tel: +65 6372 0548
Fax: +65 6372 0350
supportsg@aircominternational.com
China Tel: +86 2162792779
Fax: +86 2162792855
supportsg@aircominternational.com
India Tel: +91 124 4848200
Fax: +91 124 4517878
supportindia@aircominternational.com
When contacting us with a support query, it would help us if you:

Give us as much information as possible about the problem and the context in
which it occurred
State the version and build you are using
Have all the details of your query to hand
Are logged into the ENTERPRISE application
Can send extracts of your data sets if we need them to reproduce your problem

Introduction
Obtaining Further Information and Services
As well as comprehensive online Help and User Reference Guides and dedicated
Product Support, AIRCOM provides:
Online Knowledgebase of Articles

If you register for a customer web account, you can view our searchable technical
database in the Product Support section of the AIRCOM website. This
Knowledgebase contains articles created by our support professionals who have
resolved issues for our customers, and is constantly updated, expanded, and refined
to ensure that you have access to the very latest information and frequently asked
questions.
Power Tools
If you register for a customer web account, you can download from a selection of
useful power tools, such as file conversion utilities.
Latest Copies of the User Reference Guides

If you register for a customer web account, you can download the latest User
Reference Guides (PDFs) from our website. If you do this, please check the back of the
reference guides for any additions or corrections.
Consultancy Services
AIRCOM also provide full radio consultancy services in Network Audits, Business
Planning Support, Licence Applications, Radio Network Planning,
Telecommunications Research and System Modelling and Propagation Analysis and
Modelling.
Training
There is a wide variety of courses run by AIRCOM. These courses range from tool
training to technology training. For details, contact Competence Development
Solutions (training@aircominternational.com).

Introduction
CHAPTER 2
Overview of ADVANTAGE
Before you begin to use ADVANTAGE, you should ensure you understand the basic
concepts described in this section.
You must have the appropriate user permissions (these are specified in
ENTERPRISE Administrator) in order to use ADVANTAGE-specific functionality or
to change ADVANTAGE settings. For more information, see the Installation and
Administration User Reference Guide.
About the Main Features of ADVANTAGE

The main features of ADVANTAGE are:
Network Optimisation - you can optimise a network automatically
Network Analysis - you can evaluate any number of network plans
Measurement Data Usage - you can use area and/or cell-specific (measured or
experimental) data
The ADVANTAGE User Reference Guide describes all the steps and processes in
the tool. However, some of these steps, in particular the ones related to the radio
environment setup, will not be relevant to the general user, provided the
administrator (or super-user) has already completed them. This is also true for
optimisation scenarios that have been set up by one user that can be shared with other
users who access the same project.
You should always make sure that the ENTERPRISE project setup is up-to-date and
complete before proceeding. For more information, see the ENTERPRISE and ASSET
User Reference Guides.

About Network Optimisation
The principal feature of ADVANTAGE is the automatic Optimiser, which can
consider an extensive range of physical design and network parameter settings that
affect the performance of the radio network. It can also consider real-world financial
inputs.
Planning Mechanisms
You can set up and start the automatic optimisation of a network configuration
according to various targets, costs, actions and constraints, using any or all of the
following planning mechanisms:
Antenna
Power
Grid
For example, you might want to run an optimisation that considers the following
network changes:
Antenna azimuth changes, or electrical tilt changes
- and/or -
Changes in maximum transmit power
- and/or -
Site location, site selection or site configuration
For more information on using these planning mechanisms, see About Action-
Constraints on page 38 and Using the Action-Constraints Dialog Box on page 127.
Cost Mechanisms
The optimisation process offers a choice of two cost mechanisms with which to guide
the optimisation:
Array-based
Service-based
Each cost mechanism has its own set of metrics.
The Array-based mechanism relies on pixel-based values calculated during array
generation. The arrays can be related to signal strength, signal quality or dominance,
as appropriate. For example, in order to maximise the signal coverage/quality in your
network, you might run an array-based optimisation that uses one or more of the
planning mechanisms.
The Service-based mechanism relies on averaged values for successful connections
based on a series of simulation snapshots, and therefore requires one or more traffic
rasters. For example, in order to maximise the mean number of served users in your
network, you might run a service-based optimisation that uses one or more of the
planning mechanisms.

For more information on setting up these cost mechanisms, see Setting RF Metric
Targets on page 67.
About Network Analysis

There are several ways of performing network analysis in ADVANTAGE. In
summary, you can:
Analyse your network plan against your chosen optimisation strategy
Identify problem areas and cells
Use the ASSET analysis functionality
Analysis
The analysis functionality in ADVANTAGE enables you to analyse your network
plan against your chosen optimisation strategy, including the metrics and targets that
you have specified.
More specifically, it enables you to:
Analyse and evaluate a current plan configuration or an optimised delta plan
configuration
Compare any two plan configurations, whether current or optimised
Access the Ranking functionality, in order to assess and sequence the potential
network changes
You can evaluate a single plan, or compare two plans, in terms of their performance.
The performance achieved for each configuration is compared with the user-specified
performance targets and presented (in terms of absolute and/or relative values) on a
traffic and area basis. Depending on your licences, the performance can be based on
RF thresholds, and/or on financial or budgetary considerations.
The Analysis report generated can include:
Actions
Statistics
Costs
Financial Metrics (if licensed)
You can use the produced reports and/or graphical information to determine how
good a plan is, or the number/cost of the required optimisation actions.
Within the Analysis functionality, you can perform ranking on the potential network
changes, and create partial plans.
For more information, see Analysing and Evaluating Plans on page 165.

Problem Area and Problem Cell Identification
ADVANTAGE also enables you to quickly identify the areas and cells of poor
performance, based on user-specified targets. You can use the produced reports
and/or graphical information to determine which areas or cells should be optimised.
You can also use problem cell weighting to prioritise actions (changes) to cells that
have shown poor performance, based on the analysis output and/or network
measurements.
For more information, see Identifying Problems in a Network on page 179.
ASSET Analysis (Arrays and Reports) Functionality

For more information about this, see the ASSET User Reference Guides.
About Measurement Data

There are two aspects to the use of measurement data in ADVANTAGE. You can:
Import and spread network data, for example performance engineering data or
traffic data. This cell-specific information is imported into ADVANTAGE and
spread intelligently in the area of interest. The created arrays can describe the
network performance and may highlight problematic areas/cells. They can also be
used directly (in the case of traffic arrays) or indirectly in the analysis or
optimisation.
ADVANTAGE also enables you to use the standard ENTERPRISE traffic
functionality to create/load/modify a traffic array, using either live traffic or
specified traffic.
Load and use area-specific and/or cell-specific data (for example, drive test
measurements) to check the network modelling/performance; tune a propagation
model; generate measurement-based pathloss files in order to influence the
pathloss predictions (and predicted network performance); run a focused analysis
or optimisation (based, for example, on drive test routes).
For more information, see Using Measurement Data on page 193.

About the ADVANTAGE User Interface
As part of the ENTERPRISE Suite, ADVANTAGE not only benefits from the common
Site Database and Map View windows, but also adds specialised functionality for the
purpose of automatic network planning and optimisation.
This section briefly describes some of the user interface features that ADVANTAGE
shares with or adds to the core ENTERPRISE user interface.
There is one menu which is exclusive to ADVANTAGE:
Optimiser
The common menus are:
File*, View, Database, Equipment, Configuration, Arrays*, Tools*, Reports,
Windows, Help
(The items marked "*" also contain ADVANTAGE-specific features)
For more information about the common user interface, see either the ENTERPRISE
User Reference Guide, or the ASSET User Reference Guide.
About the File Menu

ENTERPRISE enables you to import XML files into a project or export XML files from
a project. You can do this using the File menu, which gives access to the XML Import
and Export dialog boxes.
When you have ADVANTAGE installed, these dialog boxes contain an additional tab,
enabling you to import or export ADVANTAGE-specific plans, targets, parameters,
costs and thresholds.
This picture shows an example:
Example of XML Export Dialog Box

For more information on importing and exporting XML data, see the ENTERPRISE
User Reference Guide.
About the Configuration Menu

The following table briefly describes the options available on the Configuration menu,
which ADVANTAGE shares with ASSET:
This Menu Item Enables You To
Propagation Models Define propagation models.
Propagation models are mathematical attempts to model the real radio environment as
closely as possible.
Terminal Types Specify the different terminal types and properties needed for subscribers of your
network.
Assign the terminal types to different network layers or to multiple layers, and describe
their geographical distribution in relation to the mapping data.
Carriers: Define carriers.
GSM, UMTS, WiMAX, CDMA/EV- Most radio network systems divide up spectrum into pairs for uplink and downlink
DO, LTE communication. Rather than refer to the two absolute frequencies in terms of MHz, it is
Frequency Bands (GSM) convenient to refer to a carrier number, which abstracts the absolute frequency from the
description of the carriers.
Layers: Define GSM carrier layers, which are sub-sets of the total list of carriers, grouped
Carrier Layers (GSM) together under a common name.
Cell Layers (GSM) Define GSM cell layers, which are logical groups of transceivers on a cell. By using cell
layers, you can distinguish between micro cells and macro cells or between carriers of
different frequency bands.
Bearers Define bearers that transport voice and data between cells and terminal types.
Services Define services, and then allocate the services to terminal types, to account for the
different services offered to the subscriber.
For example, services might have different data rates and other requirements such as
quality of service.
Clutter Parameters Set up clutter parameters, such as different shadow fading standard deviations and
indoor losses for each clutter type. These fades and losses are considered when you run
a simulation of network performance. For some technologies, you can set additional
clutter-specific adjustments that influence, for example, AAS Support.
For more information on any of these menu items, see the ASSET User Reference
Guide.

About the Arrays Menu
The following table briefly describes the options on the Arrays menu:
Array Manager View any non-ADVANTAGE-specific array information currently in memory, as well as
load, delete and save arrays.
Traffic: Create traffic arrays.
Traffic Array Wizard
Traffic: Scale traffic arrays (projected to increase in system load over time).
Scale Traffic
Traffic: Create traffic arrays using imported live traffic.
Load Live Traffic
Network Data: Import and spread live network data onto the region associated with the selected Plan. For
Data Array Wizard example, you can create an ADVANTAGE traffic array.
Network Data: View detailed information about the data you have spread, as values per pixel, depending
Data Pixel Analyser on the chosen area and network, the data spread and the resolution selected for
spreading.
Network Data: Scale, combine and manage data arrays.
Data Array Operations
Network Data: Spread data based on the originally spread data and an optimised network configuration.
Re-Spread Data
Coverage/Interference Create GSM coverage/interference arrays.
Signal Coverage wizards Create signal coverage arrays for the appropriate technology.
Compound Array Generator Define, generate, and analyse customised compound arrays based on the existing
available arrays.
Array Settings Define the parameters for all arrays and prediction creation/loading.
For more information on the four items listed under Network Data, see Using
Measurement Data on page 193.
For more information on the other items, see the ASSET User Reference Guide.

About the Tools Menu
This table briefly describes the ADVANTAGE-specific options on the Tools menu:
Measurements Import drive test measurements, perform propagation model analysis,
auto-tune the model parameters and create measurement-based pathloss
files (based on the imported data).
This table briefly describes the ADVANTAGE-specific options on the Problem

Identification sub-menu of the Tools menu:
Problem Area Thresholds Configure technology-specific thresholds for problematic areas. These
define the minimum clutter-specific values that are acceptable for the
purpose of the analysis.
Problem Cell Thresholds Configure technology-specific thresholds for problematic cells.
You can configure problem cell thresholds to define the criteria used to
classify problem cells in your network. When you later identify problem
cells, any cells that do not meet these thresholds will be classified as
problematic.
Problem Area and Cell Identification Identify area problems (such as low coverage, low quality) and/or cell
problems (such as large number of dropped calls, large number of
handovers).
Assign problem cell weights, in order to prioritise actions (changes) to
cells that have shown poor performance.
The options vary according to the technology that you are using.
About the Reports Menu

The following table describes the reporting options that ADVANTAGE shares with
ASSET:
Site/Node report Generate a report that includes any selected contents of the Site Database, based on any
filter.
GSM Cell Information report Generate a report containing all cells which use a certain carrier, or range of carriers,
according to the criteria.
ACP & Financial Analysis Reports Determine which report format you want to use for the associated report type. For more
Assignment information, see Selecting Report Formats on page 104.

About the Optimiser Menu
The following table briefly describes the two options on the Optimiser menu:
Optimiser Workflow
ADVANTAGE Wastebasket

Workflow The Optimiser Workflow enables you to perform the vast majority of tasks
within ADVANTAGE from a single dialog box. This incorporates the setting
up of parameters, costs, constraints and targets, and generation of
optimisation plans.
You can also use the button on the
toolbar. It comprises a number of main options:
Plan Manager
RF Array Thresholds
RF Metric Targets
Costs/Limits
Strategy
Traffic
Settings
Financial Analysis (licence-dependent)
For more information, see About the Optimiser Workflow on page 32.
ADVANTAGE Wastebasket Delete ADVANTAGE-specific items from the database.
You cannot create a new item with the same name as an item in the
ADVANTAGE Wastebasket, even if the items were placed in the
You can also use the button on the Wastebasket by another user. Therefore, to keep these problems to a
toolbar. minimum you may want to delete an item permanently.
Do not remove anything from the ADVANTAGE Wastebasket that

another user might need as these items cannot be recovered.

The ADVANTAGE Process Flow
This section outlines the complete ADVANTAGE process flow, which should be
helpful if you are using the tool for the first time. Note that parts of this process may
not be relevant to the general user, depending on user permissions. This is especially
the case if another user (for example, the administrator) has already specified and
committed the setup.
The Optimiser Workflow dialog box (the main user interface in ADVANTAGE)
has been specially designed to help you use the tool.
This diagram summarises the ADVANTAGE process:
The ADVANTAGE process flow
Setup
During this phase, you need to follow these steps (where applicable):
Import/use planning environment data.
Choose which status field you want to use to differentiate between new network
elements and existing network elements, if applicable.
Define the traffic-related configuration parameters (such as terminal types,
services), if applicable.
Create a new plan or plans for optimisation.
Specify the vectors, drive test routes, terminal types, if applicable.
Define the RF Array Thresholds for Clutter and/or Vectors.
Configure the Action-Constraints for the optimisation.
Specify the RF Metric Targets.
Define the Strategy for the optimisation, which includes the selection of which
Metrics are to be used.
Define the Settings, that is, key additional parameters and options.
Create/load traffic arrays, if applicable.
Optionally, you can also follow these steps:
Specify constraints in the Site Database.
Define the Object/Action Costs and other cost-associated options (for example,
Budget).
Specify the Problem Area and/or Cell Thresholds.

Analysis
During this phase, you can optionally perform these steps:
Review the configuration of any plan or delta plan, by checking the plan reports
(Initial, Delta, Final) and the Action-Constraints.
Use the ranking functionality, which involves evaluating and sequencing the
changes. Typically, you may find this very useful if you are planning to add some
new sites to a network of existing sites. You can also create a partial plan, selecting
only the top-ranked new cells.
Display and review the spread network data, if applicable.
Analyse the performance statistics of a network plan or compare two different
plans.
Identify problematic areas and/or problematic cells.
Re-spread network data, if applicable.
Apply a plan to the Site Database, using either the Temp Apply/UnApply or the
Apply to Database options.
If applicable, use the analysis functionality (arrays and reports) in ASSET.
Optimisation
During this phase, you can use the Plan Manager in the Optimiser Workflow to
perform a number of plan-related operations, including the starting/running of the
Optimiser. You can check the feedback from the Optimiser in terms of:
Cost Details and Graphs - information about the costs related to the optimisation.
Statistics Details and Graphs - information about the statistics
(metrics/thresholds) related to the optimisation.
Optimisation Report - comprehensive details of the generated optimisation plans.
Overall cost improvement; time taken; accepted iterations.
Analysis
During this phase, you can repeat the appropriate steps as described in the previous
Analysis section.

Action
During this phase, you can optionally perform these steps:
Apply a plan to the Site Database, using either the Temp Apply/UnApply or the
Apply to Database options.
Start a new optimisation with same plan (with different action-constraints, costs,
and so on).
Create a new plan and a new optimisation.
Start a (secondary) optimisation from a delta plan, by using the Create a New Plan
from a Delta Plan option.
Use the ranking functionality, which involves evaluating and sequencing the
changes to achieve the most benefit. You can also create a partial plan, selecting
only the top-ranked changes.
About the Optimiser Workflow

The Optimiser Workflow enables you to perform the vast majority of tasks within
ADVANTAGE from a single dialog box.
To start the Optimiser Workflow:
From the Optimiser menu, click Workflow
- or -
Click the button on the main ADVANTAGE toolbar

The following dialog box is displayed:
The Optimiser Workflow dialog box

The following table briefly describes the options in the Optimiser Workflow dialog
box:
Option Enables You To
Plan Manager Perform plan-related operations, such as setting action-constraints, running an
optimisation and performing an analysis.
RF Array Thresholds Specify the required RF performance thresholds that will be used for your optimisations
and analyses.
RF Metric Targets Define the RF performance targets for your optimisations, based on the appropriate
metrics.
Costs/Limits Set maximum limits, combinations, and costs in terms of budget. This is for actions and
action costs.
Strategy Define major factors that will influence optimisations, such as which metrics will be
optimised, and how those metrics are weighted.
Traffic Select the list of terminal types to be used in an optimisation, and/or to load cached
traffic arrays.
Settings Set additional parameters and options related to optimisations, analysis and spreading
network data. Also enables you to set the array-based settings, and the settings for
Auto Plan Setup.
Financial Analysis Assess and plan for the revenue potential of your network. This licensed module can
help you make informed network planning decisions, particularly if integrating new sites
into an existing network.
See the Financial Analysis User Reference Guide.
The tab names and options within the Optimiser Workflow vary slightly
according to the technology that you are using.
For more detailed information about the options in this dialog box, see:
Setting Up Thresholds, Targets and Parameters on page 59
Using and Managing Plans on page 107
Optimising a Network on page 155

Recommendations and Guidelines
There are some crucial factors which you should consider when using
ADVANTAGE. It is strongly recommended that you consider the following factors
carefully, otherwise you run the risk of optimisations taking much longer than
necessary. If these issues are considered properly, and the set-up is sensible,
ADVANTAGE can perform at its best in terms of speed, performance and efficiency.
Large Array Support
For performance reasons, it is strongly recommended to turn off Large Array
Support (LAS) when running optimisations.
If the scenario (region size, map data resolution, terminal count, covering cell
depth, and so on) means that there is not enough memory available to
ENTERPRISE without using LAS, it is better to reduce the memory demands of
the scenario (such as splitting the scenario into multiple parts), rather than attempt
to use LAS.
For information on the Large Array Support Settings, see the ENTERPRISE
Installation and Administration Guide.
Prediction Resolutions
For performance reasons, prediction resolutions for individual cells should be set
so that they match the resolution at which the analysis or optimisation is being
performed. Ideally, the predictions should already be available at the specified
map data resolution, before performing an analysis or optimisation.
You can use the following list of guidelines in order to maximise the ability of the
optimisation algorithm to find an optimised network configuration quickly:
Concentrate on the region and cells of interest. Use the Plan Wizard to specify the
region and cells of interest, and ignore areas or cells that should not be part of the
optimisation.
Restrict the optimisation calculations to vectors and/or drive test routes (if possible). Use
the option in the Plan Wizard (or the Edit Vectors right-click option) to restrict the
optimisation array and cost calculations to specific vectors and/or drive test
routes.
Do not use a higher array resolution than required. If you can get realistic network
performance results by specifying a low resolution for the optimisation, there is no
point in using a higher resolution.
Restrict the number of servers/cells considered for array generation. If you can get
realistic results (for example, with respect to interference) by specifying fewer
servers/cells for the optimisation, there is no need to use more.
Limit the optimisation cost calculations to a lower number of servers/cells (if appropriate).
Use the Servers/Cells per Pixel option on the Strategy page of the Optimiser
Workflow to do this.
Focus on problematic cells/areas. Use read-only filters (for network objects that
should be considered, but not modified) and/or the Problem Cells options to
ensure that the Optimiser concentrates on cells that are performing badly.

Do not under- or over-constrain the optimisation problem. Make sure that the specified
actions/constraints are reasonable, so that inappropriate configurations are not
evaluated, but also flexible enough to allow the Optimiser to produce the best
possible plan.
Fine-tune the algorithm. The nature of the algorithm is general enough to apply to a
wide range of optimisation problems. Although the algorithm can be fine-tuned
per specific scenario to further maximise its efficiency (the algorithmic fine-tuning
depends on the setup and user permissions), it is not an easy task and must be
approached with caution.
Automatically Generating Sites

To speed up the setting up of the nominal network in your project, you can
automatically generate sites or nodes onto selected Properties, based on a specific site
or node template. By setting up a Property-based filter, you can determine on which
Properties the sites/nodes are to be created (the Properties can either be empty or
already have existing sites/nodes).
Each time you run this feature, new sites/nodes will be added to the Site
Database.
(This is a general ENTERPRISE feature that can be particularly useful in
ADVANTAGE.)
To do this:
1 Click on the Utilities tab.
2 From the Tools menu, click Auto-Generate Sites/Nodes.
3 In the dialog box that appears, select the (Property-based) filter that you want to
use.
4 Select the site or node template that you want to apply to the filter.
5 Click OK (remember to click back on the ADVANTAGE tab afterwards).
You have now applied an instance of the template (that is, a new site or node) to
every Property in the filter.
The new sites/nodes will be placed in the Site Database as follows:
For GSM: under the MSC/BSC
For UMTS, CDMA2000, EV-DO, WiMAX or LTE: under the PLMN

CHAPTER 3
Setting Action-Constraints
in ADVANTAGE
The purpose of action-constraints in ADVANTAGE is to allow certain network
parameter changes to be considered in a network optimisation, but at the same time
impose meaningful limitations and restrictions on those changes, in order to
accurately represent the real-world environment.
Why the term 'action-constraint'?
An example of an 'action' may be that you want to allow the antenna azimuths for a
group of cells to be changed, but, at the same time, you might want to specify a
'constraint' for one of those cells, which could be a forbidden azimuth range due to to
a nearby school.
The ADVANTAGE tool focuses on automatic optimisation of Plans, and the

action-constraints play a crucial part in this process. Before proceeding with the
options in this chapter, it is important that you read the relevant sections in the Plan
Manager chapter, in particular About the Action-Constraints Dialog Box on page 124.
In this chapter, for the sake of brevity:

The term WiMAX represents Fixed WiMAX or Mobile WiMAX
The term CDMA/EV-DO represents CDMA2000 or EV-DO

Setting Action-Constraints in ADVANTAGE
About Action-Constraints
In ADVANTAGE, there are two separate 'sources' of action-constraints:
Action-constraints that you can set up and edit within the Optimiser Workflow
Action-constraints that you can set for specific network elements directly within
the Site Database
In both cases, these action-constraints can be configured on an object-by-object basis,
or to groups of objects through the use of filters.
The action-constraints that you can specify are mainly common, whichever source
you use. This is because, in general terms, there is nothing you can set up in the Site
Database that you cannot also set up in the Action-Constraints dialog box (in other
words, it is not compulsory to set Site Database action-constraints). However, there are
a few exceptions, listed in the table in Action-Constraints Exclusive to the Site
Database on page 39.
Action-constraints that are set in the Site Database are always auto-populated
into the Action-Constraints dialog box when you create a plan. You then have the
freedom to modify those action-constraints at that stage, if required. When you run an
optimisation, the Optimiser reads the action-constraints exclusively from the Action-
Constraints dialog box, regardless of their original 'source'.
When you run an optimisation, there are three planning mechanisms you can use:
Antenna
Power
Grid (site location/selection/configuration)
ADVANTAGE provides the flexibility to run optimisations based on any single
mechanism, or any combination of them.
So, for example, this flexibility enables you to:
1 Set specific action-constraints in the Site Database.
2 Edit these action-constraints (if required) and set up further action-constraints (if
required) in the Action-Constraints dialog box.
- or -
Set up action-constraints exclusively in the Action-Constraints dialog box.
3 Select one or more of the planning mechanisms, according to your optimisation
strategy.
The action-constraints of any plans which already have delta plans are always in
Read-Only format.
For more detailed information about the action-constraints within the Optimiser
Workflow, see About the Action-Constraints Dialog Box on page 124 and Using the
Action-Constraints Dialog Box on page 127.

Action-Constraints Exclusive to the Site Database
In general terms, there is nothing you can set up in the Site Database that you cannot
also set up in the Action-Constraints dialog box. However, there are some exceptions,
listed in the following table.
This table lists the action-constraints that you can only set in the Site Database:
Tab name Object Action-Constraint
Grid Constraints Property Define potential Property locations as valid optimisation
options, in terms of co-ordinates or Candidate Properties.
Grid Constraints Property Define the optimisation status of a Property as Nominal or
Candidate.
Grid Constraints Site or Node Define sector configurations (combinations).
If you do set any of the above action-constraints in the Site Database, when you next
create a plan, you will be able to view them in the Action-Constraints dialog box, in a
read-only state. Whether they are used in an optimisation depends on whether you
choose to use the Grid planning mechanism.
About the Action-Constraints Available

This section describes the various action-constraints that can be specified in
ADVANTAGE. They are summarised in this table, listed against the specific network
elements to which they relate.
Although these action-constraints are described here specifically in terms of

setting them in the Site Database, the concept of the action-constraints is the same if
you set them within the Optimiser Workflow. If you are setting them within the
Optimiser Workflow, you should also refer to About the Action-Constraints Dialog
Box on page 124.
Network Element Constraints
Property Antenna, Grid
Equipment Mast, BTS Type
GSM Site Installation, Grid
GSM Cell Antenna
GSM Subcell Power
UMTS Node Antenna, Grid, Resource
UMTS Cell Power, Power Control
CDMA2000/EV-DO Site Antenna, Grid
WiMAX Node Antenna, Grid
WiMAX Cell Power
LTE Node Antenna, Grid
LTE Cell Power
You can also edit a number of constraints in the Site Database simultaneously, as
described in Configuring Constraints in the Site Database Global Editor on page 55.

Configuring Property Grid Constraints
Property grid constraints can be used in conjunction with the grid planning
optimisation actions to specify how a Property will be considered in an optimisation,
for example, its grid and/or candidate Property locations.
Site location changes cannot be considered in an optimisation unless the related

options are also specified in the Action-Constraints dialog box in the Optimiser
Workflow. For more information, see About the Action-Constraints under the Grid
Tab on page 132.
To configure Property grid constraints:
1 From the Database menu, click Sites.
2 Select a Property and click on the Grid Constraints tab.
3 Select the required Optimisation Status:
Select To
Nominal Define candidate locations in terms of co-ordinates or candidate Properties as valid optimisation
options (this means that the Property can be moved to those locations).
Candidate Define the Property as a candidate only.
4 If you have selected Nominal, specify a possible candidate location. To do this,

either:
 Click in the Name field and type the ID of another Property already defined in
the Site Database:
(The co-ordinate values are auto-populated after you press the Enter key.)
- or -
 Click in the appropriate column and type co-ordinate values (in GRID, DLL, or
LL as appropriate).
Invalid co-ordinates will not be saved.

5 If required, you can constrain the Optimiser to consider only the current position
of the Property (whether candidate locations are available or not), by selecting
'Location Fixed'.
6 Click Apply to save the changes, and Commit if appropriate.

This picture shows an example, where three possible candidate locations have been
defined:
Defining candidate locations
If you need to delete a candidate location, select the location and click Delete.
If you have specified any Property IDs, the Optimisation Status on the Grid
Constraints tab of the specified candidate Property is auto-updated to 'candidate'.

Configuring Property Antenna Constraints
Property antenna constraints are related to the antenna optimisation, and enable you
to restrict the available options that can be used to optimise the antennas located on
the Property.
To configure Property Antenna Constraints:
2 Select a Property, and click the Antenna Constraints tab. This picture shows an
example:
3 In the Antenna Height Rules pane, enter the minimum and maximum height
values that you wish to use as a basis for the antenna constraints defined on this
tab.
To manually define a series of allowable antenna height values within the
minimum-maximum range:
 Select the Manual option, and then select the Constrain checkbox.
 In the value box above the Add button, type the first value in metres.
 Click Add.
 Add further values as required - to delete a value, select it and click Remove.
To edit a value, select it, change the value and then click Update.

To define a series of allowable antenna height values within the minimum-
maximum range based on the mast associated with the Property (which is defined
on the General tab of a Property in the Site Database):
 Select the Mast option, and then select the Constrain checkbox.
 The constraint values that you have defined for this mast appear. For more
information on this, see Configuring Equipment Constraints on page 44.
To define a series of allowable antenna height values within the minimum-
maximum range based on a particular step size:
 Select the Step option, and then type a value in metres for the step.
 Select the Constrain checkbox.
 A series of allowable antenna height values appear, starting with the defined
minimum height, then moving upwards in steps (according to the size you
defined) to the defined maximum height.
For example, the allowable height values for a minimum height of 20m and a
maximum of 30m with a step size of 2m would be 20, 22, 24, 26, 28, and 30m.
4 In the Height Variation pane, you can determine whether the heights for
individual antennas may differ at a specific Property (this option is cell layer-
specific for GSM). To do this, select the Allowed checkbox.
If this is not selected, all antennas on the same cell layer (GSM) or on all
carriers (UMTS) at this Property must be at the same height. However, GSM cells
for different cell layers, or cells of different technologies (for example, GSM and
UMTS) can still have antennas with heights different from each other.
5 In the Antennas at Same Height pane, you can specify a minimum azimuth
difference. This is the minimum separation (in degrees) that you are willing to
accept between antennas of the same height on this Property. To do this, select the
Constrain checkbox and type a value.
6 In the Antenna Co-location pane, select the Enable Co-location checkbox if you
want to enable antenna devices to be able to share co-location parameters
(identical location co-ordinates, height and azimuth, and on the same Property).
If Antenna Co-location is not enabled for a Property, no antenna sharing or

co-location configuration can be accepted as a valid starting configuration or
examined as a potential optimisation solution by the Optimiser. For more
information, see How the Optimiser Considers Shared Antennas on page 138.

Configuring Equipment Constraints
You can specify constraints for masts and BTS equipment, so that the constraints are
used when these objects are assigned to a network element in the Site Database. Masts
can be used to constrain the antenna heights of Properties (all technologies). BTS
types can be used to constrain the output power of GSM subcells.
Masts
To configure equipment-specific constraints for masts:
1 From the Equipment menu, select Masts.
2 In the dialog box that appears, select the mast that you want to constrain.
3 Click the Dimensions tab, and:
 Specify the structure height
 Select the required mount option - if you select Rooftop, the building height of
the Property will be added to the mast height to give the antenna height.
4 Click the Constraints tab, and specify the mast heights that you want to make
available:
 In the Available Masts Height pane, type in a height value and click Add
 To change a value, select it and enter a new value in the box and click Update
 To remove a value, select it and click Remove

BTS Types
To configure equipment-specific constraints for BTS types:
1 From the Equipment menu, select BTS Equipment.
2 In the dialog box that appears, select the BTS type that you want to constrain.
3 Click the Parameters tab, and in the PA Output Power pane, select a cell layer and
enter the minimum and maximum PA Output power values that the BTS can
provide. This picture shows an example:
These constraints are only used if these equipment types are assigned to the
relevant network elements in the Site Database. For example, masts are assigned to
Properties (all technologies), and BTS equipment types are assigned to GSM sites.

Configuring GSM Site Installation Constraints
GSM site installation constraints can be configured to restrict the options that can be
used during GSM cell power optimisation.
To configure GSM site installation constraints:
2 Select a GSM site, and click on the Installation tab.
3 In the ACP Constraint pane, select the Fix Site Equipment checkbox if you want
the specified BTS equipment type to stay unchanged during a GSM power
optimisation.
Configuring GSM Site Grid Constraints

The Grid Constraints tab of a GSM site is where you can define options to use in the
grid planning optimisation - in particular, how you choose which sector combinations
within a site are allowed to be considered during optimisation.
There are also two options on this tab relating to grid planning:
Select If You Want To
Site Always Active Ensure that this site is always used in every solution the Optimiser generates. This means that the
site will never be completely 'switched off' during optimisations.
Fixed Site DB Sector Prevent the sector configuration for a site from changing during optimisations.
Configuration
Site/sector configuration changes cannot be considered in an optimisation unless

the related options are also specified in the Action-Constraints dialog box in the
Optimiser Workflow. For more information, see About the Action-Constraints under
the Grid Tab on page 132.

To generate a configuration automatically:
2 Select a GSM site and click on the Grid Constraints tab.
3 In the Min. Sectors and Max. Sectors fields, type the required number of sectors.
4 Click Generate.
This picture shows an example of the potential configurations:

To add a configuration manually:
1 Click the Add button.
2 Select the checkboxes for the required sectors.
If you need to delete a configuration, select it and click Remove. To delete all
configurations, click Remove All.

Configuring GSM Cell Antenna Constraints
GSM cell antenna constraints are configured per antenna, as opposed to constraints
configured per Property, which relate to all antennas on the Property. For information
on how to configure these, see Configuring Property Antenna Constraints on page 42.
To configure GSM cell antenna constraints:
2 Select a cell, and click the Antenna Constraints tab.
3 Ensure that you select the appropriate antenna by selecting the required slot from
the Antenna Configuration pane:
In most cases, there will only be one antenna slot per cell, but it is possible that
multiple slots have been configured.
4 In the Wall or Other Bearing Constraints pane, select to use a Forbidden Azimuth
Range. This enables you to define an orientation region (or range) which the
automatic optimisation cannot consider for azimuth changes.
5 To set the range, type a clockwise wall bearing angle (in other words, the starting
azimuth for the forbidden range) and an anti-clockwise wall bearing angle (in
other words, the final azimuth for the forbidden range).
This picture shows an example for an original antenna azimuth of 100 degrees.
The clockwise bearing angle is set to 120 degrees and the anti-clockwise bearing
angle to 80 degrees, meaning that, depending on the considered antenna
actions/constraints, the antenna may be able to move plus or minus 20 degrees
during the optimisation:

6 In the Misc Constraints pane, you can set the following constraints per antenna
slot:
Select this checkbox To
Antenna Device Fixed Prevent changes to the antenna device during optimisation.
Antenna Pattern Fixed Prevent changes to the antenna pattern during optimisation.
If you select this, Antenna Device Fixed will be selected automatically.

Mechanical Downtilt Fixed Prevent changes to the mechanical downtilt during optimisation.
Azimuth Fixed Prevent changes to the azimuth during optimisation.
Height Fixed Prevent changes to the antenna height during optimisation.
Constrain Max Main Lobe Tilt Prevent changes to the electrical and/or mechanical downtilt that violate this constraint
during optimisation.
Configuring GSM Subcell Power Constraints

GSM subcell antenna/TRX constraints can be configured to fix the PA output during
the GSM cell power optimisation.
To configure GSM subcell antenna/TRX constraints:
2 Select a GSM subcell, and click the Antenna/TRX tab.
3 In the ACP Constraint pane, select the Fixed PA Output checkbox if you want to
prevent changes to the PA output by the Optimiser during optimisation.

Configuring UMTS, CDMA/EV-DO, WiMAX or LTE Grid
Constraints
The Grid Constraints tab of a site/node is where you can define options to use in the
grid planning optimisation - in particular, how you choose which sector combinations
within a node are allowed to be considered during optimisation.
There are also two options on this tab relating to grid planning:
Select If You Want To
Site Always Active Ensure that this site is always used in every solution the Optimiser generates. This means that
the site will never be completely 'switched off' during optimisations.
Fixed Site DB Sector Prevent the sector configuration for a site from changing during optimisations.
Configuration
Site/sector configuration changes cannot be considered in an optimisation unless

the related options are also specified in the Action-Constraints dialog box in the
Optimiser Workflow. For more information, see About the Action-Constraints under
the Grid Tab on page 132.
To generate a configuration automatically:
2 Select a node and click on the Grid Constraints tab.
3 In the Min. Sectors and Max. Sectors fields, type the required number of sectors.
4 Click Generate.

This picture shows an example of six possible configurations:

To add a configuration manually:
1 Click the Add button.
2 Select the checkboxes for the required sectors.
To delete a configuration, select it and click Remove. To delete all configurations, click
Remove All.

Configuring UMTS, CDMA/EV-DO, WiMAX or LTE Antenna
Constraints
Antenna constraints are related to the antenna optimisation, and enable you to restrict
the available options that can be used to optimise the antennas associated with a node
cell.
To configure antenna constraints:
2 Select a node and click the Antenna Constraints tab.
3 Ensure that you select the appropriate antenna by selecting the required antenna
number from the Antenna Configuration pane:
These numbers correspond to the antennas listed on the Antennas tab. The
constraints are always antenna-specific.
4 In the Wall or Other Bearing Constraints pane, select to use a Forbidden Azimuth
Range. This enables you to define an orientation region (or range) which the
automatic optimisation cannot consider for antenna azimuth changes.
5 To set the range, type a clockwise wall bearing angle (in other words, the starting
azimuth for the forbidden range) and an anti-clockwise wall bearing angle (in
other words, the final azimuth for the forbidden range).
This picture shows an example for an azimuth of 100 degrees. The clockwise
bearing angle is set to 120 degrees and the anti-clockwise bearing angle to 80
degrees, meaning that the antenna is able to move plus or minus 20 degrees
during the optimisation:

6 In the Misc Constraints pane, you can set the following constraints per cell:
Select this checkbox To
Antenna Device Fixed Prevent changes to the antenna device during optimisation.
Antenna Pattern Fixed Prevent changes to the antenna pattern during optimisation.
If you select this, Antenna Device Fixed will be selected automatically.

Mechanical Downtilt Fixed Prevent changes to the mechanical downtilt during optimisation.
Azimuth Fixed Prevent changes to the azimuth during optimisation.
Height Fixed Prevent changes to the antenna height during optimisation.
Constrain Max Main Lobe Tilt Prevent changes to the electrical and/or mechanical downtilt that violate this
constraint during optimisation.
Configuring UMTS Node Resource Constraints

Node constraints can be configured to restrict the node to a particular node type
during a power optimisation.
To configure node resource constraints:
2 Select a node and click the Resource tab.
3 In the ACP Constraint pane, select the Fix Node Type checkbox if you want the
specified Node type to stay unchanged during a power optimisation.

Configuring UMTS Cell Power Constraints
UMTS cell power constraints can be configured to restrict the power settings that can
be used to optimise the cell. Selection of any of these constraints will prevent the
relevant power from being changed during an optimisation.
To configure UMTS cell parameter constraints:
2 Select a UMTS cell, and click the Cell Params tab.
3 In the UMTS Parameters pane:
Set this parameter to TRUE If you want to prevent changes to this power
Fixed Max TX Power Maximum (total) TX power
Fixed UMTS Channel Power The power that is dedicated to the Pilot, Control, Synchronisation and Indicator
channels
Fixed HSDPA Power HSDPA power
Configuring UMTS Cell Power Control Constraints

UMTS cell power control constraints can be configured to restrict the maximum
downlink power per connection that can be used to optimise the UMTS cell.
To do this:
1 From the Site Database, click Sites.
2 Select a UMTS cell, and click the Load&Power Ctrl tab.
3 In the TX Power Limits pane, under ACP Constraint, select the Fixed checkbox.

Configuring WiMAX Cell Power Constraints
WiMAX cell constraints can be set to restrict the power settings that can be used to
optimise the cell. Selection of this constraint will prevent the relevant power from
being changed during an optimisation.
These constraints are applicable to both Fixed WiMAX and Mobile WiMAX.
To configure WiMAX cell power constraints:
2 Select a cell, and click the WiMAX Params tab.
3 In the ACP Constraints pane, select the Fix TX Power checkbox.
Configuring LTE Cell Power Constraints

LTE cell constraints can be set to restrict the power settings that can be used to
optimise the cell. Selection of this constraint will prevent the relevant power from
being changed during an optimisation.
To configure LTE cell power constraints:
2 Select an LTE cell, and click the LTE Params tab.
3 In the ACP Constraints pane, select the Fix TX Power checkbox.
Configuring Constraints in the Site Database Global Editor

Changing information for a large number of Properties, sites and cells can be a very
lengthy process when performed manually. To avoid this, you can use the Global
Editor to define constraints for objects identified by a filter.
The Global Editor is used on a per filter basis - you cannot specify a different filter
for different tabs.
To use the Global Editor:
2 In the Site Database window, click Global Edit.
3 Select the appropriate filter.
4 Select the items that you want to change for the network elements in this filter. For
a list of the ADVANTAGE-specific constraints, see ADVANTAGE-specific
Constraints in the Global Editor on page 57.

Here is an example of the constraints in the Global Editor:
Where a parameter has two checkboxes, ensure you select both if you want to
set the relevant constraint. However, if you want to disable (previously set)
constraints, you can select the first checkbox, and clear the second checkbox. In
simple terms, the first checkbox determines whether the change is to be made, and
the second checkbox determines what is to be changed. For example:
To set the constraint To unset the constraint (if previously set)

ADVANTAGE-specific Constraints in the Global Editor
This table describes the ADVANTAGE-specific constraints:
On this tab You can set these constraints
Cell Constraints Antenna Device Fixed
Antenna Pattern Fixed
Mechanical Downtilt Fixed
Azimuth Fixed
Height Fixed
Constrain Max Main Lobe Tilt
Property Constraints Antennas:
Allow Co-location
Allow Height Variation
Same Height Min Azimuth Diff
Antenna Height Rules:
Manual, Mast or Step Height
Min Height
Max Height
Grid Constraints:
Optimisation Status
Location Fixed
Heights Used
Site Constraints Grid Constraints:
Fixed Site DB Sector Configuration
Site Always Active
Sector Configuration Generator:
Min Sectors
Max Sectors
Generate Configurations
Remove All Configurations
Installation (GSM) Fixed Site/BTS Equipment
Cell Layer (GSM) Fixed PA Output
Node Config (UMTS) Fixed Node Type
Cell Params (UMTS) Fixed Max TX Power
Fixed UMTS Channels Power
Fixed HSDPA Power
Load & Power Ctrl (UMTS) Fixed Max DL Power per Connection
WiMAX Cell Params Fixed TX Power
LTE Cell Params Fixed TX Power

CHAPTER 4
Setting Up Thresholds,
Targets and Parameters
ADVANTAGE from a single dialog box. This incorporates the setting up of
parameters, costs, constraints and targets, and generation of optimisation Plans.
It comprises a number of main options in the left hand pane, and each of these
enables you to access a range of specific options that are displayed in the right-hand
pane.
This chapter focuses on the thresholds, parameters and settings, which are crucial to
the optimisation engine. In addition to setting the thresholds and metric targets, it is
here that you specify which strategy you will use for your optimisations and analyses.
These steps, in particular the ones related to the radio environment setup, are
probably not relevant to the general user, assuming that the administrator (or super-
user) has already completed them. This is also true for optimisation scenarios that
have been set up by one user that can be shared with other users who access the same
project.
- or -
In this chapter, for the sake of brevity:

The term WiMAX represents Fixed WiMAX or Mobile WiMAX
The term CDMA/EV-DO represents CDMA2000 or EV-DO

Setting Up Thresholds, Targets and Parameters
Setting RF Array Thresholds
The RF (radio frequency) array thresholds in the Optimiser Workflow enable you to
specify:
RF array thresholds for clutter
RF array thresholds for vectors
These thresholds determine the required RF performance for your optimisations and
analyses.
These thresholds are used by the array-based optimisation cost mechanism (they
are not used by the service-based cost mechanism).
Specifying RF Array Thresholds for Clutter
In the RF Array Thresholds, you can configure clutter-specific thresholds that define
the current or required performance of your network. This enables you to specify and
use minimum signal strength, signal quality, and dominance thresholds for chosen
clutter types.
These thresholds are evaluated when running optimisations and performing an
analysis.
This picture shows an example of the Clutter Thresholds:
Example of Clutter Thresholds

If you have multiple cell layers (GSM) or multiple carriers (all other
technologies), you can evaluate your network at a 'per layer' or 'per carrier' level
(rather than 'per technology'). There is a Per Layer Calculation option in the Settings
(Options tab) which enables you to activate the 'per layer/carrier' tabs in the RF
Thresholds. See About the Options Tab on page 91.
This picture shows an example of 'Per Layer' Clutter Thresholds:
Example of Per Layer Clutter Thresholds
To edit the Clutter Thresholds:
1 Open the Optimiser Workflow by clicking the shortcut button on the main
ADVANTAGE toolbar.
2 In the left-hand pane, double-click RF Array Thresholds, and then double-click
Clutter.
3 Click the required technology, as appropriate, depending on your licences.

4 Specify the threshold values as required in the columns for the appropriate clutter
types. The following table describes them:
Technology Parameter Description
GSM RSS The minimum signal level (dBm) that is required to provide
coverage in the corresponding clutter type.
UMTS RSCP
CDMA/EV-DO RSCP
Fixed WiMAX DL RSS
Mobile WiMAX Preamble RSS
LTE RSRP
GSM CINR The minimum signal quality ratio (dB) that is required in the
corresponding clutter type.
UMTS Pilot Ec/Io
CDMA/EV-DO Pilot Ec/Io
Fixed WiMAX DL CINR
Mobile WiMAX Preamble CINR
LTE RSRQ
GSM Polluters The maximum number of polluters/interferers that are acceptable
per pixel in the corresponding clutter type.
UMTS Pilot Polluters
For LTE, the number of interferers is derived directly from the
CDMA/EV-DO Pilot Polluters 'Number of RSRP OK' array, omitting the serving cell.
LTE Dominance Interferers For the other technologies, for information on setting the
thresholds (in other words, relative margins) that determine when
a cell qualifies as a polluter, see Configuring Array Settings on
page 93.
You can employ functionality similar to that in spreadsheets, such as:

 Copying and Pasting single or multiple values within the dialog box
 Copying and Pasting values directly to and from Microsoft Excel ®
 Pressing the Ctrl-Shift-DownArrow/UpArrow keys (as a quick method of
highlighting rows in a column)
All changes that you make on this page are automatically saved to the database in
the Applied state, and the changes will persist when you close the Workflow
dialog box.
However, if appropriate, you can carry out one of the following actions:
 If you want to restore the options on this page to the previous committed state
(if such a state exists), click Restore
 If you want to share the changes on this page with all other users of the
project, click Commit

Setting the General Clutter Parameters
If you want to use the sampling and/or importance options, you can do this on the
General Clutter Parameters tab. To do this:
ADVANTAGE toolbar.
2 In the left-hand pane, double-click RF Array Thresholds, then double-click Clutter,
and then click General.
3 On the General Clutter Parameters tab, specify the parameters as required in the
columns for the appropriate clutter types. The following table describes the
parameters:
Parameter Description
Sample Determines whether cost function sampling is applied to the clutter type. This
sampling is a calculation process using only a subset of the total pixels during
Used only for optimisations optimisation. The process 'removes' neighbouring pixels of the same clutter type,
and analysis. and therefore makes the optimisation faster.
Sampling is only recommended if your mapping resolution is high (under 50m) and
you want to optimise a large area.
Importance The importance of the corresponding clutter in terms of traffic density. The higher
the importance of the clutter, the higher the traffic density levels for this clutter type,
Used only for spreading and vice versa.
network data. For more information, see About the Spreading Mechanisms in ADVANTAGE on
page 197. and About the Optimisation-Based Spreading Algorithms on page 213 in
the appendix.
If required, you can change all values in a column by editing one row and then
double-clicking on the column heading.

Specifying RF Array Thresholds for Vectors
In the RF Array Thresholds, you can configure vector-specific thresholds that define
the current or required performance of your network. This enables you to specify and
use minimum signal strength, signal quality, and dominance thresholds for chosen
vectors.
These thresholds are evaluated when running optimisations and when performing an
analysis.
The Override checkbox not only enables you to edit the values, but also activates
the vector thresholds. Conversely, if unselected, the vector thresholds are not active.
Therefore, you should always bear this in mind before you run an optimisation or
perform an analysis.
When selected, vector thresholds will always have a higher priority than clutter
thresholds (in the pixels that are intersected by your chosen vectors).
This picture shows an example of the Vector Thresholds:
Example of Vector Thresholds

technologies), you can evaluate your network at a 'per cell layer' or 'per carrier' level
(rather than 'per technology'). To activate the ‘per layer/carrier’ tabs in the RF Array
Thresholds, on the Options tab in the Settings page, select the Per Layer Calculation
option. See About the Options Tab on page 91.
This picture shows an example of 'Per Cell Layer' Vector Thresholds:
Example of Per Cell Layer Vector Thresholds
To edit the Vector Thresholds:

1 In the left-hand pane of the Optimiser Workflow, double-click RF Array
Thresholds, and then double-click Vector.
2 Click the required technology, as appropriate, depending on your licences.

3 Click the Select Vectors button, and in the dialog box that appears, choose the
vectors for which you would like to configure parameters, then click OK.
4 Select the Override checkbox.

5 Specify the values as required in the columns for the appropriate vectors. The
following tables describe the thresholds:
Technology Parameter Description
All Priority You can specify the relative priority of the chosen vectors. This
will determine which parameters are to be used at locations with
intersecting vectors. To raise the priority of a vector, select it,
then drag and drop it to the required priority position.
GSM RSS The minimum signal level (dBm) that is required to provide
coverage in the corresponding vector.
UMTS RSCP
CDMA/EV-DO RSCP
Fixed WiMAX DL RSS
Mobile WiMAX Preamble RSS
LTE RSRP
GSM CINR The minimum signal quality ratio (dB) that is required in the
corresponding vector.
UMTS Pilot Ec/Io
CDMA/EV-DO Pilot Ec/Io
Fixed WiMAX DL CINR
Mobile WiMAX Preamble CINR
LTE RSRQ
GSM Polluters The maximum number of polluters/interferers that are acceptable
per pixel in the corresponding vector.
UMTS Pilot Polluters
For LTE, the number of interferers is derived directly from the
CDMA/EV-DO Pilot Polluters 'Number of RSRP OK' array, omitting the serving cell.
LTE Dominance Interferers For the other technologies, for information on setting the
thresholds (in other words, relative margins) that determine when
a cell qualifies as a polluter, see Configuring Array Settings on
page 93.

6 Leave the Override checkbox selected if you want these thresholds to be active for
your optimisations. You can deactivate them at any time, by deselecting the
checkbox.
dialog box.

Setting RF Metric Targets
The RF Metric Targets in the Optimiser Workflow enable you to:

Specify targets for array-based metrics
Specify targets for service-based metrics
These parameters enable you to define targets for optimisations and analyses. These
targets correspond to metrics that can be defined separately for each cost mechanism
(array-based and service-based).
The metric targets may vary according to the technology that you are using.
About the Targets for Array-based Metrics

The array-based metric targets are part of a cost mechanism that enables you to
optimise a network based on the results from the arrays.
You can use this cost mechanism for antenna, power or grid optimisations.
(If required, you can combine this mechanism with the service-based cost
mechanism.)
These targets can be specified separately for each technology (the metrics vary
depending on the technology).
technologies), you can evaluate your network at a 'per layer' or 'per carrier' level
(rather than 'per technology'). There is a Per Layer Calculation option in the Settings
(Options tab) which enables you to activate the 'per layer/carrier' tabs.

There are three available types of metric that can be used for targets:
Coverage:
 The required array-based coverage (target, minimum and multiplier) for the
clutter type.
Coverage target calculations are based on signal strength level alone (such as
RSS).
Quality
 The required array-based quality (target, minimum and multiplier) for the
clutter type.
Quality target calculations are based on either the quality level alone (such as
CINR) or on both quality level AND signal strength (for example, CINR and
RSS together), depending on your preferred basis for this metric. For more
information, see Specifying the Settings on page 90.
Dominance
 The number of servers (target, minimum and multiplier) for the clutter type.
Dominance target calculations are based on the appropriate dominance or
pilot polluters array.
This metric is not available for all technologies.
The following table describes the targets that can be defined for each technology.
They can be separately defined for traffic and area:
Technology Target Metrics
Coverage Quality Dominance
GSM RSS CINR Polluters
UMTS RSCP Pilot Ec/Io Pilot Polluters
CDMA2000/EV-DO RSCP Pilot Ec/Io Pilot Polluters
LTE RSRP RSRQ Dominance Interferers
Fixed WiMAX DL RSS DL CINR - not applicable -
Mobile WiMAX Preamble RSS Preamble CINR - not applicable -
Each metric type (coverage, quality, dominance) comprises three columns:

Target - target value (default is 100%)
Minimum - minimum value required (default is 95%)
Multiplier - multiplier factor (cost penalty) if the minimum is not achieved
(default is 1)

Setting Array-based Targets
To define array-based targets:
ADVANTAGE toolbar.
2 In the left-hand pane, double-click RF Metric Targets, and then double-click
Array-based.
3 Double-click the required technology, as appropriate, depending on your licences.

4 Click either Area or Traffic, as required.
5 Specify the required values in the appropriate columns for each of your clutter
types.
Here is an example of the coverage columns for GSM:

dialog box.

About the Targets for Service-based Metrics

The service-based metric targets are part of a cost mechanism that enables you to
optimise a network based on the results from the Simulator's snapshots.
You can use this cost mechanism for antenna, power or grid optimisations. You must
configure these targets before starting the optimisation.
(If required, you can combine this mechanism with the array-based cost mechanism.)
Service-based metric targets are associated with terminal capabilities. These targets
refer to:
The percentage of served terminals (on a network or per cell basis)
The percentage of served terminals in soft/softer handover
The uplink or downlink throughput (on a network or per cell basis)
The available targets can include:
Served Terminals
Served Terminals per Cell
Served Terminals in Soft or Softer Handover
Uplink Throughput
Downlink Throughput
Uplink Cell Throughput
Downlink Cell Throughput
The available metric targets may vary according to the technology that you are
using. For example, for GSM or WiMAX, the Handover metrics are not applicable.
For each metric target, you can use:
Averaged Cost Calculation - This averages the sum of calculated costs (considered
in the optimisation) for all the groups for the appropriate metric, based on the
total number of groups assigned to it.
Weighted Cost Calculation - This weights the calculated cost (considered in the
optimisation) for each group for the appropriate metric, based on the group-
specific terminal attempts or served terminals or targeted throughput (as
applicable).
In terms of the optimisation, the only time the Averaged/Weighted options will
make a difference to the results is when you have multiple groups assigned to a
metric. If that is not the case, they can be considered to be exactly the same.

There are three stages to configuring the service-based metric targets:
1 Define one or more target groups.

2 Assign the target group(s) to the required metrics.
3 Specify the target values for each metric.
Defining Target Groups

The target groups enable you to set target values for your services (or, more precisely,
service/carrier or service/cell layer combinations). You can subsequently assign these
groups to the metric(s) that you want to use.
If you want to set the same target values for all your services (per metric), it is a
simple process to place them in the same group, and specify a common set of
target values.
If you want to specify target values independently for each service (per metric),
you should ensure you place each service in a separate group.
To define the target groups:
1 Ensure that you have already defined all your services and associated parameters.
For information on defining services, carriers, cell layers, terminals and bearers,
see the ASSET User Reference Guide.
ADVANTAGE toolbar.
3 In the left-hand pane, double-click RF Metric Targets, and then double-click
Service-based.
4 Click Define Groups.
5 In the Groups dialog box, click Add to add a new group.

6 In the Group Edit dialog box, name the group, and select the appropriate service,
as in this example:
7 Click the right-arrow button. The service (and its associated carriers or cell layers)
is shown in the right pane. In this example only one service has been selected, but
you can select more if required:
Target values are specified per group. Therefore, if you want to specify target
values independently for each service, you should keep them in separate groups.
8 When you have finished editing the group, you can continue adding or editing
any other groups according to your requirements.
9 If you want to share specific group changes with all other users of the project, click
Commit, or to share all group changes, Commit All.
10 Click Close to close the dialog box.
You can now assign the target group(s) to the required metrics.
Assigning Target Groups to Metrics

After you have defined the target groups, you need to assign them to the required
metrics. To do this:
1 In the right-hand pane of the Optimiser Workflow, highlight the required metric -
for example, Served Terminals (%) (Averaged).
2 Click the Assign Groups button.

3 From the Groups available pane, select a group and click the right-arrow button.
The group appears in the Groups in-use pane, and will be associated with the
respective target.
4 If appropriate, you can assign more than one group to a metric. If you do this, you
should check whether you want to use the Averaged or Weighted metric, as
explained in About the Targets for Service-based Metrics on page 70.
5 Click OK.
If a group has already been assigned to one of the metrics, you can quickly copy
that same group to another metric by selecting it, and then dragging and dropping it
onto another metric.
You can now specify the target values.
Specifying Target Values

After you have assigned the target groups to the required metrics, you can specify the
target values. To do this:
1 Highlight the appropriate target group.
If the target group is assigned to more than one metric, ensure you select the
correct one, because the target values are independent between the metrics.
The target group values appear:
2 Depending on the target group, you can edit some or all of the following values:
Value Description
Min Minimum value required
Target Target value
Max Maximum value required (if applicable to the metric)
Multiplier Multiplier factor (cost penalty) if the value is:
- Less than the min value
or
- More than the max value

dialog box.
The Commit All and Restore All buttons are useful if you have edited a large
number of targets.
Specifying Costs/Limits
The Costs/Limits in the Optimiser Workflow enable you to:

Set maximum limits for the number of objects or actions
The optimisation will reject any plans exceeding these limits
Specify how combinations of actions and action costs are considered

Several actions (and their associated costs) can be considered as a single action
and a single cost
Specify costs for objects and/or actions

Each change considered can incur a cost, in terms of budget
Specify maximum costs

Plans may or may not be feasible from a financial, time or resource point of
view
The costs and limits may vary according to the technology that you are using.

Setting Maximum Limits for Objects or Actions
On the Max Objects/Actions tab, you can choose to reject plans according to
maximum limits for:
The number of objects for a given object type
The number of actions for a given planning type (or combined)
If you select the option to reject plans based on these limits, the optimiser will not
accept any optimisation states (apart from the starting plan state) that exceed these
limits.
This picture shows an example where limits have been set on the number of Antenna
Objects and the number of Property Objects. Any optimisation state that exceeds
either of these limits would be rejected.
Max Objects/Actions tab
To set maximum limits for objects and actions:
ADVANTAGE toolbar.
2 In the left-hand pane, click Costs/Limits.
3 Click the Max Objects/Actions tab.

4 Select the 'Reject Plans based on' checkbox.
5 Select the appropriate option(s), and specify the limit(s).
All changes that you make on this tab are automatically saved to the database in
dialog box.
 If you want to restore the options on this tab to the previous committed state
 If you want to share the changes on this tab with all other users of the project,
click Commit

You can turn this plan rejection method On/Off by using the 'Reject Plans Based
On Max Objects/Actions' checkbox (the individual selections and limits are still
stored).
Defining Combinations of Actions

On the Action Combination tab, you can optionally combine actions and action costs,
so that the number and costs of different actions can be considered as one single
action. This tab enables you to specify which actions and action costs (if any) you
want to combine for your optimisations and analyses.
You can combine actions by:
Location
Property
Site
Cell
You also have the option of combining:
All actions
Only visit actions (actions requiring a visit to the site)
Only remote actions (actions not requiring a visit to the site, such as changes to
remote adjustable antennas)
You may then specify whether power actions are to be considered as remote actions
or as visit actions (however, BTS and Node Type actions are always considered as
visit actions).
To define combinations of actions and costs:
ADVANTAGE toolbar.
3 Click the Action Combination tab.

4 Select the appropriate options.
dialog box.
click Commit

The example below specifies that all Visit Actions per Location (including power
actions in this case) will be combined:
Example of combining actions and action costs
Defining Costs for Objects and Actions

On the Cost per Object/Action tab, you can use object and action costs if, during
optimisation, you want each change considered by the Optimiser to incur a cost, in
terms of budget. This corresponds to the expenditure required in each object or action
category to implement the recommended change.
In essence, these options enable you to define object and action-related targets and
costs, so that they can be considered in an optimisation.
These may be, for example:
Object costs for changes in the number of:
Properties
Sites
Cells
Antenna devices
Action-related costs for number of changes involving, for example:
Antenna azimuth
Mechanical downtilt
GSM PA Output
UMTS Max TX Power
CDMA2000 Pilot Power

EV-DO Rated PA Power
WiMAX TX Power
LTE Max TX Power
If you also have the Financial Analysis module installed, when you run an
analysis or optimisation, these costs are included in the 'Expenditure' metric, in
addition to any specified financial (CAPEX/OPEX) costs. For more information, see
the Financial Analysis User Reference Guide.
To define costs for objects and actions:
ADVANTAGE toolbar.
3 Click the Cost per Object/Action tab.

4 Expand the required category (Combined, Antenna, Power or Grid), then expand
the appropriate object or action, and then expand Budget.
For more information about the combined category, see Defining Combinations of
Actions on page 76.
To expand or shrink any of the trees, select an object and press the * or - key, or
if you are using a laptop computer, press the Fn and * or - keys.
5 In the appropriate Values column, double-click a value and edit the Cost, as
required.
dialog box.
click Commit

About the Available Object and Action Costs
The following tables summarise the object/action costs that you can configure:
For Antennas
This Parameter Refers to the Costs of
Azimuth Changes to the antenna azimuth.
Mechanical Downtilt Changes to the antenna mechanical downtilt.
Height Changes to the antenna height.
Pattern (remote adjustable electrical Changes to the electrical downtilt of the antenna, where the adjustment can be
downtilt) performed remotely.
In the Cellular Antennas dialog box, on the Info tab, you can specify how the
pattern can be adjusted. If an antenna used on a cell is set to 'Remote', the
Optimiser considers this action as a remote adjustment.
Pattern (site adjustable electrical Changes to the electrical downtilt of the antenna, where the adjustment requires a
downtilt) site visit.
In the Cellular Antennas dialog box, on the Info tab, you can specify how the
pattern can be adjusted. If an antenna used on a cell is set to 'Swap' or 'Switch', the
Optimiser considers this action as an onsite adjustment.
Device Changes to the antenna device. This specifically relates to the addition,
replacement or removal of an antenna.
A device action will take precedence over a pattern, mechanical downtilt or

azimuth action on the same site, and will be the only action considered.
Antenna Unit Changes to the total number of antennas.
This represents the (generic) financial burden that may be imposed by changes to
the respective total numbers of antennas in an optimised plan.
For Power
PA Output Changes to the PA output power of a GSM cell.
BTS Type Replacing a BTS type (GSM only).
UMTS Max TX Power Changes to the maximum TX power of a UMTS cell.
UMTS Pilot Power Changes to the pilot power of a UMTS cell.
HSDPA Power Changes to the HSDPA power of a UMTS cell.
Only relevant to a service-based optimisation.

UMTS Max DL Power Per Changes to the maximum power per user of a UMTS cell.
Connection
UMTS All Power Settings Changes to all of the UMTS cell power settings described above (including
HSDPA).
Node Type Replacing a Node Type (UMTS only).

CDMA2000 Pilot Power Changes to the pilot power of a CDMA2000 cell.
EV-DO Rated PA Power Changes to the rated PA power of an EV-DO cell.
Fixed WiMAX TX Power Changes to the TX power of a Fixed WiMAX cell.
Mobile WiMAX TX Power Changes to the TX power of a Mobile WiMAX cell.
LTE Max TX Power, Traffic Offset, Changes to the maximum TX power of an LTE cell.
Control Offset, Synchronisation
Offset, Broadcast Offset, Multicast Changes to the Offsets (Traffic, Control, Synchronisation, Broadcast, Multicast) of
Offset, Reference Signal SNR an LTE cell.
Threshold, Max TA, Max Range. Changes to the Thresholds (Reference Signal SNR, Max TA, Max Range) of an
LTE cell.
LTE All Power Settings Changes to all of the LTE cell power settings described above.
For Grid
Property Unit Changes to the total number of nominal Properties.

Property Changing (moving or removing) a nominal Property.
Site Unit Changes to the total number of nominal sites.
Site Changing (moving or removing) a nominal site or adding a candidate site.
Cell Unit Changes to the total number of nominal cells.
Cell Changing (moving or removing) a nominal cell or adding a candidate cell.
For Property Unit, Site Unit and Cell Unit, this represents the (generic) financial
burden that may be imposed by changes to the respective total numbers of
Properties/sites/cells in an optimised plan.
For Combined
Location Combined changes (such as the antenna device or azimuth) to the network objects
in a location.
Property Combined changes (such as the antenna device or azimuth) to the network objects
on a Property.
Site Combined changes (such as the antenna device or azimuth) to the network objects
on a site.
Cell Combined changes (such as the antenna device or azimuth) to the network objects
on a cell.

Specifying a Maximum Cost
On the Max Cost tab, you can specify a threshold and associated multiplier for the
Budget cost, if costs have been set up for object/actions.
If the total budget cost of an examined network configuration exceeds the set
threshold, then the budget cost is increased by the specified multiplier. This helps to
ensure that any new network configurations are feasible from a financial point of
view.
To specify a Maximum Cost threshold and multiplier:
ADVANTAGE toolbar.
3 Click the Max Cost tab.

4 Expand the Max Cost, Budget and Cost categories.
5 In the Values column, double-click and edit each value, as required:
 Max (that is, threshold) value
 Multiplier value
dialog box.
click Commit

Setting the Strategy
The Strategy option in the Optimiser Workflow enables you to:

Select the Metrics to be used in the optimisation and set their weightings
Choose to Reject Plans based on any individual metric degradation
Specify the Metrics Synthesis for the optimisation
These parameters enable you to define the factors that will influence optimisations.
The strategy options may vary according to the technology that you are using.
Selecting the Metrics and Weights

On the Metrics Selection/Weights tab, you can define the metrics and weightings that
will be used in the optimisation or analysis.
Example of Metrics Selection/Weights tab
If you have multiple cell layers (GSM) or multiple carriers (all other technologies)
in your network, you can select and weight the Performance components at a 'per
layer' or 'per carrier' level. The Per Layer Calculation option in the Settings (Options
tab) enables you to activate these levels. See About the Options Tab on page 91.

To select the metrics and weights:
ADVANTAGE toolbar.
2 In the left-hand pane, click Strategy.
3 Click the Metrics Selection/Weights tab.

4 Expand the appropriate category.
In the case of the RF category, expand the cost mechanism, metric, technologies,
and layers (if enabled), as appropriate.
5 Select the required metrics and technologies.
When you do this for the first time, the weight automatically defaults to a
value of 1. If you subsequently deselect it, no value is shown and the weight is
zero.
To ensure a particular item is not considered in the optimisation, ensure it is

deselected.
6 For each selected item, double-click the Weight value, and edit it as required (the
corresponding % columns update automatically).
The weightings always total 100% for items that share the same hierarchical
level, are parented to the same item, and are selected.
7 In the case of Coverage, Quality or Dominance, specify Outdoor or Indoor
(representing which array to use).
8 Select the mapping resolution to be used in the optimisation.
9 Specify a Reference Terminal Type (required to generate the arrays).
10 In the Pixel Weighting pane, specify whether the calculation of the optimisation
costs should consider area only, traffic only or both combined. To do this, type a
value in the % Traffic box to define the weighted importance of traffic-specific
calculations for the optimisation; the % Area value is then automatically updated.
The pixel weightings affect the array-based cost mechanism only (in other
words, the service-based cost mechanism is always only traffic-based).
11 In the Mechanism Technologies pane, select the technologies for which you want
the metrics/weightings to be used. You can also specify, as appropriate:
 Maximum number of servers (GSM only) - the number of cells that are
considered as covering cells and interferers.
 Number of covering cells (all other technologies) - the number of cells that are
considered as primary covering cells, handover cells (if appropriate) and
interferers.

dialog box.
click Commit
Rejecting Plans Based on Metric Degradation

On the Max Degradation tab, you can choose to reject plans based on any individual
metric degradation from the starting point of the plan. For any of the metrics, you can
set a maximum degradation threshold in absolute or relative (%) terms.
If you select and set threshold values for any of these metrics (and you select the main
'Reject Plans Based On Metric Degradation' option), the optimiser will not accept any
optimisation states that violate any of these constraints, provided, of course, that the
relevant metrics are also selected on the Metrics Selection/Weights tab.
Example of Max Degradation tab
If you have multiple cell layers (GSM) or multiple carriers (all other technologies)
in your network, you can specify the Performance degradation thresholds at a 'per
layer' or 'per carrier' level. The Per Layer Calculation option in the Settings (Options
tab) enables you to activate these levels. See About the Options Tab on page 91.
All the options are independent. For example, you could choose to select 'Array-
based' without also selecting 'RF', and you could select 'Coverage' without also having
to select 'Array-based'. Alternatively, you could choose to prevent the 'Array-based'
category degrading too much without specifying thresholds on any individual sub-
categories (such as Coverage or Quality). Each selected option would have an
influence on the optimisation process.

To set a threshold:
ADVANTAGE toolbar.
3 Click the Max Degradation tab.

4 Select the 'Reject Plans Based On Metric Degradation' option.
5 Expand the appropriate category.
In the case of the RF category, expand the cost mechanism, metric, technologies,
and layers (if enabled), as appropriate.
6 Select the appropriate items.
7 For each item, you can choose to set the threshold as an ABSOLUTE degradation
of the starting cost value, or as a RELATIVE (%) degradation of the starting cost
value.
You can change from one to the other by clicking the appropriate row in the Max
Degradation column, and using the drop-down box.
For example, if you have a starting cost value of 20:
 An absolute threshold of 5 would mean that configurations with costs =< 25
(for that metric) would be considered
 A relative (%) threshold of 10 would mean that configurations with costs =< 22
(for that metric) would be considered
8 Type the value for the maximum degradation threshold.
In the example, an Array-based threshold has been set, which specifies a
degradation threshold of 10% relative to the initial cost. So if the initial cost for
that component was 3%, then any configurations with costs equal to or less than
3.3% would be considered.
dialog box.
click Commit
You can turn this plan rejection method On/Off by using the 'Reject Plans Based
On Metric Degradation' checkbox (the individual selections and thresholds are still
stored).

Defining the Metrics Synthesis
On the Metrics Synthesis tab, you can:
Define the metric multipliers
Select the metrics prioritisation
Example of Metrics Synthesis tab
Metric Multipliers
These enable you to normalise the units used for the different metric categories, so
that the respective units can be considered in the optimisation on a common basis (the
RF cost category does not really refer to a specific measurable unit; it is an abstract
number or percentage).
The multiplier values indicate the scale used to represent the following parameters:
Budget, which is defined in a single currency
Financial (if licensed), which is defined in a single currency
RF, based on the array-based and service-based cost mechanisms
The way that you define the multipliers will have a significant impact on the
optimisation. You should ensure that all of the values are correct before proceeding.
For example, suppose you are using the Budget and RF metrics in an optimisation,
where the budget has been defined in Euros. If you know or assume that 10,000 Euros
of expenditure is equivalent to an RF cost of 1 unit, then the multiplier values should
be 1 for Budget, and 10,000 for RF.

Metrics Prioritisation
This enables you to determine how the metrics and multipliers are considered in the
optimisation.
You can select one of these options:
Option Description
Weighted Sum of All Metrics All the metrics selected and weighted on the Metrics Selection/Weights tab will
be considered in each optimisation iteration.
Worst Performing Metric Only Only the worst performing overall metric (Budget, Financial or RF) will be
considered in each optimisation iteration.
To define the options on the Metrics Synthesis tab:
ADVANTAGE toolbar.
3 Click the Metrics Synthesis tab.

4 Double-click the multiplier value(s) that you want to edit, and type the new
value(s).
5 Select the required metrics prioritisation option.
dialog box.
click Commit

Setting Traffic Options
The Traffic option in the Optimiser Workflow enables you to:

Select or view the list of terminal types to be used in an optimisation
Load Cached Traffic Arrays
These options are relevant if you want to consider traffic in your optimisations.
Even if you do not consider traffic, you still need to specify a Reference Terminal
type. You can do this on the Metrics Selection/Weights tab of the Strategy page.
Selecting the Terminal Types

On the Terminal Types tab, you can select (or view) the list of terminal types to be
used in an optimisation.
This is not required for an area-based analysis/optimisation, nor for network data
spreading.
To do this:
ADVANTAGE toolbar.
2 In the left-hand pane, click Traffic.
3 Click the Terminal Types tab.

4 Select (or view) the required terminal type(s) from the list displayed.
dialog box.
click Commit

Loading Cached Traffic Arrays
The Cached Traffic tab, which relates to network data spreading, is available for
GSM and UMTS only.
On the Cached Traffic tab of the Settings, you can load any cached traffic arrays. This
is because whenever you spread network data, the resulting traffic array is stored,
which means you do not have to create the same array again. For more information,
see About Spreading Network Data on page 201.
To load a cached traffic array:
ADVANTAGE toolbar.
2 In the left-hand pane, click Traffic.
3 Click the Cached Traffic tab.

4 In the dialog box that appears, select the Use Advantage Traffic checkbox to
enable the use of the arrays that are selected in the Cached Traffic Arrays pane.
Select the Use Cell Traffic Offset Values checkbox if you want to use these
values in optimisations, analyses and problem cell identification.
5 Right-click the required traffic array and select Load Ticked Traffic Arrays.
The selected arrays are loaded into memory.
To delete a cached array:
Right-click the required cached traffic array and select Delete Array. This is only
available if the array is not selected.
ENTERPRISE Traffic Arrays

As an alternative to cached traffic arrays, you can load ENTERPRISE traffic arrays
using the Array Manager. To do this:
1 Ensure you clear the Use Advantage Traffic checkbox.
2 From the Arrays menu, click Array Manager, and select the required arrays.
For more information on using the Array Manager, see the ASSET User Reference
Guide.

Specifying the Settings
The Settings in the Optimiser Workflow enable you to:

Set additional parameters and options related to optimisations, analyses and
spreading network data
Set the array-based options and parameters
Specify the parameters and options that relate to the Auto Plan Setup method of
creating an optimisation plan
Choose which network element status field you want to use to represent new cells
in your project
The settings options may vary according to the technology that you are using.
Configuring General Options and Settings

On the Options tab, you can specify a variety of options and settings.
This picture shows an example of part of the Options tab:
Example of Options tab
To define the options:
ADVANTAGE toolbar.
2 In the left-hand pane, click Settings.
3 Click the Options tab.

4 Set the required options for the appropriate technology, as described in the
following section.

dialog box.
click Commit
About the Options Tab

This table describes the available settings on the Options tab:
From This Category This Option Enables You To
Quality Metric Definition Only consider: Set the Quality metric cost calculations to consider only the
CINR (GSM) signal to interference ratio or signal quality ratio (appropriate to
Pilot Ec/Io (UMTS, the technology).
CDMA/EV-DO) If you do not select this option, the Quality metric cost
DL CINR (Fixed WiMAX) calculations consider this ratio and Signal Strength together.
Preamble CINR (Mobile
WiMAX)
RSRQ (LTE)
Problem Cell Weights Use Problem Cell Weights Prioritise actions (changes) to cells of (measured or predicted)
poor performance during the optimisation.
You can use Problem Cell Identification to help you

prioritise actions.
Shared Antenna Prevent for inter cell layer (GSM) Choose to not allow device or pattern variation for implicitly or
Device/Pattern ID Variation antenna sharing explicitly shared antennas that belong to different cell layers
(GSM).
Prevent for inter-technology Choose to not allow device or pattern variation for implicitly or
antenna sharing explicitly shared antennas that belong to different
technologies.
Shared Antenna Consistency Enable consistency checks for Check the consistency of co-location parameters for implicitly
Checks implicitly shared antennas shared antennas.
By default, this option is unselected. This default is strongly
recommended if your network models multiple separate
(For more information on shared physical antenna devices in one approximate location. The
antennas in ENTERPRISE, see default option means that consistency checks are NOT
How the Optimiser Considers performed, which gives more freedom to the optimisation
Shared Antennas on page 138). process.
If, however, you decide to select this option, then an
ADVANTAGE optimisation will not run unless the mechanical
downtilt and, optionally*, the pattern ID of implicitly shared
antennas are consistent in the plan.
* This is conditional on the Shared Antenna Device/Pattern ID
Variation setting.
Modification Strategy Only modify problem cells and Set the optimisation to only modify problem cells and their
their neighbours with plan status neighbours (if their status is set to 'plan'). For more
information, see Identifying Problems in a Network on page
179.

From This Category This Option Enables You To
Grid Planning Apply Grid Planning to DB Choose to save the results for site or sector selection directly
to the database when you Apply an optimised plan.
However, if you do not want to lose the associated cell
parameters, you should leave this option unselected, and use
the Set Active Cells to Selection Filter option, described in
Using the Context Menu on page 119.
GSM CINR Calculation Calculate GSM CINR Analyse and optimise the interference in GSM networks
independently of current independently of the currently applied frequency plan.
frequency plan.
Optimisations and analyses for GSM that use the Quality
metric are based on the calculated average CINR in the
network. By default, this is derived from the frequency plan
currently applied in the Site Database.
This option enables you to do this independently of the
currently applied frequency plan. This is achieved by
temporarily removing any current frequency plan, replacing it
with a single carrier allocation on all subcells, and
automatically reducing the CINR threshold by 15dB.
This option should be enabled if your project does not

contain a frequency plan. It is completely independent of
carriers and carrier layers, and does not even require these to
exist in the project.
Per Layer Calculation Calculate costs and statistics per
layer This option is only relevant if you have multiple cell layers
(GSM) or multiple carriers (all other technologies).
If you have a multi-layered network, and you wish to evaluate
each layer with a different set of threshold values, you should
select this option. When selected, the option activates:
'per layer' tabs in the RF Array Thresholds for Clutter and
Vectors, enabling you to specify 'per cell layer' or 'per
carrier' values
'per layer' RF settings on the Max Degradation tab on the
Strategy page of the Optimiser Workflow
‘per layer’ cost breakdowns in the Cost Details dialog box
during optimisations
‘per layer’ statistics in the Optimisation and Analysis
Reports
If, on the other hand, you have a multi-layered network and
you wish to evaluate the overall network (that is, across all
layers at a 'per technology' level), you should not select this
option.
Simulator Speed Run Simulator in memory- Service-based optimisations and analyses, are, by default, run
optimised mode in speed-optimised mode, which can have an impact on the
memory used.
If you prefer to use the memory-optimised mode (lower speed)
option, select this option.
Workflow Display Use Windows Colour Scheme Use the Windows colour scheme for the Optimiser Workflow
dialog box and the Optimiser progress bar.
The settings options vary according to the technology that you are using.

Configuring Array Settings
On the Array Settings tab, you can specify the array-based parameters and options.
ADVANTAGE toolbar.
3 Click the Array Settings tab.

4 Set the required options for the appropriate technology, as described in the
following section.
dialog box.
click Commit

Specifying the Array Settings for GSM
This table describes the GSM array-based parameters and options on the Array
Settings tab:
To edit the parameters, double-click the appropriate item in the Values column.
Number of Snapshots A snapshot represents an individual component within the simulation process. For each
snapshot, specified densities of user terminals are positioned in statistically determined
locations. The ability of each terminal to make its connection to the network is calculated
through an iterative process. The performance of the network is then analysed from the
averaged results.
Max Power Change (%) Set the Max. Power Change (%) convergence parameter to set the 'stabilisation' target for
each snapshot. This limits the number of iterations per snapshot.
If the percentage change in total uplink and total downlink interference (summed over all
cells) changes by an amount smaller than this target value for 15 consecutive iterations, then
the iterations are deemed to have converged.
Only Scan Where Traffic Exists If you want to only scan pixels where traffic exists (a valid traffic raster must be in memory),
select YES.
GSM Dominance Threshold The simulation can calculate the average number of 'polluting cells' at any location, as
determined by the threshold that you set here (xdB).
This threshold determines the relative margin below the best server within which a cell
qualifies as a polluter.
The exact definition of polluting cells for GSM in ASSET is:
The number of cells (from any cell layer) providing an RSS level within xdB of the best RSS.
The threshold is relative. The default value is 40dB.
Best Server: If you want to consider any priorities that have been set in the Cell Layers dialog box, and the
Use Priorities and Offsets signal offsets, when determining the better serving sub-cells, select YES.
If this is set to NO, the best server results are based on signal strength alone.
Best Server: If you want to use generic values for Minimum Service Level and Maximum Timing Advance,
Override Sub-Cell specific select YES, and then specify the two generic values.
values
If this is set to NO, the best server results are based on Signal Threshold and TA Threshold
set specifically for each sub-cell on the General tab of the Site Database.
Cell Traffic Calculation Method Select 'Snapshots' if you want the traffic-loading of the cells to be calculated by the Simulator
by running snapshots.
Select '100% Load' if you want to model a fully loaded network (without running snapshots).
Per Carrier Analysis: If you want to restrict the serving sub-cells to those that have been assigned a specific
Carrier Number carrier, select YES in the Per Carrier Analysis parameter, and then specify a number in the
Carrier Number.
Channel Selection Method You can select what type of interference you want to be considered for the interference
arrays, in terms of Co- and/or Adjacent channels.
Adjacent Channel Offset You can set the value for adjacent channel offset which is used to calculate interference.
Use Frequency Hopping If you want to scale the interference levels by the Fractional Load of the interferer when
generating interference arrays, select YES.
Use Frequency Diversity If you want to add a gain to the serving cell signal to simulate the diversity improvement in C/I
(related to the number of hopping frequencies), select YES.
Use DTX If you want to use DTX factors when creating interference arrays, select YES.
Use Antenna Hopping If you want to scale the interference levels by the Antenna Hopping gain, (where enabled on
the cells), select YES.

Specifying the Array Settings for UMTS
This table describes the UMTS array-based parameters and options on the Array
Settings tab:
averaged results.
Intra-Site Correlation Coefficient The correlation between fades (for a terminal) to cells on the same node.
Inter-Site Correlation Coefficient The correlation between fades (for a terminal) to cells on different nodes.
If the percentage change in total uplink and total downlink interference (summed over all cells)
changes by an amount smaller than this target value for 15 consecutive iterations, then the
iterations are deemed to have converged.
select YES.
Pilot Pollution Threshold The simulation can output an array that shows the average number of pilot polluters at any
location, as determined by the threshold that you set here (xdB).
This threshold determines the relative margin below the best Ec/Io within which a cell qualifies
as a pilot polluter.
The exact definition of pilot polluters for UMTS in ASSET is:
The number of cells not in the active set, but providing an Ec/Io level within xdB of the best
Ec/Io in the active set. The threshold is relative. The default value is 6dB.
Power Control Standard The error due to imperfect power control in dB, which can be used to influence the simulation
Deviation results. It is recommended that this parameter is set to zero.
In a real network, imperfect power control produces a (log-normal) distribution of achieved
Eb/No values for successfully served terminals. One consequence might be a higher uplink
noise rise. If a non-zero value is entered here, the simulation models this effect by including
uncorrelated log-normal errors on the UL and DL transmit powers. Errors are applied only after
all other handover gains and margins have been considered.
Chip Rate The chip rate of the system to be simulated. This value is used in combination with the service
bit rate to calculate the processing gain for a service.
Orthogonality Factor per Clutter If you have specified values for orthogonality per clutter type in the Clutter Parameters dialog
Type box, you have the option here to enable them to be used in the simulation. To do this, select
YES.
If this is set to NO, the orthogonality factor used by the Simulator is the generic value on the
Cell Params tab in the Site Database.
HSDPA Scheduling You can select one of the scheduling strategies: Round Robin, Max Ec/Io, or Proportionally
Fair.
Only the terminals that support HSDPA will be sorted, even if they do not end up using an
HSDPA bearer.

HSDPA Dynamic Power If you want to use HSDPA Dynamic power allocation, select YES.
Allocation
If this is set to NO, the simulation will use Non-Dynamic power allocation.
The HSDPA power for a cell is specified on the Cell Params tab in the Site Database.
If you use Non-Dynamic, an HSDPA user (or a number of users if code multiplexing is
enabled) will be served with the HSDPA Power value, regardless of their location relative
to the cell.
If you use Dynamic, HSDPA users will be served either with the HSDPA power value, or
(if it is lower) the available power on the cell. Therefore, with this method, you should
ensure that the HSDPA power value is set accurately.
Use Neighbour Lists If you want to restrict handovers to your defined neighbours, select YES.
If this is set to NO, handovers can potentially occur between any cells.
Specifying the Array Settings for CDMA2000 or EV-DO

This table describes the CDMA2000 or EV-DO array-based parameters and options on
the Array Settings tab:
averaged results.
Intra-Site Correlation Coefficient The correlation between fades (for a terminal) to sectors on the same site.
Inter-Site Correlation Coefficient The correlation between fades (for a terminal) to sectors on different sites.
sectors) changes by an amount smaller than this target value for 15 consecutive iterations,
then the iterations are deemed to have converged.
select YES.
Pilot Pollution Threshold The simulation can output an array that shows the average number of pilot polluters at any
location, as determined by the threshold that you set here (xdB).
This threshold determines the relative margin below the best Ec/Io within which a cell qualifies
as a pilot polluter.
The exact definition of pilot polluters for CDMA2000 or EV-DO in ASSET is:
The number of sectors not in the active set, but providing an Ec/Io level higher than xdB. The
threshold is absolute. The default value is -15dB.
Power Control Standard The error due to imperfect power control in dB, which can be used to influence the simulation
Deviation results. It is recommended that this parameter is set to zero.
In a real network, imperfect power control produces a (log-normal) distribution of achieved
Eb/Nt values for successfully served terminals. One consequence might be a higher uplink
noise rise. If a non-zero value is entered here, the simulation models this effect by including
uncorrelated log-normal errors on the UL and DL transmit powers. Errors are applied only after
all other handover gains and margins have been considered.
Orthogonality Factor per Clutter If you have specified values for orthogonality per clutter type in the Clutter Parameters dialog
Type box, you have the option here to enable them to be used in the simulation. To do this, select
YES.

Use Neighbour Lists If you want to restrict handoffs to your defined neighbours, select YES.
If this is set to NO, handoffs can potentially occur between any sectors.
Use CDMA2000 Clusters If you want to restrict handoffs to your defined neighbours, select YES.
If this is set to NO, handoffs can potentially occur between any base stations.
This is also applicable to EV-DO.

EV-DO Scheduling You can select one of the two scheduling strategies: Round Robin or Max Ior/Ioc.
Specifying the Array Settings for WiMAX

This table describes the WiMAX (Fixed or Mobile) array-based parameters and
options on the Array Settings tab:
averaged results.
cells) changes by an amount smaller than this target value for 15 consecutive iterations, then
the iterations are deemed to have converged.
select YES.

Specifying the Array Settings for LTE
This table describes the LTE array-based parameters and options on the Array
Settings tab:
averaged results.
If the percentage change in total uplink and total downlink interference (summed over all cells)
changes by an amount smaller than this target value for 15 consecutive iterations, then the
iterations are deemed to have converged.
select YES.
Configuring the Settings for Auto Plan Setup

On the Auto Plan Setup tab, you can specify the parameters and options that relate to
the Auto Plan Setup method of creating an optimisation plan. The settings under this
tab are used by the cell identification algorithm which is used within the Auto Plan
Setup process.
For information on this method, see Using the Auto Plan Setup Method to Create a
Plan on page 115.
The options may vary according to the technology that you are using.
1 Within the left-hand pane of the Optimiser Workflow, click Settings.
2 On the Auto Plan Setup tab, set the required options for the appropriate
technology, as described in the following topic.
dialog box.
click Commit

About the Auto Plan Setup Tab
This table describes the available settings on the Auto Plan Setup tab:
The options may vary according to the technology that you are using.
Parameters Description
Handover Hysteresis Margin This margin is used to determine which cells interact with other cells in each pixel.
For example, if the margin is set to 3dB, an interacting cell can be defined as 'a cell
whose signal strength is within 3dB of the Best Serving signal at that pixel'.
For each pixel, the threshold parameter/s (in next row) must also be satisfied.
Signal Threshold (GSM) Only pixels containing values (signal strengths or quality, as appropriate) equal to
or higher than the threshold will be included, providing the Search Area Margin is
Signal & Quality Thresholds (all other also satisfied.
technologies)
All pixels below the threshold will be excluded.
In the case of UMTS, CDMA/EV-DO, WiMAX and LTE, the signal and the
quality thresholds must both be satisfied.
Neighbour Planning margin (dB) Within the search area, on a pixel-by-pixel basis, the wizard finds potential target
cells. The difference between the power of the source cell and target cell is
calculated. This value is then compared to the margin, and the difference is
converted into an interaction probability factor (based on a normal distribution
formula). These factors are summed to find the net interaction probability for each
target cell on the whole search area. Based on the qualifying criteria (in the next
rows), the wizard creates a list of valid target cells for each source cell.
Maximum number of covering cells The maximum number of target cells that are considered at each pixel during the
calculations. On a pixel-by-pixel basis, this parameter determines how many 'sets'
of covering cell data is to be evaluated for potential interacting cells.
Maximum distance In order to qualify as a valid target cell, a target cell must be within this specified
distance.
Maximum number of neighbouring cells The maximum number of target cells that can qualify as valid interacting cells for
the source cell. (The overlapping percentage ranking determines which cells
qualify).
In the case of LTE, this value comes from the cell-specific values defined on
the Neighbours tab in the Site Database.
Minimum number of neighbouring cells This option can be used to ensure a minimum number of interacting cells for each
source cell, even if the percentage (in next row) is not attained. This parameter is
activated by the associated checkbox.
All the supporting criteria must also be satisfied.

Minimum overlapping (%) A target cell must attain at least this percentage of the overlapping area to qualify
as a valid interacting cell.
If you also select the 'Minimum number of interacting cells' option, this means that if
the number of valid interacting cells (>n%) is less than the specified minimum
number, other target cells (<n%) will be added as valid interacting cells, until the
minimum is satisfied.
All the supporting criteria must also be satisfied.

Standard Deviation (dB) Enables you to set a specific standard deviation for the signal strength/quality (as
appropriate). This parameter is activated by the associated checkbox, otherwise
the propagation model value is used.
Make co-located cells neighbours If you select this option, cells that exist on sites belonging to the same Property will
automatically qualify as valid interacting cells.

Specifying a Field to Differentiate New/Existing Elements
In most situations, you will want ADVANTAGE to recommend a better network plan
which is based primarily on your starting network.
Where this is the case, the Element Status tab on the Settings page is very important,
because it enables you to:
1 Choose which status field you want to use to differentiate between:
 New elements
 Existing elements
The network element types that can be associated with your chosen status field
are: Cell, Site, or Property. The field type to be used can be Pick-list or Boolean.
2 Control whether such elements are ON or OFF at the creation of a plan.
This functionality can provide several benefits:
Improved Selection Planning: The Optimiser can start from a realistic snapshot of
the existing network, because new elements will not be initially switched 'ON'.
Improved Cost Modelling: The Optimiser can discriminate between new and
existing elements when it considers action costs (for actions such as azimuth
changes) - only existing elements can incur such costs.
Improved Cost Comparisons: You can compare the cost/benefits of turning 'ON'
new cells, and/or switching 'OFF' existing cells.
If you have a licence for the Financial Analysis module, there are additional
benefits. For more information, see the Financial Analysis User Reference Guide.
If you do not use this differentiation, all your network elements will be
considered as existing.
Status fields represent a very crucial part of ENTERPRISE, and can be used for a
variety of reasons, for example to track the network deployment phase of network
elements. It is probable that your project administrator has already set up most of the
fields for your project.
If you want to use this functionality, you should request that your administrator sets
up a special field dedicated for this purpose (unless your organisation has already
decided to use one of the existing fields for this).
A simple example would be a field named 'State (Existing or New)' with Pick-list
options of 'Existing' and 'New'.
For information on how to set up fields, see the ENTERPRISE Installation and
Administration Guide.

Assuming your administrator has set up or designated a field for this purpose, this is
how you activate it to differentiate between new and existing elements:
ADVANTAGE toolbar.
3 Click the Element Status tab.

The drop-down list displays all the Pick-list or Boolean fields that have been
created for the project by your administrator.
4 From this list, select the field that you want to represent the element status. This
picture shows an example:
5 In the State pane, select the field state(s) that you want to indicate a new element.
Here is an example:
6 Select the respective checkbox(es) if you want your new and/or existing network
elements to be initially considered as OFF when creating a new plan.
A plan can include both new and existing network elements; the purpose of these
options is to enable you to specify one or both categories as OFF.
If you do not select either option, the created plan will initially consider all
elements as ON (in effect, it makes no distinction between new and existing
elements).

Here are some examples of when you might find these options useful:
If You Want to Achieve an You Can Perform These Steps
Optimised Network Plan
Where the plan's starting point is a true 1. Select the 'New network elements...OFF' checkbox:
representation of the real-life starting point, such that
the proposed new network elements are not yet built.
This can be used as a baseline plan to compare with
other plans which model the new elements as built.
2. Create your plan.

3. Run an optimisation.
Where the plan's starting point is independent of the 1. Select the 'Existing network elements...OFF' checkbox:
real-life network.
This enables you, for example, to model a plan
where existing elements have all been
decommissioned, allowing a totally new network to
be evaluated.
Where the plan's starting point has all the elements 1. Select both of these checkboxes:
set to OFF.

Where the plan's starting point has all the elements 1. Select neither of these checkboxes:
set to ON.

It is possible for the new/existing status field to be different between parent-child

elements in the Site Database. When you run an optimisation, these differences are
respected unless the status of the parent element is new, in which case all its child
elements are considered as new too. For example, if a Property has a status of new,
then all its sites and cells will be considered as new. If a site has a status of new, then
all its cells will be considered as new. This logic allows an optimisation to respect, for
example, a configuration of an existing Property containing an existing site and a new
site, or an existing site containing existing cells and new cells.
All changes that you make on this tab are automatically saved to the database in the
Applied state, and the changes will persist when you close the Workflow dialog box.
If you want to restore the options on this tab to the previous committed state (if
such a state exists), click Restore
If you want to share the changes on this tab with all other users, click Commit

Globally Committing All Your Changes
If you want to Commit all your changes in the Optimiser Workflow, you can use the
Global Commit All option from the main menu.
This will Commit all the Applied parameters in the workflow, such as the RF Array
Thresholds, Settings and so on.
This action will also Commit all the Applied changes in the ASSET tool, not only
in the Site Database, but also in all other dialog boxes.
To do this:
From the Database menu, click Global Commit All:
If other people are logged into the same database as you, it is possible that they have
Committed changes to network element(s) that you are now trying to commit. If this
happens, you are prompted either to cancel the Commit or to continue, overriding
their Committed data with your own changes.

Selecting Report Formats
ADVANTAGE enables an organisation to configure its own presentation styles for the
following (licence-dependent) reports:
Analysis report
Optimiser report
Rollout Planning report
Financial Analysis report
Financial Analysis (Difference Method) report
The last two report types depend on a Financial Analysis licence.

This can be done using report formats that can be configured and managed by your
administrator. For information on this, see the ENTERPRISE Installation and
Administration Guide.
If such formats have been configured, an individual user can determine the 'mapping'
of the required report format to each ADVANTAGE report type.
A default set of formats already exists in any new project. These formats are
already mapped to each report type, so if you are satisfied with the default reports,
you do not need to do anything (neither in ENTERPRISE Administrator nor in
ADVANTAGE).
If you need to view or modify the mapping relationships, you can use the ACP &
Financial Analysis Reports Assignment dialog box.
To open this dialog box:
From the Reports menu, click ACP & Financial Analysis Reports Assignment.

The ACP & Financial Analysis Reports Assignment dialog box appears:
To change the mapping relationship for a report type:

1 For the appropriate report type, click in the Report Name column.
2 In the drop-down list, select the required report name (this is only meaningful if
multiple formats have been made available for the report type).
3 Repeat the above steps if you want to modify any other mapping relationships.
4 Click Close.
The reports will automatically be output in the chosen format when they are next
generated.
You can check the basic details of the currently mapped report formats by selecting
the report type and clicking the 'Info...' button.

CHAPTER 5
Using and Managing Plans

pane.
This chapter focuses on how to use the Plan Manager, which controls the Plans and
Delta Plans output by the optimisation engine.
- or -

The first workflow item is the Plan Manager.
The Plan Manager enables you to perform a number of Plan-related operations:

View and use existing Plans
Create new Plans
View and Edit Action-Constraints
Analyse the performance of any Plan, or compare Plans
Start/Run Optimisations
Delete Plans
Temp Apply/UnApply
Apply to Database
There is also a context menu, which you can access by right-clicking on the
icon of the appropriate Plan. This provides quick access to the same options as most
of the main buttons, but also provides extra options. For more information, see Using
the Context Menu on page 119.

When you are using the Optimiser Workflow for the first time, you need to set up
the general parameters, strategy, settings, and so on, before you run any
optimisations. These may include:
RF Array Thresholds
RF Metric Targets
Costs/Limits
Strategy
Traffic
Settings
However, this depends whether you have the appropriate user permissions. Parts of
this process may not be relevant to the general user, and it is possible that the above
options and parameters are centrally specified within the user's organisation.
About the Concept of Plans in ADVANTAGE

There are two 'categories' of plan in ADVANTAGE:
Plan
Delta plan
However, in essence, the two types of plan, once created, can be considered to be the
same. This is because, in general terms, you can perform similar operations using a
plan of either category, and you can choose to Apply any of these plans to the
database.
Here are some basic principles:
Before you can start an optimisation, you must have at least one plan created. For
more information, see Creating Plans for Optimisation or Analysis on page 110.
Plans are created by way of a 'snapshot' from the current Site Database (this is the
only way a 'new' plan can be created). During that process, you can choose to
restrict the scope of the plan in terms of (i) region, (ii) sites/nodes/cells, and (iii)
vectors/drive test routes, by using the options in the Plan Wizard. At the end of
that process, the plan appears within the Plan Manager list.
Plans and delta plans are listed in the Plan Manager section of the Workflow
dialog box.
Delta plans can only emanate from a plan, and they must always be 'parented' to a
plan, since they represent changes to the starting plan.
When you run an optimisation for the plan, the delta plans appear as 'children' of
the parent plan.
Plans are categorised by the icon. Delta plans are categorised by the icon.

This picture shows an example of how plans and delta plans are listed in the Plan
Manager:
Viewing and Using Plans in the Plan Manager

When you are viewing plans, there are three viewing options:
These options are visual 'filters' that help you to distinguish which plan(s) you are
working with.
The 'Created By Me' option always lists the plans that you (the logged in User ID)
have created.
The 'All Plans' option always lists all existing plans, regardless of who created them.
The 'Used' option requires a more detailed description:
The concept behind the 'Used' option is that, generally speaking, only one individual
would be working with a particular plan at any one time. This would avoid 'multi-
user' problems if you are intending to work iteratively with a plan, making
progressive changes toward a new plan which has the potential to improve the
quality of your network.
However, it is possible, if required, for a plan to be 'used' by more than one person.
When this is the situation, the Action-Constraints are viewable but not editable, and
the plan cannot be deleted.
When you create a plan, it automatically becomes 'used' by you. However, it is
possible to turn this status on/off, using the Toggle option in the context menu. In a
similar way, any user who did not create the plan, can use the Toggle option to
activate his/her 'used' status for that plan. The option can therefore be used to hand
over the 'use' of the plan to a different single user, or (if explicitly required) it can be
used to share the 'use' of the plan amongst multiple users.
In situations where you may want multiple users to work on the same plan, but have
the freedom to edit the Action-Constraints for that plan, you can utilise the Duplicate
option. This enables different users to 'branch off' from the same original plan into
potentially different proposed network plans. It also enables you to work on a copy of
an existing plan, so that you can experiment with different Action-Constraints, while
still retaining the original plan.

Creating a New Plan from a Delta Plan
In situations where you want to work with a plan that emanates from a delta plan,
you can convert any delta plan into a (normal) plan. This enables you to work with a
plan whose values are equivalent to how they stood at the latest stage of the delta
plan, and then you can edit the Action-Constraints (this is not possible in a delta
plan). You can then run a secondary optimisation from the point already reached in
the delta plan.
For more information on the context menu, including the Toggle and Duplicate
options, see Using the Context Menu on page 119.
Creating Plans for Optimisation or Analysis

There are two basic methods of creating a plan in ADVANTAGE.
Using the Plan Setup to create a plan
Using the Auto Plan Setup to create a 'recommended' plan
Here is a brief summary of each method:
The Plan Setup method enables you to specify the region and the filters (cells) for
the plan, and then manually assign the appropriate Action-Constraints templates.
It can be launched either from the Workflow, or directly from the Map View. The
latter is quicker and easier if the Map View is already displaying the correct region
and filters.
This method is recommended for users who wish to create plans without any
recommendations from the tool.
The Auto Plan Setup method can automatically recommend the grouping of cells
into filters, and consequently facilitates the assigning of the appropriate Action-
Constraints template to those filters. It can also automatically determine the
geographic area for the resultant plan, by creating a vector. The concept behind
this method is that it can automate some of the pre-optimisation tasks (which
would be done manually when using the Plan Setup method).
This method is recommended for users who wish to create plans helped by
recommendations from the tool.
It can be launched either from the Workflow, or directly from the Map View. The
latter is quicker and easier if the Map View is already displaying the correct region
and cell filters.
A fuller description of this method is included in Using the Auto Plan Setup
Method to Create a Plan on page 115.
If you launch either method directly from the Map View, you should ensure that the
display includes the region and the cells that you want to choose from when creating
the plan.

If you launch either method from the Workflow (Plan Manager), you should ensure
that the display includes the region that you want to use when creating the plan. In
this case, it is possible to choose cells that are not displayed on the Map View, but
they must be located within the region.
Important :
When creating a plan, two of the steps are crucial in determining which cells will
be included: (i) specifying the region and (ii) selecting the site/cell filter(s).
A further (optional) step enables you to select specific vectors and/or drive test
routes, which can be useful if you want to precisely define the pixels that will be
included in the metrics evaluation. This is an important way of focusing the
optimisation calculations, but it does not (for example, in the case of a polygon)
determine which cells are included.
Using the Plan Setup Method to Create a Plan

There are two basic methods of creating a plan in ADVANTAGE. This section
describes the Plan Setup method.
To create a new plan for optimisation:
1 Check that you have a Map View window open that displays the region and cells
that you want to include. (However, if you prefer to enter precise co-ordinates, an
open Map View is not essential.)
2 Open the Workflow by clicking the shortcut button on the main

ADVANTAGE toolbar.
3 In the left-hand pane, select Plan Manager.
4 Click the Plan Setup button, then click the Plan Setup option.
5 In the Plan Wizard that appears, type a name for the plan.
If required, you can select an existing plan as a template. For information on this,
see the following section.
Click Next.

6 Check that the region for the plan is correct. If necessary, you can modify the
region by entering precise co-ordinates.
Click Next.
7 Select one or more filters to determine which sites/nodes and cells are to be
considered in the plan.
Click Next.
8 The next step of the wizard enables you to select the appropriate Action-
Constraints templates on a filter basis.
Anything you edit here can be modified after creating the plan, using the
Action-Constraints dialog box. In fact, if preferred, you can skip this step now, and
do it later, as described in Using the Action-Constraints Dialog Box on page 127.
Use the Add button to specify each filter-template combination. (You can delete a
row by clicking .) Here is an example:
Where appropriate, you can use the up and down arrows to set the filter
priorities. Only one template (per mechanism) can be assigned to a filter.
Therefore, in cases where an object exists in more than one filter in this dialog box,
the filter priority number is important in determining which template is assigned.
If required, you can check the contents of the relevant filter by clicking .

You can edit any of the filter selections and/or template assignments by
clicking in any of the columns. You can also edit any of the Action-Constraints
Templates (in the normal way) by clicking the Manage Templates button.
Click Next.
9 If appropriate to your requirements, restricting optimisation calculations to
vectors can make calculations faster and more focused, by focusing on the
improvement of specific areas and/or drive test routes.
If you want to restrict the optimisation to particular vectors, select the Use Vectors
checkbox and then specify the vectors under the System or User folders, as
appropriate.
- and/or -
If you want to restrict the optimisation and/or analysis to a drive test route, select
the appropriate vectors from the Measurements folder.
You can subsequently modify the restriction selections at any time, by right-
clicking on the plan in the Plan Manager of the Workflow, and selecting Edit
Vectors.
10 Click the Finish button.
There is also a button on the main ADVANTAGE toolbar which enables you to
create a 'Quick Plan' based on an open Map View, enabling you to short-cut some of
the processes. For more information on this, see Creating a Quick Plan from a Map
View on page 114.

Using an Existing Plan as a Template
When you are creating a new plan for optimisation using the Plan Setup Method, you
can choose to select an existing plan as a template for the new plan.
If you do this, the cells to be included in the new plan are still determined by the
region and filters that you select within the Plan Wizard, but the key difference is that
all the action-constraints for cells that exist both in the original 'template' plan and in
the new plan are 'copied' into the new plan. In effect, it copies the action-constraints
for such cells into the Action-Constraints dialog box, but takes a fresh snapshot of the
parameters in the Site Database.
This option may therefore be useful if you have made changes in the Site Database
since creating the original plan, and want to bring those changes into a new plan.
Any cells that were in the original 'template' plan, but not captured by the region
and filters for the new plan, are always excluded from the new plan. Conversely, if
there are cells in the new plan that did not exist in the original 'template' plan, they
would need their action-constraints to be edited in the Action-Constraints dialog box
(in the usual way).
Creating a Quick Plan from a Map View

There is a shortcut button on the Map View toolbar which enables you to create a plan
from a currently opened Map View window.
In effect, this shortcut method simplifies the process of creating a plan with the Plan
Setup Wizard. It relies on the fact that, beforehand, you set up the Map View to show
the correct filters for the sites/nodes and cells, and (if appropriate) the required
vectors/drive test routes.
To use this option:
1 Ensure you have the appropriate Map View open, so that it is displaying:
 The region you want to include
 The cells you want to include
 If applicable, the vectors/drive test routes you want to include
2 In the horizontal toolbar of the Map View, click the 'Plan Setup' button
(alternatively, click on the View and press Ctrl-U).
3 The Action-Constraints dialog box appears, so that you can edit the actions and
constraints for the new plan. For more information, see About the Action-
Constraints Dialog Box on page 124.
4 In the Workflow dialog box, the new plan appears in the Plan Manager list. The
plan name is automatically set, but you can right-click on it and rename it, if
required.
When using this 'Quick Plan' method, any vectors that are visible within the
relevant Map View will automatically be added to the resulting plan definition, but
these vector selections can then be amended.

Using the Auto Plan Setup Method to Create a Plan
There are two basic methods of creating a plan in ADVANTAGE. This section
describes the Auto Plan Setup method.
The Auto Plan Setup method can be considered as an automatic plan-recommendation
system. This method may of be of particular benefit when the interactions between
the cells to be planned are not well known at the time when you are creating the plan.
The concept behind the Auto Plan Setup method is that it can automatically identify
some of the pre-optimisation tasks which would be done manually when using the
Plan Setup method.
In basic terms, you begin with a Map View window which contains your required
region and cells. You then need to specify which cells are your 'main focus'. This
requires that (a) those cells are already in one or more filters, or (b) that you create a
Selection Filter (exists only in memory) on the Map View, using the Selection Expert.
At the stage where the Auto Plan Setup is aware of the 'main focus' cells, it can
recommend the grouping of other cells into 'tiered' filters (using an algorithm based
on user-defined settings). It is then simple to make the appropriate Action-Constraints
template assignments. For example:
Filter Action-Constraints Template selection
Main focus Template allowing significant changes
Recommended (tier 1) Template allowing some changes
Recommended (tier 2) Read-Only
Furthermore, the Auto Plan Setup can then automatically determine the geographic
area that should be taken into consideration during analysis and optimisation of the
resultant plan. The algorithm builds a list of all cells contained within the plan that
have any 'non-Read-Only' Action-Constraints Templates associated with them. It then
finds all pixels where any of these cells provides a signal strength above the relevant
signal threshold defined on the Auto Plan Setup tab of the Settings page in the
Workflow. An enclosed vector (polygon) is then created around all these pixels.
In summary, the main benefits of this method are:
The 'tiered' filters are recommended automatically (and they are independent of
currently existing filters). These tiered filters can be considered as a form of cell
'hierarchy' in terms of what can happen in the optimisation.
This is based on a cell identification algorithm that uses the settings under the
Auto Plan Setup tab in the Settings page of the Workflow. For more information,
see Configuring the Settings for Auto Plan Setup on page 98.
The templates in the Action-Constraints dialog box are assigned based on the
previous sequence of assignments in this dialog box, which creates consistency for
iterative use of the Auto Plan Setup.
You can manually override these recommendations (if you have the relevant
permissions).
The geographic area for the eventual evaluation of the plan can be automatically
determined.

Depending on the planning region size, cell volumes, and map data
resolution, the running of the algorithms for the filters and the geographic area
can take some time.
To create a new auto plan for optimisation:
1 If you intend to use the 'Create Restriction Polygon' option, a valid Reference
Terminal Type must have been specified on the Strategy page of the Optimiser
Workflow.
2 Ensure that you have a Map View window open that displays the region and cells
that you want to include.
3 In the top-right corner of the Map View window, click the Auto Plan Setup button
(alternatively, click on the View and press Ctrl-V).
4 The Auto Plan Setup Wizard appears. Name the plan, and insert any comments.
Click Next.
5 Select one or more filters to define which cells should represent the 'main focus'.
Click Next.
6 The 'Review Recommendations' step of the wizard shows the Focus filter and the
recommended 'Tier 1' and 'Tier 2' filters, each associated with their appropriate
Action-Constraints templates. Here is an example:
You can edit any of the filter selections and/or template assignments by clicking
in the Filter column or in any of the planning mechanism columns. You can also
edit any of the Action-Constraints Templates (in the normal way) by clicking the
Manage Templates button.
You can use the button if you need to specify more filter-template
combination rows, and you can delete rows by clicking .
priorities. Only one template (per mechanism) can be assigned to a filter.
Therefore, in cases where an object might exist in more than one filter in this
dialog box, the filter priority order is important in determining which template is
assigned.
You can check the contents of the relevant filter by clicking .

7 If you want the Auto Plan Setup to automatically determine the geographic
area that should be taken into consideration during evaluation of the resultant
plan, select the 'Create Restriction Polygon' option.
You can only do this if a valid Reference Terminal Type has been specified on
the Strategy page of the Optimiser Workflow.
If you select this option, the Auto Plan Setup will run the restriction polygon
algorithm and store the associated vector.
The new vector subsequently appears in the ACP folder in the Vector Manager
and in the Map View data types list (where it can be visualised).
Click Next.
8 If required, you can restrict optimisation calculations to vectors to make
calculations faster and more focused, by concentrating on the improvement of
specific areas and/or drive test routes.
If you want to restrict the optimisation to particular vectors, select the Use Vectors
checkbox and then specify the vectors under the System or User folders, as
appropriate.
- and/or -
If you selected the 'Create Restriction Polygon' in the previous step, the 'Use
Restriction Polygon' checkbox will be already selected, but you have the option to
deselect it.
- and/or -
If you want to restrict the optimisation and/or analysis to a drive test route, select
the appropriate vectors from the Measurements folder.
You can subsequently modify any of the restriction selections at any time, by
right-clicking on the plan in the Plan Manager of the Workflow, and selecting Edit
Vectors.

9 Click the Finish button.
There is also an option to launch the Auto Plan Setup by clicking the Plan Setup
button (and then the Auto Plan Setup option) on the Workflow dialog box. If you do
this, you need to confirm (or specify) the region and select the site/cell filters. The key
difference is that you can select filters not currently displayed on the Map View.
Differentiating New/Existing Elements
If you use Selection Planning and/or you use Object/Action Costs, the Element
Status tab is very important, because it enables you to choose which status field you
want to use to differentiate between new network elements and existing network
elements. This provides two benefits in plan creation:
Improved Selection Planning: The Optimiser can start from a realistic snapshot of
the existing network, because new elements will not be initially switched 'ON'.
Improved Cost Modelling: The Optimiser only considers action costs (for actions
such as azimuth changes) for elements that already exist.
If you do not use this differentiation, all your network elements will be considered
as existing.
For more information, see Specifying a Field to Differentiate New/Existing Elements
on page 100.

Using the Context Menu
When you are viewing the Plan Manager, there is also a context menu available,
which you can access by right-clicking on the appropriate plan or delta plan. Here is
an example:
Example of Context Menu for Plans or Delta Plans
This not only provides quick access to the same options as most of the main buttons,
but also provides extra options:
Option Available for Description/Comments
Action-Constraints Plans See Using the Action-Constraints Dialog Box on page 127.
Edit Vectors Plans and delta plans Enables you to modify the vector selection for a plan.
Summary Plans Shows the included cells, the planning region (size, location,
resolution).
It also provides an Update 2D View button, which can be

very useful.
Initial Report Plans Shows the current values, and the constraints, of the network
contained in the plan, and the possible network parameter
changes that may be considered in an optimisation (as
appropriate).
Delta Report Delta plans The current values, and the constraints, of the network contained
in the delta plan, and the specific network parameter changes
'proposed' by the Optimiser.
Final Report Delta plans A complete report of the state of the 'optimised' network.
In other words, the current values are replaced by the 'proposed'
values (only in the report, not in the database).

Option Available for Description/Comments
Analysis Plans and delta plans This enables you to run an analysis, in order to evaluate any plan
configuration or compare any two configurations. You can output
associated reports.
See Analysing and Evaluating Plans on page 165.
Financial Analysis Plans and delta plans Perform a financial analysis of your network. This is a licensed
module that can help you make informed network planning
decisions. For more information, see the Financial Analysis User
Reference Guide.
Optimise Plans and delta plans The automatic Optimiser can consider an extensive range of
physical design and network parameter settings in order to
improve the performance of the radio network.
See Running an Optimisation on page 157.
Duplicate Plans This is a useful option in situations where you want to:
Work on a copy of an existing plan, so that you can
experiment with different Action-Constraints, while still
retaining the original plan.
Work on a copy of a plan that is being 'Used' by someone
else, but want the freedom to edit the Action-Constraints for
that plan.
For more information, see Viewing and Using Plans in the Plan
Manager on page 109.
Duplicate Delta plans This is a useful option in situations where you want to work on a
plan which emanates from a delta plan. The key benefits are:
The plan values are equivalent to how they stood at the
latest stage of the delta plan
You can edit the Action-Constraints (this is not possible in a
delta plan)
You can then run a secondary optimisation from the point
already reached in the delta plan
For more information, see Viewing and Using Plans in the Plan
Manager on page 109.
Rename Plans and delta plans A quick way to rename a plan or delta plan. These names must
always be unique within a project.
Delete Plans and delta plans When you delete a plan, its 'child' delta plans are also removed.
However, a delta plan can be deleted individually.
Bookmark Plans and delta plans This simply acts as a 'bookmark', so that you can quickly identify
the plan you have been working on. It also appears as the default
plan in the dialog boxes where you need to select a plan.
Toggle Use Plans and delta plans You can use this option to toggle the 'Used' status of a plan.
The option can be used, for example, to 'release your usage' of a
plan. This may, for example, enable another user to 'obtain the
usage' of that plan.
For more information, see Viewing Plans in the Plan Manager on
page 109.
Set Active Cells to Selection Plans and delta plans This enables you to quickly update (overwrite) the contents of the
Filter Selection Filter with the 'active' cells that are in the selected plan.
For more information about the Selection Filter, see the
ENTERPRISE User Reference Guide.
Refresh Plans and delta plans Refreshes the page.

Viewing Plans in the Map View Window
In addition to viewing plans within the Plan Manager, there are also some viewing
options in the Map View window.
When you have created plans, you can view that region in the Map View. To do this:
1 Ensure you have a Map View window open that will include the planning region
for the plan.
2 Open the Map Information and Control, and select the required plan under the
Plans heading in the Data Types:
3 Click the Apply button.

The planning region is displayed:

4 If required, you can double-click the plan name in the Map Information and
Control, and select a different display colour.
The other items displayed (including the nodes or sites) depend on which other
items are selected in the Data Types (this may also depend whether a Favourite View
has been initially displayed). This plan viewing option does not discriminate in terms
of nodes/sites; it simply visualises the planning region.
About Plan Viewing Options

When you are viewing plans in the Map View, you can use some additional options
in the Map View window.
To access these options:
1 In the Map Information and Control, right-click the required plan:
2 Click the required option. This table describes the options:

Option Description
Plan Summary A summary which lists the included cells, and the planning region (size,
location, resolution).
The summary also includes an Update 2D View button, which can be

very useful.
Apply (or Remove) Sampling See About the Sampling Option on page 123.
Update Selection Filter Enables you to quickly update (overwrite) the contents of the Selection Filter
with the cells that are in the selected plan.
For more information about the Selection Filter, see the ENTERPRISE User
Reference Guide.
Properties (all options) In the same way as for other items in the Data Types, these options enable
you to manage the display properties of each item.
The Properties option can also be accessed by double-clicking the plan

name.
3 If you have modified one of the visual options (Apply Sampling, Properties), you
need to click the Redraw button to refresh the Map View.

About the Sampling Option
In the Clutter Parameters, on the General Parameters tab, it is possible to specify that
you want to enable cost function sampling for specific clutter types, so that only a
subset of the total pixels are used for an optimisation. This is described in Setting the
General Clutter Parameters on page 63.
If you have used sampling, whenever you are viewing plans in the Map View, you
can choose to modify the highlighted planning region so that it displays only the
exact pixels that will be included in the optimisation calculations.
To do this:
1 In the Map Information and Control, right-click the required plan (under the Plans
heading in the Data Types).
2 Click the 'Apply Sampling' option.
3 Click the Redraw button.
If some of the clutter parameters have been set to use sampling, only the
corresponding pixels will be displayed. Here is an example:

About the Action-Constraints Dialog Box
The ADVANTAGE tool focuses on automatic optimisation of plans. The Action-
Constraints dialog box plays a crucial part in this process.
Here is some key information about the important role it plays:
The concept of the Action-Constraints dialog box is that it not only sets the
constraints for the network optimisation, but, crucially, it also sets the possible
actions (namely, the network parameter changes ) that can take place.
In the majority of cases, when you have created a new plan, you must set possible
changes in the Action-Constraints dialog box, otherwise an optimisation will not
run. The only exception to this is when you are performing a Grid-only
optimisation, which uses Grid action-constraints for Properties/Sites/Nodes that
had been set in the Site Database before the plan was created.
For additional information about the action-constraints, see Setting Action-
Constraints in ADVANTAGE on page 37.
Example of Action-Constraints dialog box
The user interface of the Action-Constraints dialog box is designed to help you. The
two main guiding factors are the colour distinctions and the checking facility:

Colour Backgrounds
There are two colour backgrounds for columns in the dialog box:
The columns that cannot be edited (for example, those that show the current
values of the plan) are presented on a blue background.
The columns that can be edited (for example, those for which action-constraints
can be set for the plan optimisation) are presented on a green background.
Checking Facility
The Check button is extremely useful for automatically verifying that the plan's
action-constraints are valid, and ready for the optimisation to run.
For example, it can show you:
How many 'Degrees of Freedom' are in the plan, according to the current state of
the Action-Constraints. This value emanates from the amount of variables in the
plan. This picture represents a plan where fifteen of the antennas can each
undergo a possible azimuth change:
If there are no degrees of freedom, then the optimisation will not be allowed to
run.
The feedback may display an error or a warning, for example:
Errors will not allow the optimisation to run; warnings will allow it to run, but the
message is aimed at making you aware of the situation.
It is recommended that you make full use of all these guiding factors in this
section to ensure everything is set up correctly before optimising any plan.

About the Fixed Columns for the Action-Constraints
The Action-Constraints dialog box comprises many columns for the potential network
parameter changes. These sets of columns exist for each planning mechanism
(Antenna/Power/Grid).
One of the most important columns for each group of action-constraints is the 'Fixed'
column.
Some basic principles are:
If the Fixed checkbox for any action-constraint is selected:
 That action-constraint (for the object in that row) can be considered as
completely inactive.
 The existing values - although inactive - remain in place just in case you want
to reuse them later, by removing the Fixed setting. Unless that happens, they
stay inactive.
Here is an example:
In one of the rows, the Fixed checkbox for the Azimuth action-constraint is
selected. Therefore, when the optimisation is run, no azimuth changes will be
considered for that particular antenna in that row.
The above principles are true whether the Action-Constraints dialog box is edited
manually or by using Template Assignments. With specific regard to changes
made to the Action-Constraints values by assignment from Templates, you should
note the following:
 For each planning mechanism (Antenna/Power/Grid), there is a Read Only
template available. When this is assigned to a filter, all the 'Fixed' checkboxes
(for the objects in the associated filter, and independently for each mechanism)
become automatically selected in the Action-Constraints dialog box.
 When you create a template, it is likely that you will not have selected all the
potential action-constraints in that template. When you assign that template to
a filter, the 'Fixed' checkboxes for the action-constraints that were unselected in
the template become automatically selected in the Action-Constraints dialog
box (for the objects in the associated filter and independently for each
mechanism).

For example, if a template has only Azimuth (Antenna mechanism) selected,
the other action-constraints (Tilts, Heights, Device/Pattern) would all be set to
'Fixed' in the Action-Constraints dialog box, after the template assignment.
For more information, see Assigning Action-Constraints Templates to Objects
on page 147.
Using the Action-Constraints Dialog Box

The Action-Constraints dialog box plays a crucial role in ADVANTAGE, because it
enables you to specify which parameters can be changed (for the cells that can be
planned) during optimisation. You can do this for any or all of the planning
mechanisms (Antenna/Power/Grid).
The Action-Constraints dialog box presents a tabular display containing four tabs:
Summary
Antenna
Power
Grid
The Summary tab page displays how many Sites, Cells, and Antennas are in the Plan,
itemised in terms of Total, Plan, Read-only values.
The other tabs (Antenna/Power/Grid) display the parameters relevant to each
planning mechanism, which can be briefly described as:
The current values of the network contained in the Plan
The constraints, that is, the restrictions on what can be changed, in terms of
objects, ranges, limits and so on
The actions, that is, all the possible network parameter changes that may be
considered in the optimisation
The action-constraints of any Plans which already have Delta Plans are always in
Read-Only format.
If you are only intending to analyse a Plan, you may not need to edit the action-
constraints.
You can edit the Action-Constraints for an optimisation Plan. To do this:
ADVANTAGE toolbar.
3 Select the appropriate Plan, and click the Constraints button.

The Action-Constraints dialog box appears.

For the selected Plan, you can edit the constraints and/or the possible changes. You
can do this:
Individually for each object, on a manual basis. You can employ functionality
similar to that in Microsoft® Excel® to do this, such as copying and pasting.
- or -
Using Action-Constraints Templates that you have created, which you can then
either:
 Manually assign to objects in the Action-Constraints dialog box, under the
Templates column,
- or -
 Assign to objects on a 'filter-specific' basis, by clicking the Assign Templates

button.
When you have finished making changes in the Action-Constraints dialog box,
you must always click 'Apply', in order to save the changes.
About the Viewing Options for Action-Constraints

You can perform many kinds of viewing operations similar to that in Microsoft®
Excel®, by clicking the appropriate within the dialog box.
There are two distinct 'levels' in the Action-Constraints dialog box, where the
appears:
The section headings (ID, Current Values, Azimuth, Pilot Power, Candidate
Planning and so on)
The column headings (Property, Cell, Min, Max, Step, Fixed and so on)
Example of Heading levels in Action-Constraints dialog box
For the Section headings, when you click , you can perform this viewing option:
Show/hide columns (within the section)
For the Column headings, when you click , you can perform these viewing options:
Show/hide column
Sort ascending
Sort descending
Show all rows
Filter (gives option to show only the rows containing a chosen value in column)

In addition, if you prefer, you can perform similar viewing operations using the
Show/Hide button:
Show/Hide button
About the Methods of Editing the Action-Constraints

The Action-Constraints dialog box is very flexible, and enables you to set up the
action-constraints for your optimisation plans in ways that suit your specific
requirements. As you gain experience in using the ADVANTAGE tool, you will
develop your own preferences in how you approach this important part of the
optimisation process.
Whichever method(s) you use, you must always click 'Apply' in the Action-
Constraints dialog box, when you have finished, in order to save the changes.
In summary, as previously described, you can take different approaches to editing

these values:
Individually for each object, on a manual basis
Using action-constraints templates
A combination of the above
In very simplified terms, here is some general advice on how you might use each
method:
Manually Editing the Action-Constraints Values

If you only want to set up or edit a single parameter, for example an Azimuth Change
Step, it is probably easier and quicker to edit the value directly in the Action-
Constraints dialog box:
Example of Azimuth values in the Action-Constraints dialog box

If you want to set up different values for different groups of cells, make full use of
the filters when you edit the values.
Important :
 These filters only display the cells included in the plan when it was created.
Therefore, they are intrinsically 'subsets' of the corresponding filters that you
would view in the Site Database.
 Different filters can be selected for each planning mechanism.
 Each time you open a project, the filters in this dialog box will always default
to the filter specified on the Filters tab of the Preferences dialog box, under the
File menu.
You can employ functionality similar to that in Microsoft® Excel®, such as:
 Copying and pasting single/multiple values within the dialog box
 Copying and Pasting values directly to and from Excel
highlighting an active column)
Assigning Action-Constraints Templates to Cell Filters

If you want to set up or edit a variety of parameters, such as values for Mechanical
Downtilt, Azimuth and Height, it is probably easier and quicker to set up Templates,
and then use the Assign Templates button to assign the template values to the objects:
Example of Assigning Action-Constraints Templates to Cell Filters
For more information, see Assigning Action-Constraints Templates to Objects on page

147.

About the Action-Constraints on the Antenna Tab
In the Action-Constraints dialog box, whilst the majority of column headings are
intuitive, there are a few columns that need descriptions.
On the Antenna tab, there is a section heading named Constraints, and these
constraints enable you to restrict the available options that can be used to optimise the
antennas located on a Property.
Height Variation
If you want to use height variation, select the checkbox. This defines whether the
heights for individual antennas may differ at a specific Property (for GSM, this option
is cell layer-specific).
If height variation is not selected, all antennas on the same cell layer (GSM) or all
carriers at this Property (all other technologies) must be at the same height. However,
GSM cells for different cell layers, or cells of different technologies (for example, GSM
and UMTS) can still have antennas with heights different from each other.
Minimum Azimuth Difference

This enables you to set a minimum separation (in degrees) that you are willing to
accept between antennas of the same height on a specific Property.
Antenna Co-location Enabled

This enables you to allow antenna devices to share co-location parameters (identical
location co-ordinates, height and azimuth, and existing on the same Property).
If Antenna Co-location is not enabled for a Property, no antenna sharing or co-

location configuration can be accepted as a valid starting configuration or examined
as a potential optimisation solution by the Optimiser. For more information, see How
the Optimiser Considers Shared Antennas on page 138.
Forbidden Azimuth Min/Max

This enables you to select to define an orientation region (or range) which the
automatic optimisation cannot consider for azimuth changes. For this, the minimum
represents a clockwise wall bearing angle (the starting azimuth for the forbidden
range) and the maximum represents an anti-clockwise wall bearing angle (the final
azimuth for the forbidden range).
For example, for an original antenna azimuth of 100º, if the clockwise bearing angle is
set to 120º and the anti-clockwise bearing angle to 80º, the antenna may be able to
move plus or minus 20º during the optimisation.

About the Action-Constraints on the Power Tab
In the Action-Constraints dialog box, whilst the majority of column headings are self-
explanatory, there are a few columns that may need further explanation.
On the Power tab, there is an option to set a Uniform Power constraint. This enables
you to specify groups of cells that you want to be adjusted uniformly by the
Optimiser.
To do this:
In the Uniform Group ID column, specify a number (0 or greater) for the cells that
you want to be grouped by the Uniform Power constraint. It is possible, if
required, to use different numbers to make separate groups.
If this option is inactive for a cell, the value shows as -1.
If this is enabled, the respective initial power values for the associated cells must
be the same in order for changes to be considered by the Optimiser. If the initial
power values are not the same, then this constraint will not be applicable and will be
ignored.
About the Action-Constraints on the Grid Tab

In the Action-Constraints dialog box, whilst the majority of column headings are self-
explanatory, there are a few columns that may need further explanation.
On the Grid tab, there are a number of options which relate to:
Selection Planning - potential configurations at various network levels: Site, Sector
and Property
Candidate Planning - potential site locations
About Selection Planning Action-Constraints

In the Action-Constraints dialog box, on the Grid tab, under the Selection Planning
heading, there is a column heading named 'Network Level'. This enables you to
specify a planning option at various levels: site, sector, Property.
Sector configuration changes (Sector planning) cannot be considered in an

optimisation unless you have already set up the relevant parameters in the Site
Database. For information on how to do this, see Configuring GSM Site Grid
Constraints on page 46 or Configuring UMTS, CDMA/EV-DO, WiMAX or LTE Grid
Constraints on page 50.

There are various options in this column that may be considered during an
optimisation:
Planning Option Has this Effect on the Optimisation Implication of Site Active Option
(Network Level column) (for each appropriate object) (Site Always Active column)
None No effect. n/a.
Site Site can be switched ON or OFF. That is: In the case of site planning, setting a site
All its sectors ON as 'always active' means that the site
would be 'read-only'. This setting should
-or- therefore be used with caution.
All its sectors OFF
Sector Sector can be switched ON or OFF individually, In the case of sector planning, setting a
according to the sector configurations on the Grid site as always active will ensure that at
Constraints tab for the site in the Site Database. least one sector (of that site) always
remains active.
Sector planning cannot be used unless
allowable configurations have been generated on the
Grid Constraints tab.
Property All sites of a Property can be switched ON or OFF. In the case of Property Planning, if all of
That is: a Property's sites are set as always
All its sites and their cells ON active, the Optimiser would have no
flexibility for optimising that Property.
-or- This setting should therefore be used
All its sites and their cells OFF with caution.
This option only has an effect where there are two or
more sites co-located on the same Property
(otherwise site selection should be used).
Whenever you select or de-select this option, all the
sites co-located on that Property are always updated
consistently. This is so that the Property option can
never be inconsistently selected for co-located sites.
All the other network level options behave
independently between co-located sites.
The selection planning options can also be set up using the Grid Planning Action-
Constraints Template, as described in Configuring Action-Constraints for Grid
Planning on page 144.
About Candidate Planning Action-Constraints

In the Action-Constraints dialog box, on the Grid tab, under the Candidate Planning
heading, there is a column heading named 'Use'.
'List' changes (in other words, specified locations) cannot be considered in an

optimisation unless you have already set up the relevant parameters in the Site
Database. For information, see Configuring Property Grid Constraints on page 40.
There are four options in this column that may be considered during an optimisation:
Option During an Optimisation:
None No effect.
List Sites can be moved to specified locations (corresponding to the Candidate Properties and/or 'co-
ordinate only' locations defined in the Site Database).
Search Step Sites can be moved to locations determined by globally generated grid co-ordinates, as defined in the
Grid Planning Action-Constraints Template.
Both Both of the above can be considered.

These options can also be set up using the Grid Planning Action-Constraints
Template, as described in Configuring Action-Constraints for Grid Planning on page
144.
About Action-Constraints Templates

The Action-Constraints Templates provide you with a quick and easy way of setting
up Action-Constraints so that they can be reused across all or some of your plans.
This flexibility enables you to specify the action-constraints for any or all of the
planning mechanisms:
Antenna
Power
Grid (site location/selection/configuration)
You should make full use of these templates so that you avoid duplication of
constraints that may be generic to all plans. In other words, you should avoid
spending time setting many constraints directly in the Action-Constraints dialog box,
if there is a high chance that you will be using those action-constraints for other plans.
Example of the options available within the Actions Constraints Template Editor

When they are created, these templates can then be either:
Manually assigned to objects in the Action-Constraints dialog box, under the
Templates column,
- or -
Assigned to objects on a 'filter-specific' basis, by clicking the Assign Templates
button.
If you subsequently modify any values directly in the Action-Constraints dialog

box after assigning a template, the Templates column (for the relevant object)
automatically reverts to 'Custom'.
Creating and Editing Action-Constraints Templates

To create or edit Action-Constraints Templates:
ADVANTAGE toolbar.
3 Select the appropriate plan, and click the Constraints button.

4 In the Action-Constraints dialog box, click the Manage Templates button.
The Action-Constraints Template Manager dialog box appears, enabling you to

add, edit, remove, or rename a template.
To add or edit a template in the Action-Constraints Template Manager dialog box:
1 If you are adding a template, click Add, name the template, click OK, and then
click Edit
- or -
If you are editing an existing template, select it and click Edit.
2 In the dialog box that appears, click the first action or constraint that you wish to
configure, for example Antenna Planning - Electrical Downtilt.
For details on the different planning actions and constraints that you can
configure, see one of the following sections:
 Configuring Action-Constraints Templates for Antenna Planning on page 136
 Configuring Action-Constraints Templates for Power Planning on page 139
 Configuring Action-Constraints Templates for Grid Planning on page 144

3 In the right hand pane, edit the values for this action or constraint. For example:
4 Click the next action or constraint that you want to configure, and in the right
hand pane edit the values as appropriate.
You can configure any combination of actions or constraints in the same template.
For example, a template can contain both Antenna Planning and Power Planning
actions or constraints.
5 When you have configured all of the actions and constraints that you require, click
OK, and then, in the Action-Constraints dialog box, click Close.
6 You can now assign this (or any other) template to objects on a 'filter-specific' basis
in the Action-Constraints dialog box, as described in Assigning Action-Constraints
Templates to Objects on page 147.
Configuring Action-Constraints Templates for Antenna

Planning
When creating or editing Action-Constraints Templates, you can configure antenna
planning optimisation actions and constraints. These can be used with either cost
mechanism to identify the optimum configuration of the antenna subsystem for a
network.
The concept of antenna planning in ADVANTAGE is to incorporate into the
optimisation the practical details of the site construction and the real environment
limitations that affect the antenna subsystem.
The antenna optimisation can support all the main types of actions that are allowed
for the antenna subsystem. These include changes to the number of antennas, the
antenna type (device and pattern), downtilt (electrical, mechanical and total), azimuth
and height.
This picture shows an example of the actions and constraints for antenna heights:
Example of Action-Constraints Template for Antenna Height

This table describes the antenna planning action-constraints that you can configure:
Select To
Device/Pattern Enable the antenna devices/patterns to be changed.
Select the required antenna devices/patterns from the antenna database tree.
To locate a particular antenna device or pattern, type the name in the Find pane, and click
Find.
To restrict what is displayed to just the selected items, click Show Selected. To undo this, click
Show All.
Electrical Downtilt Enable the electrical downtilt of the antenna to be changed:
Change Step indicates the allowed step of change (in degrees).
Max Change defines the maximum permitted change from the respective original value in the
Site Database (in degrees).
Total Downtilt must also be selected, unless Mechanical Downtilt is considered and the Total
Downtilt is to remain unchanged.
For an optimisation to consider electrical downtilt changes, the appropriate antenna patterns
(for each antenna device) need to be set up in the Cellular Antennas dialog box.
Mechanical Downtilt Enable the mechanical downtilt of the antenna to be changed:
Min Value sets the minimum mechanical downtilt that is permitted (in degrees). Any downtilts
below the minimum will not be modified in the optimisation.
Max Value sets the maximum mechanical downtilt that is permitted (in degrees). Any
downtilts above the maximum will not be modified in the optimisation.
Site Database.
Total Downtilt must also be selected, unless Electrical Downtilt is considered and the Total
Downtilt is to remain unchanged.
Total Downtilt Enable the total downtilt (electrical plus mechanical) of the antenna to be changed:
Min Value sets the minimum total downtilt that is permitted (in degrees). Any downtilts below
the minimum will not be modified in the optimisation.
Max Value sets the maximum total downtilt that is permitted (in degrees). Any downtilts
above the maximum will not be modified in the optimisation.
Azimuth Enable the azimuth of the antenna to be changed:
Max Change defines the maximum permitted change (in degrees).
Min Diff at Same Height specifies the minimum permitted angular distance (in degrees) that
has to be maintained if antennas for the same technology and cell layer (if applicable) are
positioned at the same height.
Height Enable the height of the antenna to be changed:
Min Value sets the minimum antenna height that is permitted (in m). Any antennas below the
minimum will not be modified in the optimisation.
Max Value sets the maximum antenna height that is permitted (in m). Any antennas above
the maximum will not be modified in the optimisation.
Change Step indicates the allowed step of change (in m).
Site Database (in m).

When configuring antenna planning actions and constraints, you should
remember the following:
The original parameter settings (for example, antenna types) are always included
in the optimisation.
Any antenna parameters with values outside the {min, max} range set in the
respective constraints will not be changed during the optimisation.
The antenna type, electrical downtilt, mechanical downtilt and total downtilt
actions/constraints are interdependent. For example, you cannot consider changes
to the mechanical downtilt without enabling changes to the electrical and/or total
downtilt as well.
How the Optimiser Considers Shared Antennas

This section provides definitions of the two types of shared antenna in ENTERPRISE,
and summarises how they are considered when you run the Optimiser.
In ENTERPRISE, there are two definitions of shared antennas, described as follows:
Explicitly Shared Antennas:
In ENTERPRISE, this is defined as two or more logical antenna devices that
represent a single physical antenna device in a real network.
This can be configured in the Site Database by using the option

on the Antennas tab (at the cell level for GSM, and at the node level for all other
technologies). This option uses shared antenna identities, and is explained fully in
the ENTERPRISE User Reference Guide).
When this setting is used, the physical configuration of the shared antenna is
forced to remain identical between the appropriate cells or nodes co-located on the
respective Property.
Implicitly Shared Antennas:
In ENTERPRISE, this is defined as two or more antenna devices that are not
explicitly shared, but share the same co-location parameters (identical location co-
ordinates, height and azimuth, and existing on the same Property).
If you want the Optimiser to consider a network configuration that allows antenna
sharing (implicit or explicit), you must ensure the option is enabled
on the Antenna Constraints tab for the relevant Properties in the Site Database. For
more information, see Configuring Property Antenna Constraints on page 42. There
are also options related to antenna sharing within the Settings. For more information,
see Specifying the Settings on page 90.

Depending on the antenna planning actions and constraints that you have specified
for the considered cells:
In the case of any considered antennas that are 'explicitly' shared, their
configuration (for example, mechanical tilt) can be modified (jointly) during the
optimisation, but the respective antennas will remain explicitly shared.
In the case of any considered antennas that are 'implicitly' shared, their sharing
status may change during the optimisation. For example, antennas that were
initially shared may each end up having different configurations, and become
non-shared.
In the case of all other considered antennas, their sharing status may change
during the optimisation. For example, antennas that were not initially shared may
each end up having the same configuration, and become implicitly shared.
Whenever antennas are shared, the number of actions and respective action costs
are considered appropriately, and are only counted once for the same physical
antenna object. For example, a mechanical tilt change to an antenna shared between
two cells would only be counted once.
Configuring Action-Constraints Templates for Power Planning

When creating or editing Action-Constraints Templates, you can configure power
planning optimisation actions and constraints. These can be used with any cost
mechanism to identify the optimum power levels for individual base stations.
In addition, the optimum BTS Types (GSM) and Node Types (UMTS) can be
identified.
When optimising power levels, there are key differences between technologies. For
example, in UMTS - unlike in GSM - the physical channels can be transmitted at
different powers. The power in the node is shared between signalling and user traffic,
and so, if less power can be allocated for signalling, more can be made available to
user traffic, thus increasing the cell downlink capacity.
The ADVANTAGE power optimisation is sufficiently advanced to handle the
differing requirements by offering technology-specific actions, such as GSM PA
Output Power, UMTS Pilot Power, CDMA2000 Pilot Power, EV-DO Rated PA Power,
WiMAX TX Power or LTE Max TX Power.
This picture shows an example of the action-constraints for GSM PA Output Power:
Example of Action-Constraints Template for GSM cell PA Output

About GSM Power Planning Action-Constraints
This table describes the GSM power planning actions you can activate for cells:
Select This Action To
PA Output Power Enable the power amplifier (PA) output to be changed.
BTS Type Enable the BTS equipment type to be changed on a site.
j
If you have selected PA Output Power, the constraints described in this table become
active:
This Constraint Enables You To
Min Value (dBm) Set the minimum power that is permitted (in dBm).
Max Value (dBm) Set the maximum power that is permitted (in dBm).
Change Step (dB) Set the permitted step of power change (in dB).
Max Change (dB) Set the maximum permitted change from the current value in the cell (in dB).
Changes Allowed Define how the current value will be allowed to change within the set ranges:
'Any' allows both higher and lower values to be examined during the optimisation.
'Only decreases' just allows lower power settings to be examined.
'Only increases' just allows higher power settings to be examined.
ff
When defining GSM power planning actions and constraints, you should
The original parameter settings (for example, BTS equipment types) are always
included in the optimisation.
Any power parameters with values outside the {min, max} range set in the
Certain actions/constraints depend on specified performance metrics and/or cost
mechanisms. For example, the BTS Type action and constraint may have an effect
on the performance costs, providing that the PA Output Power option is also
considered.
About UMTS Power Planning Action-Constraints

This table describes the UMTS power planning actions you can activate for cells:
Max TX Power Enable the maximum transmit power to be changed.
Pilot Power Enable the pilot power (CPICH) to be changed.
HSDPA Power Enable the HSDPA power to be changed.
Max DL Power Per Connection Enable the maximum power per connection to be changed.
Node Types Enable the Node equipment type to be changed on a node.

If you have selected any of the above power options, the constraints described in this
table become active:
Fixed % of Max TX Power Specify that the pilot power (for all the cells associated with the template) is always adjusted
in proportion with the Max TX Power. This maintains the same ratio that exists in the
(for Pilot Power only) starting plan.
When this is selected, the Change Step and the Changes Allowed become read-only,
and the values that you set for the Max TX Power are used instead.
When configuring UMTS power planning actions and constraints, you should
The original parameter settings (for example, Node equipment types) are always
included in the optimisation.
Certain actions/constraints depend on specified performance metrics and/or cost
mechanisms. For example, the Max Power per User or the Node Type option may
have an effect on the performance costs, if you choose to use the service-based cost
mechanism in the optimisation.
When you are using the Fixed % of Max TX Power checkbox (for Pilot Power,
HSDPA Power or Max Power Per User):
 You should ensure that all the values you set for the Max TX Power planning
action are compatible with your overall objectives
 If optimising HSDPA Powers, cells will be considered for HSDPA power
optimisation only if they are enabled for HSDPA (and have a Node Type that
supports HSDPA) and you choose to use the service-based cost mechanism in
the optimisation
If the Fixed Ratio and/or Uniform Power constraint has been enabled, the
Optimiser will not change the Node Type from one that supports HSDPA to one
that does not, and vice versa.
If a cell considered by the Optimiser cannot support HSDPA (in other words, none
of its available Node Types support HSDPA or it is not supported on the cell), the
Optimiser will not allow any changes to the HSDPA Power and will not consider
the HSDPA-specific Fixed Ratio and Uniform Power constraints for this cell.

About CDMA/EV-DO Power Planning Action-Constraints
This table describes the CDMA/EV-DO power planning actions you can activate for
cells:
CDMA2000 Pilot Power Enable the pilot power to be changed.
EV-DO Rated PA Power Enable the rated PA power to be changed.
If you have selected any of the above power planning actions, the constraints
described in this table become active:
When configuring CDMA/EV-DO power planning actions and constraints, you

should remember the following:
The original parameter settings are always included in the optimisation.
About WiMAX Power Planning Action-Constraints

This table describes the WiMAX power planning actions you can activate for cells:
TX Power Enable the transmit power to be changed.
(Fixed and Mobile)
If you have selected the above power planning action, the constraints described in this
table become active:

When defining WiMAX power planning actions and constraints, you should
About LTE Power Planning Action-Constraints

These are the LTE power planning actions that you can activate for cells:
Max TX Power (dBm)
Traffic Offset (dB)
Control Offset (dB)
Synchronisation Offset (dB)
Broadcast Offset (dB)
Multicast Offset (dB)
Reference Signal SNR Threshold (dB)
Max TA Threshold (msec)
Max Range Threshold (km)
If you have selected any of the above options, the constraints described in this table
become active:
Min Value Set the minimum power that is permitted.
Max Value Set the maximum power that is permitted.
Change Step (dB) Set the permitted step of power change.
Max Change (dB) Set the maximum permitted change from the current value in the cell.
When configuring LTE power planning actions and constraints, you should

Configuring Action-Constraints Templates for Grid Planning
When creating or editing Action-Constraints Templates, you can configure grid
planning optimisation actions and constraints. These can be used to identify the
optimum plans for networks, in terms of:
Candidate Planning - potential site locations
Selection Planning, which consists of:
 Site planning - potential site selection/deselection
 Sector planning - potential sector configurations
 Property planning - sites belonging to a single Property are considered as one
variable, so that all of its sites can be switched ON or OFF simultaneously
These action-constraints incorporate various limitations that impact upon network
planning in practice, for example, the inability to consider certain site locations due to
environmental, financial or other concerns. The grid optimisation in ADVANTAGE
can take account of these limitations when it examines potential changes in the
network.
In order for the Optimiser to start, the initial locations for the sites associated with
a Grid template must satisfy the Min/Max Inter-site Distance or the Forbidden Areas
option if selected (unless the ignore options are chosen).

Candidate Planning in the Template Editor
The Action-Constraints Template Editor contains options for Candidate Planning -
potential site locations.
This picture shows an example of the actions and constraints for candidate planning:
Example of Action-Constraints for Grid planning (Candidate)

This table describes the action-constraints that you can configure for candidate
planning:
Select To
Min and Max Inter-site Distance Specify the minimum and maximum acceptable distance (in m) between any Property-
Property pairs that are first-order neighbour pairs (in other words, nominal-nominal,
nominal-candidate or candidate-candidate) considered in a plan.
You can then choose to modify the way that nominal-nominal first-order neighbour pairs
are considered, by selecting to:
Ignore the minimum and maximum distances during optimisation
Ignore the minimum and maximum distances during the first optimisation iteration
only
Candidate Locations Enable candidate locations to be examined in the optimisation. These candidate
locations can be those:
Specified in the Site Database Grid Constraints tab for each considered nominal
Property
Generated by an algorithm that takes into account either the Property-specific
value (as defined in the search area for a Property), or a global radius distance
and a step distance (as defined in the template)
If the number of globally generated locations exceeds 100 per Property, a warning
message is produced so that the step value is then adjusted (either automatically or
manually).
Forbidden Areas Define areas that should not be considered as potential site locations, including the
original (Site Database) nominal Properties.
Ignore forbidden areas for nominal Ignore forbidden locations for nominal Properties during optimisation.
Properties
Selection Planning in the Template Editor

The Action-Constraints Template Editor contains options for Selection Planning:
Site planning - potential site selection/deselection
Sector planning - potential sector configurations
Property planning - sites belonging to a single Property are considered as one
variable, so that all of its sites can be switched ON or OFF simultaneously
This picture shows an example of the actions and constraints for selection planning:
Example of Action-Constraints for Grid planning (Selection)

This table describes the action-constraints that you can configure for selection
planning:
Option Description
Site Site can be switched ON or OFF (= all its sectors ON, or all its sectors OFF).
If required, the option to set a site as 'Site Always Active' can be used in Site Planning, but it means
that the site would, in effect, be 'read-only'.
Sector Sector can be switched ON or OFF individually, according to the sector configurations on the Grid
Constraints tab for the site in the Site Database.
Sector planning cannot be used unless allowable configurations have been generated on the Grid
Constraints tab.
The option to set a site as 'Site Always Active' can be used to ensure that at least one sector of that
site always remains active.
Property All sites of a Property can be switched ON or OFF (= all its sites and their cells ON, or all its sites and their
cells OFF).
This option only has an effect where there are two or more sites co-located on the same Property
(otherwise site selection should be used).
Whenever you select or de-select this option, all the sites co-located on that Property are always updated
consistently. This is so that the Property option can never be inconsistently selected for co-located sites.
All the other network level options behave independently between co-located sites.
Any site set as 'Site Always Active' can be used in Property planning. However, if all of a Property's
sites are set as always active, the Optimiser would have no flexibility for that Property.
Site Always Active Sites that are assigned with this option are always used in every solution the Optimiser generates. This
means that the site will never be 'switched off' during optimisations.
The way that this option may affect Selection Planning (Site, Sector, Property) is described in each of the
rows above.
Assigning Action-Constraints Templates to Objects

When you have created Action-Constraints Templates, you can assign them to objects
in the Action-Constraints dialog box.
You can do this manually within the Action-Constraints dialog box, under the
Templates column. However, it will often be easier to make 'filter-specific'
assignments by using the Action-Constraints Assignments dialog box.
To do this:
1 Within the left-hand pane of the Optimiser Workflow, select Plan Manager.
2 Select the appropriate Plan, and click the Constraints button.

3 In the Action-Constraints dialog box, click the Assign Templates button.
4 In the dialog box that appears, click Add.
If you have previously set up some filter-template combinations on this dialog

box (and clicked OK) you can retrieve them by clicking the Get Last button.

5 In the row that appears, select a filter.
6 Select the required template(s) to assign to that filter.
Depending on your optimisation planning approach, you can either assign the
same template to all the planning mechanisms, or you can assign different
templates to each. This allows flexibility if you want to experiment with different
combinations of templates.
7 Continue with the Add button until you have specified all the required filter-
template combinations. (You can delete a row by clicking .) Here is an example:
priorities. Only one template can be assigned to an object. Therefore, in cases
where an object might exist in more than one filter in this dialog box, the filter
priority number is important in determining which template is assigned.
You can check the contents of the relevant filter by clicking .

8 Click OK. The assignments you have made now appear in the Action-Constraints
dialog box.
9 To save these assignments, click Apply.
When you have finished making changes in the Action-Constraints dialog

box, you must always click 'Apply', in order to save the changes.
When you have finished, you can close the Action-Constraints dialog box.
There are three points you should note regarding template assignments. Two of
these points relate to default templates that are always available to you (these are in
addition to the templates that are user-defined):
Read Only template - when this is assigned to a filter, all the 'Fixed' checkboxes (for
the objects in the associated filter) become automatically selected in the Action-
Constraints dialog box.
Unchanged template - when this is assigned to a filter, nothing is changed (for the
objects in the associated filter) in the Action-Constraints dialog box. This option is
necessary because you may want, for example, to assign a template for just one or
two planning mechanisms, and leave the other(s) unchanged.

When you create a template, it is likely that you will not have selected all the
potential action-constraints in that template. When you assign that template to a
filter, the 'Fixed' checkboxes for the action-constraints that were unselected in the
template become automatically selected in the Action-Constraints dialog box, for
the objects in the associated filter.
For example, if a template has only Azimuth (Antenna mechanism) selected, the
other action-constraints (Tilts, Heights, Device/Pattern) would all be set to 'Fixed'
in the Action-Constraints dialog box, after the template assignment.
All templates (read only, leave unchanged and user-defined) are assigned
separately to each individual planning mechanism. Therefore, the above points are
valid independently for each mechanism.
For more specific information about the 'Fixed' columns, see About the Fixed
Columns for the Action-Constraints on page 126.
Modifying Templates after Assigning them to Objects

In situations where you modify an Action-Constraints Template that is already
assigned to various objects, those changes will not be made retrospectively in the
Action-Constraints dialog box for those objects.
However, you can explicitly choose to make those changes in the Action-Constraints
dialog box by either:
Manually reassigning the template to objects in the Action-Constraints dialog box,
under the Templates column
Reassigning the template to objects on a 'filter-specific' basis, by clicking the
Assign Templates button
Using the 'Reassigning All Templates' option
Reassigning All Templates

This method represents a quick way of implementing changes from modified
Templates (as described in the first paragraph) into the Action-Constraints dialog box.
This special option re-applies all the modified (that is, current) settings from all
templates that are currently assigned to objects in the Action-Constraints dialog box.
This operation is applicable to all three planning mechanisms.
To do this:
Click the 'Reassign All Templates' button.
If you want to reassign some of your currently assigned templates, but not all, you
can change the template selection in the Action-Constraints dialog box to 'Custom' on
the objects that you don't want to modify, before pressing the above button.

Applying a Plan to the Database
The Apply to Database option enables you to Apply any of your plans or delta plans
to the database. It is equivalent to a normal manual Apply in the Site Database. It
enables you to use the complete functionality within ADVANTAGE and ASSET. For
example, you can analyse the performance of the plan (using arrays and reports)
within ASSET, and make any necessary subsequent manual changes to the Site
Database. As is the normal case for all Applied data, you can choose to subsequently
Commit the data.
There is also a 'Temp Apply' option, described in the following section.
There are some key differences between the Temp Apply/UnApply and the Apply
to Database options. For more information, see Key Differences between Temp Apply
and DB Apply on page 152.
In the normal way, if required, you can use the Restore All option after using
Apply to Database, but please note that this will restore the database back to the last
Committed configuration, which may lead to:
 Any previously Applied changes in the Site Database being lost (in the normal
way)
 A configuration in the Site Database that is different from the plan that you
created to start with (because the plan, once created in the Plan Manager, is
independent of subsequent database changes)
To apply a plan:
1 Within the left-hand pane of the Workflow, select Plan Manager.
2 Select the appropriate plan.

3 Click the Apply Plan button.
4 Click the Apply to Database option.
The plan is now applied to the database.

Applying a Plan Temporarily to the Database
This option enables you to 'Temporarily Apply' of one of your plans to the database,
so that you can analyse the performance of the plan (using arrays and reports) within
ASSET. The main benefit of this is that you can experiment with the potential benefits
of the plan, and subsequently revert to the previous configuration in the database.
There is also a normal 'Apply to Database' option, described in the previous

section.
There are some key differences between the Temp Apply/UnApply and the Apply
to Database options. For more information, see the following section.
To temporarily apply a plan:
1 In the left-hand pane of the Workflow, select Plan Manager.

3 Click the Apply Plan button.
4 Click the Temp Apply option.
The plan is now temporarily applied to the database.
You will see the appropriate cell parameters temporarily modified in the Site
Database window, but the whole Site Database is in a read-only state.
The read-only state will remain in place until you decide to revert to the previous
configuration in the database. To do this:
2 Click the Temp UnApply button.
The database is now reverted to its previous configuration, and the Site Database
window is active again.

Key Differences between Temp Apply and Apply to
Database
There are some key differences between the Temp Apply/UnApply and the Apply to
Database options, as summarised here:
Summary of Temp Apply

When you click Temp Apply, you can view the temporary changes in the Site
Database window, which, at this point, appears in a read-only state. This operation is
fundamentally different from the normal Apply operation used in the rest of
ENTERPRISE, because it does not overwrite any changes you might have made in the
Site Database since you created the plan. In other words, when you subsequently
revert it from its 'temporary' state (by clicking Temp UnApply), nothing will have
changed from the configuration that was in place immediately before you clicked
Temp Apply.
You cannot make any manual changes to the Site Database while it is in this
'temporary' restrictive state.
The operation does not affect other users who are sharing the project.
You cannot close a session (that is, close the project) while the Site Database is in
the 'temporary' state. It is obligatory to revert it by clicking Temp UnApply before
you close your session.
The Temp Apply operation is independent of your user-specific object
permissions (since no values are written to the database).
Summary of Apply to Database

This is equivalent to a normal (manual) Apply, which means that it will overwrite any
changes you might have made in the Site Database since you created and optimised
the plan. In other words, if you had made some changes to the relevant cells since that
time, it will overwrite those changes with the new values when you click the Apply to
Database option.
You can make further manual changes to the Site Database, in the normal way,
after this operation.
You will be able to use the Restore option in the Site Database, if necessary, to
restore to the previous committed state (assuming the network elements had at
some stage been previously committed).
The operation may subsequently affect other users who are sharing the project, in
the normal way, if you choose to Commit the changes.
You can close a session (that is, close the project) in the normal way, if required,
with some changes in the Applied state.
The Apply to Database operation is always dependent on your user-specific object
permissions.

Deleting a Plan
To delete an optimisation plan:
3 Click the Delete Plan button.
4 Click Yes to proceed, or No to cancel.
If you clicked Yes, the plan is now removed.
You cannot delete a plan if it is 'in use' by more than one user.

CHAPTER 6
Optimising a Network
pane.
This chapter focuses on how to run an optimisation, and how to interpret the
feedback.
- or -

Prerequisites for an Optimisation
The principal feature of ADVANTAGE is the automatic Optimiser, which can
consider an extensive range of physical design and network parameter settings that
affect the performance of the radio network.
You can set up and start the automatic optimisation of a network configuration
according to various targets, costs, actions and constraints, using any or all of the
planning mechanisms (Antenna/Power/Grid).
For a fuller summary of the optimisation process, see About the ADVANTAGE
Optimisation Framework on page 14 and About Network Optimisation on page 22.
Before you start optimising your network, ensure that you, or your administrator,
have (where appropriate):
Set up a project with the necessary planning data, including traffic (if applicable).
Defined the RF Array Thresholds and the RF Metric Targets.
Defined the object/action-related costs, if you want the optimisation to consider
such costs (for example, costs for antenna azimuth changes).
The above step is optional.

Created a plan (defining the area, cell filters, and, optionally, vectors), using the
Plan Manager. For more information, see Using and Managing Plans on page 107.
Defined the appropriate parameters or options on the Strategy, Traffic and
Settings tabs. The Strategy tab governs the selection of which Metrics are to be
used, and their weightings. The Traffic tab governs the selection of terminal types.
The Settings tab includes key additional parameters and options, including array
settings. For more information, see About the Optimiser Workflow on page 32.
Configured the Action-Constraints for the optimisation.
Created/loaded traffic arrays, if applicable. For traffic-based optimisations, an
ENTERPRISE traffic array or a technology-specific ADVANTAGE traffic array
(using Spread Network Data or Loaded Cached Traffic) must be available.
For a problem cell related optimisation, you must run Problem Cell Identification
and/or define cell-specific weights.
This then enables you to start an optimisation.

Running an Optimisation
Before you can run an optimisation, you must have created at least one plan.
(If appropriate, you can also choose to optimise a delta plan.)
For a full list of the prerequisites, see Prerequisites for an Optimisation on page 156.
To start an optimisation:
1 Open the Workflow by clicking the shortcut button on the main

ADVANTAGE toolbar.
3 Select the appropriate plan, and click the Optimise button. The Optimiser dialog
box appears:
4 Set the minimum time interval for the 'best cost value' plan to be saved (at each
time interval, a new delta plan is saved only if the best cost value is less than the
previous saved value). To do this, in the Delta Plan Writing Interval edit box, type
the number of minutes and click Set.
At the point where you stop the optimisation, an additional delta plan is saved
(according to the same criteria above), as if the next time interval had been
reached.
5 If you want to view statistics information using the Statistics Graph, Statistics
Details or Report buttons, ensure that the Calculate Statistics checkbox is selected.
6 To start the Optimiser, click Start.
The Optimiser starts running, and can be monitored.

Monitoring an Optimisation
When you have started an optimisation, the Optimiser runs. This picture shows an
example of a running scenario:
Example of the Optimiser dialog box
The following values are displayed in the Optimiser dialog box:

Value Description
Starting configuration The name of the plan or delta plan.

Modification strategy The modification strategy specified in the Settings.
Starting cost value The cost for the starting configuration.
Best cost value The cost for the best configuration that the Optimiser has found so far.
Current cost value The current optimisation cost.
Generated cost value The cost for a generated optimisation state.
Cost value gain; absolute; relative The absolute gain value represented by the difference between the starting
and best cost values; this gain expressed as a relative percentage.
Cost function calls The total number of iterations that have taken place up to this point in the
optimisation. This includes the iteration required for optimisation initialisation
and (if applicable) any iterations rejected based on the Max Objects/Actions or
Max Degradation criteria.
Iterations: accepted; generated; A/G Accepted: The number of iterations that have been accepted by the
Optimiser's search algorithms as the correct "path" to take to the optimal
solution. These may or may not decrease the best plan cost at any particular
point in an optimisation, depending on the search algorithm in use at the time.
Generated: The number of performed iterations (this is the same as the
number of accepted states).
A/G: The 'Accepted to Generated' ratio.
States: accepted; generated; A/G Accepted: The number of states that have been accepted by the Optimiser as
valid (that is, a state that has broken no hard constraints such as Max
Degradation, Max Objects/Actions, Min/Max Inter-Site Distance).
Generated: The number of performed states.
A/G: The 'Accepted to Generated' ratio.
Start Time, Stop Time, Elapsed Time The time the Optimiser was started, the time it was stopped, and the elapsed
time.

While the optimisation is running, you can view a variety of useful feedback
information, by clicking any of the following buttons:
Cost Graph - for a graphical representation of the best, current and generated cost
values for each iteration
Statistics Graph(s) - for the initial and best plan values for the selected series
Cost Details - for a variety of information about the costs related to the
optimisation
Statistics Details - for the statistics for the initial iteration and the most recent best
plan
Optimisation Report - for complete details of the generated optimisation plans
To stop the Optimiser at any point:

Click Stop (you cannot resume the optimisation once it has been stopped)
After stopping the Optimiser, you can still view the data it displays and the
feedback graphs. This data and the graphs are available until you close the Optimiser
dialog box. The data in the Optimisation Report, on the other hand, is still available
until you start another optimisation.
About the Cost Graph

When you are running the Optimiser, you can choose to display the Cost Graph, by
clicking the appropriate button.
This displays a graphical representation of the best, current and generated cost value
at or up to (as applicable) each optimisation iteration.
Example of a Cost Graph
You can use this feedback to assess whether a satisfactory cost value has been
achieved, and also to see the pattern of values generated by the Optimiser.

To zoom in on a particular section of the graph:
1 Click and hold down the left mouse button on the graph where one corner of the
required section will be and drag the mouse to create a box.
2 Release the mouse button.
To zoom back out, right-click.
About the Statistics Graph(s)

When you are running the Optimiser, you can choose to display the Statistics
Graph(s), by clicking the appropriate button.
This displays a graphical representation of the initial and best plan values for a
selected (Metric) series.
Example of a Statistics Graph
To select what information is shown on the graph, click Series, and in the dialog box
that appears, select the required categories of information. Then click OK.
To zoom in on a particular section of the graph:
1 Click and hold down the left mouse button on the graph where one corner of the
required section will be and drag the mouse to create a box.
2 Release the mouse button.
To zoom back out, right-click.
To create another graph, click New Graph.
If you are starting from a delta plan, you can view statistics from the previous
optimisation by clicking Show History.

About the Cost Details
When you are running the Optimiser, you can choose to display the Cost Details, by
clicking the appropriate button.
This displays the following information:
The number of independent optimisation variables (Degrees of Freedom, or DOF)
The number of pixels in the area that will be considered by the Optimiser
The contribution of each considered cost category (and its components) to the
starting, best, current and generated optimisation cost (the relevant metric
selection/weights and multiplier coefficients are also displayed)
The number of considered optimisation actions on a starting, best, current and
generated optimisation plan basis
The examined optimisation states (or iterations) and the respectively generated
optimisation cost (the best and current cost values are also displayed)
To get details of different cost values besides the current ones, ensure that the Log
states option is selected.
Example of Cost Details
You can also use this information to check the entire optimisation setup after an
optimisation has started. For example, you can ensure that the weights and multiplier
coefficients are correctly configured and that the optimisation targets are realistic and
can be met.

About the Statistics Details
When you are running the Optimiser, you can choose to display the Statistics Details,
by clicking the appropriate button.
This displays the statistics relevant to the RF Metric Targets (array-based and/or
service-based) for the optimisation, depending on the type of optimisation that you
are running. You can view statistics per technology, for traffic and/or area.
Example of Statistics Details
About the Optimisation Reports

When you are running the Optimiser, you can choose to display the Optimisation
Report, by clicking the Report button.
This report includes coverage statistics based on the RF Array Thresholds that you
set, as defined in the following categories:
For this technology Statistics on the Report tabs
GSM RSS, CINR, Quality
UMTS RSCP, Pilot Ec/Io, Quality
CDMA2000 RSCP, Pilot Ec/Io, Quality
EV-DO RSCP, Pilot Ec/Io, Quality
Fixed WiMAX DL RSS, DL CINR, Quality
Mobile WiMAX Preamble RSS, Preamble CINR, Quality
LTE RSRP, RSRQ, Quality

You can view these details in terms of overall coverage, per clutter threshold and/or
per vector threshold. You can also view action information, and cost information.
If appropriate, you can choose to optimise a delta plan. If you begin a new
optimisation, the statistics information for the previous one will be deleted. However,
if you continue optimisation from the last generated delta plan, the statistics
information for the last optimisation will still be available.
The optimisation report provides details of the actions, statistics and costs for the
starting plan and each subsequent best plan. This picture shows an example:
Example of Part of an Optimisation Report
You can produce a similar report (for a specific delta plan) after you have stopped
the Optimiser, by selecting the appropriate plan in the Plan Manager section of the
Workflow, and clicking the Analysis button.
You may be able to choose which customised report format you want to use for
this report type. For more information, see Selecting Report Formats on page 104.

Alternative Optimisation Scenarios
When you have finished running the Optimiser, you can investigate alternative
optimisation scenarios, such as:
Using a different traffic array or traffic/service mix
Examining different types of actions and/or the impact of limiting the number of
actions further
Considering drive test measurements in the pathloss predictions and/or running a
drive test route-based optimisation
Modifying the optimisation targets and/or approach through the Strategy and
Settings and (depending on the setup and user permissions) the algorithmic setup
Explicitly focusing the optimisation on problematic areas/cells only
Using a generated delta plan as the starting configuration
Any combination of the above scenarios
In addition, you should also refer to Recommendations and Guidelines on page

34.
Applying a Plan to the Database

When a plan has been optimised, it becomes a delta plan. At any time, you can Apply
a plan or a delta plan to the Site Database. This also enables you to analyse the
performance of the plan (using arrays and reports) within ASSET.
For more information on this, see:
Applying a Plan to the Database on page 150.
Applying a Plan Temporarily to the Database on page 151.

CHAPTER 7
Analysing and Evaluating

Plans
The analysis functionality in ADVANTAGE enables you to analyse your network
plan against your chosen optimisation strategy, including the metrics and targets that
you have specified.
More specifically, it enables you to:
Analyse and evaluate a current plan configuration or an optimised delta plan
configuration
Compare any two plan configurations, whether current or optimised
Access the Ranking functionality, in order to assess and sequence the potential
network changes
Example of Analysis dialog box
You can evaluate a single plan, or compare two plans, in terms of their performance
(with respect to measurements and optimisation metrics).
As part of the network evaluation, statistics similar to those available in ASSET can
also be generated. The statistics include array-based metrics such as coverage and
interference (presented per clutter type and/or per vector) and, if applicable, service-
based metrics. In addition, feedback based on the specified optimisation metrics can
be provided.
The performance achieved for each configuration is compared with the user-specified
targets and presented (in terms of absolute and/or relative values) on a traffic and
area basis.

Analysing and Evaluating Plans
For optimised (delta plan) network configurations, the considered actions and action
costs are also included in the analysis. If this is the case, the analysis will generate a
report with separate information on:
Actions
Statistics
Costs
You can use the produced reports and/or graphical information to determine how
good a plan is, or the number/cost of the required optimisation actions (if applicable).
You can also use the Analysis dialog box to access the Ranking functionality, in order
to assess and sequence the potential network changes for either a Plan or Delta Plan.
For more information, see About Rollout Planning and Partial Plans on page 173.
As an ADVANTAGE user, you can use parts of the related ENTERPRISE analysis
functionality in addition to the ADVANTAGE-specific options. With specific regard
to measurements, please see Using Measurement Data on page 193.
Information Generated by the Analysis

You can use the generated analysis to evaluate (or compare) your plan configurations
in terms of the following types of information.
For more information on the metrics and parameters that are used by the analysis
functionality, see Setting RF Metric Targets on page 67.
The report generated can include (as appropriate):
Information Description Type

Actions The number of changes that the Antenna - antenna unit, device, pattern (remote and site
Optimiser has considered. These are adjustable electrical downtilt), mechanical downtilt, azimuth,
divided into antenna, power, grid and height
combined actions.
Power - powers (technology-specific), as well as BTS type
for GSM, and Node type for UMTS.
Grid - Property unit, Property, site unit, site, cell unit, cell
Combined - the combination of actions (for example, visit
actions) on a particular level (for example, per site).
Statistics The statistics for the metrics used in the Array-based: coverage, quality
optimisation calculations, according to the
array-based and service-based cost Service-based: served terminals, served terminals per cell,
mechanisms. served terminals in soft or softer handover, uplink and
downlink throughput, uplink and downlink cell throughput
(both averaged and weighted cost calculation)
Optimisation Costs All costs relating to the optimisation Array-based and/or service-based optimisation metrics as
metrics (array-based and/or service- specified above.
based).
If you have a Financial Analysis licence, you can also analyse financial metrics
such as Revenue, Expenditure, Net Income and Return On Investment (ROI). For
more information see the Financial Analysis User Reference Guide.

Prerequisites for Running an Analysis
Before performing an analysis, ensure that you (or your administrator) have:
For more information, see the ENTERPRISE and ASSET User Reference Guides.
Defined the RF Array Thresholds and the RF Metric Targets.
Settings tabs. For more information, see About the Optimiser Workflow on page
32.
(Optionally) defined the object/action-related costs. A post-optimisation analysis
may also consider action-related targets or delta plan costs (for example, costs for
antenna azimuth changes). For more information, see Specifying Costs/Limits on
page 74.
The above step is optional. If you do this, you must also specify the
performance targets of interest.
Created (or have access to) a plan. For more information, see Using and Managing
Plans on page 107.
Created/loaded traffic arrays, if applicable. For traffic-based optimisations, an
ENTERPRISE traffic array or a technology-specific ADVANTAGE traffic array
(using Spread Network Data or Loaded Cached Traffic) must be available.

Performing an Analysis for a Single Plan
Using the analysis functionality, you can analyse the performance of a network plan
or compare any two plans. Analysing the performance of a single plan enables you to
evaluate either a starting (new) plan or a delta (optimised) plan.
For information about the metrics used, see Analysing and Evaluating Plans on page
165 and Setting RF Metric Targets on page 67.
To analyse a single plan:
1 Ensure you have performed the required preparation steps, as described in
Prerequisites for Running an Analysis on page 167.
3 Select the appropriate plan, and click the Analysis button.

4 In the Analysis dialog box, the selected plan appears as the Base Plan.
(If you want to select a different plan, you can do this by clicking the browse
button .)
5 Select the reporting level you require (Property, Site or Cell).
6 Click Analyse to perform the analysis.
When the analysis has finished running, the Report button will become active.
7 To generate the report, click the Report button, then select the format for your
report, and click OK.
This report is similar to the Optimisation report (available from the Optimiser).
The difference is that this report focuses on a specific plan or delta plan.

Here is an example:
8 When you have finished, in the Analysis dialog box, you can either click Reset to
analyse or compare other plans, or you can click Close.
You may be able to choose which customised report format you want to use for
this report type. For more information, see Selecting Report Formats on page 104.

Performing an Analysis to Compare Plans
Using the analysis functionality, you can evaluate the performance of a network plan
or compare any two plans. Comparing the performance of two plans enables you to
assess one against the other, and evaluate any differences or improvements.
For information about the metrics used, see Analysing and Evaluating Plans on page
165 and Setting RF Metric Targets on page 67.
You can analyse and compare the performance between any two plans according to
your needs, whether they are plans or delta plans. You can also compare any two
delta plans, even if they originated from different starting plans.
To compare any two plans:
1 Ensure you have performed the required preparation steps, as described in
Prerequisites for Running an Analysis on page 167.
3 Select one of the two plans you want to compare, and click the Analysis button.
4 In the Analysis dialog box, the selected plan appears as the Base Plan.
(If you want to select a different plan, you can do this by clicking the browse
button .)
5 In the Analysis dialog box, for the Compare Plan, click the browse button,
and select the other required plan.
6 Select the reporting level you require (Property, Site or Cell).

7 If required, click the Compare Options button if you want to set default values for
comparing array pixels where one has a server and one does not.
8 Click Analyse to perform the comparison analysis. When the analysis has finished
running, the Report button will become active.
9 To generate the reports, click the Report button, then select the format for your
reports, and click OK.
10 When you have finished, in the Analysis dialog box, you can either click Reset to
analyse or compare other plans, or you can click Close.
You can also view the comparison analysis results in the Map View window. For
information on how to do this, see Displaying Plan Comparison Results in the Map
View on page 171.

Displaying Plan Comparison Results in the Map View
After you have performed an analysis to compare two plans, you can display your
results in the Map View window.
To do this:
1 Ensure you have a Map View window showing the considered network
configuration(s). If not, you can select the region(s) for the plans using the Plans
heading in the Data Types list:
2 On the Map View toolbar, click the Show Data Types button , or click the Map
Information & Control button and then click the Data Types tab.
3 To display plan comparison results (which show the coverage/interference arrays
for the chosen plans), expand the Delta Plan Analysis heading, and then expand
the required plan (or the 'Diff' category).
4 From the list that appears, select the array type that you want to view and click
Redraw to view the related analysis results:
5 To define how the array is displayed, double-click the required array and edit the
display properties in the dialog box that appears. You can set the following
display options:
 Which layers are displayed
 The colour used for the level of improvement
 The level of improvement you want to display

6 Click OK and then click OK and Redraw.
This picture shows an example of plan comparison analysis information displayed
on the Map View window. The values show the improvement between plans 2
and 1 for the Nth Pilot Server.

About Rollout Planning and Partial Plans
The Rollout Planning functionality provides a very useful way of determining the
order in which to make changes to a network.
You can sequence the changes (grouped by cell, site or Property) according to any
user-selected metric value (such as coverage, quality, revenue), and then assess the
potential cumulative improvement in the chosen metric (or any other chosen metric)
as the changes are implemented one by one.
In basic terms, this functionality asks the question: Which is the best (user-subjective)
sequence to perform the potential network changes, and how many of those changes are really
needed to achieve the required benefits?
For ADVANTAGE users, this functionality can be used with plans or delta plans.
Here are two examples:
Deployment or integration of new sites
Rollout Planning may be very useful if you are planning to add some new sites to
a network of existing sites.
By providing the ability to analyse the statistics (coverage, signal strength, cell
throughput, revenue and so on) down to the cell level, this functionality enables
you to assess the potential benefits of adding new cells. You can then use this
information to decide which sites you want to include in the network rollout, and
in which sequence.
For example, you might have 50 existing sites and 50 proposed sites in a plan.
After the initial analysis, this functionality enables you to sequence the changes
and evaluate the progressive or cumulative effect of the new sites. You could then
choose a modified sequence for the deployment of those proposed sites. Then,
after running a new analysis and report, you could re-evaluate the changes, and
specify a new sequence. When you are finally satisfied, you may decide that only
40 of those new sites are worth deploying, and create a partial plan.
Changes to an existing network
For this, the Rollout Planning would be more relevant to labour-intensive changes
requiring site visits, such as antenna azimuth or height changes.
For example, you might have a plan that proposes antenna changes on 30 sites.
After the initial analysis, this functionality enables you to sequence the changes
and evaluate their progressive or cumulative effect. You could then choose a
modified sequence for the deployment of those changes. Then, after running a
new analysis and report, you could re-evaluate the changes, and specify a new
sequence. When you are finally satisfied, you may decide that the changes on only
15 of those sites are worth deploying, and create a partial plan.

The Rollout Planning functionality is accessible from the Analysis dialog box. The
Analysis dialog box, in its normal usage, provides the ability to analyse your network
configurations based on any user-selected metric, and then generate analysis reports
that contain single columns per metric. However, the added benefit of the Rollout
Planning functionality is that it enables you to sort, re-analyse and produce a
cumulative report with multiple columns per metric.
In summary, after performing an analysis, you can use this functionality to:
1 Set the ranking level to Property, Site or Cell.
2 Re-sequence the rows of potential network element changes according to any of
their analysed metric values.
3 Re-analyse.
4 Choose a reporting level.
5 Produce a cumulative report based on your chosen sequence.
In addition, if required, you can create a partial plan.
New and Existing Cells

There are several important benefits from choosing a status field to use to differentiate
between new network elements and existing network elements. For more information,
see Specifying a Field to Differentiate New/Existing Elements on page 100.
There are three principles to note about which elements are listed in the Element
Ranking dialog box:
1 All new network elements of a plan (plan, delta plan or partial plan) always appear
in the Ranking list.
2 The existing network elements of a delta plan (or partial plan from a delta plan)
appear in the Ranking list only if they have been changed by the Optimiser.
3 The existing network elements of a plan (or partial plan from a plan) all appear in
the Ranking list if there are not any new elements in the plan.

Using the Rollout Planning Dialog Box
When you are using the Analysis dialog box, you can use the Rollout Planning
functionality to assess and sequence the potential network changes for a plan or delta
plan. You can also choose to create a partial plan.
To do this:
1 Run the Analysis in the normal way.
2 Wait until the analysis has finished running.
3 Click the Rollout Planning button.
The Rollout Planning dialog box appears, as in this example:
pp
You can:
 List the elements by their Ranking level: Property, Site or Cell
 Show the columns for Absolute Values and/or Additional Improvement in the
dialog box (this has no impact on the report, which always includes both types
of information).
 Sort the rows by clicking on any of the column headings
 Promote or demote any elements by selectively highlighting the row(s) and
using the Up/Down arrow buttons
4 To generate a fresh analysis of your changes (taking the new sequence into
account), click Analyse.
When the analysis has finished running, the Report button will become active.
5 Select the reporting level you require.

6 Click the Report button, then select the format for your report, and click OK.
This report enables you to view and assess the cumulative statistics (relating to the
chosen metrics) for each cell, site or Property. Here is an example of a report, after
ranking the above results by coverage:
This example report has been simplified (rows have been removed) for clarity.
In this example, the 'partial plan' values in the columns (when read left to right)
illustrate how the overall coverage value increases as each additional site/node in
the sequence is considered for inclusion in the plan. Obviously, at the same time as
the summed value increases, the individual coverage value for each site/node
tends to diminish.
A separate report will be generated for each of the metrics that you specified
when setting up the analysis. For example, if you selected Coverage and Quality,
two separate reports would be presented.
7 In the Rollout Planning dialog box, if you want to change the element sequence
and re-analyse, you can now click the Reset button.

Creating a Partial Plan
In the Rollout Planning dialog box, when you have finished re-sequencing the
potential changes, you can optionally create a 'partial plan'. This means that you can
decide which changes are really beneficial (based on the chosen metric) to the
improvement of your network, and create a new reduced plan.
If appropriate to your requirements, you can then Apply (or Temp Apply) the partial
plan to the database, or use it in an optimisation.
To do this:
1 Check that you have finished re-sequencing and analysing your changes in the
Rollout Planning dialog box.
2 Decide which items you want to include in the partial plan (sequence 1 to n).
3 Click on the row that relates to Sequence n (that is, the lowest ranked item in your
proposed partial plan).
4 In the example shown here, clicking the row relating to Sequence 6 would create a
plan that includes the items in the top six rows (1 to 6 inclusive):
5 Click the Partial Plan button.

A new partial plan is automatically created, and listed in the Workflow dialog box,
under the plan from which it was created. Here is an example:
Example of Partial Plan appearing in Workflow dialog box

CHAPTER 8
Identifying Problems in a
Network
ADVANTAGE enables you to focus the optimisation process, either automatically or
manually, on the areas or cells of the network that are underperforming. The focus is
on the identification of:
Problem areas in the network
Problem cells in the network
The problem area and/or cell identification analysis allows you to define the expected
performance both in terms of design targets for offered services, and also in terms of
area served or traffic captured, or both. This identifies the areas of poor performance
that are critical to network efficiency. By correlating the performance achieved and
the area and/or traffic served, ADVANTAGE can quickly improve the achieved
revenue from the network.
This functionality is only available for GSM and UMTS.

Identifying Problems in a Network
About Problematic Areas and Cells
Problems with areas may include:
Low Coverage
Low Quality
Low Dominance
For information on defining problem criteria for areas, see Configuring Problem Area
Thresholds on page 181.
Problems with cells may include those that:
Are associated with coverage problems within their best server area
Are associated with quality problems within their best server area
Provide coverage to low levels of traffic
Provide coverage to small areas
Provide coverage to high levels of traffic
Provide coverage to large areas
Are associated with interference (low quality) problem areas
Provide coverage to areas of low dominance
Experience a large number of dropped calls
Experience a large number of handovers (as source cells)
To identify these last two options, the respective network data must have been
imported, as described in Spreading Network Data on page 202.
For problem cell identification, the imported (rather than spread) data is used.
For information on defining problem criteria for cells, see Configuring Problem Cell
Thresholds on page 183.
After you have set the necessary area/cell problem criteria, you can identify
problematic areas or cells by using Problem Area and Cell Identification. For
information, see Identifying Problem Areas and Cells on page 185.
You can also specify (or produce automatically) cell-specific weights that can be
considered during optimisation. The problem cells can subsequently be targeted by
the automatic optimisation algorithm. This ensures that increased priority is given to
these cells, enabling more efficient automatic optimisation. For information, see
Configuring Problem Cell Weights on page 190.

Configuring Problem Area Thresholds
Problem area thresholds are only available for GSM and UMTS.
You can configure problem area thresholds to define the criteria used for identifying
problem areas in your network. When you later identify problem areas, any areas that
do not satisfy these thresholds will be classified as problematic.
The problem area categories available are:
Low Coverage
Low Quality
Low Dominance
The array used during the identification process for Low Coverage and Low
Dominance is the Best Server array (GSM) or Best Pilot Server array (UMTS).
The array used during the identification process for Low Quality is the Average
Connection (C/I) array (GSM) or Best Ec/Io array (UMTS).
To configure problem area thresholds:
1 From the Tools menu, point to Problem Identification, then point to Problem Area
Thresholds, and then click the required technology (GSM or UMTS).
2 On each tab, you can set clutter-specific threshold values as follows:
Category Threshold Classification of Problem Area
Low Coverage Min Signal Strength (dBm) Anything less than this value
Low Quality Min Quality (dB) Anything less than this value
Low Dominance Max Servers Anything more than this value
The above criteria also depend on whether at least one of the associated
traffic/area thresholds is also exceeded, as described below.
3 On each of the three tabs, you can also set associated threshold values as follows:
Category Threshold Classification of Problem Area
Low Coverage Min Traffic (E - but this can Anything more than this value (for a contiguous
Low Quality represent any unit) area)
Low Dominance
Low Coverage Min Area (km²) Anything more than this value (for a contiguous
Low Quality area)
Low Dominance
If either of the above values is exceeded, the area may qualify as problematic,
depending on the associated value for Low Coverage, Low Quality or Low
Dominance.
4 When you have completed your changes, click Apply, and then click Close.

Example
Here is an example, valid for either GSM or UMTS:
Example of configuring problem area thresholds
In this example, on the Low Coverage problem area category, the criteria for a
contiguous low coverage (that is, problematic) area have been set to any urban area:
 with at least 10 Erlangs* of traffic OR of at least 1 km² in area
AND
 where the signal strength is less than -100 dBm

* (E can represent any unit)
If the Min Traffic and Min Area had not been set, even a single pixel with less than -
100 dBm signal strength would be classified as a low coverage problem area.

Configuring Problem Cell Thresholds
Problem cell thresholds are only available for GSM and UMTS.
You can configure problem cell thresholds to define the criteria used to classify
problem cells (both GSM and UMTS) in your network. When you later identify
problem cells, any cells that do not satisfy these thresholds will be classified as
problematic, and you can use this information to focus on problem cells and their
neighbours when you run an optimisation. For more information, see Specifying the
Settings on page 90.
To configure problem cell thresholds:
1 From the Tools menu, point to Problem Identification, then click Problem Cell
Thresholds.
2 In the dialog box that appears, expand either GSM or UMTS, as appropriate.
3 Expand the required category, and select the threshold you want to configure. The
following table describes these thresholds:
Category Threshold Description Classification of Problem Cell
Large # of Dropped Max Maximum number of dropped calls. Anything exceeding this value.
Calls
Max % of Carried Traffic Maximum number of dropped calls, As above.
as a proportion of traffic.
Large # of Max Maximum number of calls in Anything exceeding this value.
Handovers handover
Max % of Carried Traffic Maximum number of calls in As above.
handover, as a proportion of traffic.
Low Coverage Min Signal Strength Minimum level of signal strength Anything less than this value - but
(dBm) for the best server cell in the pixel. only if one or both of the associated
traffic/area thresholds is also
exceeded.
Min Coverage Probability Minimum probability of the above As above.
(%) signal strength being reached in
the pixel.
Min Traffic Minimum traffic associated with Anything exceeding this value - but
low coverage. only if one or both of the associated
coverage thresholds is also
exceeded.
Min Area Minimum area associated with low As above.
coverage.
Low Quality Min Quality (dB) Minimum signal quality level Anything less than this value - but
required for the best server cell in only if one or both of the associated
the pixel. traffic/area thresholds is also
exceeded.
Min Quality Probability Minimum probability of the As above.
(%) minimum quality level being
reached in the pixel.
Min Traffic Minimum traffic associated with Anything exceeding this value - but
low quality. only if one or both of the associated
quality thresholds is also exceeded.
Min Area Minimum area associated with low As above.
quality.

Category Threshold Description Classification of Problem Cell
Low Traffic Min (E - but can Minimum amount of traffic that a Anything less than this value.
represent any unit) cell should carry.
Min % of Mean Traffic Minimum proportion of the mean As above.
carried traffic that a cell should
carry.
Small Area Min (km²) Minimum area that a cell is Anything less than this value.
required to cover.
Min % of Mean Area Minimum proportion of the mean As above.
covered area that a cell is required
to cover.
High Traffic Max (E - but can Maximum amount of traffic that a Anything exceeding this value.
represent any unit) cell should carry.
Max % of Mean Traffic Maximum proportion of the mean As above.
carried traffic that a cell should
carry.
Large Area Max (km²) Maximum area that a cell is Anything exceeding this value.
required to cover.
Max % of Mean Area Maximum proportion of the mean As above.
covered area that a cell is required
to cover.
Notes :
 Within the Problem Cell categories that contain a pair of thresholds, the two
thresholds operate on an OR basis. Within the Low Coverage and Low Quality
categories, the first pair of thresholds operate on an OR basis, but each one also
operates on an AND basis with its respective Min Traffic OR Min Area
threshold.
 Dropped Call and Handover problem cells will only be identified if you have
corresponding network data. Furthermore, if you have more than one type of
data for these (for example, DroppedCallsLev and DroppedCallsQual),
ADVANTAGE combines the respective data into a single value per cell for
problem cell identification purposes.
4 In the Values column, double-click a value and type the new one.
5 When you have completed your changes, click Apply, and then click Close.

Identifying Problem Areas and Cells
You can run the Problem Area and Cell Identification to identify problematic areas
and cells in your network. The identification process always relates to a specific plan,
therefore the area and cells are determined by the Map View and filters that were
appropriate when the plan was created.
Problem area and cell identification is only available for GSM and UMTS.
Prerequisites
Before performing problem area and cell identification, ensure that you (or your
administrator) have:
For more information, see the ENTERPRISE and ASSET User Reference Guides.
Defined the RF Thresholds in the Optimiser Workflow.
Settings tabs (such as terminal types, array settings). For more information, see
About the Optimiser Workflow on page 32.
Defined the Problem Area and/or Cell Thresholds, as appropriate. For more
information, see:
 Configuring Problem Area Thresholds on page 181
 Configuring Problem Cell Thresholds on page 183
To identify problem areas and cells:
1 Ensure you have performed the required prerequisites, as described in Identifying
Problems in a Network on page 179.
2 From the Tools menu, point to Problem Identification, then click Problem Area
and Cell Identification.
3 Select the appropriate plan, and click OK. This is necessary to focus on the
relevant area and cells.
4 In the dialog box that appears, on the Problem Area Cell Identification tab, select
the checkboxes next to the parameters that you wish to be considered when
identifying problem areas and cells.
If you select one of the problem cell types that relate to a similar problem area
type (Low Coverage, Low Quality, Low Dominance), then the corresponding
problem area type is also selected. In these cases, you cannot identify problem
cells independent of the area they are associated with.
5 Click Start.
Problem areas and cells are identified.

6 When you have run the identification, you can generate one or both of these
reports:
 Problem Area Report
 Problem Cell Report
Click the appropriate button, and then select the type of report you want to
generate, and click OK.
You can also specify (or produce automatically) cell-specific weights that can be
considered during optimisation. The problem cells can subsequently be targeted by
the automatic optimisation algorithm. This ensures that increased priority is given to
these cells, enabling more efficient automatic optimisation. For more information, see
Configuring Problem Cell Weights on page 190.
About the Information Shown in a Problem Area Report

After you have identified problem areas, you can view a problem area report. This
picture shows an example of a problem area report for low coverage (UMTS
network):
Example Problem Area Report (UMTS Problem Area tab)
The report details the number of problem areas, the amount of affected traffic (given
in E, but this can represent any unit) and the size of the affected area (in km²).
To quickly identify the most or least problematic area, use the Sort
Ascending/Descending function in Excel.

As well as generating a report, you can also view problem area data in the Map View
window. For information on how do this, see Displaying Problem Area Data in the
Map View on page 187.
Displaying Problem Area Data in the Map View

After you have generated a Problem Area Report, you can also view problem area
data in the Map View window. To do this:
1 Ensure you have a Map View window showing the considered network
configuration(s). If not, you can select the region for the plan using the Plans
heading in the Data Types list:
3 Select the appropriate problem areas from the Problem Areas folder.
4 Click Redraw.
The problem area data will be displayed.
This picture shows UMTS Coverage Problem Areas in the Map View window:
Example UMTS Coverage Problem Areas (Map View)

If you want to display several problem areas at once, and view information on each as
you hover over the Map View:
1 Click the Edit Map Information button .

2 In the Map Information Field Selector, select the required problem areas, and then
click Add.
3 Click OK.
If you want to define colour profiles for different problem areas, double-click on
the problem area in the Map Information and Control dialog box. In the dialog box
that appears, on the Problem Area tab select a colour to represent the starting value,
and on the Selected Areas tab choose which problem areas to show on the Map View
window.

About the Information Shown in a Problem Cell Report
After you have identified problem cells, you can view a problem cell report (for both
GSM and UMTS). This picture shows an example of the Summary tab of a Problem
Cell Report for Low Coverage and Low Quality:
Example Problem Cell Report (Summary tab)
As well as the summary, each report has a separate page for each problem type
ADVANTAGE has identified. In the example above, the problem of Low Coverage is
identified. This picture shows the Low Coverage tab:
Example Problem Cell Report (Low Coverage tab)

Notes :
The report also shows the problem areas related to the respective problem cells,
since these are considered when identifying problematic cells.
Traffic values in the summary and separate problem type reports are given in E,
but this can represent any unit.
Configuring Problem Cell Weights

Problem cell weights are only available for GSM and UMTS.
You can use problem cell weighting to prioritise actions (changes) to cells that have
shown poor performance (based on the analysis output and/or network
measurements) or should be given a higher priority anyway. You can use this
information to focus on problem cells and their neighbours when you run an
optimisation. For more information, see Specifying the Settings on page 90.
You can configure problem cell weights automatically or manually.
To configure the problem cell weights automatically:
1 Identify the problem cells in your network. For more information on how to do
this, see Identifying Problem Areas and Cells on page 185.
4 In the Problem Area and Cell Identification dialog box, click the Problem Cell
Weights tab.
Based on the problem cells identified:
 Cell weights are produced (if applicable), and displayed in the cost multiplier
column. The default weight is 1.0000 (no priority) and higher values indicate a
more problematic cell and therefore a greater priority for the optimisation.
 Cells are classified as problematic (or otherwise) in the Problem column.
This picture shows an example, where 3 problem cells have been identified:

5 Click Apply to save to the database, and (if required) Commit.
You can choose to manually edit the automatically produced weight values, and
also select/deselect any of the cells.
To configure the problem cell weights manually:
3 In the In the Problem Area and Cell Identification dialog box, on the Problem Cell
Weights tab, double-click the required cell's Cost Multiplier value and type the
new value. The default weight is 1.0000 (no priority) and higher values indicate a
more problematic cell and therefore a greater priority for the optimisation.
For example, a cost multiplier of 2.0000 would give that cell a weight twice that of
the other cells. You can also use lower values if you require. You can even use 0, in
which case the cell will be included in the optimisation but will not contribute to
the cost calculations.
If you edit the weight of a problem cell, it is automatically selected.

To remove the manual problem cell weights and use the default unitary weights:
1 Select the appropriate technology level checkbox, and then deselect it, so that all of
the cell-specific checkboxes are automatically unselected.

CHAPTER 9
Using Measurement Data

ADVANTAGE enables you to import and use:
Network data
This data (such as performance engineering data), can provide information that is
crucial to understanding the performance of your network.
You can import cell (and cell pair)-specific information into ADVANTAGE, which
is spread intelligently in the area of interest and used in the analysis/optimisation.
Measurement data that is area or cell-specific
This data (typically drive test data) can be used to generate measurement-based
pathloss files, which you can then use to influence predictions and/or run a drive
test route-based analysis/optimisation.
It can also be used for model analysis, model tuning (calibration) and to identify
signal reception problems.
In a similar way to ASSET, you can also use the standard ENTERPRISE traffic
functionality in ADVANTAGE to create/load/modify a traffic array, whether live
traffic is considered or not. For more information on this, see the ASSET User
Reference Guide.
Using measured data, ADVANTAGE can model the network more accurately, basing
its results on measured performance, and consider the measurements in the analysis
and optimisation.
Network data spreading is available for GSM and UMTS only. However, the use
of measurement data functionality is available for all technologies.

About Intelligent Spreading of Network Data
Network data spreading is available for GSM and UMTS only.
ADVANTAGE can incorporate cell-specific measurements into the optimisation
process. This enables you to consider measured data in addition to the most accurate
pathloss predictions. In this way, it is possible to use measurements to tune the
predicted network behaviour.
Using the ADVANTAGE-specific spreading mechanisms, you can import and spread
on a pixel basis any Key Performance Indicator (KPI) data. You can then visualise and
pinpoint the areas and/or cells that are under-performing, focus the Optimiser on the
network problem regions, thus increasing efficiency and reducing optimisation
process times.
The default types of network data that you can import in ADVANTAGE are traffic,
congestion (%), dropped calls and handover statistics.
For details about how other data types can be imported, see Configuring the
Format for Additional Data on page 200.
The following picture shows an example of different types of network data being
imported into ADVANTAGE:
Importing network data in ADVANTAGE
The values shown are only for representative purposes.

The following pictures show examples of arrays (Traffic and DroppedCallsOther)
created by spreading network data over a selected area:
A typical array of spread network data - Traffic
A typical array of spread network data - DroppedCallsOther
In the first example, the areas of green represent low traffic density. In the second
example, the areas of red represent a high number of dropped calls due to reasons
other than signal strength or interference.

How ADVANTAGE Spreads Traffic Data
Amongst cell-specific data, traffic is fundamental for analysis/optimisation purposes.
In ADVANTAGE, the imported traffic per cell can be spread within the examined
area in an intelligent and realistic fashion, so that any subsequently produced
optimisation plan is more likely to improve the 'real-life' network performance.
The standard ENTERPRISE traffic functionality can also be used in ADVANTAGE

to create/load/modify a traffic array.
There are a number of potential chronic problems inherent in planning, as
summarised here:
Potential Problems
Traffic only spread to an individual best server cell within a pixel:
Unrealistic discontinuities in traffic density. This will skew any cost function based on traffic covered.
Traffic not spread to areas with no coverage:
Any cost function based on traffic will see no benefit in increasing coverage. Network coverage expansion cannot be automatically
planned based on this data.
Traffic spread dictated by user-defined density weightings:
You must pre-estimate weightings. This is likely to incorrectly skew traffic distribution between land usage categories.
Direct usage of network-recorded traffic:

The traffic recorded in the statistics is the carried traffic, rather than the traffic offered to the network. Using this traffic will
underestimate the load on the network.
Imperfect coverage not accounted for:
When an infill site is introduced for capacity reasons, it is typical to see a traffic increase due to improved coverage. For instance, if
the coverage probability is increased from 80% to 90% in a region, it is reasonable to expect a similar increase in offered traffic.
The way that traffic is spread by ADVANTAGE alleviates the above problems,
because the traffic spreading process acknowledges the likelihood that a pixel may be
covered by any of the predicted servers/cells. The calculated coverage probability
and the traffic per cell (from the imported network data) are used to generate a
system of equations, which are solved so that the predicted and measured data are
consistent. The two end products of traffic spreading are a technology-specific traffic
array and a set of cell-specific traffic modifiers.

About the Spreading Mechanisms in ADVANTAGE
The spreading mechanisms used in ADVANTAGE are described in the following
table, for which these definitions apply:
Coverage Probability is based on (as applicable):
 The Nth Best Server array for GSM
 The Nth Best Pilot Server array for UMTS
 The respective minimum signal strength value specified in the Data Array
Wizard
Interference is based on (as applicable):
 The Nth Average Connection (C/I) array for GSM
 The Nth Best Ec/Io array for UMTS
Use This To Example of Network Default Naming

Mechanism Data spread this way Convention in
ADVANTAGE
Traffic Spread data based on clutter and Traffic Traffic
coverage probability for each cell; this
spreading process is actually an
optimisation that will identify the optimal
clutter type traffic densities, based on
the imported data and the considered
network configuration and RF
Thresholds in the Optimiser Workflow.
Weighted Average Spread data (weighted) based on the Congestion probability Congestion
coverage probability for each cell.
Even Spread data (uniformly) based on the Dropped calls due to reasons DroppedCallsOther
traffic and coverage probability for each other than signal strength or
cell. interference
Signal Strength Spread data based on the traffic, clutter Dropped calls due to signal DroppedCallsLev
and coverage probability for each cell; strength
this spreading process is actually an
optimisation that will identify the
minimum signal strength threshold
below which calls are dropped, based on
the imported data and the considered
network configuration and RF
Interference Spread data based on the traffic, clutter, Dropped calls due to DroppedCallsQual
coverage probability and interference interference
probability for each cell; this spreading
process is actually an optimisation that
will identify the minimum interference
threshold below which calls are dropped,
based on the imported data and the
considered network configuration and
RF Thresholds in the Optimiser
Workflow.

Use This To Example of Network Default Naming
Mechanism Data spread this way Convention in
ADVANTAGE
Relative Signal Spread data based on the traffic and Handovers due to link budget HandoverLinkBudget
Strength (1) coverage probability for each cell pair,
taking into account the handover margin
values defined in the Site Database and,
if not, the Handover Margin specified in
Settings in the Optimiser Workflow.
Relative Signal Spread data based on the traffic and Handovers due to signal HandoverLev
Strength (2) coverage probability for each cell pair, strength
taking into account the absolute signal
strength thresholds defined in the Site
Database and, if not, the RF Thresholds
in the Optimiser Workflow.
Relative Interference Spread data based on the traffic, Handovers due to interference HandoverQual
and (absolute) Signal coverage probability and interference
Strength probability for each cell pair, taking into
account the relative interference and
absolute signal strength thresholds
defined in the Site Database and, if not,
the RF Thresholds in the Optimiser
Workflow.
Relative Signal Spread data based on the traffic, Handovers due to interference N/A
Strength and coverage probability and interference
(absolute) interference probability for each cell pair, taking into
account the relative signal strength and
absolute interference thresholds defined
in the Site Database and, if not, the RF
For more information on the RF Thresholds and Settings, see About the Optimiser
Workflow on page 32.
For more information on configuring networks, see the ASSET User Reference Guide.

Configuring the Format for Importing Network Data
You can import network data (that is, cell-specific data) into ADVANTAGE using:
An appropriate ADVANTAGE-specific Excel spreadsheet
An appropriate table and view in an Oracle (for example, OPTIMA) database
Data types named as traffic or congestion are automatically recognised by
ADVANTAGE and associated with the correct default spreading mechanism.
However, additional data can be imported in ADVANTAGE and spread, based on
any of the existing spreading mechanisms. For information on how to configure the
format for this additional data, see Configuring the Format for Additional Data on
page 200.
The following table describes how to configure the Excel spreadsheet for use in
importing generic network data:
Table sheet Description
1st Sheet (Network data per Cell) The first row must contain a description of the data, for example, Network Data -
Per Cell.
COMPULSORY
The second row is empty.
The third row contains three columns which are fixed (Cell Technology, Cell ID, Cell
Layer / 3g Carrier). The subsequent columns represent a network data counter,
such as Traffic, Congestion or Dropped Calls. The first sheet should always have
one data column representing Traffic.
To import additional data, you can add more columns with different names. For
information on how to configure the format for this additional data, see Configuring
the Format for Additional Data on page 200.
Data starts on the fifth row. The first column identifies the technology type (GSM,
UMTS and so on). The second column is the cell ID, the third the cell layer / 3g
carrier name. Subsequent columns represent the per cell value, which may be
blank.
2nd Sheet (Network Handover data, The first row must contain a description of the data, for example, Network Data -
per cell pair) Handovers.
OPTIONAL The second row is empty.
The third row contains six columns which are fixed (Cell Technology, Cell ID, Cell
Layer / 3g Carrier for both the handover source and destination cell). The
subsequent columns represent a handover data counter, such as Handover due to
Link Budget.
Handover data can be defined between a GSM and a UMTS cell. But
ADVANTAGE will only (at present) consider handover data for cells of the same
technology. Also, ADVANTAGE will ignore handover data defined for the same cell
(for example, Site3A GSM-900 -> Site3A GSM-900).
Data starts on the fifth row. The format is the same as for network data, with the
addition of entries for the handover source and the destination cells.
If you are using OPTIMA, the import file format could match the (optional) report
generated by the Data Array Wizard. This enables you to import from an OPTIMA
database, generate a report, and import the data from the report whenever the
database is not accessible.

Configuring the Format for Additional Data
As well as data types such as traffic and congestion, which are automatically
recognised by ADVANTAGE, you can import additional cell-specific data, for
example, revenue per cell.
To configure this data to be in the correct format for import:
1 Ensure you have a column with the required counter name, containing the data of
interest, in the Network Data Excel file.
2 Add a key named as the required counter to the registry, under
HKEY_CURRENT_USER\Software\AIRCOM\ENTERPRISE\Settings\Server(the
name of the server where the database of interest is located)\Instance(the database
ID)\Project (the ENTERPRISE project number saved in the database)\User(the
ENTERPRISE user ID)\ADVANTAGE\Counters, with String values similar to the
ones created for Traffic, assuming that traffic has already been spread and a
registry entry has been created.
- or -
Rename one (or more) of the default counter registry entries and then change the
rest of the related settings in the Data Array Wizard.
If an OPTIMA database is used, only the table and view for the consideration of
network data should be appropriately defined. If you require assistance in setting this
up, please contact the support team at the address described in Obtaining Support on
page 18.
Examples of the ADVANTAGE Import Format

The following pictures show examples of configured Excel spreadsheets, depicting
the import format.
The values shown in these pictures are only for representative purposes.
This picture shows an example of the first sheet (Per Cell) of an Excel spreadsheet
used to import network data:
Example of the first sheet (Per Cell) of an Excel spreadsheet used to import network data

This picture shows an example of the second sheet (Handovers) of an Excel
spreadsheet used to import network data:
Example of the second sheet (Handovers) of an Excel spreadsheet used to import network data
About Spreading Network Data

ADVANTAGE enables you to import and use network data, enabling you to use
information that is crucial to understanding the performance of your network. After
you import the cell-specific (or cell pair-specific) information into ADVANTAGE, it is
spread intelligently in the area of interest.
Using measured data, ADVANTAGE can model the network more accurately, basing
its results on measured performance, and consider the measurements in the
optimisation and analysis processes.
You can also use the imported network data to identify and visualise particular areas
and/or cells of the network that are underperforming. You can then focus the
optimisation on these areas and/or cells, thus ensuring that the resulting changes will
respond directly to real problems. For more information on this, see Identifying
Problems in a Network on page 179.
Using the ADVANTAGE-specific spreading mechanisms, you can import and spread
on a pixel basis any Key Performance Indicator (KPI) data. The default types of
network data that you can import in ADVANTAGE are:
Traffic levels
Congestion percentage
Dropped call statistics
Handover statistics
For details about how other data types can be imported, see Configuring the
Format for Importing Network Data on page 199.

Prerequisites
Before spreading network data, you (or your administrator) need to have:
Set up a project with the necessary planning data. For more information, see the
ENTERPRISE and ASSET User Reference Guides.
Specified the RF Thresholds and General Clutter Parameters (Importance) in the
Optimiser Workflow. For more information, see Specifying RF Array Thresholds
for Clutter on page 60 and About the Optimisation-Based Spreading Algorithms
on page 213.
Settings tabs (such as terminal types, array settings). For more information, see
About the Optimiser Workflow on page 32.
Correctly configured the format (based on an Excel file or a Performance
Engineering management database) of the data that you want to import. For more
information, see Configuring the Format for Importing Network Data on page 199.
Spreading Network Data

To import and spread network data:
1 Ensure you have performed the required prerequisites, as described in About
Spreading Network Data on page 201.
2 From the Arrays menu, point to Network Data and click Data Array Wizard.
3 In the dialog box that appears, select the appropriate plan. This contains the
required information in terms of cells and region, and, if appropriate, vectors (in
which case the data spreading will be restricted accordingly).
4 To specify the folder where the cached traffic arrays will be saved, click the
button in the Cached Array Path pane, browse to the folder where you want to
save the arrays, and click OK.
5 Specify the minimum signal strength for GSM and/or UMTS as appropriate.
Network data will only spread to areas where the signal strength is above this
threshold.
6 Click Next.
7 Select the data you want to import:
 To import from a file, select Import from file and click the Browse button.
Locate the file, click Open and then click Next.
 To import directly from an OPTIMA database, select Import from Database
and choose an application and data source. Type in your user ID and
password and then click Next.

8 Select the checkboxes for the specific network data types you want to spread, and
(if you wish to change the default mechanism for that type) click in the Spreading
Mechanism column and choose from the resulting list. Each list is dependent on
the specific network data type (for example, only the handover-related spreading
mechanisms are available for data described as HandoverLinkBudget). If required,
you can also enter or modify the unit for each network data type.
If you are importing from an OPTIMA database, you can choose to filter the
data, by selecting a start date and an end date and a time. (Currently, the most
recent data matching these conditions is loaded).
9 To generate a report about the spreading of network data:
 Select the Generate Report box.
 Click Next.
 In the dialog box that appears, select the format for your report. If you choose
a text file, select a program to open it with.
 Click OK.
The results are displayed in your chosen format. You can save the report if
required.
10 Click Finish. The network data is spread, and a summary list is displayed:
11 Click Done.
After you have spread network data, you can then display it, in either:
The Map View window
- or -
The Network Data Values dialog box

Displaying Spread Data on the Map View
In the Map View window, you can view the network data you have spread, enabling
you to identify geographical areas or cells where problems in the network may be
experienced.
To do this:
1 Open a Map View window displaying the area you want to view.
3 From the list of Data Types, expand Processed Performance Data, then the
required technology (GSM or UMTS), and then select the data you want to
display.
4 Click Redraw.
The chosen network data array is displayed.
If you want to change how the data is displayed, double-click on the data you
want to display in the list of Data Types. Select the start colour, the Start value
(this is the minimum value to be displayed), the Interval value (this is the step
value), as well as the Units (for example, Erlangs). Click OK and then click OK and
Redraw.
5 If you want to view the value per pixel for this array, ensure Show Map View
Gadgets is selected from the View menu on the Map View window.
6 On the pane, click the Edit Map Information button .

7 In the dialog box that appears, in the Available Items pane, select Processed
Performance Data, and click the button.
8 Click OK.
9 Double-click the 'Please select Data Array' text at the bottom of the Map View
window:
10 In the dialog box that appears, select the array for which you want to display
information, and click OK.

11 As you move the mouse cursor over the map, the pane at the bottom of the Map
View window displays the network data value for the specific pixel under the
cursor:
Displaying Spread Data in the Data Values Pixel Analyser

As well as viewing spread network data in the Map View, you can view more
detailed information in the Data Values Pixel Analyser. The values are per pixel, and
are based on the chosen area and network, the data spread and the resolution selected
for spreading.
To display network data in this way:
1 Ensure you have opened the Map View window, and displayed the area of
interest.
2 From the Arrays menu, point to Network Data and click Data Pixel Analyser. The
Data Values dialog box appears.
3 Hover the mouse pointer over the pixel where you wish to view the data values.
The corresponding values for this location are displayed:

The types of data you can view correspond to the four tabs on the Data Values dialog
box. The following table describes these tabs:
Click this tab To view
Spread Data The estimated values per pixel for the data imported through spreading.
If handover data has been considered, information on the estimated traffic in handover
(denoted as Traffic Affected) is also displayed.
Clutter Thresholds The estimated threshold values per clutter type for the used Spreading Mechanisms that involve
an optimisation; these thresholds are the traffic density for Traffic and the minimum signal
strength and interference thresholds for Signal Strength and Interference (if applicable) spread
data.
You need to have displayed clutter data on the Map View for this to be applicable.
Cell Modifiers The estimated modifier values per best server cell (pilot for UMTS) for the used Spreading
Mechanisms that involve an optimisation. These modifiers may be required for all the considered
cells and traffic, signal strength and interference (if applicable) spread data to ensure that the
respectively imported (measured) and estimated network data information is identical.
Probabilities The estimated Coverage and Quality Probability per pixel.
The Coverage Probability is actually calculated during the traffic spreading process; the
non-signal strength-based Quality Probability is not, and will return zero values, unless a Quality-
based Spreading Mechanism is considered, or the Problem Cell Identification Quality criterion is
used. See Identifying Problem Areas and Cells on page 185 for more information.
Re-Spreading Network Data

Re-spreading network data enables you to view estimated network data after an
optimisation plan has been considered.
To re-spread network data, you should have already spread network data. This is
because re-spreading is based on the initially spread data, as well as the Site Database
information for the appropriate cells.
You cannot re-spread network traffic data, so if there is no other type of network data,
the Re-Spread Data option will not be applicable.
To re-spread data:
1 From the Arrays menu, point to Network Data, and click Re-Spread Data.
2 In the dialog box that appears, select the appropriate plan. This contains the
required information in terms of cells and region.
3 Click OK.
Once the network data is re-spread, you can view the estimated network data in the
Map View window in the same way as you view spread network data. For more
information, see Displaying Spread Data on the Map View on page 204.

About Cached Traffic Arrays
Each time you spread data, the resulting traffic array is stored (cached), which means
you do not have to recreate the same array again. In ADVANTAGE, you can easily
load these stored arrays. For information on how to do this, see Loading Cached
Traffic Arrays on page 89.
Performing Network Data Array Operations

In ADVANTAGE, you can perform a number of network data array operations. You
can:
Manipulate network data arrays:
 Scale the arrays
 Combine the arrays
Manage network data arrays:
 Rename, load, save or delete the arrays
You can also re-spread network data, which enables you to view estimated network
data after an optimisation plan has been considered. For more information, see Re-
Spreading Network Data on page 206.
Scaling Network Data Arrays

After you have spread network data, you can scale the network data arrays.
By scaling arrays, you can see the effects on your network of, for example, doubling,
or halving an array's data values. Scaling increases or decreases the values present in
a spread data array at a given ratio. This ensures that the data values are uniformly
increased or decreased.
To scale arrays:
1 From the Arrays menu, point to Network Data and click Data Array Operations.
2 On the Manipulate Data Array tab, select the array you wish to scale.
3 In the Array Scaling pane, click .

4 Type the required scaling (between 0 and 10) into the box, or drag the bar
horizontally to the required scaling value.
5 Click Apply Scaling Factor.
6 Click Close.

Combining Network Data Arrays
After you have spread network data, you can combine the network data arrays.
By combining arrays, you can visually compare the results from different arrays.
To combine arrays:
1 From the Arrays menu, point to Network Data and click Data Array Operations.
2 On the Manipulate Data Array tab, select the first array you wish to combine.
3 In the Array Combining pane, click the upper .
4 Select the second array, and in the Array Combining pane, click the lower .
The two arrays must be of the same resolution and same area.
5 To add, subtract, or multiply the two arrays, select the appropriate button. A new
combined array is created.
6 If you want to change the name of the new combined array, type the new name.
7 Click to add it to the list.

8 Click Close.
Managing Network Data Arrays

After you have spread network data, you can rename, load, save and delete arrays in
the Data Array Operations dialog box. To open this:
From the Arrays menu, point to Network Data and click Data Array Operations.
Remember that if you are saving and loading arrays, you should only use them for
the respectively considered network data sets and network.
To rename network data arrays:
1 On the Manage Data Array tab, select an array.
2 In the Array Management pane, type in a new name for the array and then click
Rename.
You array is renamed.
To load network data arrays:
1 On the Manage Data Array tab, click Load.
2 In the dialog box that appears, browse to a saved array and click Open.
The array appears in the list.
The array can only be used for editing and visualisation purposes.

To save network data arrays:
1 On the Manage Data Array tab, select an array and click Save.
2 In the dialog box that appears, browse to a suitable location in which to save your
file and click Save.
Your array is saved. You can now load the array in the future, rather than re-create
the array.
To delete network data arrays:
On the Manage Data Array tab, select an array and click Delete.
The array is deleted from memory.
Using Measurement Data for Analysis and Tuning

Area and cell-specific measurement data (typically drive test data) can be used for
several purposes in ENTERPRISE:
Model Analysis
Model Tuning (Calibrating)
Generation of Measurement-based Pathloss Correction Files
Identification of Signal Reception Problems (Crossed Feeders)
Neighbour Planning
Loading Data (File Formats)

You can load any type of measurement data for use with a planning project, as long as
the data is in one of the supported file formats:
 Signia (*.hd, *.dat) or WGS84 Signia
 TMR (*.tmr)
 TEMS (*.fmt)
 Nemo Outdoor 4.x (*.dt?)
 Nemo Outdoor 5 (*.nmf)
 Rohde Schwarz (*.pro)
 DingLi (*.txt)
 Microsoft Office Access Database (*.mdb)
More file formats may be supported in future releases.
For full information on loading the measurement data, and all the above
processes, please see the Using Measurement Data chapter in the ASSET User
Reference Guide.

Using Measurement-Based Pathloss Files
The inclusion of drive test data measurements in ADVANTAGE has been designed
specifically to support optimisation activities in the field.
ADVANTAGE enables you to load your own drive test data (or other area and cell-
specific data) to generate measurement-based pathloss files, which you can then use
to:
Influence the normal pathloss predictions
- and/or -
Run an analysis/optimisation that is specifically focused on a drive test route
Example of Drive Test Route displayed on the Map View
Incorporating Drive Test Data into Pathloss Predictions
After they have been generated, measurement-based pathloss files contain the co-
ordinates of the measurement-based pathloss data, and the measurement-based
pathloss values. They are automatically saved into the directories already designated
for the project's normal pathloss prediction files.

If you use them to influence the normal pathloss predictions, the amount of influence
they have depends on the percentage weightings that you specify in the Array
Settings dialog box. You can also use interpolation to influence surrounding pixels
that do not contain measurement-based data. These weightings and interpolation
(and any changes to them) will be automatically invoked whenever you create a
coverage/interference array, or when you run the Simulator, or when you use the
Pathloss Prediction Generator.
For full information on loading the original measurement data, and generating
measurement-based pathloss files, please see the Using Measurement Data chapter in
the ASSET User Reference Guide.

APPENDIX A
Technical Reference
This appendix provides more in-depth technical information about how
ADVANTAGE works.
About the Optimisation-Based Spreading Algorithms

The following optimisation-based algorithms can be used to spread live network data,
such as Performance Engineering data or other cell-specific data:
1 Traffic spreading.
The cost function takes the following shape:
Where are clutter-specific optimisation parameters, is cell (k)-
specific PE data and is a model intended to be calibrated against PE data

by means of a least squares fit (as defined in the cost function).
In addition, the traffic spreading algorithm imposes a set of user-defined
constraints, which require relationships between some of the optimisation
parameters to be upheld, for example . These
relationships are uniquely defined using the Importance (priority) settings on the
General Clutter Parameters tab of the Optimiser Workflow dialog box.
2 Signal strength (clutter coverage) and interference (clutter interference) spreading.
The cost function takes the following shape:
Where are clutter-specific optimisation parameters, is cell (k)-
specific PE data and is a model intended to be calibrated against PE data

by means of a least squares fit (as defined in the cost function).

Technical Reference
About the Network Optimisation Domain
The cost function for automatic network optimisation is defined over a constrained n-
dimensional parameter space (the domain of optimisation) representing
possible network states . The initial network configuration is based on the
current Applied state of the database and denoted by ; it is also a member of . It
should be noted that the optimisation problem is well defined through the cost
function alone, because already accounts for any parameter constraints.
The parameters represent possible changes in network objects such as

antennas. The optimisation algorithm determines which network objects to change
and how to change them. All objects with plan/read–only status can generate costs,
but only objects with plan status can be changed.
About the Network Optimisation Cost Function

Automatic network optimisation uses a composite cost function which expresses the
overall cost of a network configuration taking into account various types of costs.
These costs can be categorised as follows:
1 Action costs.
These are understood as the budget/manpower costs of actions (in other words,
changes) performed on the network, such as costs of changing an antenna. Action
costs are calculated as aggregates of user-defined unitary cost values. They are not
normalised in any way, and therefore are proportional to the magnitude of
changes in a given network.
Antenna planning also considers antenna unit costs, while Grid Planning also
considers Property, site and cell unit costs. Strictly speaking, these differ from the
rest of action costs and are only budget-related. Furthermore, it is possible to
consider a number of actions and their respective costs as a single combined action
and cost on a location, Property, site or cell basis.
2 Performance costs.
These are understood as costs generated for a network based on various
performance metrics such as coverage probability. Contrary to action costs,
performance costs depend on the state of the network, not on the changes
themselves. However, the considered actions influence network performance
indirectly. Performance costs are calculated in percentages based on various
normalisation schemes that ensure their objectivity with respect to networks of
arbitrary sizes.
These costs are broken down into various sub-components so that every sub-
component can be modelled individually and then added to the other sub-
components to produce the overall cost. The synthesis bias is controlled through a set
of multi-stage weights.

Technical Reference
The cost function for automatic network optimisation is defined over a constrained
n-dimensional parameter space (as described in About the Network Optimisation
Domain on page 214):
Where:
is the total action cost due to changing the network configuration

from state to state
is the action cost generated by one of the action cost components

(for example budget or manpower)
is the total performance cost generated for the network at

state
is the performance cost generated by a particular cost

mechanism (i)
is the cost generated by component (k) of optimisation cost

mechanism (i)
is the performance risk coefficient due to changing the

network configuration from state to state
are cost conversion coefficients expressing the number of budgetary

cost units corresponding to one unit of non-budgetary costs, in other words
manpower and performance

Technical Reference
are normalised weights combining action costs and
performance costs at the global level
are normalised weights combining performance costs generated by cost

mechanisms
are normalised weights combining costs generated by the performance cost

components of the optimisation cost mechanism (i)
About Efficient Network Optimisation

You can use the following list of guidelines in order to maximise the ability of the
optimisation algorithm to find an optimised network configuration quickly:
Concentrate on the region and cells of interest. Use the Plan Wizard to specify the
region and cells of interest, and ignore areas or cells that should not be part of the
optimisation.
Restrict the optimisation calculations to vectors and/or drive test routes (if possible). Use
the option in the Plan Wizard (or the Edit Vectors right-click option) to restrict the
optimisation array and cost calculations to specific vectors and/or drive test
routes.
Do not use a higher array resolution than required. If you can get realistic network
performance results by specifying a low resolution for the optimisation, there is no
point in using a higher resolution.
Restrict the number of servers/cells considered for array generation. If you can get
realistic results (for example, with respect to interference) by specifying fewer
servers/cells for the optimisation, there is no need to use more.
Limit the optimisation cost calculations to a lower number of servers/cells (if appropriate).
Use the Servers/Cells per Pixel option on the Strategy page of the Optimiser
Workflow to do this.
Focus on problematic cells/areas. Use read-only filters (for network objects that
should be considered, but not modified) and/or the Problem Cells options to
ensure that the Optimiser concentrates on cells that are performing badly.
Do not under- or over-constrain the optimisation problem. Make sure that the specified
actions/constraints are reasonable, so that inappropriate configurations are not
evaluated, but also flexible enough to allow the Optimiser to produce the best
possible plan.
Fine-tune the algorithm. The nature of the algorithm is general enough to apply to a
wide range of optimisation problems. Although the algorithm can be fine-tuned
per specific scenario to further maximise its efficiency (the algorithmic fine-tuning
depends on the setup and user permissions), it is not an easy task and must be
approached with caution.

Technical Reference
About the Voronoi Diagrams
Given a set of n distinct points on the plane, a Voronoi diagram is the partition of the
plane into n polygons such that the borders of these polygons are equidistant between
neighbouring pairs of points.
This picture shows a typical two-dimensional Voronoi diagram, consisting of
polygons with equidistant borders between points in the displayed configuration:
A two-dimensional Voronoi diagram
This picture shows a three-dimensional convex hull, whose projection constitutes the
two-dimensional Voronoi diagram for the displayed set of points on the plane:
A three-dimensional convex hull

Technical Reference
About Optimisation Problem Definitions
An optimisation problem can be defined when the following are given:
A real-valued cost function, mapping parameter configurations in its domain into
costs in its range.
Parameter constraints, in other words, additional information on admissible states
within the domain of the cost function.
Constraints can be incorporated into the domain of the cost function, but for
practical reasons they are normally treated separately.
The notion of optimisation is then understood as follows:
Find any parameter configuration within the domain of the cost function that satisfies
the parameter constraints and minimises the cost function.
Here are a few remarks on possible optimisation scenarios, which highlight some key
aspects of an optimisation problem:
An optimisation problem may have many local minima, and this can produce
problems for optimisation algorithms that are not capable of escaping them.
Adaptive Simulated Annealing (ASA) is designed to overcome local minima
trapping.
These are different from the global minimum of the cost function, and should
not be confused.
An optimisation problem may not have a global minimum at all. If this is the case,
any sufficiently small cost function value will be appropriate for a parameter
configuration to be regarded as optimum.
Any change to the cost function or parameter constraints results in a different
optimisation problem, whose solutions may be completely different from those of
the original problem.
With most network optimisation problems involving a large number of variables (as
many as 500), the algorithm that can identify the best possible solution within a
reasonable amount of time must be very sophisticated. The current ADVANTAGE
optimisation algorithm is based on a proprietary adaptation of ASA, specifically
tuned to mobile communications problems. The algorithm combines the reliability of
ASA in identifying the best solution with a sophisticated 'greedy' algorithm designed
to rapidly target the largest immediate gains. A comprehensive research program has
identified major speed benefits (as much as 300% difference in some cases) over the
standard ASA implementation.

Technical Reference
About Adaptive Simulated Annealing
Adaptive Simulated Annealing (ASA) is a powerful optimisation algorithm especially
suitable for finding the global minimum of cost functions that have a large number of
local minima. It is based on an analogy with the thermodynamics of crystallisation.
More specifically, when liquids freeze or metals anneal, they undergo a process of
structural change that leads to the crystal state (the state of minimum energy).
A crucial factor in reaching this state by a physical body is the rate at which
temperature decays. If temperature is lowered at an appropriately low rate, particles
in the liquid are given more time to make the transition into the perfect crystal state. If
the body is cooled quickly, or quenched, it does not reach this state, ending up in a
quasi – crystal/amorphous state. In adaptive simulated annealing, energy is
generalised into the mathematical concept of a cost function defined over an n-
dimensional parameter space.
The optimisation variables are analogues of molecules in thermodynamics, and any
admissible configuration of these parameters with respect to the optimisation
problem is an analogue of a molecular configuration in thermodynamics. A physical
fact of paramount importance to the way the algorithm is designed is that molecules
wander around quasi-chaotically based on their current temperature; this allows them
to escape from configurations of locally minimised energy in favour of finding the
global minimum.
Simulated annealing uses a probability distribution to generate candidate states and
to establish acceptance criteria for these states. Adaptive simulated annealing uses an
exponential rate of temperature decay, so that even the global minimum can be found
very quickly compared to other forms of annealing, and indeed, to any other non-
local optimisation algorithm being used to this day.

Technical Reference
Technical Reference
problem area thresholds • 181
problem cell thresholds • 183
site constraints • 37
Constraints
about • 38
Action-Constraints dialog box • 127, 128
Index BTS equipment and mast • 44

GSM cell antenna • 48
GSM site grid • 46
GSM site installation • 46
GSM subcell antenna/TRX • 49
in Site Database • 37
max units/actions • 75
metric degradation • 82
A Property antenna • 42
Property grid • 40
Action costs UMTS cell load and power ctrl • 54
available • 79 UMTS cell params • 54
combining • 76 UMTS node antenna • 52
configuring • 74 UMTS node grid • 50
Action-Constraints UMTS node resource • 53
about • 37, 38 Context menu for plans • 119
antenna planning • 127, 136 Cost function, setting up • 86
dialog box • 124, 127 Costs
grid planning • 132, 144 action • 81
power planning • 127, 139 combining • 76
setting • 37 configuring • 74
templates • 134 function setup • 86
Actions metrics synthesis • 86
combining • 76 multipliers • 86
setting a maximum number of • 75
ADVANTAGE
benefits • 15 D
process flow • 30
Delta Plans • 108
workflow • 32
Drive test data
Algorithms
loading • 210
spreading • 213
Analysing and evaluating plans • 165
Analysis E
for a single plan • 168
network improvement • 170 Editing
network performance • 168 data arrays • 208
to compare plans • 170 Element status • 100
Antennas
sharing • 90, 138 G
Application environment • 13
Arrays Global Editor
combining • 208 setting constraints in site database • 55
deleting • 208
loading • 208
loading cached traffic • 89 L
renaming • 208 Loading
saving • 208 cached traffic arrays • 89
scaling • 207
Auto Plan Setup, using • 98, 99, 115
M
C Max units/actions, setting • 75
Measurement data
Cached traffic arrays using • 193
editing • 208 Menus
loading and deleting • 89 arrays • 27
Clutter configuration • 26
thresholds • 60 optimiser • 29
Clutter/Vector parameters • 60 tools • 28
Combining, action costs • 76 Metric Targets
Configuring array-based • 67

Index
service-based • 70 Spreading, network data • 194
Metrics Statistics
array-based • 67 graphs • 160
degradation • 84 reports • 160, 162
service-based targets • 70
T
N
Thresholds
Network Improvement Analysis • 170 problem area • 181
Network Performance Analysis • 168 problem cell • 183
New/Existing elements • 100 setting • 60
Traffic
loading cached arrays • 89
O
Operational environment, ADVANTAGE • 13 V
Optimisation
Action-Constraints templates • 134 Vectors
antenna • 127, 136 thresholds • 64
grid planning • 132, 144 Voronoi diagrams, about • 217
parameters • 32
power planning • 139
prerequisites • 156
reports • 158, 162
running the optimiser • 158
starting the optimiser • 157
strategy • 82
thresholds • 60
Optimiser Workflow
about • 32
using • 32
P
Partial plans • 173
Per Layer calculations • 60, 64, 91
Plan Manager, using • 107
Plans
concept • 108
creating • 110
rejecting • 75, 84
Traffic Options • 88
using the Plan Manager • 107
viewing and using • 109
Problem areas, identifying • 185
Problem cell weights, configuring • 190
Problem cells, identifying • 185
R
Rejecting plans
based on max units/actions • 75
based on metric degradation • 84
Reports
problem area • 186
problem cell • 189
Re-spreading, network data • 206
RF Thresholds • 60
Rollout planning • 173
S
Sampling, for clutter • 60
Shared antennas
how considered • 138
optimisation settings • 90

Index

ADVANTAGE User Reference Guide PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ADVANTAGE User Reference Guide PDF

Uploaded by

Copyright:

Available Formats

ADVANTAGE

User Reference Guide

Software Version 7.0

Chapter 2 Overview of ADVANTAGE 21

Chapter 3 Setting Action-Constraints in ADVANTAGE 37

ADVANTAGE 7.0 User Reference Guide Page 7

Chapter 4 Setting Up Thresholds, Targets and Parameters 59

Chapter 5 Using and Managing Plans 107

Page 8 ADVANTAGE 7.0 User Reference Guide

Chapter 6 Optimising a Network 155

Chapter 7 Analysing and Evaluating Plans 165

ADVANTAGE 7.0 User Reference Guide Page 9

Chapter 9 Using Measurement Data 193

Appendix Technical Reference 213

Page 10 ADVANTAGE 7.0 User Reference Guide

ADVANTAGE 7.0 User Reference Guide Page 11

There is a Technical Reference appendix at the back of the ADVANTAGE User

Page 12 ADVANTAGE 7.0 User Reference Guide

The optimisation life cycle using ADVANTAGE

ADVANTAGE 7.0 User Reference Guide Page 13

Page 14 ADVANTAGE 7.0 User Reference Guide

Obtaining User Assistance

ADVANTAGE 7.0 User Reference Guide Page 15

Adobe and Acrobat are trademarks of Adobe Systems, Incorporated.

If neither of these exists, please contact your administrator.

Checking Release Notes

Who is This User Reference Guide For?

Page 16 ADVANTAGE 7.0 User Reference Guide

ADVANTAGE 7.0 User Reference Guide Page 17

Can You Improve Our User Assistance?

Logging Support Requests Online

Page 18 ADVANTAGE 7.0 User Reference Guide

Europe United Kingdom Tel : +44 1932 442000

When contacting us with a support query, it would help us if you:

ADVANTAGE 7.0 User Reference Guide Page 19

Online Knowledgebase of Articles

Latest Copies of the User Reference Guides

Page 20 ADVANTAGE 7.0 User Reference Guide

About the Main Features of ADVANTAGE

ADVANTAGE 7.0 User Reference Guide Page 21

Page 22 ADVANTAGE 7.0 User Reference Guide

About Network Analysis

ADVANTAGE 7.0 User Reference Guide Page 23

ASSET Analysis (Arrays and Reports) Functionality

About Measurement Data

Page 24 ADVANTAGE 7.0 User Reference Guide

About the File Menu

Example of XML Export Dialog Box

ADVANTAGE 7.0 User Reference Guide Page 25

About the Configuration Menu

Page 26 ADVANTAGE 7.0 User Reference Guide

ADVANTAGE 7.0 User Reference Guide Page 27

This table briefly describes the ADVANTAGE-specific options on the Problem

About the Reports Menu

Page 28 ADVANTAGE 7.0 User Reference Guide

This Menu Item Enables You To

Do not remove anything from the ADVANTAGE Wastebasket that

ADVANTAGE 7.0 User Reference Guide Page 29

The ADVANTAGE process flow

Page 30 ADVANTAGE 7.0 User Reference Guide

ADVANTAGE 7.0 User Reference Guide Page 31

About the Optimiser Workflow

Click the button on the main ADVANTAGE toolbar