Professional Documents
Culture Documents
Asset ACP User Reference Guide
Asset ACP User Reference Guide
Asset ACP User Reference Guide
Your feedback is important to us: The TEOCO Documentation team takes many measures in
order to ensure that our work is of the highest quality.
If you found errors or feel that information is missing, please send your Documentation-related
feedback to Documentation@teoco.com
Thank you,
The TEOCO Documentation team
Change History
This table shows the change history of this guide:
Edition
Date
Reason
23 February 2015
First edition.
Table of Contents
Table of Contents
1
Introduction ..................................................................................................... 7
Index............................................................................................................... 99
Introduction
1 Introduction
ASSET ACP is ASSET's automatic cell planning and optimisation tool. Relying on the same
advanced algorithm used by ADVANTAGE, the tool searches for improvements based on userspecified criteria, and greatly speeds up the cell planning process.
ASSET ACP enables the automatic optimisation of the physical network configuration to maximise
capacity for the desired range of services and traffic demands. It can optimise design parameter
settings (antenna, power) to meet the network performance objectives.
Notes:
The maximum number of cells that can be experimentally modified within any one
optimisation is 150. That is, when creating a plan, 150 cells is the maximum that can be in
the 'plan' state. There is no limit on the number that can be in the 'read-only' state.
If, in addition to ASSET ACP, you also have a Financial Analysis licence, these two
modules share the same dialog box (ACP & Financial Analysis).
GSM
UMTS FDD
CDMA2000
EV-DO
Fixed WiMAX
Mobile WiMAX
LTE
In this guide, for simplicity, the term WiMAX may represent Fixed or Mobile WiMAX, and
the term CDMA/EV-DO may represent CDMA2000 or EV-DO.
The ACP Workflow 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.
Note: The tab names and options within the ACP Workflow dialog box will vary slightly according to
the technology that you are using.
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 to maximise the ability of the optimisation algorithm to
find an optimised network configuration quickly:
10
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.
For more information on importing and exporting XML data, see the ENTERPRISE User Reference
Guide.
11
The RF (radio frequency) array thresholds in the ACP Workflow enable you to specify:
These thresholds determine the required RF performance for your optimisations and analyses.
12
Parameter
Description
GSM
RSS
UMTS
RSCP
CDMA/EV-DO
RSCP
Fixed WiMAX
DL RSS
Mobile WiMAX
Preamble RSS
LTE
RSRP
GSM
CINR
UMTS
Pilot Ec/Io
CDMA/EV-DO
Pilot Ec/Io
Fixed WiMAX
DL CINR
Mobile WiMAX
Preamble CINR
LTE
RSRQ
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:
o
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, click Commit
13
2. On the General Clutter Parameters tab, specify the Sampling parameters, if required, for
the appropriate clutter types. The following table describes the parameter:
Parameter
Description
Sample
If required, you can change all values in a column by editing one row and then doubleclicking on the column heading.
Note:
14
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).
Parameter
Description
All
Priority
GSM
RSS
UMTS
RSCP
CDMA/EV-DO
RSCP
Fixed WiMAX
DL RSS
Mobile WiMAX
Preamble RSS
LTE
RSRP
GSM
CINR
UMTS
Pilot Ec/Io
CDMA/EV-DO
Pilot Ec/Io
Fixed WiMAX
DL CINR
Mobile WiMAX
Preamble CINR
LTE
RSRQ
15
Tip: You can employ functionality similar to that in spreadsheets, such as:
o
Copying and Pasting single or multiple values within the dialog box
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.
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:
o
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, click Commit
16
To do this:
1. Within the left-hand pane of the ACP Workflow, select Strategy.
2. On the Metrics Selection/Weights tab, either specify exact percentages in the edit boxes
for Coverage or Quality, or use the slider control.
3. Select the mapping resolution to be used in the optimisation.
4. Specify a Reference Terminal Type (required to generate the arrays).
5. 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.
6. In the Mechanism Technologies pane, select the technologies for which you want the
metrics/weightings to be used. You can also specify, as appropriate:
o
Maximum number of servers (GSM) - 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.
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.
However, if appropriate, you can carry out one of the following actions:
o
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
17
To do this:
1. Within the left-hand pane of the Workflow, select Traffic.
2. On the Terminal Types tab, you can select the required terminal type(s) from the list
displayed.
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.
However, if appropriate, you can carry out one of the following actions:
o
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
Specify the thresholds that relate to the Auto Plan Setup method
To access these settings, in the left-hand pane of the Workflow, select Settings:
There are two tabs available: Options tab and Auto Plan Setup tab.
18
Simulator Speed
Service-based optimisations and analyses, are, by default, run 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, you can select this option as follows:
On the Options tab, select the 'Run Simulator in memory-optimised mode' checkbox.
Threshold
Description
GSM
UMTS
CDMA/EV-DO
Fixed WiMAX
Mobile WiMAX
LTE
RSS
RSCP
RSCP
DL RSS
Preamble RSS
RSRP
The thresholds vary according to the technology that you are using.
All changes that you make on these tabs 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:
o
If you want to restore the options on each tab to the previous committed state (if such a
state exists), click Restore
If you want to share the changes on each tab with all other users, click Commit
19
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.
Managing Plans
The ACP Workflow enables you to perform all the tasks within ASSET ACP from a single dialog
box.
This section focuses on how to use the Plan Manager, which controls the plans and delta plans
output by the optimisation engine.
To start the ACP Workflow:
From the Tools menu, click ASSET ACP.
20
The Plan Manager in the ACP Workflow enables you to perform a number of plan-related
operations:
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 30.
Important: When you are using the ACP 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:
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. Depending on the situation, it is possible that the above
options and parameters are centrally specified and committed within the user's organisation.
Plan
Delta plan
A delta plan is the result of an optimisation run from an original plan. However, in essence, the two
types of plan, when 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.
21
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 23.
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.
icon.
This picture shows an example of how plans and delta plans are listed in the Plan
Manager:
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
22
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 27.
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.
23
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.
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.
24
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.
Note: Anything you edit here can be modified after creating the plan, using the ActionConstraints 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 41.
Use the Add button to specify each filter-template combination. (You can delete a row by
clicking .) Here is an example:
Tip: 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.
25
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.
26
Main focus
Recommended (tier 1)
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' ActionConstraints 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 Specifying the
Settings on page 18.
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.
Note: 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.
27
5. Click the Plan Setup button, then click the Auto Plan Setup option.
6. In the Auto Plan Wizard that appears, type a name for the plan.
Click Next.
7. Check that the region for the plan is correct. If necessary, you can modify the region by
entering precise co-ordinates.
Click Next.
8. Select one or more filters to determine which sites/nodes and cells are to be considered in
the plan.
Click Next.
9. Select one or more filters to define which cells should represent the 'main focus'. Click
Next.
10. 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 ActionConstraints 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 ActionConstraints 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 .
28
11. 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's Data Types list (where it can be visualised).
Click Next.
12. 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.
13. Click the Finish button.
29
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
Edit Vectors
Summary
Plans
Initial Report
Plans
Delta Report
Delta plans
Final Report
Delta plans
30
Option
Available for
Description/Comments
Analysis
Financial Analysis
Optimise
Duplicate
Plans
Delta plans
Delete
When you delete a plan, its 'child' delta plans are also
removed. However, a delta plan can be deleted
individually.
Bookmark
Toggle Use
31
Option
Available for
Description/Comments
Refresh
button.
3. In the Map Information Control dialog box, click the Data Types tab.
4. Select the required plan under the Plans heading:
32
6. If required, you can double-click the plan name in the Map Information and Control, and
select a different display colour.
Important: 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.
33
Description
Plan Summary
In the same way as for other items in the Data Types, these
options enable you to manage the display properties of each
item.
Tip: The Properties option can also be accessed by doubleclicking 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.
34
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, when created in the Plan Manager, is independent of subsequent
database changes)
35
36
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).
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.
37
Deleting a Plan
To delete an optimisation plan:
1. Within the left-hand pane of the Workflow, select Plan Manager.
2. Select the appropriate plan.
3. Click the Delete Plan button.
4. Click Yes to proceed.
The plan is now removed.
(You cannot delete a plan if it is 'in use' by more than one user.)
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
Important: 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'.
This flexibility enables you to:
Set specific action-constraints in the Site Database, and then edit these action-constraints
(if required) and set up further action-constraints (if required) in the Action-Constraints
dialog box.
- or -
This chapter focuses on the plan-specific Action-Constraints dialog box within the Optimiser
Workflow. For more detailed information about the action-constraints within the Site Database, see
About Action-Constraints on page 83.
38
The Action-Constraints dialog box 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 is when you are performing an Antenna optimisation where electrical or
mechanical tilts have been set on the Antenna Constraints tab in the Site Database before
the plan was created.
For additional information about the action-constraints, see About Action-Constraints on page 83.
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.
39
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.
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.
Important: It is recommended that you make full use of all these guiding factors to ensure
everything is set up correctly before optimising any plan.
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.
40
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 ActionConstraints values by assignment from Templates, you should note the following:
o
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
63.
Antenna
Power
ASSET ACP provides the flexibility to run optimisations based on any single mechanism, or both,
according to your optimisation strategy.
The Action-Constraints dialog box presents a tabular display containing a tab for each mechanism.
There is also a Summary tab showing how many sites, cells, and antennas are in the Plan.
The other tabs (Antenna/Power) display the parameters relevant to each planning mechanism,
which can be briefly described as:
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
Important: The action-constraints of any plans which already have delta plans are always in ReadOnly format.
You can edit the Action-Constraints for an optimisation plan.
Note: If you are only intending to analyse a plan, you may not need to edit the action-constraints.
41
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:
o
Manually assign to objects in the Action-Constraints dialog box, under the Templates
column,
- or -
Important: When you have finished making changes in the Action-Constraints dialog box, you must
always click 'Apply', in order to save the changes.
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)
42
Show/hide column
Sort ascending
Sort descending
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
In summary, as previously described, you can take different approaches to editing these values:
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:
43
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:
o
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.
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:
o
For more information, see Assigning Action-Constraints Templates to Objects on page 63.
44
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
Tip: 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. 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 actionconstraints for other plans. See About Action-Constraints Templates on page 53.
Columns in the ID section of the Antenna tab in the Action-Constraints dialog box
Description
Template
45
Columns in the Current Values section of the Antenna tab in the Action-Constraints dialog box
Description
Columns in the Antenna Constraints section of the Antenna tab in the Action-Constraints dialog box
Description
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.
Note: 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.
Co-Location Enabled
46
Column Heading
Description
Forbidden Azimuth
Range Min/Max
This enables you to define, for a specific antenna, an orientation range that the
automatic optimisation cannot consider for azimuth changes. For this, the
minimum represents a clockwise bearing (the start azimuth of the forbidden
range) and the maximum represents an anti-clockwise bearing (the end azimuth
of the forbidden range).
For descriptive detail on this, see About the Forbidden Azimuth Range on page
47.
Examples of forbidden azimuth ranges with corresponding parameters in the Action-Constraints dialog box
47
This next picture illustrates a more specific example of how the forbidden azimuth might be used
within an antenna optimisation.
The example represents an antenna currently set to 60 with an optimisation azimuth range
between 0 and 120, but with a forbidden range between 90 and 105:
Specific example of how the forbidden azimuth might be used within an antenna optimisation
This picture shows how the corresponding parameters would be set in the Action-Constraints dialog
box:
48
Columns in the Electrical Tilt / Patterns section of the Antenna tab in the Action-Constraints dialog box
Description
Use Min/Max/Step
Serves as a 'switch'. Select this if you want Min/Max/Step values to be used in the
optimisation, but do not select it if you want Specified Device/Patterns to be used
instead.
Min/Max/Step
You can enable the electrical downtilt of the antenna to be changed, by specifying
Minimum and Maximum downtilts, and the allowed Step of change (all in degrees).
Fixed
Select this if you want nothing to be changed for Electrical Tilt/Patterns. If this is
selected, the 'Use Min/Max/Step' checkbox will have no effect.
Specified
Device/Patterns
Device Fixed
Select this if you want the pattern to be allowed to change, but not the device.
Notes:
Total downtilt must also be set, in order to allow the required changes to the electrical
downtilt during optimisation. See Antenna Tab - Total Downtilt Heading on page 50.
If any of the three antenna constraints for electrical tilt (Min; Max; Step) are enabled for an
antenna in the Site Database, the Use Min/Max/Step checkbox for that antenna is
automatically selected in the Action-Constraints dialog box, but this is editable.
49
Columns in the Mechanical Downtilt section of the Antenna tab in the Action-Constraints dialog box
Description
Min/Max/Step
You can enable the mechanical downtilt of the antenna to be changed, by specifying
Minimum and Maximum downtilts, and the allowed Step of change (all in degrees).
Fixed
Note: Total downtilt must also be set, in order to allow the required changes to the electrical
downtilt during optimisation. See Antenna Tab - Total Downtilt Heading on page 50.
Columns in the Total Downtilt section of the Antenna tab in the Action-Constraints dialog box
50
Column
Heading
Description
Min/Max
You can specify limits for the total downtilt. Any changes made to the electrical and/or
mechanical downtilt during optimisation would not be allowed to exceed these limits.
Fixed
Select this if you want nothing to be changed for the total downtilt.
Columns in the Azimuth section of the Antenna tab in the Action-Constraints dialog box
Description
Min/Max/Step
You can enable the azimuth of the antenna to be changed, by specifying Minimum
and Maximum azimuths, and the allowed Step of change (all in degrees).
Fixed
If you want to set up a forbidden azimuth range, see About the Forbidden Azimuth Range on page
47.
Columns in the Height section of the Antenna tab in the Action-Constraints dialog box
Description
Use Min/Max/Step
Serves as a 'switch'. Select this if you want Min/Max/Step values to be used in the
optimisation, but do not select it if you want Values to be used instead.
Min/Max/Step
You can enable the height of the antenna to be changed, by specifying Minimum
and Maximum heights, and the allowed Step of change (all in degrees).
Values
If applicable, this initially shows a list of values specified in the Site Database (see
Configuring Property Antenna Constraints on page 87). Alternatively, you can
manually edit the list of values in the column.
Note: If you want to enable these values to be used during optimisation, ensure
that the Min/Max/Step checkbox is not selected.
Fixed
Select this if you want nothing to be changed for the antenna height. If this is
selected, the 'Use Min/Max/Step' checkbox will have no effect.
51
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 columns contain all the power-related parameters that correspond to the technology of the
network element.
For some of these parameters, there is an option to set a 'uniform group' constraint. This enables
you to specify groups of cells that you want to be adjusted uniformly by the Optimiser.
To do this:
In the appropriate '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.
Note: 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.
Tip: 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. 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 actionconstraints for other plans. See About Action-Constraints Templates on page 53.
52
Antenna
Power
Tip: 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.
Manually assigned to objects in the Action-Constraints dialog box, under the Templates
column
- or -
Note: 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'.
53
For details on the different planning actions and constraints that you can configure, see
one of the following sections:
o
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 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.
54
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 63.
This table describes the antenna planning action-constraints that you can configure:
Select
To
Device/Pattern
Electrical Downtilt
Max Change defines the maximum permitted change from the respective
original value in the Site Database (in degrees).
55
Select
To
Mechanical Downtilt
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.
Max Change defines the maximum permitted change from the respective
original value in the Site Database.
Total Downtilt must also be selected, unless Electrical Downtilt is considered and
the Total Downtilt is to remain unchanged.
Total Downtilt
Azimuth
Height
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.
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.
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.
Max Change defines the maximum permitted change from the respective
original value in the Site Database (in m).
Important: When configuring antenna planning actions and constraints, you should remember the
following:
56
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.
Note: 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 87. There are also options related to antenna
sharing within the Settings. For more information, see Specifying the Settings on page 18.
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.
Note: 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.
57
BTS Type
If you have selected PA Output Power, the constraints described in this table become active:
58
This Constraint
Enables You To
Set the maximum permitted change from the current value in the cell (in dB).
This Constraint
Enables You To
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.
Important: When defining GSM power planning actions and constraints, you should remember the
following:
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 respective
constraints will not be changed during the optimisation.
To
Max TX Power
Pilot Power
HSDPA Power
Node Types
If you have selected any of the above power planning actions, the constraints described in this
table become active:
This Constraint
Enables You To
Set the maximum permitted change from the current value in the cell (in
dB).
Fixed % of Max TX Power Specify that the appropriate 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 starting plan.
Note: 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.
Uniform Power
Specify that all the cells associated with the template are adjusted
together. If the initial power values are not the same, then this constraint
will not be applicable and will be ignored.
59
This Constraint
Enables You To
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.
Important: When configuring UMTS power planning actions and constraints, you should remember
the following:
The original parameter settings (for example, Node equipment types) are always included
in the optimisation.
Any power parameters with values outside the {min, max} range set in the respective
constraints will not be changed during the optimisation.
If the Uniform Power constraint has been enabled, the respective initial power values for
the associated cells must be the same in order for changes to be considered by the
Optimiser.
When you are using the Fixed % of Max TX Power checkbox (for Pilot Power, HSDPA
Power or Max Power Per User):
o
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)
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.
To
If you have selected any of the above power planning actions, the constraints described in this
table become active:
60
This Constraint
Enables You To
This Constraint
Enables You To
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.
Important: When configuring CDMA/EV-DO power planning actions and constraints, you should
remember the following:
Any power parameters with values outside the {min, max} range set in the respective
constraints will not be changed during the optimisation.
To
TX Power
(Fixed and Mobile)
If you have selected the above power planning action, the constraints described in this table
become active:
This Constraint
Enables You To
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.
Important: When defining WiMAX power planning actions and constraints, you should remember
the following:
Any power parameters with values outside the {min, max} range set in the respective
constraints will not be changed during the optimisation.
61
If you have selected any of the above options, the constraints described in this table become
active:
This Constraint
Enables You To
Min Value
Max Value
Set the maximum permitted change from the current value in the cell.
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.
Important: When configuring LTE power planning actions and constraints, you should remember
the following:
62
Any power parameters with values outside the {min, max} range set in the respective
constraints will not be changed during the optimisation.
8. Click OK. The assignments you have made now appear in the Action-Constraints dialog
box.
9. 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.
63
Important: 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 ActionConstraints 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 40.
Manually reassigning the template to objects in the Action-Constraints dialog box, under
the Templates column
Optimising a Network
The ACP Workflow enables you to perform all the tasks within ASSET ACP from a single dialog
box:
The principal feature of ASSET ACP is the automatic Optimiser, which can consider an extensive
number 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 a
choice of:
This section focuses on how to run an optimisation, and how to interpret the feedback.
To start the ACP Workflow:
From the Tools menu, click ASSET ACP.
Set up a project with the necessary planning data, including traffic (if applicable).
Created a plan (defining the area, cell filters, and, optionally, vectors), using the Plan
Manager. For more information, see Using the Plan Manager on page 21.
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. The Traffic tab
governs the selection of terminal types. The Settings tab includes thresholds for the Auto
Plan Setup method.
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 65.
To start an optimisation within the Plan Manager:
1. Open the Workflow by clicking the shortcut button
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.
Note: 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.
66
Monitoring an Optimisation
When you have started an optimisation, the Optimiser runs. This picture shows an example of a
running scenario:
Description
Starting configuration
Modification strategy
The cost for the best configuration that the Optimiser has found so far.
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; Accepted: The number of iterations that have been accepted by the
A/G
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
The time the Optimiser was started, the time it was stopped, and the
elapsed time.
67
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
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.
68
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.
69
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)
Tip: To get details of different cost values besides the current ones, ensure that the Log states
option is selected.
This picture shows an example:
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.
70
GSM
UMTS
CDMA2000
EV-DO
Fixed WiMAX
Mobile WiMAX
LTE
71
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.
Tip: 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:
Tip: 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 96.
72
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
Analyse and evaluate a current plan configuration or an optimised delta plan configuration
Access the rollout planning functionality, in order to assess and sequence the potential
network changes for a delta plan
You can evaluate a single plan, or compare two plans, in terms of their performance (with respect
to measurements and optimisation metrics).
73
As part of the network evaluation, statistics similar to those available in ASSET can also be
generated. The statistics include the coverage and interference metrics (presented per clutter type
and/or per vector). In addition, feedback based on the specified optimisation metrics can be
provided.
The performance achieved for each configuration is presented (in terms of absolute and/or relative
values) on a traffic and area basis.
The analysis report generated can include:
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 rollout planning functionality, in order to
assess and sequence the potential network changes for a delta plan. For more information, see
About Rollout Planning and Partial Plans on page 79.
74
Actions
Statistics
Costs
Information
Description
Type
Actions
Statistics
Coverage, quality.
Optimisation Costs
Set up a project with the necessary planning data, including traffic (if applicable). For more
information, see the ENTERPRISE and ASSET User Reference Guides.
Defined the appropriate parameters or options on the Strategy, Traffic and Settings tabs.
Created (or have access to) a plan. For more information, see Using the Plan Manager on
page 21.
(If you want to select a different plan, you can do this by clicking the browse button
.)
75
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 96.
76
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
the other required plan.
.)
77
2. On the Map View toolbar, click the Map Information Control button
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:
o
78
This picture shows an example of plan comparison analysis information displayed on the
Map View window. The values show the improvement between Plan 1 and Plan 2 for the
Nth Pilot Server.
79
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.
Partial Plans
From your original plan, you can create a "Partial Plan", which is a plan that will consider making
changes only for the elements that you choose.
The benefit is that, having re-sequenced the potential changes, you can decide which ones are
really beneficial (based on the chosen metric) to the improvement of your network.
80
You can:
o
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).
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:
(For clarity, the above example report has been simplified; rows have been removed.)
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.
Note: 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 reanalyse, you can now click the Reset button.
81
82
About Action-Constraints
The purpose of action-constraints in ASSET ACP 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, to accurately represent the real-world environment.
An example of an 'action' may be that you want to allow the antenna azimuths of 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 because of a nearby school.
Important: The ASSET ACP tool focuses on automatic optimisation of plans, and the ActionConstraints dialog box plays a crucial part in this process. This section focuses on the ActionConstraints within the Site Database. For more detailed information about the plan-specific ActionConstraints dialog box within the Optimiser Workflow, it is important that you read the section
Setting Action-Constraints for Plans on page 38.
Action-constraints that you can set up and edit within the ACP Workflow
Action-constraints that you can set for specific network elements directly within the Site
Database
Antenna
Power
ASSET ACP provides the flexibility to run optimisations based on any single mechanism, or both of
them.
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 both of the planning mechanisms, according to your optimisation strategy.
Note: The action-constraints of any plans which already have delta plans are always in Read-Only
format.
83
For more detailed information about the action-constraints within the ACP Workflow, see About the
Action-Constraints Dialog Box on page 39 and Using the Action-Constraints Dialog Box on page
41.
Network Element
Constraints
Equipment
Property
Antenna
GSM Site
Installation
GSM Cell
Antenna
GSM Subcell
Power
UMTS Node
Antenna, Resource
UMTS Cell
CDMA2000/EV-DO Site
Antenna
WiMAX Node
Antenna
WiMAX Cell
Power
LTE Node
Antenna
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 94.
84
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 a height value and click Add
To change a value, select it and enter a new value in the box and click Update
85
3. Ensure that you select the appropriate antenna from the list (if there is more than one).
4. Use the scroll bar to scroll to the right, to reveal the antenna constraints (Height Fixed,
Azimuth Fixed, and so on). This picture shows an example:
5. You can activate the following constraints per antenna, if you want to prevent such changes
during optimisation:
o
Height Fixed
Azimuth Fixed
Device Fixed
6. You can, if required, define a Forbidden Azimuth Range for the cell's antenna. This enables
you to define an orientation range which the automatic optimisation cannot consider for
azimuth changes.
To set the range, specify a clockwise bearing (the start azimuth for the forbidden range)
and an anti-clockwise bearing (the end azimuth for the forbidden range).
(For a fuller description of these settings, see About the Forbidden Azimuth Range on page
47.)
86
7. You can activate and set the following constraints per antenna, if you want to enable such
changes during optimisation:
o
Note: Valid Total Downtilt values must also be set on the Antenna Constraints tab for the
cell (GSM), or the node (all other technologies).
8. Click Apply to save the changes, and Commit if appropriate.
87
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 minimummaximum range:
o
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):
o
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 84.
To define a series of allowable antenna height values within the minimum-maximum range
based on a particular step size:
o
Select the Step option, and then type a value in metres for the step.
A series of allowable antenna height values appears, 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.
Note: 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 coordinates, height and azimuth, and on the same Property).
Important: If Antenna Co-location is not enabled for a Property, no antenna sharing or colocation 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 57.
7. Click Apply to save the changes, and Commit if appropriate.
88
These numbers correspond to the antennas listed on the Antennas tab. The constraints are
always antenna-specific.
89
4. In the Misc Constraints pane, you can activate the following constraint per antenna, if you
want to prevent such changes during optimisation:
o
You can also activate and set the following constraints per antenna, if you want to enable
such changes during optimisation:
o
90
(These numbers correspond to the antennas listed on the Antennas tab. The constraints
are always antenna-specific.)
4. In the Misc Constraints pane, you can activate the following constraint per antenna, if you
want to prevent such changes during optimisation:
o
You can also activate and set the following constraints per antenna, if you want to enable
such changes during optimisation:
o
91
HSDPA power
92
93
Important: 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 deselect 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:
94
Properties
Cell Constraints
Property Constraints
Antennas:
Allow Co-location
Min Height
Max Height
Installation (GSM)
Fixed PA Output
Fixed TX Power
Fixed TX Power
95
Analysis report
Optimiser report
Note: 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 ASSET ACP report type.
Important: 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.
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:
96
97
98
Index
Index
O
A
Action-Constraints
about 83
antenna planning 41, 55
dialog box 39, 41
power planning 41, 58
setting 83
templates 53
ADVANTAGE
workflow 9
Analysing and evaluating plans 73
Analysis
for a single plan 75
network improvement 77
network performance 75
to compare plans 77
Antennas
sharing 57
Auto Plan Setup, using 27
Azimuths, forbidden ranges 47, 86
C
Clutter/Vector parameters 12
Constraints
about 83
Action-Constraints dialog box 42
BTS equipment and mast 84
GSM cell antenna 89
GSM site installation 89
GSM subcell antenna/TRX 90
in Site Database 83
metric degradation 16
Property antenna 87
UMTS cell load and power ctrl 93
UMTS cell params 92
UMTS node antenna 91
UMTS node resource 92
Context menu for plans 30
D
Delta Plans 21
Optimisation
Action-Constraints templates 53
antenna 41, 55
parameters 9
power planning 58
prerequisites 65
reports 67, 71
running the optimiser 67
starting the optimiser 66
strategy 16
thresholds 12
Optimiser Workflow
using 9
P
Partial plans 79
Plan Manager, using 21
Plans
concept 21
creating 23
Traffic Options 18
using the Plan Manager 21
viewing and using 22
R
RF Thresholds 12
Rollout planning 79
S
Sampling, for clutter 12
Shared antennas
about 57
how considered 57
Statistics
graphs 69
reports 69, 71
T
Thresholds
setting 12
F
Forbidden Azimuth ranges 47, 86
G
Global Editor
setting constraints in site database 94
N
Network Improvement Analysis 77
Network Performance Analysis 75
99
100