Asset ACP User Reference Guide
Asset ACP User Reference Guide
Asset ACP User Reference Guide
Copyright 2010 AIRCOM International All rights reserved ASSET ACP, 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 15 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: Support Hotline: Fax: Web: +44 (0) 1932 442000 +44 (0) 1932 442345 +44 (0) 1932 442005 www.aircominternational.com
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 Note Tip Warning or Important Full Description Signifies text that should be noted or carefully considered. Signifies text that may help you do something in an easier or quicker way. Signifies text that is intended as a warning or something important.
Contents
Chapter 1 Introduction
9
10
11 11 12 12 14
15
16 16 18
18 23 25 26 27
Using the ACP Workflow Recommendations and Guidelines Setting Up Thresholds and Parameters
Setting RF Array Thresholds Setting the Strategy Setting Traffic Options Specifying the Settings Globally Committing All Your Changes
Managing Plans
Using the Plan Manager About the Concept of Plans in ASSET ACP Viewing and Using Plans in the Plan Manager Creating Plans for Optimisation or Analysis Using the Context Menu Viewing Plans in the Map View Window About the Action-Constraints Dialog Box Using the Action-Constraints Dialog Box About Action-Constraints Templates Assigning Action-Constraints Templates to Objects Deleting a Plan Applying a Plan to the Database Applying a Plan Temporarily to the Database Key Differences between Temp Apply and Apply to Database
28
28 29 30 31 39 41 44 47 53 64 66 67 68 69
Optimising a Network
Prerequisites for an Optimisation Running an Optimisation Monitoring an Optimisation
70
70 71 72
79
80 80 81 83 84 86
90
90 Page 7
91
104
Index
107
Page 8
CHAPTER 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 user-specified 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. The technologies explicitly supported are: GSM UMTS FDD CDMA2000 EV-DO Fixed WiMAX Mobile WiMAX 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.
Page 9
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. 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 2 Make sure you have an appropriate PDF reader installed on your PC. 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 12.
Page 10
Page 11
Contains Information On 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.
Using DATASAFE, our network configuration tool to implement both small and large scale changes to networks 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.
Using the Financial Analysis module to evaluate and plan for the revenue potential of your network. (Optional add-on to ASSET and ASSET ACP.)
ILSA User Reference Guide AIRCOM OPTIMA User Reference RANOPT User Reference WEBWIZARD User Reference
Using ILSA, ASSET's automatic 2g frequency planning tool. Using AIRCOM OPTIMA to view performance data and statistics both with ENTERPRISE and standalone. Using RANOPT to efficiently find faults in your network, optimise and validate its performance prior to commercial launch. 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.
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
Page 12
Logging Support Requests Online To log a support request online: 1 2 3 4 5 6 Go to the AIRCOM website, at www.aircominternational.com. Click the link for Product Support Login. Log in, using your customer web account username and password. In the Technical Support pane, click Online Helpdesk. Click Log New UTS Call. Type the details of your request, and then click Submit.
Contacting us via Telephone or Email If you wish to contact us directly, here are the contact details of our regional offices:
Location Europe Regional Office United Kingdom Contact Details Tel : +44 1932 442000 Fax :+44 1932 442005 support@aircominternational.com Belgium France Germany Italy Sweden Middle East, Africa and Central Asia United Arab Emirates support@aircominternational.be support@aircominternational.fr support@aircominternational.de support@aircominternational.it support@aircominternational.se 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 USA support@aircominternational.com.mx Tel : +1 214 576 2700 Fax : +1 214 576 2794 support@aircominternational.us Brazil Asia and Oceania Singapore support@aircominternational.com.br 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
Page 13
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
Page 14
CHAPTER 2
Page 15
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. The tab names and options within the ACP Workflow dialog box will vary slightly according to the technology that you are using. To start the ACP Workflow: From the Tools menu, click ASSET ACP.
Page 16
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.
Page 17
The RF (radio frequency) array thresholds in the ACP 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.
Page 18
To edit the Clutter Thresholds: 1 Within the left-hand pane of the ACP Workflow, double-click RF Array Thresholds, and then double-click Clutter.
2 3
Click the required technology, as appropriate, depending on your licences. Specify the threshold values as required in the columns for the appropriate clutter types. The following table describes them:
Technology GSM UMTS CDMA/EV-DO Fixed WiMAX Mobile WiMAX LTE GSM UMTS CDMA/EV-DO Fixed WiMAX Mobile WiMAX LTE Parameter RSS RSCP RSCP DL RSS Preamble RSS RSRP CINR Pilot Ec/Io Pilot Ec/Io DL CINR Preamble CINR RSRQ The minimum signal quality ratio (dB) that is required in the corresponding clutter type. Description The minimum signal level (dBm) that is required to provide coverage in the corresponding clutter type.
Page 19
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 options, you can do this on the General Clutter Parameters tab. To do this: 1 Within the left-hand pane of the ACP Workflow, select RF Array Thresholds, then double-click Clutter, and then click General.
On the General Clutter Parameters tab, specify the Sampling parameters, if required, for the appropriate clutter types. The following table describes the parameter:
Parameter Sample Description 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 optimisation. The process 'removes' neighbouring pixels of the same clutter type, and therefore makes the optimisation and analysis faster. Sampling is only recommended if your mapping resolution is high (under 50m) and you want to optimise a large area.
If required, you can change all values in a column by editing one row and then double-clicking on the column heading.
Page 20
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:
To edit the Vector Thresholds: 1 Within the left-hand pane of the ACP Workflow, double-click RF Array Thresholds, and then double-click Vector.
2 3 4
Click the required technology, as appropriate, depending on your licences. 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. Select the Overrride checkbox.
Page 21
Specify the values as required in the columns for the appropriate vectors. The following tables describe the thresholds:
Technology All Parameter Priority Description 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. The minimum signal level (dBm) that is required to provide coverage in the corresponding vector.
GSM UMTS CDMA/EV-DO Fixed WiMAX Mobile WiMAX LTE GSM UMTS CDMA/EV-DO Fixed WiMAX Mobile WiMAX LTE
RSS RSCP RSCP DL RSS Preamble RSS RSRP CINR Pilot Ec/Io Pilot Ec/Io DL CINR Preamble CINR RSRQ
The minimum signal quality ratio (dB) that is required in the corresponding vector.
You can copy and paste values from one edit box into one or more other boxes, by copying the value(s) you want to duplicate, selecting the target box(es), and then pasting. 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: 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
Page 22
The Strategy option in the ACP Workflow enables you to: Select the metrics to be used in the optimisations, that is Coverage or Quality, or a combination of both Select the mapping resolution to be used in the optimisation Specify a Reference Terminal Type Set the pixel weighting for Area vs. Traffic Select the technology or technologies (depending on licences) Set the maximum number of servers or number of covering cells This picture shows an example:
Page 23
To do this: 1 Within the left-hand pane of the ACP Workflow, select Strategy.
2 3 4 5
On the Metrics Selection/Weights tab, either specify exact percentages in the edit boxes for Coverage or Quality, or use the slider control. Select the mapping resolution to be used in the optimisation. Specify a Reference Terminal Type (required to generate the arrays). 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. 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) - 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: 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 of the project, click Commit
Page 24
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: 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 of the project, click Commit
Page 25
On the Auto Plan Setup tab, set the required options for the appropriate technology, as described in the following section. 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: 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 of the project, click Commit
This table describes the available settings on the Auto Plan Setup tab:
Technology GSM UMTS CDMA/EV-DO Fixed WiMAX Mobile WiMAX LTE Threshold RSS RSCP RSCP DL RSS Preamble RSS RSRP Description Only pixels containing values equal to or higher than the threshold will be included. All pixels below the threshold will be excluded.
The thresholds vary according to the technology that you are using.
Page 26
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.
Page 27
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.
The Plan Manager in the ACP Workflow enables you to perform a number of planrelated 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 39. 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: RF Array Thresholds (Clutter/Vectors) 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.
Page 28
This picture shows an example of how plans and delta plans are listed in the Plan Manager:
Page 29
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 'multiuser' 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 39.
Page 30
Page 31
2 3
4 5
Click the Plan Setup button, then click the Plan Setup option. 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.
Check that the region for the plan is correct. If necessary, you can modify the region by entering precise co-ordinates.
Click Next.
Page 32
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 ActionConstraints 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 47. 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.
Page 33
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 rightclicking 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 ASSET ACP 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 35.
Page 34
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).
In the horizontal toolbar of the Map View, click the 'Plan Setup' button (alternatively, click on the View and press Ctrl-U). 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 ActionConstraints Dialog Box on page 44. 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.
Page 35
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 26. 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.
Page 36 ASSET ACP User Reference Guide 7.0
Using ASSET ACP
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. Ensure that you have a Map View window open that displays the region and cells that you want to include. 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 5 6 The Auto Plan Setup Wizard appears. Name the plan, and insert any comments. Click Next. Select one or more filters to define which cells should represent the 'main focus'. Click Next. 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:
2 3
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 . 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 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 .
Page 37
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.
Page 38 ASSET ACP User Reference Guide 7.0
Using ASSET ACP
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.
Page 39
This not only provides quick access to the same options as most of the main buttons, but also provides extra options:
Option Action-Constraints Edit Vectors Summary Available for Plans Plans and delta plans Plans Description/Comments See Using the Action-Constraints Dialog Box on page 47. Enables you to modify the vector selection for a plan. 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). The current values, and the constraints, of the network contained in the delta plan, and the specific network parameter changes 'proposed' by the Optimiser. 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). 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 79. 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. 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 71. 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 30. 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 30. Rename Plans and delta plans A quick way to rename a plan or delta plan. These names must always be unique within a project.
Delta Report
Delta plans
Final Report
Delta plans
Optimise
Page 40
Available for Plans and delta plans Plans and delta plans
Description/Comments When you delete a plan, its 'child' delta plans are also removed. However, a delta plan can be deleted individually. 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. 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 30.
Toggle Use
This enables you to quickly update (overwrite) the contents of the 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
Page 41
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.
Page 42
If you have modified one of the visual options (Apply Sampling, Properties), you need to click the Redraw button to refresh the Map View.
Page 43
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.
Page 44
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 to ensure everything is set up correctly before optimising any plan.
Page 45
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), 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).
Page 46
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 64.
Page 47
You can edit the Action-Constraints for an optimisation Plan. To do this: 1 2 Open the Optimiser Workflow, by clicking ASSET ACP from the Tools menu. In the left-hand pane, select Plan Manager.
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.
Page 48
For the Section headings, when you click Show/hide columns (within the section) For the Column headings, when you click Show/hide column Sort ascending Sort descending Show all rows
, you can perform this viewing option: , you can perform these viewing options:
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
Page 49
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 ActionConstraints 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.
Page 50
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 Pressing the Ctrl-Shift-DownArrow/UpArrow keys (as a quick method of 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:
For more information, see Assigning Action-Constraints Templates to Objects on page 64.
Page 51
Page 52
Page 53
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'.
3 4
Select the appropriate plan, and click the Constraints button. In the Action-Constraints dialog box, click the Manage Templates button.
5 1
You can now either add, remove, edit, or rename a template. 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.
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 55 Configuring Action-Constraints Templates for Power Planning on page 58
Page 54
In the right hand pane, edit the values for this action or constraint. For example:
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 6
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. 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 64.
Page 55
This table describes the antenna planning action-constraints that you can configure:
Select Device/Pattern To 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. 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. 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: Change Step indicates the allowed step of change (in degrees). 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). Max Change defines the maximum permitted change from the respective original value in the Site Database (in m).
Page 56
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 coordinates, 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 94. There are also options related to antenna sharing within the Settings. For more information, see Specifying the Settings on page 26.
Page 57
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.
Page 58
About GSM Power Planning Action-Constraints This table describes the GSM power planning actions you can activate for cells:
Select This Action PA Output Power BTS Type
j
To Enable the power amplifier (PA) output to be changed. Enable the BTS equipment type to be changed on a site.
If you have selected PA Output Power, the constraints described in this table become active:
This Constraint Min Value (dBm) Max Value (dBm) Change Step (dB) Max Change (dB) Changes Allowed Enables You To Set the minimum power that is permitted (in dBm). Set the maximum power that is permitted (in dBm). Set the permitted step of power change (in dB). Set the maximum permitted change from the current value in the cell (in dB). 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 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. 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.
Page 59
About UMTS Power Planning Action-Constraints This table describes the UMTS power planning actions you can activate for cells:
Select This Action Max TX Power Pilot Power HSDPA Power Max Power Per User Node Types To Enable the maximum transmit power to be changed. Enable the pilot power (CPICH) to be changed. Enable the HSDPA power to be changed. Enable the maximum power per user to be changed. Enable the Node equipment type to be changed on a node.
If you have selected any of the above power planning actions, the constraints described in this table become active:
This Constraint Min Value (dBm) Max Value (dBm) Change Step (dB) Max Change (dB) Fixed % of Max TX Power Enables You To Set the minimum power that is permitted (in dBm). Set the maximum power that is permitted (in dBm). Set the permitted step of power change (in dB). Set the maximum permitted change from the current value in the cell (in dB). 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. When this is selected, the Change Step and the Changes Allowed become readonly, 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. 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.
Changes Allowed
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.
Page 60
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)
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:
Select This Action CDMA2000 Pilot Power EV-DO Rated PA Power To Enable the pilot power to be changed. 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:
This Constraint Min Value (dBm) Max Value (dBm) Change Step (dB) Max Change (dB) Changes Allowed Enables You To Set the minimum power that is permitted (in dBm). Set the maximum power that is permitted (in dBm). Set the permitted step of power change (in dB). Set the maximum permitted change from the current value in the cell (in dB). 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.
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. Any power parameters with values outside the {min, max} range set in the respective constraints will not be changed during the optimisation.
Page 61
About WiMAX Power Planning Action-Constraints This table describes the WiMAX power planning actions you can activate for cells:
Select This Action TX Power (Fixed and Mobile) To Enable the transmit power to be changed.
If you have selected the above power planning action, the constraints described in this table become active:
This Constraint Min Value (dBm) Max Value (dBm) Change Step (dB) Max Change (dB) Changes Allowed Enables You To Set the minimum power that is permitted (in dBm). Set the maximum power that is permitted (in dBm). Set the permitted step of power change (in dB). Set the maximum permitted change from the current value in the cell (in dB). 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.
When defining WiMAX power planning actions and constraints, you should remember the following: The original parameter settings 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.
Page 62
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:
This Constraint Min Value Max Value Change Step (dB) Max Change (dB) Changes Allowed Enables You To Set the minimum power that is permitted. Set the maximum power that is permitted. Set the permitted step of power change. Set the maximum permitted change from the current value in the cell. 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.
When configuring LTE power planning actions and constraints, you should remember the following: The original parameter settings 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.
Page 63
2 3
Select the appropriate Plan, and click the Constraints button. In the Action-Constraints dialog box, click the Assign Templates button.
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 6
In the row that appears, select a filter. 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.
Continue with the Add button until you have specified all the required filtertemplate combinations. (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 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 .
Page 64
8 9
Click OK. The assignments you have made now appear in the Action-Constraints dialog box. 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 ActionConstraints 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 46.
Page 65
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.
Deleting a Plan
To delete an optimisation plan: 1 2 3 4 Within the left-hand pane of the Workflow, select Plan Manager. Select the appropriate plan. Click the Delete Plan button. Click Yes to proceed.
The plan is now removed. You cannot delete a plan if it is 'in use' by more than one user.
Page 66
2 3 4
Select the appropriate plan. Click the Apply Plan button. Click the Apply to Database option.
Page 67
2 3 4
Select the appropriate plan. Click the Apply Plan button. 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: 1 2 Select the appropriate plan. Click the Temp UnApply button.
The database is now reverted to its previous configuration, and the Site Database window is active again.
Page 68
Page 69
Optimising a Network
The ACP Workflow enables you to perform all the tasks within ASSET ACP from a single dialog box. 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.
Page 70
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 70. To start an optimisation: 1 2 Open the Workflow by clicking the shortcut button toolbar. In the left-hand pane, select Plan Manager. on the main ASSET ACP
Select the appropriate plan, and click the Optimise button. The Optimiser dialog box appears:
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 6
If you want to view statistics information using the Statistics Graph, Statistics Details or Report buttons, ensure that the Calculate Statistics checkbox is selected. To start the Optimiser, click Start.
Page 71
Monitoring an Optimisation
When you have started an optimisation, the Optimiser runs. This picture shows an example of a running scenario:
Page 72
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.
Page 73
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 2 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. Release the mouse button. To zoom back out, right-click.
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 2 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. 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.
Page 74
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.
Page 75
Page 76
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:
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.
Page 77
Page 78
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 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 Ranking 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 86.
Page 79
The statistics for the metrics used in the optimisation calculations. All costs relating to the optimisation metrics.
Page 80
3 4
Select the appropriate plan, and click the Analysis button. 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 6 7 Select the reporting level you require (Property, Site or Cell). Click Analyse to perform the analysis. When the analysis has finished running, the Report button will become active. 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.
Page 81
Here is an example:
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.
Page 82
3 4
Select one of the two plans you want to compare, and click the Analysis button. 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 .)
In the Analysis dialog box, for the Compare Plan, click the browse and select the other required plan.
button,
6 7 8 9
Select the reporting level you require (Property, Site or Cell). 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. Click Analyse to perform the comparison analysis. When the analysis has finished running, the Report button will become active. 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.
Page 83
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 84.
2 3
On the Map View toolbar, click the Show Data Types button Information & Control button
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).
From the list that appears, select the array type that you want to view and click Redraw to view the related analysis results:
Page 84
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
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.
Page 85
Page 86
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.
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
Page 87
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. Select the reporting level you require. 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:
5 6
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.
Page 88
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:
Page 89
About Action-Constraints
In ASSET ACP, there are two separate 'sources' of action-constraints: 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 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. There is nothing you can set up in the Site Database that you cannot also set up in the Action-Constraints dialog box. 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 ActionConstraints dialog box, regardless of their original 'source'. When you run an optimisation, there are two planning mechanisms you can use: Antenna Power ASSET ACP provides the flexibility to run optimisations based on any single mechanism, or both of them.
Page 90
This flexibility enables you to, for example: 1 2 Set specific action-constraints in the Site Database. 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.
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 ACP Workflow, see About the Action-Constraints Dialog Box on page 44 and Using the ActionConstraints Dialog Box on page 47.
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 102.
Page 91
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
Page 92
To configure equipment-specific constraints for BTS types: 1 2 3 From the Equipment menu, select BTS Equipment. In the dialog box that appears, select the BTS type that you want to constrain. 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.
Page 93
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.
Page 94
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 minimummaximum 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 92.
To define a series of allowable antenna height values within the minimummaximum 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 layerspecific 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. 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 57. 7 Click Apply to save the changes, and Commit if appropriate.
Page 95
In most cases, there will only be one antenna slot per cell, but it is possible that multiple slots have been configured.
Page 96 ASSET ACP User Reference Guide 7.0
Using ASSET ACP
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. 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:
In the Misc Constraints pane, you can set the following constraints per antenna slot:
Select this checkbox Antenna Device Fixed Antenna Pattern Fixed To Prevent changes to the antenna device during optimisation. Prevent changes to the antenna pattern during optimisation. If you select this, Antenna Device Fixed will be selected automatically. Mechanical Downtilt Fixed Azimuth Fixed Height Fixed Constrain Max Main Lobe Tilt Prevent changes to the mechanical downtilt during optimisation. Prevent changes to the azimuth during optimisation. Prevent changes to the antenna height during optimisation. Prevent changes to the electrical and/or mechanical downtilt that violate this constraint during optimisation.
Page 97
Page 98
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. 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:
Page 99
In the Misc Constraints pane, you can set the following constraints per cell:
Select this checkbox Antenna Device Fixed Antenna Pattern Fixed To Prevent changes to the antenna device during optimisation. Prevent changes to the antenna pattern during optimisation. If you select this, Antenna Device Fixed will be selected automatically. Mechanical Downtilt Fixed Azimuth Fixed Height Fixed Constrain Max Main Lobe Tilt Prevent changes to the mechanical downtilt during optimisation. Prevent changes to the azimuth during optimisation. Prevent changes to the antenna height during optimisation. Prevent changes to the electrical and/or mechanical downtilt that violate this constraint during optimisation.
Page 100
Page 101
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:
To set the constraint To unset the constraint (if previously set)
Page 102
ASSET ACP-specific Constraints in the Global Editor This table describes the ASSET ACP-specific constraints:
On this tab Cell Constraints You can set these 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: Installation (GSM) Cell Layer (GSM) Node Config (UMTS) Cell Params (UMTS) Manual, Mast or Step Height Min Height Max Height
Fixed Site/BTS Equipment Fixed PA Output Fixed Node Type Fixed Max TX Power Fixed UMTS Channels Power Fixed HSDPA Power
Load & Power Ctrl (UMTS) WiMAX Cell Params LTE Cell Params
Page 103
Page 104
The ACP & Financial Analysis Reports Assignment dialog box appears:
To change the mapping relationship for a report type: 1 2 3 4 For the appropriate report type, click in the Report Name column. 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). Repeat the steps if you want to modify any other mapping relationships. 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.
Page 105
Page 106
N
Network Improvement Analysis 83 Network Performance Analysis 81
Index
A
Action-Constraints about 90 antenna planning 47, 55 dialog box 44, 47 power planning 47, 58 setting 90 templates 53 ADVANTAGE workflow 15 Analysing and evaluating plans 79 Analysis for a single plan 81 network improvement 83 network performance 81 to compare plans 83 Antennas sharing 57 ASSET ACP workflow 16 Auto Plan Setup, using 36
O
Optimisation Action-Constraints templates 53 antenna 47, 55 parameters 16 power planning 58 prerequisites 70 reports 72, 76 running the optimiser 72 starting the optimiser 71 strategy 23 thresholds 18 Optimiser Workflow using 16
P
Plan Manager, using 28 Plans concept 29 creating 31 Traffic Options 25 using the Plan Manager 28 viewing and using 30
R
RF Thresholds 18
C
Clutter/Vector parameters 18 Constraints about 90 Action-Constraints dialog box 49 BTS equipment and mast 92 GSM cell antenna 96 GSM site installation 96 GSM subcell antenna/TRX 98 in Site Database 90 metric degradation 23 Property antenna 94 UMTS cell load and power ctrl 101 UMTS cell params 100 UMTS node antenna 99 UMTS node resource 98
S
Sampling, for clutter 19 Shared antennas how considered 57 Statistics graphs 74 reports 74, 76
T
Thresholds setting 18
D
Delta Plans 29
G
Global Editor setting constraints in site database 102
Page 107
Page 108