ASSET
User Reference Guide
Version 2023 Q2
Confidentiality, Copyright Notice & Disclaimer
Due to a policy of continuous product development and refinement, TEOCO Corporation or a
TEOCO affiliate company ("TEOCO") reserves the right to alter the specifications, representation,
descriptions and all other matters outlined in this publication without prior notice. No part of this
document, taken as a whole or separately, shall be deemed to be part of any contract for a product
or commitment of any kind. Furthermore, this document is provided “As Is” and without any
warranty.
This document is the property of TEOCO, which owns the sole and full rights including copyright.
TEOCO retains the sole property rights to all information contained in this document, and without
the written consent of TEOCO given by contract or otherwise in writing, the document must not be
copied, reprinted or reproduced in any manner or form, nor transmitted in any form or by any
means: electronic, mechanical, magnetic or otherwise, either wholly or in part.
The information herein is designated highly confidential and is subject to all restrictions in any law
regarding such matters and the relevant confidentiality and non-disclosure clauses or agreements
issued with TEOCO prior to or after the disclosure. All the information in this document is to be
safeguarded and all steps must be taken to prevent it from being disclosed to any person or entity
other than the direct entity that received it directly from TEOCO.
TEOCO and Helix are trademarks of TEOCO.
All other company, brand or product names are trademarks or service marks of their respective
holders.
This is a legal notice and may not be removed or altered in any way.
COPYRIGHT © 2023 TEOCO Corporation or a TEOCO affiliate company.
All rights reserved.
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 find 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
1
27 March 2023
First edition.
Introduction to ASSET
Table of Contents
1
Introduction to ASSET .................................................................................. 15
About This User Reference Guide ................................................................... 15
2
Setting Up a Project ...................................................................................... 17
Starting ASSET ............................................................................................... 17
Logging In to a Database ................................................................................. 17
Adopting an Open Session with Administrator Permissions ..................................... 19
Changing Your Password .......................................................................................... 19
Logging Out of a Database .............................................................................. 19
Creating a New Project .................................................................................... 20
Sharing Data between Projects ................................................................................. 22
Duplicating Projects ................................................................................................... 22
Defining the Project Settings ..................................................................................... 22
Exporting Project Settings ................................................................................ 29
Importing Project Settings ................................................................................ 30
Opening an Existing Project ............................................................................. 31
Defining the Project Load Options ................................................................... 32
Loading a Subset of Project Data (Site Region Load) ...................................... 33
How Region Loading Affects the Project ................................................................... 34
Setting Up Site Region Load Using Method 1 ........................................................... 34
Setting Up Site Region Load Using Method 2 ........................................................... 36
Setting Up Site Region Load Using Method 3 ........................................................... 37
Setting Up Your Preferences ........................................................................... 38
Setting General Preferences ..................................................................................... 39
Setting Earth Radius Preferences ............................................................................. 40
Setting Network Preferences ..................................................................................... 41
Setting Technology Preferences ............................................................................... 42
Setting Diffraction Preferences .................................................................................. 42
Setting Candidate Options Preferences .................................................................... 43
Setting Filter and History Preferences ....................................................................... 44
Setting Electrical Tilts Preferences ............................................................................ 45
Enabling or Disabling Large Array Support within a Project ............................. 46
Defining the Site Database Settings ................................................................ 48
Customising the Object Count in the Site Database ......................................... 49
Defining the Map View Options ........................................................................ 50
About the New Project Default Objects ............................................................ 51
3
About the Core User Interface ..................................................................... 53
About the Tabs and Main Menu ....................................................................... 53
About the Main Toolbar in ASSET ................................................................... 53
About the Core Windows ................................................................................. 54
Displaying and Hiding Windows ................................................................................ 55
About Workspaces..................................................................................................... 56
About the Site Database Window .............................................................................. 60
5
ASSET User Reference Guide
About the Core Map View Window ............................................................................ 64
About the Equipment Windows ................................................................................. 73
About the Logical/Cellular Connection Database Window ........................................ 75
About the Message Log Window ............................................................................... 76
About the Wastebasket.............................................................................................. 76
About Add-Ins ............................................................................................................ 77
About the Licence Administrator ...................................................................... 77
Getting or Dropping Licences .................................................................................... 78
Commuting Licences ................................................................................................. 79
Editing your Startup Option ....................................................................................... 79
About the Distributed Task Agent Menu ........................................................... 80
4
Viewing and Editing Networks on the Map ................................................. 81
Using the Layer Control Pane .......................................................................... 81
Selecting Data Types to View on the Map................................................................. 82
Changing the Display Order of the Layers ................................................................ 83
Displaying and Changing Legend Information .......................................................... 84
Selecting an Item on the Map to Find it in the Site Database ........................... 84
Using the Tiled View ........................................................................................ 85
Viewing Web Maps .......................................................................................... 86
Adding, Moving and Deleting Network Elements on the Map ........................... 87
Setting a Default Network .......................................................................................... 87
Adding Properties ...................................................................................................... 88
Automatically Generating Sites/Nodes ...................................................................... 88
Adding Network Elements with a Selected Template ................................................ 89
Copying Network Elements ....................................................................................... 90
Deleting Network Elements ....................................................................................... 90
Moving Network Elements ......................................................................................... 91
Adding Logical and Cellular Connections on the Map ............................................... 92
About Displaying Site Visibility ......................................................................... 93
Displaying Site Visibility ............................................................................................. 95
Changing Antenna Heights Used in the Site Visibility Calculation ............................ 97
Zooming, Moving and Redrawing the Map ....................................................... 98
Zooming on the Map .................................................................................................. 98
Saving a Favourite (Home) Zoom Level .................................................................... 99
Shortcut Keys for Zooming ...................................................................................... 100
Repositioning (Panning) the Map ............................................................................ 100
Redrawing the Map.................................................................................................. 100
About the GIS Export of Map Layers.............................................................. 100
About Favourite Map Views ........................................................................... 101
Saving a Favourite View .......................................................................................... 102
Loading a Favourite View ........................................................................................ 103
Managing Favourite Views ...................................................................................... 104
Searching the Map View Window with the Quick Finder ................................ 106
Using Jump To Location ................................................................................ 108
Examples of Searching by Regular Expression ............................................. 109
Other Regular Expressions Examples ..................................................................... 111
Viewing Map Information in Other Windows................................................... 111
Viewing Information about a Specific Pixel.............................................................. 111
Viewing Information in the Height Profile Window ................................................... 115
About the Master View............................................................................................. 125
6
Introduction to ASSET
Printing from the Map View ............................................................................ 126
Choosing the Legend Information for the Printouts ................................................. 126
Customising the Page Layout for Printing ............................................................... 126
Printing the Whole Map View .................................................................................. 127
Printing a Specific Area of the Map View ................................................................ 127
Printing a Map View to File ...................................................................................... 128
Using Third Party 3D Visualisation Tools ....................................................... 128
5
Generating Arrays and Reports for Analysis............................................ 129
About Arrays .................................................................................................. 129
About the Array File Formats ................................................................................... 130
About Large Array Support ...................................................................................... 130
Using the Array Manager ............................................................................... 131
Saving Arrays .......................................................................................................... 133
Loading Arrays ......................................................................................................... 134
Loading Arrays Generated by ARRAYWIZARD ...................................................... 135
Deleting Arrays ........................................................................................................ 136
Viewing Array Progress and Aborting Arrays .......................................................... 136
Viewing a Summary of Simulation Data .................................................................. 137
Displaying Arrays in the Map View ................................................................. 138
Displaying Arrays ..................................................................................................... 139
Customising the Array Display Properties ............................................................... 140
Defining Display Schemas for Arrays ...................................................................... 143
Loading Display Schemas into the Array Display Properties .................................. 144
Producing Delta Difference Plots ................................................................... 145
Baseline Comparison ..................................................................................... 146
Using Graphical Analysis ............................................................................... 147
About the Pixel Analyser ................................................................................ 149
Using the Pixel Analyser to View Information ................................................. 150
Selecting the Arrays to Display in the Pixel Analyser .............................................. 152
Setting the Pixel Column Details in the Pixel Analyser ........................................... 153
Displaying Vector Analysis Plots ............................................................................. 155
About the Options Pane on the Pixel Analyser ....................................................... 156
Using the Pixel Analyser to Export Array Data ............................................... 157
Exporting Array Data to a Report for a Single Grid Location ................................... 158
Exporting Array Data to a Report Based on Multiple Points .................................... 159
Generating Statistical Reports for Arrays ....................................................... 162
Using the Statistics Dialog Box ................................................................................ 164
Results of the Statistical Reports for Arrays ............................................................ 166
How Polygons are considered in the Statistical Analysis ........................................ 168
6
Changing How Data Appears on the Map ................................................. 169
Controlling the Selection and Appearance of the Data ................................... 169
Customising How Text is Displayed ............................................................... 169
Customising How Height Data is Displayed ................................................... 170
Customising How Clutter is Displayed ........................................................... 171
Using the Automatic Map Resolution Option .................................................. 172
Customising How the Map Backdrop is Displayed ......................................... 173
Customising How Web Map Data is Displayed .............................................. 174
7
ASSET User Reference Guide
Customising the Map Grid and Scale Bar ...................................................... 175
Customising How Filters are Displayed .......................................................... 177
Quickly Changing How Items in Filters are Displayed ............................................. 178
Making Detailed Changes to the Display of Items in Filters .................................... 179
Changing the Shape of Symbols, Radials, Hexagons for Items in Filters ............... 180
Changing the Line for Items in Filters ...................................................................... 183
Changing the Fill for Items in Filters ........................................................................ 183
Changing the Colour Based on a Variable .............................................................. 184
Changing the Background of Items in Filters........................................................... 186
Changing the Visibility of Items in Filters ................................................................. 186
Changing the Display of Labels in Filters ................................................................ 186
Changing the Display of Service Areas in Filters .................................................... 187
Example of Displaying Properties According to Ground Height .............................. 188
Example of Displaying Address Information for Properties in Filters ...................... 190
Customising How Vector File Features are Displayed ................................... 191
Making Simple Changes to the Display of Vector File Features ............................. 192
Making Detailed Changes to the Display of Vector File Features ........................... 193
Changing the Fill Colour or Pattern of Vector File Features .................................... 194
Changing the Line Attributes of Vector File Features .............................................. 195
Changing the Visibility of Vector File Features ........................................................ 196
Changing the Labels of Vector File Features .......................................................... 197
Changing the Symbol of Points ............................................................................... 198
Changing the Symbol Appearance of Points ........................................................... 198
Changing the Appearance of (Vector) Text ............................................................. 199
Copying the Display Properties of Filters ....................................................... 200
Using Visualisers ........................................................................................... 200
Adding Visualisers ................................................................................................... 200
Changing the Display Properties of Visualisers ...................................................... 201
Copying and Resetting Display Properties of Visualisers ....................................... 201
Exporting and Importing Display Properties of Visualisers...................................... 202
Removing Visualisers .............................................................................................. 202
Viewing Attribute Data as Site Tips ................................................................ 203
7
Saving Data to the Database ...................................................................... 205
Saving Your Changes to the Database .......................................................... 205
Applying Your Data .................................................................................................. 205
Committing Your Data ............................................................................................. 206
Committing All Your Data in the Dialog Box ............................................................ 206
Committing All Your Data in the Project .................................................................. 206
Restoring Your Data ................................................................................................ 207
Examples of Using Apply and Commit .................................................................... 207
Logging Out and Logging In Recommendation .............................................. 210
Using Refresh to Update Network Elements .................................................. 211
Example of Using Apply, Commit and Refresh ....................................................... 212
About the Refresh Functionality and Database Warnings .............................. 213
Saving Sandbox Changes to the Database.................................................... 213
Checking Blocked Actions between Different Users ....................................... 215
Resolving Commit Failures ............................................................................ 216
Generating Reports of Uncommitted Changes ............................................... 218
Using the Version Reporter ............................................................................ 219
8
Introduction to ASSET
8
Viewing and Editing the Site Database ..................................................... 221
Using Templates for Network Elements ......................................................... 222
Creating a Template for a Network Element ........................................................... 223
Creating a Template from an Existing Network Element ......................................... 224
Editing and Copying Templates ............................................................................... 225
Deleting a Template................................................................................................. 225
Choosing the View in the Site Database ........................................................ 226
Refreshing the Display of Network Elements in Site Database ............................... 227
Selecting Which Tabs to Display in Site Database ................................................. 227
Opening the Site Database at a Particular Site ....................................................... 229
Using the Map View to Find Elements in Site Database ......................................... 229
Creating a PLMN Network or Logical Network ............................................... 230
About Properties ............................................................................................ 231
Viewing Properties in the Site Database ................................................................. 231
Viewing and Changing Address and Contact Details .............................................. 232
Adding and Deleting Network Elements in the Site Database ........................ 234
Adding Properties and Sites/Nodes Simultaneously ............................................... 235
Adding Network Elements Based on Templates ..................................................... 237
Deleting Network Elements in the Site Database .................................................... 237
Adding Logical and Cellular Connections in the Site Database ...................... 240
Making Changes to Network Elements in Site Database ............................... 242
About the Tabs in the Site Database Window ......................................................... 242
Making Global Changes to Network Elements ............................................... 246
What Data Can You Edit Globally? ......................................................................... 248
Reparenting Network Elements ..................................................................... 249
9
Using Vector File Features ......................................................................... 251
About the Vector Manager ............................................................................. 252
Configuring Vector Files................................................................................. 253
Importing Vector File Data ............................................................................. 254
MapInfo Vectors - Coordinate System Conversion ................................................. 255
Exporting Vector File Data ............................................................................. 256
Troubleshooting Vector Files ......................................................................... 256
Classifying User Vector Files ......................................................................... 256
Creating Your Own Vector File Features ....................................................... 259
Creating a Region Polygon ...................................................................................... 262
Defining Attributes for a Vector File Feature ........................................................... 264
Setting Values for the Attributes .............................................................................. 265
Editing Lines and Polygons ..................................................................................... 268
Creating Holes or Islands for Polygons ................................................................... 269
Saving Vectors ......................................................................................................... 271
Exporting Vectors .................................................................................................... 271
10
Using Filters and Fields .............................................................................. 273
Using Fields in ASSET................................................................................... 273
Examples of Field Definitions .................................................................................. 274
Viewing and Editing Fields for Network Elements ................................................... 274
9
ASSET User Reference Guide
Using Filters in ASSET .................................................................................. 275
Purpose and Uses of Filters .................................................................................... 276
Creating a Dynamic Filter using the Filter Wizard ................................................... 277
Creating a Static Filter using the Filter Wizard ........................................................ 281
Editing and Deleting Filters ...................................................................................... 284
Organising Filters ..................................................................................................... 284
Copying Filters ......................................................................................................... 285
Example Filters ........................................................................................................ 286
Filtering Objects by their Technology and Activity Settings ..................................... 293
About the Selection Expert and Selection Filter ...................................................... 294
Making Your Dynamic Filters More Efficient............................................................ 306
Displaying Filters ..................................................................................................... 309
Exporting Filters using XML Export ......................................................................... 310
11
Managing Antennas and Equipment ......................................................... 311
Managing Antennas and Equipment using Folders ........................................ 311
Storing Antennas in the Database ................................................................. 312
Using the Cellular Antennas Dialog Box ........................................................ 313
About the Tabs on the Cellular Antennas Dialog Box ............................................. 315
About the Filter Option in the Cellular Antennas Dialog Box ................................... 316
About the Display Options in the Cellular Antennas Dialog Box ............................. 316
Adding Antenna Devices ......................................................................................... 317
About Switched Beam Antennas ............................................................................. 319
Creating Beam Sets ................................................................................................. 320
Adding Patterns to an Antenna Device .................................................................... 323
About the Azimuth Offset ......................................................................................... 325
Using the Basic Search for Cellular Antennas ........................................................ 326
Using the Hierarchy Tab to View, Delete or Reparent Patterns .............................. 326
Deleting Antenna Devices and Patterns .................................................................. 327
Editing or Moving Antenna Devices and Patterns ................................................... 328
Viewing Pathlosses for Patterns .............................................................................. 329
Comparing Two Patterns ......................................................................................... 329
About the Context Menu on the Tree Tab ............................................................... 331
Using the Advanced Search for Antennas............................................................... 331
Using the Switched Beam Antenna Utility ...................................................... 339
Digitally Splitting Antennas ............................................................................ 342
Using the Planet PAFX Antenna Import ......................................................... 342
Using the Planet Antenna Utility..................................................................... 343
Adding Microwave Antennas ......................................................................... 344
Adding Microwave Antenna Patterns ...................................................................... 345
Editing the Mask Data for Microwave Antennas ...................................................... 347
Editing, Moving and Deleting Microwave Antennas ................................................ 348
Storing Equipment in the Database ............................................................... 349
Creating Site (BTS) Equipment ............................................................................... 350
Creating Cell Equipment .......................................................................................... 351
Creating Cabins ....................................................................................................... 351
Creating Feeders ..................................................................................................... 352
Creating Masts ......................................................................................................... 353
Creating Mast Head Amplifiers ................................................................................ 354
Viewing and Changing Equipment Suppliers Details .............................................. 355
10
Introduction to ASSET
12
Using Propagation Models ......................................................................... 357
How Many Propagation Models are Required? .............................................. 357
About the Accuracy Required for a Propagation Model .................................. 358
About the Supplied Propagation Models ........................................................ 358
About the Standard Macrocell Models ..................................................................... 360
About the DHM Model ............................................................................................. 363
About the Enhanced Macrocell Model ..................................................................... 364
About the Free Space Loss Model .......................................................................... 365
About the MYRIAD Model........................................................................................ 365
About the Volcano Models ....................................................................................... 366
About the SUI Model................................................................................................ 370
About the SLR Model............................................................................................... 371
Adding and Editing Propagation Models ........................................................ 371
Configuring a Standard Macrocell Model ................................................................ 372
Configuring a DHM Model ....................................................................................... 374
Configuring an Enhanced Macrocell Model ............................................................. 375
Configuring a Free Space Loss Model .................................................................... 377
Configuring a SUI Model.......................................................................................... 377
Configuring an SLR Model....................................................................................... 379
Deleting a Propagation Model ................................................................................. 379
About Multiple Height Pathloss Predictions .................................................... 380
Model Types Supported by Multiple Height Capability ............................................ 382
Specifying Additional Heights on the Propagation Model........................................ 382
About the Receiver Heights Mode in the Coverage Analysis Wizard ..................... 383
Generating Multiple Height-specific Arrays in a Simulation ..................................... 384
Recommended Mapping Data for Propagation Models .................................. 384
Countrywide Dataset Mapping Data ........................................................................ 385
Urban Datasets Mapping Data ................................................................................ 385
High Resolution Datasets Mapping Data................................................................. 385
13
Working with Data ....................................................................................... 387
Using Nominal and Candidate Properties ...................................................... 387
Adding Nominals and Candidates in the Site Database .......................................... 387
About the Candidate Options on the Toolbar .......................................................... 388
Adding Nominals and Candidates in the Map View Window................................... 389
Displaying Candidates and Nominals in the Map View ........................................... 392
Removing Candidate Status from a Property .......................................................... 394
What Happens When Search Areas Overlap? ........................................................ 394
Viewing and Editing Logical/Cellular Connections.......................................... 395
Adding Routes and Hops to a Logical/Cellular Connection..................................... 397
Viewing and Editing the Traffic on a Logical/Cellular Connection ........................... 399
About Using GPS........................................................................................... 400
Positioning the GPS Receiver ................................................................................. 400
Using GPS ............................................................................................................... 400
Setting Default Identifiers ............................................................................... 401
Converting Files ............................................................................................. 403
Editing the Map Data ..................................................................................... 403
Editing Terrain Height .............................................................................................. 403
Editing Clutter Types ............................................................................................... 404
Editing Building Heights ........................................................................................... 406
Using Attachments......................................................................................... 408
Using Photographs ........................................................................................ 409
11
ASSET User Reference Guide
Associating a Photograph with Equipment .............................................................. 409
Associating a Photograph with a Network Element ................................................. 410
14
Importing and Exporting ............................................................................ 411
Importing Data ............................................................................................... 411
Importing ASSET Data ............................................................................................ 411
Importing XML Data ................................................................................................. 411
Using the 3GPP Import/Export ................................................................................ 416
Importing PlaNet/EET Data ..................................................................................... 417
Importing Property Data........................................................................................... 419
Importing GSM Data ................................................................................................ 420
Importing CellOpt Data ............................................................................................ 420
Importing Vector File Data ....................................................................................... 421
Exporting Data ............................................................................................... 423
Exporting ASSET Data ............................................................................................ 423
Exporting XML Data ................................................................................................. 424
Exporting 3GPP Data .............................................................................................. 429
Exporting Filters ....................................................................................................... 431
Exporting Vector File Data ....................................................................................... 432
Exporting PlaNet/EET Data ..................................................................................... 432
Exporting Property Data .......................................................................................... 433
Exporting CellOpt Data ............................................................................................ 433
Exporting Web Service Data.................................................................................... 434
Exporting Map Layers using GIS Export ........................................................ 435
Preparation for the GIS Export ................................................................................ 435
Performing the GIS Export....................................................................................... 436
Using the XML Data Editor ............................................................................ 437
About the XML Data Editor User Interface .............................................................. 438
Setting Preferences for the XML Data Editor .......................................................... 440
Opening and Closing XML Files .............................................................................. 441
Editing and Deleting Data ........................................................................................ 442
Viewing and Editing Antenna XML Files .................................................................. 443
Changing the Display of Data in the XML Data Editor ............................................ 444
Using Advanced Filtering and Sorting ..................................................................... 445
Creating New XML Data Files ................................................................................. 447
Editing Fields ........................................................................................................... 448
Copying and Pasting Data in the XML Data Editor ................................................. 448
Using the XML Data Editor with Microsoft Excel ..................................................... 450
Using the XML Data Editor with CSV Files.............................................................. 451
Updating an ASSET Project with the Edited Data ................................................... 452
Importing and Exporting Equipment ............................................................... 453
Exporting Equipment ............................................................................................... 453
Modifying the All Equipment File for Re-Import of Data .......................................... 453
Importing Equipment................................................................................................ 454
Importing and Exporting User Settings........................................................... 455
Exporting User Settings ........................................................................................... 455
Importing User Settings ........................................................................................... 456
Deleting User Settings ............................................................................................. 456
15
About the Grid Data Loader ....................................................................... 457
Before Using the Grid Data Loader ................................................................ 458
Basic Difference between Insert and Update ................................................. 459
Hierarchy and Information Flow ..................................................................... 459
Guidelines for the Grid Data Loader............................................................... 460
Using the Grid Data Loader ........................................................................... 461
12
Introduction to ASSET
Setting Preferences ................................................................................................. 462
Setting the Header Row........................................................................................... 464
Inserting and Deleting Columns .............................................................................. 465
Integrating the Site Database Reports with the Grid Data Loader .......................... 466
Using Site Database Reports Data as Input to Grid Data Loader ........................... 468
Loading Data from a File ......................................................................................... 469
Manually Editing the Data Rows .............................................................................. 471
Inserting and Deleting Rows .................................................................................... 472
Editing the Data Rows Using Copy and Paste ........................................................ 473
Editing the Data Rows Using Paste Special ............................................................ 474
About the Validation Messages ............................................................................... 475
Exporting (Saving) a File ......................................................................................... 476
Creating a New File ................................................................................................. 476
Valid Headers for Each Object Type .............................................................. 477
Sample Header Row Files ....................................................................................... 477
Object Type: Property .............................................................................................. 477
Object Type: MU-Node ............................................................................................ 480
Object Type: Cell ..................................................................................................... 482
Object Type: Property (for ASSET Backhaul) ......................................................... 494
Object Type: Point to Multi Point Link ...................................................................... 495
Object Type: Multi Band Link ................................................................................... 495
Object Type: Multi Radio Link .................................................................................. 496
Object Type: Repeater............................................................................................. 497
Object Type: Point to Point Link .............................................................................. 498
Object Type: Reflector ............................................................................................. 498
Object Type: Dual Polar Link ................................................................................... 499
About Antenna Indexes ........................................................................................... 500
About the Location Parameters ............................................................................... 500
Examples of Use Cases................................................................................. 501
1 - Creating New MU-Nodes (INSERT mode) ......................................................... 502
2 - Creating New Properties, Nodes, Cells, Antennas (INSERT mode) .................. 503
3 - Modifying a Data Parameter of an MU-Node (UPDATE mode) ......................... 505
4 - Modifying an Antenna Parameter using Cell Identity (UPDATE mode) ............. 506
5 - Changing a Physical Antenna Assignment (UPDATE mode) ............................ 507
Index............................................................................................................. 509
13
ASSET User Reference Guide
14
Introduction to ASSET
1 Introduction to ASSET
The ASSET suite of products incorporates a range of advanced tools which provide valuable
integrated support in the areas of radio network planning and transmission planning. As well as
operating standalone, the tools can operate seamlessly together, sharing critical information without
duplication.
The ASSET products link to a common industry standard relational database (RDBMS) where you
can store all your network data. In addition, ASSET products use the same user-friendly
Geographical Information System (GIS) to give you a common interface.
The main ASSET products are:
Product
Description
Administrator
For specifying and configuring your database, projects and users
ASSET Radio*
Radio network planning and analysis for cellular networks
ARRAYWIZARD
Automated tool for pathloss predictions and coverage arrays
ASSET Backhaul
Network transmission and microwave link planning software
*There are also other products that ASSET Radio can integrate with:
 ASSET Capacity - Dimensions end-to-end mobile networks and transmission layers, from
base stations to media gateways.
 ASSET Design - Searches for the optimal network design, based on specific planning
objectives, including addition of new small cells.
 ASSET Geo - Enables the use of geo-located traffic and performance maps to assist the
planning process.
About This User Reference Guide
This User Reference Guide describes functionality that is common to more than one tool in the
ASSET suite, such as Projects, Map View, Arrays, Filters, Equipment. Functionality that is specific
to a tool (such as the Simulator in ASSET Radio, or the Link Database in ASSET Backhaul) is
described in the tool-specific User Reference Guide.
This table shows where to look for information in the ASSET User Reference Guide:
Read
For Information On
Chapter 2
Starting ASSET
Setting up a project
Setting your preferences
Chapter 3
Basic components of the user interface
Chapter 4
Adding and editing network elements in the Map View window
Displaying items in the Map View window
Moving around the map and zooming
Chapter 5
Using the Array Manager
Displaying arrays in the Map View
Using the Pixel Analyser to view information and export array data
Generating statistical reports for arrays
15
ASSET User Reference Guide
Read
For Information On
Chapter 6
Changing how items appear on the map
Changing the display of filters, with examples
Chapter 7
Saving Data to the Database
Apply, Commit, Restore, Refresh
Saving Sandbox Changes to the Database
Chapter 8
Using Templates for Network elements
Adding and editing network elements in the Site Database window
Making global changes to items
Applying and Committing
Chapter 9
Configuring vector files
Creating polygons, lines, points and text
Chapter 10
Creating filters
Creating fields
Chapter 11
Storing antennas
Storing equipment
Chapter 12
Creating and using propagation models
Chapter 13
Using nominal and candidate Properties
Viewing and editing logical /cellular connections
Chapter 14
Importing and exporting data in a variety of formats
Chapter 15
Using the Grid Data Loader
There is also a separate ASSET Technical Reference Guide, which contains information on the
following:
16
Read
For Information On
Chapter 1
Map data file formats used in ASSET
Chapter 2
General file formats used in ASSET
Chapter 3
XML file formats used in ASSET
Chapter 4
Miscellaneous vendor and third party file formats used in ASSET
Chapter 5
Antenna and Diffraction Calculations
Chapter 6
Interfaces and APIs
Chapter 7
Chinese Character Support
Chapters 8-12
Information about algorithms, arrays and outputs specific to ASSET Radio
Setting Up a Project
2 Setting Up a Project
ASSET uses projects as a way of grouping your network data within the database. Each project
can be configured differently and you can share data across projects.
Starting ASSET
Once your system administrator has set up the database and created a user account for you, you
can start ASSET and create a new project ready for planning work.
To start ASSET:
From the Windows Start Menu, select Start>All Programs>TEOCO>ASSET V2023
Q2>TEOCO ASSET Suite
The main toolbar appears along the top of the screen. The title bar summarises the database,
project and user details. The tabs correspond to the different modules available, depending on
which modules have been licensed.
Here is an example:
Example of tabs - these correspond to the different modules that have been licensed and installed
Simultaneous Login to Multiple Projects
It is possible for the same ASSET user to log in to two or more separate projects in the same
database with write access (dependent on permissions), by starting multiple instances of ASSET.
Write access to each project is achieved by using separate instances of the ASSET client.
If the user logs into the same project twice, the second instance of the project will be read-only.
This rule is the same for master projects and sub-projects. Also, for the second instance of the
project, any 'All Projects' options in Equipment or Antenna dialogs will be read-only.
This can be on the same machine, or different machines. Each instance will consume a licence.
Logging In to a Database
Before you can log in to a database, an administrator must have used the ASSET Administrator
program to set you up as an authorised user of a database. For information on using this product,
see the ASSET Installation and Administration Guide.
To log in to a database:
1. Ensure the Database Login dialog box is open.
If it is not, from the File menu, click Login or click the Login button
.
17
ASSET User Reference Guide
The Database Login dialog box appears:
2. In the Database Login dialog box, ensure the correct database is shown in the Data
Source box.
3. Choose whether to log into ASSET:
o
By typing in a username and password as set up by your administrator.
o
Automatically, using authentication from the operating system (OS) where you are
connected automatically to the database if the server confirms that you exist. This
means you do not have to use a separate password here. For information on setting
this up, see the ASSET Installation and Administration Guide.
4. Click Login.
If you belong to the Administrators group or have been made a member of a Sandbox then
the Login Type dialog box appears.
If you belong to the Administrators group you have the choice of:
o
Logging in as yourself.
o
Logging in as another user who is not already logged into the project. For example, to
create new objects on their behalf.
If you are a member of one or more Sandboxes then you can log in to a Sandbox.
Note: A sandbox is an optional environment within ASSET in which users can experiment
with network changes and can see each other's applied changes without having to commit
them and without making them visible to other users. For more information on how
administrators give users access to Sandboxes, see the ASSET Installation and
Administration Guide.
Select which user to log in as. If you choose to log into a Sandbox and your administrator
has given you access to more than one, select the required Sandbox from the drop-down
list of those available.
When you have made the required selections in the Login Type dialog box, click OK.
Also see Saving Sandbox Changes to the Database on page 213.
18
Setting Up a Project
Adopting an Open Session with Administrator Permissions
Using the username and password for an administrator account, you can make changes that your
own user permissions may not ordinarily allow.
To adopt your own open session, or that of another user - either at the user's PC or remotely
using appropriate software, with administrator permissions:
1. When you are logged on or the other user whose session you wish to adopt is logged on,
click the Utilities tab.
2. From the Tools menu, click Adopt Session.
3. Type in a username and password for an administrator account, then click OK.
4. Make the changes required. All these changes are credited to the logged on user.
5. From the Tools menu, click Cancel Adopt Session to stop the adopted session and return
the logged on user’s normal permissions.
Changing Your Password
To change your password:
1. Click the Utilities tab.
2. From the Tools menu, click Change Password.
3. Type in your existing password.
4. Type in your new password.
5. Type in your new password again.
6. Click OK.
Logging Out of a Database
Whenever you close ASSET, It is always recommended to Log Out of the database first. This is
because the logging out procedure clears any 'left-over' data that might cause future problems with
Apply and Commit.
To log out of a database:
1. Click the Close Project
button to close the project.
2. Click the Logout button
to log out of the database.
If appropriate, you can then close the ASSET application.
19
ASSET User Reference Guide
Creating a New Project
When you have logged into a database, the Project Manager dialog box appears. This picture
shows an example:
Project Manager dialog box
After projects have been created, the Project Manager dialog box shows all projects that are
currently available within the database.
(When all projects are closed, you can access this dialog box by clicking the
main toolbar.)
button in the
Note: If you simply want to start an existing project, see Opening an Existing Project on page 31.
20
Setting Up a Project
To create a new project:
1. In the Project Manager dialog box, click Add.
2. If you have no existing projects, go to step 3. If you have existing projects, the Table
Selection dialog box appears:
Choose either:
o
New Project data (if you want no interdependency between this project and any
existing projects)
- or -
o
Share existing Project data (if you want this to be a dependent sub-project of an
existing project)
Warning: Only share data if your map data cannot be contained within a single projection
or zone as then you will need multiple projects to accurately model the site co-ordinates.
You cannot share projects whose project data is already shared. For more information, see
Sharing Data between Projects on page 22.
3. If you choose to share project data, select the project whose data you want to share from
the drop-down list.
This project will subsequently appear at the top level of the tree shown in the Project
Manager dialog box with the new project shown underneath.
4. If ASSET has been set up with a settings database schema, the Project Defaults field is
enabled in the Table Selection dialog box. You can use the browse button to select a .stt
file containing user settings to be used as defaults in the new project. For more information
about the settings schema, see Database Settings Management in the ASSET Installation
and Administration Guide. For more information on storing user settings see Importing and
Exporting User Settings on page 455.
5. In the Project Manager dialog box, set up your:
a. Project Settings, as described in Defining the Project Settings on page 22.
b. Project Load Options, as described in Defining the Project Load Options on page 32.
6. When you have entered all the required information on the tabs, click OK.
21
ASSET User Reference Guide
Sharing Data between Projects
Sharing data between projects in the same database is useful in countries where the radio network
spans more than one co-ordinate projection system. For example, Australia could span seven
different UTM projection zones, each requiring different settings to obtain the correct co-ordinate
conversion between spherical co-ordinates (latitude/longitude) and Cartesian co-ordinates (grid).
In this case, it would be possible to set up seven different projects, one for each set of map data but
have them all connected to the same set of database tables containing network data.
You could also use shared data in conjunction with loading a region or subset of a project. For
example, you could have one project where all the sites are visible and a number of sub-projects
each with different load areas.
Shared projects are shown in the project list as a hierarchy, with the project (chosen to share its
data) at the top level and the newer project appearing as a sub-folder. Only two levels are
permitted:
Shared Projects shown in the project list
Important: If you have anything shared between projects, for example antennas, and you export
and re-import as a new project in the same database you will get a message telling you that you
are re-importing duplicate information. This message appears for each data point on an antenna,
so ideally, do not try and re-import items that are shared between projects.
Duplicating Projects
If you are an Administrator User, a Regional Super User, a Power User or a member of the
Administrators group, you can duplicate a project or sub-project by using the Duplicate button in
the Project Manager dialog box. For more information, see the ASSET Installation and
Administration Guide.
Defining the Project Settings
To access the Project Settings:
In the Project Manager dialog box, select the required project and click Settings to access
the project settings.
The Project Settings dialog box appears.
22
Setting Up a Project
This picture shows an example:
The dialog box contains several tabs, which are described in the following sections.
Tip: Within an open project, you can view these settings in a read-only mode, by clicking View
Project Settings from the File menu.
Overriding Database Directory Settings
Your ASSET administrator should have configured the database directory settings for all the
projects stored in the database, so you will not usually need to override database directory settings.
However, if you are working remotely with a copy of the database on a laptop and no longer have a
connection to the map data file server, you can override the global settings by selecting the
Override Database Directory Settings checkbox, then setting these directories to be your local
ones (this depends if you have the permission to do this).
This will affect the following tabs:
 Map data directories
 Shared data directories
 Map Data Extents
 Region Load
The alternative settings you define will be retained and become active whenever the checkbox is
selected. When you deselect the checkbox, the database directory settings revert to those set by
your administrator.
23
ASSET User Reference Guide
Notes:
 If you have created user vectors that you want to use on the laptop, you will need to import
the vector files to your new folder.
 If you duplicate a project when Override Database Directory Settings is ticked, the local
directory paths stored in the registry are not duplicated. You can export the overridden
values using the Export button in the Project Settings dialog box, and then import them
using the Import button in the Project Settings dialog box of the duplicated project.
About the Coord System Tab
The map co-ordinate system is used to translate between geographic co-ordinates and Cartesian
co-ordinates based on the projection system which the mapping data uses. It is important to set this
correctly because mapping data is only valid for the particular co-ordinate system to which it
relates.
ASSET is designed to work with one (and only one) map data projection per project. The projection
settings for the project MUST match the settings for the map data that will be used since the map
data is stored in Cartesian not spherical co-ordinates.
On the Coord System tab of the project settings, you can set the co-ordinate system to be used for
the map data. See Setting the EPSG Values on page 24.
Note: On this tab you can also import and export your project settings.
Setting the EPSG Values
The Projected EPSG and the Geodetic EPSG values can be edited manually, if you already know
the values.
However, if preferred, you can select from tables of values, as follows:
1. On the Coord System tab of the Project Settings, for the Projected EPSG, click the
Configure button.
2. In the dialog box that appears, select the required setting:
24
Setting Up a Project
3. For the Geodetic EPSG, either:
o
Click the Configure button, and, in the dialog box that appears, select the required
setting
- or -
o
Click the 'Set from projected' button.
4. Click OK.
Tips:
 For both values, you can use the 'Find' box to search for any numbers or names.
 On the Coord System tab of the Project Settings, you can also import and export your
project settings.
About the Map Data Directories Tab
On the Map Data Directories tab of the project settings, specify the locations that contain the
various index files for the map data categories you are using (for example, clutter, heights and so
on). You can either use the Browse option to find the directory, or type in the pathname.
Important: It is essential that you set up your map data directories to point to the correct folders. If
your map data does not contain a particular category, leave the box for that type of data blank.
Tip: In the Backdrops box, you can specify a path to a folder that can contain map backdrops and
aerial photos as sub-folders. For example:
An index file and data file(s) should exist in each of the sub-directories.
About the Shared Data Directories Tab
On the Shared Data Directories tab of the project settings, you can specify directory paths for
different categories of shared data, such as Prediction File folders, User Vectors and Favourite
views. You can do this either by typing the path, or using the Browse option.
Note: If your map data does not contain a particular category, leave the box for that type of data
blank.
Important:
 It is strongly recommended that you do not share the same directory paths between
different databases.
 It is also recommended that you set these directory paths to be unique per project (rather
than shared between projects), and enter paths to directories that are currently empty.
The above advice is especially applicable to the Prediction directory and Output Array directory,
because it simplifies the management of these files.
25
ASSET User Reference Guide
This table describes what you can specify:
Path or Setting
Description
System preferences
The path to the folder where system-wide Favourite views will be stored
(accessible to all users).
User preferences
The path to the folder where your own Favourite views will be stored.
Prediction directory
The path to the folder where all your pathloss predictions will be stored. You
can also view any prediction folders already known to the database, using the
drop-down box.
Important: You should ensure that all users of this project have adequate
read/write permissions for the files and folders in the specified directory.
Maximum prediction disk
space
A value that represents the maximum disk space you want to reserve for the
storage of prediction files. For more information, see About the File Caching
System for Predictions and Arrays on page 26.
Colour palette
The path to a text file that details the RGB values for the 253 colours that are
used in your project. This is optional. If you do not specify anything, a default
will be used.
Output array directory
The path to the folder where you want output arrays to be saved.
Max array disk space
A value that represents the maximum disk space you want to reserve for the
storage of array files. For more information, see About the File Caching System
for Predictions and Arrays on page 26.
Archive Folder
The path to the archive folder for what-if scenarios generated by the Simulator.
The folder will contain one or more iterations of output from the Simulator which
individually contain stored arrays and, if requested, a subset representation of
the data model at that time. These sets of cell and property parameters can be
used later for visualisation purposes in the Map View, in the form of Map Info
TAB\DAT files.
User line (vector) data
The path to the folder where user vectors (lines, polygons or points) will be
stored. Depending on your set-up, this may be:

Your own user vectors only

The user vectors for everyone in your User Group

All user vectors that exist in the database
Note: This depends whether the paths to other people's user vectors are
shared. If the user vector folder is shared between users, you should be aware
that any folder deletion will impact other users trying to use that folder until they
restart that project.
If you want to edit other people's user vectors, you will need the correct
permissions, which are set by your administrator.
Web cache directory
The path to the folder where web maps and WMS information will be cached.
For more information, see About the Web Maps Cache Folder on page 27.
Max web disk space
Maximum size of the Web Cache folder.
Working data folder
If you intend to launch ASSET Design and/or ASSET Capacity from within
ASSET Radio, you need to specify a path to the folder to be used for sharing
the project data. For more information, see 'Using ASSET Radio with Related
Products' in the ASSET Radio User Reference Guide.
About the File Caching System for Predictions and Arrays
Files relating to created predictions and arrays contain data that can be freshly regenerated at any
time, but, as this process takes time, it is more efficient to store the files on the disk every time they
are created, and manage them as a cache of precalculated data.
Therefore, in ASSET Radio, the concept behind the storage of these files is that they are stored on
disk and remain stored, even if they become 'invalid' due to changes to the cell parameters or
locations. The major benefit of this is that they can be reused whenever they become 'valid' again.
26
Setting Up a Project
It is evident from the above approach that, on some occasions, the disk might become full and
consist of many unwanted files.
For this reason, these files are automatically managed within ASSET Radio by a caching algorithm,
which can dispose of unwanted files on the basis of specific criteria, such as the elapsed time since
the file was last loaded.
As a vital input to this algorithm, you must set the maximum disk space for the storage of these
files, for the prediction folder and output array folder, which are specified on the Shared Data
Directories tab of the Project Settings dialog box.
Notes:
 The default value represents 80% of the free disk space on the drive(s) where the
prediction folder and array folder exist.
 The specified settings for maximum disk space are stored in configuration files in the root of
the Prediction folder and the Output Array folder.
 A setting of 0 for Max prediction disk space would result the deletion of all pathloss
predictions. To prevent this from happening you can either:
o
Set the following registry key to 1:
HKEY_LOCAL_MACHINE\SOFTWARE\AIRCOM
International\ENTERPRISE\23.2\Prediction\PreventAutoDeletePrediction
- or o
Include a file called DO_NOT_DELETE_PREDS.txt in the Prediction directory for the
project
The concept of the File Management System is also described in the 'Predicting Pathloss and
Displaying Coverage' chapter of the ASSET Radio User Reference Guide, including the speed,
efficiency and benefits involved in the creation and loading of files.
For information on the caching algorithm itself, see the 'Prediction and Array File Management
System' chapter in the ASSET Technical Reference Guide.
About the Web Maps Cache Folder
The cache folder that you have specified for Web Maps on the User Data Directories tab can be
shared between multiple users. Map data downloaded and processed by one user is then available
to other users. This sharing is appropriate if the cache folder is on a network and the same project
is used from different machines. In some cases, the cache folder can be shared between different
projects.
The cache folder should only be shared where these are identical for all the projects sharing it:
 The Map Data Extents
 The coordinate system projection EPSG
 The list of WMS services configured for the project
You must delete the contents of the cache folder if:
 The Map Data Extents of the owning project are altered
 The coordinate system projection EPSG is altered
 WMS Services are removed (deletion is not required if you only ever add services)
You can delete Individual files from the cache folder as required. This might be necessary in the
case of an error leading to an invalid file in the cache. Manual deletion avoids having to wait for the
natural expiry of the file.
27
ASSET User Reference Guide
About the Map Data Extents Tab
On the Map Data Extents tab of the project settings, click Calculate for ASSET to read the map
data and set the grid co-ordinates so that the whole of the mapped area can be viewed. An
automatic border of 5% is included.
This means that when the map is first opened, it will display the correct part of the world.
Tip: If the extents look incorrect, it is likely that erroneous points exist in one of the map data index
files.
If you require only a part of the mapped area, then these can be set manually to cover a smaller
area, by entering the grid co-ordinates of the extent of the map that you want to be visible in the
Map View window.
About the Region Load Tab
You can use the Region Load tab of the project settings to load only sites or nodes in a specified
region, which can be either a polygon or rectangle. By loading a subset of site data, ASSET can run
faster.
For information about how to load a region, see Loading a Subset of Project Data (Site Region
Load) on page 33.
About the Info Tab
You can use the Info tab of the project settings to add supplementary information about your
project.
This tab displays the time and date when the project was created and when it was last modified.
If required, you can enter a brief description of the project and any further comments related to it.
About the Simulation Distribution Tab
If you have ASSET Radio installed, the project settings will contain a Simulation Distribution tab.
On this tab, you set up the folders that will be used for storing distributed simulations. These make
use of extra processing power by enabling you to perform simulation snapshots on a collection of
networked PCs then merge the results.
For this to work, one computer (called the Server) will be running ASSET and will control all the
other computers. Multiple other computers (clients) will be either running ASSET or the ASSET
Radio Simulator Client Software.
The client computers process *.3gr files. They are loaded from the central location, visible to all the
Clients, snapshots are run on the files, then they are saved back to their original locations. The
server is used to set up what client computers are to be used, and what files are to be run.
To set up the folders for distributed simulations:
1. Ensure that you have the correct permissions to use distribution. If you do not, see your
administrator.
2. On the Simulation Distribution tab, specify a Distribution Folder. This folder is where
ASSET will store all *.3gr files used for distribution. The distribution clients will also pick up
their files from this location, so the folder needs to be accessible to all computers
participating in Distribution. For example:
28
Setting Up a Project
\\server\shared\ASSET_Distribution.
3. For each database user who is permitted to use Distribution, create a sub-folder under the
distribution folder, which has the same name as the database user. For example, if the
database user is demouser, the folder created in the distribution folder would be
\\server\share\ASSET_Distribution\demouser.
Note: The Use Distributed Sim Load option is also on this tab. It does not relate to the simulation
distribution referred to above, but to a separate function enabling the simulator to make use of
distributed array agents. This is a performance enhancing function that is enabled by default, but
which you can turn off by deselected this option if problems with it are encountered.
Exporting Project Settings
Having completed the project settings, you can export them for use in other projects.
To export project settings:
1. In the Project Settings dialog box, click the Export Settings button.
The XML Export dialog box appears:
2. Type or browse to the path of the folder where your exported file is to be kept.
3. Select the 'Project Settings' checkbox.
4. Click the Export button.
Your project settings xml file is exported to the specified folder.
Tip: You can also export project settings when you have a project open. To do this, from the File
menu, click View Project Settings, and then click the Export Settings button.
29
ASSET User Reference Guide
Importing Project Settings
If you have exported project settings as described above, you can import these settings into
another project.
To import project settings:
1. In the Project Settings dialog box, click the Import Settings button.
2. Click the Import button.
Assuming the Override Database Directory Settings checkbox* was not selected in the
Project Settings dialog box, a warning appears to inform you that you are about to
overwrite all project settings.
3. Click Yes.
The XML Import dialog box appears:
4. Type or browse to the path of the folder where your project settings xml file is kept.
5. Ensure the Project Settings checkbox is selected.
6. Click Import.
7. Click Close.
Your project settings are imported and will be visible on the tabs of the Project Settings
dialog box.
*If the Override Database Directory Settings checkbox was selected, you would instead
overwrite all the database overrides. If you accept, the database overrides are imported and will be
visible on the applicable tabs of the Project Settings dialog box. See Overriding Database
Directory Settings.
30
Setting Up a Project
Opening an Existing Project
When you have logged into a database, the Project Manager dialog box appears, showing any
projects that are currently available within the database.
Note: For information on how to create a new project, see Creating a New Project on page 20.
Projects are normally independent from each other. However, if, during project creation, you or your
administrator chose to share project data with another project, you will see a hierarchy in this dialog
box, with the project whose data is shared at the top level and the newer project as a sub-folder.
Only two levels are permitted.
This picture shows an example, with a mix of independent projects and shared projects:
Project Manager dialog box
To open an existing project:
1. In the Project Manager dialog box, select the project you require.
Note: If the project contains a large number of sites, and you have permission to do so,
you can choose to load only the sites within a specific area, rather than the whole project.
For information, see Loading a Subset of Project Data (Site Region Load) on page 33.
2. Ensure that you only include the item categories that you need to load. You can
significantly reduce loading time by excluding item categories (such as technologies) that
you do not need. For more information, see Defining the Project Load Options on page 32.
3. Click Start.
If the Start button is unavailable to you, contact your administrator to ensure you have the
correct permissions.
31
ASSET User Reference Guide
Defining the Project Load Options
Before you open a project, you should ensure that you only include the item categories that you
need to load. You can significantly reduce loading time by excluding item categories (such as
technologies) that you do not need. This is known as 'Partial Load'.
Most of the options are self-explanatory, but here are some specific notes about some of the
options:
 Neighbours: This will include/exclude all neighbours in the project, and all the associated
functionality such as wizards and analysis.
 Technologies: This will include/exclude specific technologies in the project. When a
technology is excluded, the tab for that technology will not appear on a multi-technology
cell, even if it is supported.
 Antenna Masks (Load on demand), Radio Masks (Load on demand) and User Defined
Fields (Load on demand):
These special options can achieve a faster project load time. This means that the relevant
data is not loaded upfront, but only when needed during the project session. This may incur
a time cost when you are working in the project, for example when clicking an object in the
Cellular Antennas dialog or the Site Database, respectively. Likewise, in the case of
antenna masks, the data would be loaded on demand when creating predictions, and the
field data would be loaded when editing/reporting fields or using filters with field-based
rules. But each time these data demands occur, it is only reduced sets of data that are
loaded (in contrast to the whole set). In addition, these sets are cached for the project
session. If you do not select these options, the whole set of mask data and/or field data will
be loaded.
Note: The MW Antenna Masks option is selected by default.
To select what is loaded:
1. In the Project Manager dialog box, in the Project Load Options pane, select which items
and technologies you want to load, as in this example:
The settings will persist after closing and reopening the project, unless you change them
again.
2. Click OK.
When you open the chosen project, only the selected item categories are loaded. Any that
you chose not to load will not be available in the project.
32
Setting Up a Project
Note: The title bar of the ASSET user interface will show 'Partial Load' to notify you that not all the
items or technologies are loaded.
Tip: To view the project load options after you have opened a project, from the File menu, click
View Project Load Options.
Loading a Subset of Project Data (Site Region Load)
If you have large numbers of sites in a project, you may want to load only sites in a specified
region, which can be either a polygon or rectangle. By loading a subset of site data, ASSET can run
faster.
For the implications of region loading, see How Region Loading Affects the Project on page 33.
When setting up a site region load for a project, you can use any of these methods:
Method 1 (recommended)
Summary: While the project is open, create the polygon in the usual way, within the normal Map
View window (or just use a polygon that already exists in your normal vector folders). Then, after
closing the project, specify that it is also to be used as the region load polygon.
This method has the significant benefit that you can visualise your sites/nodes in the normal 'open
project' Map View while viewing or creating the polygon.
For full instructions, see Setting Up Site Region Load Using Method 1 on page 34.
Method 2
Summary: While the project is closed, create a polygon within the Region Load Map View (this
polygon is exclusive to site region load and will not be stored in your normal vector folders.) With
this method, you cannot visualise your sites/nodes while creating the polygon.
For full instructions, see Setting Up Site Region Load Using Method 2 on page 36.
Method 3
Summary: While the project is closed, create a rectangle by specifying coordinates. With this
method, you cannot visualise your sites/nodes while creating the rectangle.
For full instructions, see Setting Up Site Region Load Using Method 3 on page 37.
Important: Whichever method you choose, there is one restriction: any polygon used for region
load must be a single polygon only (in other words, the vector must contain only one feature) and it
must be limited to a maximum of 100 points.
33
ASSET User Reference Guide
How Region Loading Affects the Project
When using region loading, each time you open the project, the title bar indicates that you have
'Region Load' in operation.
The project will contain:
 All 'Committed' network elements (sites, nodes, microwave links, and so on) that are inside
the region you have chosen
 All 'Committed' repeaters, and all their parent objects (sites, nodes, Properties, and so on)
regardless of the chosen region
 All 'Applied-only' network elements (sites, nodes, repeaters, microwave links, and so on)
relating to the individual user, regardless of the chosen region
 All hierarchical parent switches (such as MSCs, BSCs, WMSCs, RNCs, SGSNs, SAEGWs)
and their associated Properties, regardless of the chosen region
Where remote antennas are used, the project will contain:
 Any Properties (regardless of the chosen region) that contain an antenna that is used by a
cell that is located inside the chosen region
 Any Properties (regardless of the chosen region) that contain a cell that uses an antenna
that is located inside the chosen region
When region loading is active:
 Map data is not affected in any way. You can leave your map data extents as they are,
seeing map data for the whole country, while viewing only the subset of sites you have
loaded.
 You can still add sites to all areas or move sites outside the chosen region.
Setting Up Site Region Load Using Method 1
This section describes how to load a subset of project data using a polygon created in an open
project.
Tip: This is the recommended method, because you can visualise your sites/nodes in the normal
Map View window while creating the polygon.
To do this:
1. Visualise your sites/nodes in the normal Map View window.
2. Create your polygon in the usual way, or decide which existing polygon you want to use.
3. If the project is already open, close it.
4. In the Project Manager dialog box, select the appropriate project, and click
5. In the Project Settings dialog box, click on the Region Load tab.
34
.
Setting Up a Project
6. Select the 'Restrict Site Load to Region' checkbox:
7. Click
.
8. In the Map View window that appears, right-click and then click Properties.
9. From the Data Types list, choose what you want to display, for example any map layers or
vectors, and then click OK & Redraw.
Tip: If necessary, you can use zooming and panning options by right-clicking on the Map
View.
10. In the Map View window, click the Vector Editor button:
11. In the Vector Manager dialog box, select the required vector.
Note: Any system or user vector can be used, provided it consists of a single polygon with
no more than 100 points.
12. Right-click on the vector and select 'Copy to Regional Load polygon', as shown in this
example:
35
ASSET User Reference Guide
The polygon is displayed on the Regional Load Map View:
13. When you have finished, close the Map View window.
14. In the Project Settings dialog box, ensure that the 'Region Polygon' radio button is
selected, and it reads 'Polygon Defined':
15. Click OK.
16. In the Project Manager dialog box, click Start.
Setting Up Site Region Load Using Method 2
This section describes how to load a subset of project data using a polygon that you create within
the temporary Regional Load Map View, while the project is closed.
Note:
 This method does not enable you to visualise your sites/nodes while creating the polygon.
 A polygon created with this method is exclusive to site region load and will not be stored in
your normal vector folders.
To do this:
1. If the project is already open, close it.
2. In the Project Manager dialog box, select the appropriate project, and click
3. In the Project Settings dialog box, click on the Region Load tab.
4. Select the 'Restrict Site Load to Region' checkbox:
36
.
Setting Up a Project
5. Click
.
6. In the Map View window that appears, right-click and then click Properties.
7. From the Data Types list, choose what you want to display, for example any map layers or
vectors, and then click OK & Redraw.
8. In the Map View window, click the Create Polygon button
:
9. Click the start point and all subsequent points of the polygon (up to a maximum of 100).
Tip: You can use zooming and panning options at any time by right-clicking on the Map
View. You can continue making a polygon after panning, by clicking Cancel Pan. To undo
your polygon points and start again, press the Esc key.
10. To complete your region polygon, double-click at the final point of the polygon.
If you are not satisfied with your region polygon, either:
o
Click the Delete Polygon button
o
Click the Move Point button
required
and start again
, and then click and drag the points of your polygon as
11. When you have finished, close the Map View window.
12. In the Project Settings dialog box, ensure that you select the 'Region Polygon' option.
13. Click OK.
14. In the Project Manager dialog box, click Start.
Setting Up Site Region Load Using Method 3
This section describes how to load a sub-set of project data using the rectangle method (specifying
region coordinates).
To do this:
1. If the project is already open, close it.
2. In the Project Manager dialog box, select the appropriate project, and click
.
37
ASSET User Reference Guide
3. In the Project Settings dialog box, click on the Region Load tab.
4. Select the 'Restrict Site Load to Region' checkbox.
5. Select the 'Region Coordinates' option:
6. Use the Regional Load Map View to define the area:
o
Click
o
In the Map View window that appears, right-click and then click Properties.
o
From the Data Types list, choose what you want to display, such as map layers or
vectors, and then click OK & Redraw.
o
In the Map View window, right-click and you can then use the zoom and pan options to
help finalise your region.
o
When you have finished, close the Map View window.
.
The coordinates will appear automatically.
7. In the Project Settings dialog box, click OK.
8. In the Project Manager dialog box, click Start.
As an alternative, you can specify the Longitude/Latitude values manually.
Setting Up Your Preferences
Setting up your preferences is the next step after you have set up and opened a project, and before
you begin planning a network.
Warning: If you do not set your preferences properly, this may have a significant impact on your
whole network plan.
The tabs and items available depend on the products you have installed. If you use ASSET
Backhaul, you should also see the sections under 'Setting Your Preferences in ASSET Backhaul' in
the ASSET Backhaul User Reference Guide, where you can find ASSET Backhaul-specific
information about the ASSET Backhaul, Earth Radius and Diffraction tabs.
38
Setting Up a Project
To open this dialog box:
From the File menu, click Preferences.
This picture shows an example of the Preferences dialog box:
Preferences Dialog Box
Setting General Preferences
On the General tab of the Preferences dialog box, you can choose from the following options:
Item
Description
Power Preferences The field strength unit chosen here will be used throughout the project, for example, in the
cell powers in the Site Database, the Coverage schemas, the Map Information pane, the
Pixel Analyser, and so on.
If you choose dBm, the frequency is ignored for the purposes of field strength.
If you choose dBµV/m, the frequency becomes significant and you cannot plan for multiple
bands, for example, GSM 900/1800. If required, you can change the conversion formula for
dBµV/m (temporarily switch to dBm mode to do this).
Note: The most commonly used unit is dBm, therefore this is the default unit.
EMF Preferences
Select the required EMF units, dBV/m or dBmW/m2. The conversion formula is shown below
your selection.
39
ASSET User Reference Guide
Item
Description
Frequency Bands
(GSM)
Select this checkbox only if:

You use ILSA (the automatic frequency planning tool), and you want to enable
intermodulation analysis. (For more information, see the ILSA User Reference Guide.)

You want to delimit the carriers you can assign to a carrier layer, so that the carrier
layer's assigned carriers must be within the range of the corresponding frequency band.
(For more information, see 'Defining Carrier Layers' in the ASSET Radio User
Reference Guide.)
Ctrl Click Opens
You can enable quick access to a closed Site Database and/or Links Database. Normally,
when you click on a site or link in the Map View window, the appropriate element is
highlighted in the appropriate database window, if it is open. If you select these checkboxes,
you can do this even if the appropriate database window is closed, by holding down Ctrl
when you click on the element in the Map View.
FCC
Select the checkbox to activate FCC functionality in ASSET Radio. This will enable you to
view the Site Area Boundary for the FCC in the Map View window, as well as run the FCC
Reporting function.
Miscellaneous
Select the Refresh DB On Commit checkbox if you want your project to be automatically
updated with changes made by other users whenever you commit any objects. For
example, if another user has changed the address for a site and has committed it, and you
add a comment for that same site and commit it, you will see not only your comment but
also the changed address. For more information, see Using Refresh to Update Network
Elements on page 211.
Select the Prompt For New Template ID checkbox if you want to be prompted for a name
when creating templates from existing objects in the Site Database or Map View window.
Select the Log Refresh checkbox if you want the Message Log to record all refresh events.
Select the Prevent manual code changes if neighbour clashes arise checkbox if you use
BSICs (GSM) and/or scrambling codes (UMTS) and/or Physical Cell IDs (LTE) in your
project, and want to prevent manual changes in the Site Database that cause 1st or 2nd
order neighbour clashes.
Select the Prevent TCH or MA List allocations before BCCH allocation checkbox if, for a
2g network, you want to ensure that BCCH carrier allocations are a prerequisite for TCH
carrier allocations (this setting is controlled by user permissions).
Select the Retain no. of TRXs when switching from RF hopping checkbox if you want
the Carriers Required value automatically reset to match the TRX Required value on cells in
Site Database, when switching from synthesised or site hopping to baseband or nonhopping. Otherwise, the TRX Required value is automatically reset to match the Carriers
Required value. This is applicable to manual changes (including global edits) and XML
imports.
Select the Report elements in use checkbox if you want to activate detailed information in
the Message Log that explains why a user's action is blocked due to the action of another
user. You can also set a limit on the number of messages displayed. See Checking Blocked
Actions between Different Users on page 215.
For more information on the parameters affected by the above options, see the ASSET
Radio User Reference Guide.
Setting Earth Radius Preferences
On the Earth Radius tab of the Preferences dialog box, you can set the True Earth radius
(normally 6370 km) and the K factor value (normally 1.3333333), for various calculations
throughout the installed products.
The Effective Earth radius is then calculated for you automatically.
40
Setting Up a Project
Setting Network Preferences
On the Network tab of the Preferences dialog box:
 2G Parenting
If you want to activate automatic parenting when adding 2G network elements to the Map
View, select 'Parent 2G network elements in logical hierarchy'.
If you activate this automatic parenting, any BSCs you add on the Map View will be
parented to the nearest MSC, and any BTSs you add on the Map View will be parented
according to your choice:
o
The nearest BSC
o
The BSC of the nearest Distribution Node
Note: For all technologies in ASSET, network hierarchies are optional.
 2G Automatic Reparenting
If you use ASSET Backhaul, whenever you make or break a link on the Map View, you may
want the BTS-BSC parenting in the Site Database to be automatically updated to match
any changed linking relationships in the Link Database. If you do, select 'Check all BTSBSC parenting after making or breaking links, and reparent in Site Database if
necessary'.
Important: It is generally recommended that you do not activate this option, so that you
can maintain user control of the BTS-to-BSC parenting within the Site Database.
 Network Element Creation (Logical Links View)
If you want to be prompted for which Property to choose (existing or new) when you create
a network element in the Site Database, select 'When adding an element, prompt for a
new property'.
If you do this, each time you add a new element, you will see a Property Information dialog
box where you can choose to locate the element on any existing Property, or on a new
Property for which you can specify the coordinates.
This option is only relevant when:
o
The Site Database View mode is 'Logical Links'.
o
You are adding an element under a parent hierarchy (for example, adding a Site under
an existing BSC, or adding a NodeB under an existing RNC. (If you add an element by
right-clicking directly on the PLMN, this option is not relevant, because the Property
Information dialog box is mandatory in that case.)
41
ASSET User Reference Guide
Setting Technology Preferences
On the Technology tab of the Preferences dialog box:
You can control which technologies are visible in the project. To do this:
Select the technology type(s) you require to be active within the project. Choose from:
These options are always dependent on what licences you have.
In general, any combination of technology modes can be used in the same project. The only
exceptions to this is that GSM and PMR/TETRA/iDEN are mutually exclusive.
Note:
 With reference to the flexibility to model multiple technology MU-Nodes and Cells in ASSET
Radio, here is a clarification of when they should be visible in the application:
o
Any 'Fixed' MU-Node or Cell that is set to a technology that is OFF in the technology
preferences will NOT be visible.
o
A 'Variable MU-Node or Cell that does NOT support at least one of the technologies
that is ON in the preferences will NOT be visible. The only exception is if it supports no
technologies, in which case it must be visible.
For information on the multiple technology flexibility, see 'Configuring Networks in ASSET'
chapter in the ASSET Radio User Reference Guide.
 You can edit the technology preferences at any time while the project is open, but not while
any configuration data dialog boxes (such as bearers, services and so on) are open.
Setting Diffraction Preferences
On the Diffraction tab of the Preferences dialog box, select the diffraction model that will be used
in the height profile and link availability calculations.
For detailed information on the different options, see the 'Antenna and Diffraction Calculations'
chapter of the ASSET Technical Reference Guide.
42
Setting Up a Project
Setting Candidate Options Preferences
In ASSET, a nominal Property is a Property placed in an approximate location, that you can use as
a way of indicating that you need a site somewhere near this area. Using the search area of the
nominal Property, you define the radius that you consider as suitable for your new Property. In this
search area, you can place a number of other Properties – called candidates - that are possible
alternative locations for the new site.
On the Candidate Options tab of the Preferences dialog box, you can set up a number of
candidate-related preferences.
This picture shows the parameters on this tab:
Candidate Options tab of the Preferences dialog box
You can:
 Enable candidate functionality. This will apply to any search areas you create after
selecting this option, but will not affect any existing search areas you may have defined.
 In the Automate pane:
Select
To
Candidate Status
Apply candidate status to any new Properties that you create inside
an existing search area.
Renaming
Rename any candidates (when they are created) with the same name
as the nominal, plus a letter suffix (for example "Property99_A").
Note: If the Property's candidate status is subsequently removed, the
Property will revert to its original name.
Capturing candidates
Add candidate status to Properties when you enlarge the search area
to include them, or remove candidate status from Properties that no
longer fall into a reduced search area.
Not selecting this option means that when you resize a search area
the numbers of candidates remains the same.
43
ASSET User Reference Guide
 In the Candidate Restrictions pane, select whether you can move the candidates
anywhere, move them into and within the search area, or not move them at all.
 In the candidate's BTS Equipment pane, select whether you want:
o
The candidate's existing equipment to remain the same
o
The candidate's existing equipment to be removed and replaced with the nominals
o
The candidate's existing equipment to be added to with the equipment from the
nominal
For more information on using candidates and nominals, see Using Nominal and Candidate
Properties on page 387.
Setting Filter and History Preferences
On the Filters tab of the Preferences dialog box, you can:
 Choose the view you require whenever filters are displayed:
The first and second options offer a basic choice between showing only your own user
filters or all user filters.
The third option is more flexible, because it enables you to show a restricted set of user
filter folders, based on group membership and/or individually selected users.
To use this option, select the third radio button and then:
a. Click the Configure button to open a new dialog box.
b. In the Groups list, select the required groups
- and/or In the Users list, select the required individual users
Note: The lists exclude the default All group, and the current user.
c. Click OK.
The resulting user filter folders visible in the user interface (Filters dialog, Map View, Site
Database, and so on) will be restricted to those relating to members of your selected
groups, and/or your individually selected users.
 Opt to only show active antennas in the Site Database:
By default, on the Antenna tab at the cell level, all available logical antennas are shown,
that is, both active (assigned) and inactive (unassigned) antennas. However, if you want to
show only the active antennas, you can select the above option. Some users prefer this so
that they can easily see the logical antenna(s) that the cell is connected to.
44
Setting Up a Project
 Opt to have History details displayed on the History tabs in the Site Database
automatically, rather than having to click the Show History button on the tab.
For more information about viewing history details, see 'About the History Tab' in the
ASSET Radio User Reference Guide.
For information on activating the history, see 'Using Version History' in the ASSET
Installation and Administration Guide.
 Choose if you want to save created or modified objects from recent imports (from XML
Import and Grid Data Loader) into the Selection Filter automatically.
For more information, see Saving the Contents of an Import into the Selection Filter on
page 305.
Setting Electrical Tilts Preferences
On the Electrical Tilts tab of the Preferences dialog box, you can choose the way that you want
your show antenna patterns to be displayed when using the 'Electrical Tilt' drop-down list on the
Logical Antennas tab of a Property.
Note: This option is only applicable to Passive antennas, not Switched Beam antennas.
The basic choice is between showing:
 All the tilt values of all the patterns parented to the device. This option allows two different
sorting options.
- or  Only the tilt values belonging to patterns parented to the device that have the same
frequency as the currently assigned pattern.
The impact is on what you see in the drop-down list on the Logical Antennas tab of a Property.
The examples below help to explain this:
45
ASSET User Reference Guide
 Example of showing all the tilt values of all the patterns parented to the device:
 Example of showing only the tilt values that have the same frequency as the currently
assigned pattern:
Note that even if you choose to use the frequency-restricted option, you can still see all the
patterns (and assign any of them) if you click on the 'Pattern ID' drop-down list:
Enabling or Disabling Large Array Support within a Project
If you frequently create large arrays, you can take advantage of the large array support provided in
ASSET. This is applicable to all types of array, for example: simulation arrays,
coverage/interference arrays, traffic arrays, and height or clutter rasters.
ASSET enables you to enable support for large arrays on the local machine. The process uses a
swapping system, in which a swap folder is used to store the temporary files when more memory is
required. This can significantly increase the RAM available for array creation.
For information on how to access and set up the Large Array Settings dialog box, see 'Allowing
Large Array Support on a Machine' in the ASSET Installation and Administration Guide.
For an individual project, you can enable or disable the large array support swapping system
process, and also override the process memory reserved defaults.
46
Setting Up a Project
To do this:
1. Ensure that Large Array Support has been allowed (as referenced above) and then open
the relevant project.
2. From the File menu, click Swapping Manager. The Swapping System Manager dialog
box appears:
3. Use the checkbox to enable or disable the swapping system process for the project, as
required
4. You can override the process memory reserved value for the project here, if necessary.
The default is based on the values in the Large Array Settings dialog box.
Note: The maximum memory in the Large Array Settings dialog box determines the
absolute limit in most circumstances. However, in exceptional circumstances, the specified
limit can be automatically extended to a higher value, which is a calculated optimum for the
task in progress. When this happens, the higher value is reported in the Message Log, and
it remains active within the project session.
5. Click OK.
Warning: It is strongly recommended to turn off Large Array Support when not creating large
arrays. This is because it consumes a large amount of memory, and can be detrimental to the
general performance of ASSET. It is therefore recommended to only enable the feature when
required. You can contact Product Support for further advice.
47
ASSET User Reference Guide
Defining the Site Database Settings
To change how the Site Database window displays network elements, from the Tools menu of the
Site Database, click Options. The Site Database Settings dialog box appears:
Site Database Settings Dialog Box
 The 'Display Options' radio buttons enable you to choose which identifier is shown next to
each type of network element in the left pane of the Site Database window.
 The 'Network Display Mode' radio buttons enable you to choose how to show the list of
network elements in the Site Database. The modes are listed here:
Display mode
Description
Logical Links View
This shows the network elements listed as a hierarchical list under
the appropriate PLMN.
Physical Links View
This shows a list of Properties, showing how each of them are
physically linked if you use ASSET Backhaul.
Location View
This shows a list of Properties (locations), and shows the network
elements at each of those locations.
Network View
This shows the network elements listed (regardless of hierarchies)
under the appropriate PLMN or logical network
Cell-Antenna View
This shows the Properties (locations) containing the antennas from
which each cell is physically transmitting. These locations may be the
same as or different from the location of the cell.
For example images of the above display modes, see Choosing the View in the Site
Database on page 226.
Tip: You can also change the display mode from the View menu in the Site Database.
 The 'Antenna Pattern Sort Options' radio buttons enable you to determine how you want
the antenna patterns to be sorted in the drop-down list that appears on the Logical
Antennas tab for a Property in the Site Database.
48
Setting Up a Project
The options are as follows listed here:
Sort by
Parameter (from Cellular Antennas dialog box)
Pattern Name
Pattern ID as specified on General tab
Pattern Electrical Tilt
Elec. Downtilt as specified on Mask tab
Pattern Frequency
Frequency as specified on Info tab
Azimuth Offset
Azimuth Offset as specified on Mask tab
Customising the Object Count in the Site Database
When you are viewing the Site Database, you can see the object count at the bottom of the left
pane:
Example of Object Count in Site Database
These counts are influenced by which technologies are currently enabled in the project, which filter
is currently selected in the Site Database, and which Network Display Mode is being used.
The default object count represents the number of:
 Properties (all technologies)
 Sites/Nodes (all technologies)
 Cells (all technologies)
However, if required, you can customise this display, to show the count for other network elements
or objects such as:
 Networks
 MSCs, BSCs, RNCs, SAEGWs and so on
 Sites/Nodes/Cells/Repeaters (technology-specific)
 Logical nodes
 Logical and cellular connections
 Antenna devices (the number of antennas specified at Node level, or Cell level for GSM,
irrespective of them being used by the cells)
To do this:
1. At the bottom of the left pane of the Site Database, click the
button.
2. In the Custom Object Count Configuration dialog box that appears, select or deselect
the items you require using the Left or Right arrow buttons.
49
ASSET User Reference Guide
Here is an example:
The maximum you can select is 10 items.
3. Use the Up or Down buttons to modify the display sequence.
4. Click OK.
The object counts appear at the bottom of the left pane in the Site Database, according to your
configuration.
Tip: If necessary, you can resize the Site Database horizontally by dragging the left bar or the right
bar. You can do this whether it is in collapsed mode (left pane only) or expanded mode (both left
and right pane).
Defining the Map View Options
Before you start to use the Map View window to model your network, you can define certain
options which will determine how you will use the Map View. For example, you can specify which
template is used each time you add a particular network element.
To set the options:
In the Map View window, from the Tools menu, click Options.
The Tool Options dialog box appears.
Tip: You can leave this dialog box open while you are working.
The tabs are described below:
 Selection tab
On the Selection tab, you can choose which network elements you want to be
included/excluded when you use the Selection Expert
options in the Map View. For
more information, see Choosing Which Types of Network Elements are Added to the
Selection Filter on page 296.
 Add Element tab
50
Setting Up a Project
On the Add Element tab, you can select which template is used when you add a particular
type of network element:
o
In the Object Type drop-down list, select the network element type
o
In the Template drop-down list, select the template that you want to be active when
you add this network element type
o
In the Property drop-down list, select the Property template that you want to be active
in the event of a new Property being required (only active when applicable)
Note: The Templates dialog box (under the Database menu) is automatically updated
with the new default. Therefore the same default will also operate when elements are
added in the Site Database.
For more information, see Adding Network Elements with a Selected Template on page 89.
 Best Server tab
On the Best Server tab, you can select a particular array. Based on your choice, when you
click on any pixel within that array in the Map View Window, the best serving cell is
highlighted in the Site Database (as long as the Site Database window is open). For more
information, see Using the Map View to Find Elements in Site Database on page 229.
Note: The options you choose are always saved when you close this dialog box, and will be
persisted in future sessions.
About the New Project Default Objects
In order to make a new ASSET project easy to use right from the start, the following default objects,
with pre-set parameters, are provided:
 Antenna default
 Propagation model defaults (450, 900, 1800 and 2100MHz)
 Template defaults (for each technology)
 Terminal type default (for each technology)
These default objects represent the minimum parameters required to add/place sites and generate
coverage arrays in ASSET Radio. The default templates include sites (nodes) and cells (sectors)
that in turn make use of the default propagation models and antenna.
Note: These defaults are only present when new projects are added in ASSET. Existing projects
will not have these defaults created.
51
ASSET User Reference Guide
52
About the Core User Interface
3 About the Core User Interface
This chapter describes the main user interface parts common to products in the ASSET suite.
About the Tabs and Main Menu
When you start ASSET, at the top of the screen, you can see the project name, the database
source name and the user name.
There is also a set of tabs. Each tab corresponds to an ASSET product, according to what is
licensed and installed, such as RADIO (for ASSET Radio) and BACKHAUL (for ASSET Backhaul).
There is also a Utilities tab.
The main menu options (such as File, View, Database, Equipment, Tools) appear under each
tab. Some of these menu options are the same for each product, but some options are productspecific.
The rest of the ASSET display is transparent, so your desktop is visible beneath the menus.
About the Main Toolbar in ASSET
You can access the core functionality of ASSET from the main toolbar, shown here:
Main toolbar: ASSET Radio is accessed by the 'RADIO' tab; ASSET Backhaul is accessed by the
'BACKHAUL' tab
The above picture shows the toolbar relating to ASSET Radio. The toolbar relating to ASSET
Backhaul is only slightly different.
Most of the buttons on the toolbar relate to the core functionality of the ASSET suite, and are
described here in this ASSET User Reference Guide. But some are described in the productspecific user guide for ASSET Radio or ASSET Backhaul.
For ease of reference, this table briefly describes the function of each button, and where to look for
more information:
Button
Function
Described in
Closes the ASSET software.
Log In to the database.
Logging In to a Database on page 17.
Log Out of the database.
Open a project (button only active
after you have closed a project).
Opening an Existing Project on page 31.
Close a project (but leaves you
logged in to the database).
53
ASSET User Reference Guide
Button
Function
Described in
Open a new Map View window
(multiple views can be open).
Viewing and Editing Networks on the Map on page 81.
Opens Site Database window.
ASSET User Reference Guide (for general
functionality).
ASSET Radio User Reference Guide (for technologyspecific parameters).
Opens Link Database window in
ASSET Backhaul.
ASSET Backhaul User Reference Guide.
Opens Pathloss Prediction Generator ASSET Radio User Reference Guide.
in ASSET Radio.
Opens Filter Database dialog box.
Using Filters in ASSET on page 275.
Opens Selection Expert dialog box.
About the Selection Expert and Selection Filter on
page 294.
Opens the Site Database Site
Database Reports dialog box in
ASSET Radio.
ASSET Radio User Reference Guide.
ASSET Backhaul User Reference Guide.
Opens the Search dialog box.
Locates equipment, links and network
elements in ASSET Backhaul.
Opens Wastebasket
About the Wastebasket on page 76.
Opens a menu from which you can
select the Workspaces dialog box (to
maintain Workspaces) or quick
access links to Workspaces that you
have created.
About Workspaces on page 55.
Launches ASSET Design.
ASSET Radio User Reference Guide.
Launches the Design Wizard Setup
Manager.
ASSET Radio User Reference Guide.
Launches ASSET Capacity.
ASSET Radio User Reference Guide.
About the Core Windows
A number of windows are common to products in the ASSET suite and they are described in the
following sections.
Note: If you close a project with any of these windows open, the windows will be opened
automatically in the same position when you next open the project.
54
About the Core User Interface
Displaying and Hiding Windows
In ASSET, all currently open windows are listed under the Windows menu item, as in this example:
If you have a number of windows open, with some of them hidden or overlapping, you can bring a
required window into focus at the front. This is also useful when you have minimised a window and
you want to maximise it.
To bring a window to the front or maximise it:
1. On the main menu, click Windows.
2. Click the required item in the displayed list, such as Site Database, 2D View, or Message
Log.
The chosen window is brought to the front or maximised, as appropriate.
To see a list of all currently open windows:
1. On the main menu, click Windows.
2. From the list that appears, click the Windows... option.
3. A dialog box appears, listing the windows that are currently open:
To close an unwanted window:
1. Repeat as above.
2. Select the required item and click Close Window.
(The Activate button is just another way of bringing a window to the front or maximising it.)
Tip: You can save a commonly-used layout of windows and dialog boxes as a workspace, which
can be easily loaded at any time. See About Workspaces on page 55.
55
ASSET User Reference Guide
About Workspaces
A workspace is a personalised combination of windows and dialog boxes that you use regularly,
organised on the screen in a convenient layout that is saved for future use. This means you can
easily load your required screen layout at any time. You can create any number of workspaces.
There are already two default workspaces available to you:
 Default Workspace, which includes the Layer Control Pane, Site Database (under the Layer
Control Pane), Map View, and Message Log
 Default Workspace (Backhaul), which includes the Link Database, Map View, and Message
Log
Notes:
 Workspaces can save the displayed contents (such as filters, vectors, heights) of the Map
View windows, as well as the region.
 Workspaces can save multiple Map View windows.
 The workspace remembers which filter is active in other windows, such as the Site
Database.
 Workspaces cannot be shared across machines, databases, projects or users.
 Workspaces created from the RADIO tab are maintained separately from those created on
the BACKHAUL tab. Workspaces can only be accessed from the tab on which they were
created.
Tip: In the specific context of the Map View window, you can also use Favourite Views. Here is a
quick comparison:
 Use Favourite Views if you are only working with the Map View window. Additionally, in
the case of System Favourites, you can share them with other users of the project. See
About Favourite Map Views on page 101.
 Use Workspaces when you want to personalise the layout and positioning of several
dialog boxes, optionally including the Map View.
Creating Workspaces
A workspace is a personalised combination of windows and dialog boxes that you use regularly,
organised on the screen in a convenient layout.
You can easily load your required screen layout at any time by clicking the workspace button
and then selecting the required workspace. You can create any number of workspaces.
Tip: There is already a Default Workspace available from the Workspaces button on the RADIO
tab, and a Default Workspace (Backhaul) available from the workspace button on the BACKHAUL
tab. Workspaces that you create are available from the workspace button on the tab under which
you created them.
56
About the Core User Interface
To create a workspace:
1. Ensure that all of the required windows and dialog boxes are arranged in your preferred
positions. Here is an example:
2. On the RADIO or the BACKHAUL toolbar, click the Workspaces button
the Workspaces... option.
, then click
57
ASSET User Reference Guide
The Workspaces dialog box appears, as in this example:
3. To save this set of windows as a workspace, click Save As.
4. In the dialog box that appears, type a name (and if required, a description) for the
workspace:
5. Click OK.
The layout is saved as a workspace, and appears in the Workspaces dialog box:
58
About the Core User Interface
6. For any of the workspaces, you can select the Quick Access option. This will make them
immediately accessible in a list under the toolbar when you click the
button:
For information on loading, modifying, renaming and deleting workspaces, see Managing
Workspaces on page 59.
Notes:
 Workspaces can save the displayed contents (such as filters, vectors, heights) of the Map
View windows, as well as the region.
 Workspaces can save multiple Map View windows.
 The workspace remembers which filter is active in other windows, such as the Site
Database.
 Workspaces cannot be shared across machines, databases, projects or users.
Managing Workspaces
After you have created workspaces (as described in the previous topic), you can use the
Workspaces dialog box to manage them. Workspaces that you have created are available from
the Workspaces button on the tab under which you created them.
You can:
 Load workspaces
 Modify workspaces
 Rename workspaces
 Delete workspaces
To load a workspace:
If you assigned the 'Quick Access' option to the workspace (see About Workspaces on page 55),
you can immediately access it from a list under the toolbar when you click the
example:
button. For
Alternatively, you can load any of your workspaces as follows:
1. On the RADIO or the BACKHAUL toolbar, click the Workspaces button, then click the
Workspaces... option.
The Workspaces dialog box appears.
2. Select the workspace that you want to load.
59
ASSET User Reference Guide
3. Click Load.
Any windows that are already open are closed, and the requested workspace is loaded.
4. Close the Workspaces dialog box.
To modify a workspace:
1. Ensure that the required workspace is already loaded (using either method described
above).
2. Make the required layout changes - for example, add or remove windows, or re-position the
windows.
3. Click the Workspaces button and then click the Workspaces... option to open the
Workspaces dialog box.
4. Select the appropriate workspace.
5. Click Save.
The changes to the workspace are saved.
To rename a workspace:
1. Select the workspace that you want to rename.
2. Click Rename:
3. In the Enter Workspace Details dialog box that appears, specify the new name for the
workspace and add any description required.
4. Click OK.
The workspace details are updated in the Workspaces dialog box.
To delete a workspace:
1. Select the workspace that you want to delete.
2. Click Delete:
The workspace is immediately deleted.
About the Site Database Window
Use the Site Database window to view and edit the attributes of all your network elements within
the ASSET database.
60
About the Core User Interface
The left pane contains your network hierarchy and when you select an item in this pane, related
information appears in the right pane. The information changes depending on your selection. This
picture shows an example:
Site Database Window showing parameter information for selected item
Note: If required, you can maximise the Site Database window, or you can extend the right edge
outwards or the bottom edge downwards. If you extend it outwards, this enables you to use the
splitter bar in the middle to adjust the relative size of the left and right panes. When you close and
reopen the window, or the project, the window's size and position will be remembered.
In the left pane:
 You can use the Filter box to ensure that all or a subset of data is displayed. All the items
present in the filter selected in the Filter box are listed in the left pane.
When you close or reopen the Site Database window, or the project, the last selected filter
will be remembered.
 You can use the Find box to search for a site containing a particular substring. For
example, you could type Site77 and all elements with Site77 in their name will be displayed
in the drop-down list.
- or If you know the full name of the element you are searching for, type the name in the Find
box and click the Find button.
 Items marked with an asterisk (*) indicate that the item has been modified, but that the
changes have been Applied but not Committed.
 You can display the list of network elements according to your preferred view. See
Choosing the View in the Site Database on page 226.
 You can use a number of keyboard shortcuts when viewing and selecting items.
For more information, see Viewing and Editing the Site Database on page 221.
61
ASSET User Reference Guide
About the Keyboard Shortcuts in the Site Database Window
This table describes the shortcuts available in the Site Database:
Item
Description
Up arrow
Moves up to the next visible level in the hierarchy (for example, from cell level to site
level).
Down arrow
Moves down to the next visible level in the hierarchy (for example, from Property level
to site level).
Left arrow
Contracts the selected element to the parent level (for example, from a cell to its site).
Right arrow
Expands the selected element by one level (for example, from a site to its sub-cell).
About the Buttons on the Site Database Window
This table describes the functions of the buttons that appear on the expanded Site Database
window (unless you logged in as a Sandbox user):
Click
To
>> or <<
Show or hide the right hand side of the Site Database window.
Apply
Apply a change you have made only to your own account, that is, the change can only
be seen by yourself. For more information on Applying elements, see Saving Your
Changes to the Database on page 205.
Commit
Copy your change to the database, and therefore make it available to everyone.
Before using Commit, you need to have clicked Apply. For more information on
Committing elements, see Saving Your Changes to the Database on page 205.
Restore
Remove a change that you have Applied and revert to using the master database
settings, getting the latest Committed version of that object.
Restore only works if there is a version of the object already Committed to the
database. If you have created a new object and want to remove it, you should delete it.
Commit All
Copy all your changes to the database in one action, and therefore make them
available to everyone. Before using Commit All, you need to have clicked Apply for
each change you made.
Note: If there is nothing to Commit when you click Commit All, a dialog box will appear
telling you that there is nothing left to Commit.
Restore All
Delete all changes that you have Applied and revert to using the master database
settings, getting the latest Committed version of the items marked with an asterisk.
Note: If there is nothing to Restore when you click Restore All, a dialog box will appear
telling you that there is nothing left to Restore.
Global Edit
62
Open the Global Editor, for when you want to change all network elements identified
by a filter. For more information on using the Global Editor, see Making Global
Changes to Network Elements on page 246.
About the Core User Interface
About the Buttons in Sandboxes
This table describes the functions of the buttons that appear on the expanded Site Database,
Logical/Cellular Connection Database, and Link Database windows if you logged in to a
Sandbox:
Click
To
>> or <<
Show or hide the right hand side of the Site Database window.
Apply
Apply a change you have made to the Sandbox account. The change can only be
seen by yourself and the other users of this Sandbox. For more information on
Applying Sandbox elements, see Saving Sandbox Changes to the Database on page
213.
Commit
Copy your change to the database and therefore make it available to everyone,
whether they are users of this Sandbox or not.
Before using Commit, you need to have clicked Apply. For more information on
Committing Sandbox elements, see Saving Sandbox Changes to the Database on
page 213.
To use Commit, you must have been granted the Sandbox Commit/Restore functional
privilege by your administrator. For more information see the ASSET Installation and
Administration Guide.
Restore
Remove a change that you have Applied to the Sandbox and revert to using the
master database settings, getting the latest Committed version of that object.
Restore only works if there is a version of the object already Committed to the
database. If you have created a new object and want to remove it, you should delete it.
To use Restore, you must have been granted the Sandbox Commit/Restore functional
privilege by your administrator. For more information see the ASSET Installation and
Administration Guide.
Commit All
Copy all your Sandbox changes to the database in one action, and therefore make
them available to everyone. Before using Commit All, you need to have clicked Apply
for each change you made.
Note: If there is nothing to Commit when you click Commit All, a dialog box will appear
telling you that there is nothing left to Commit.
Restore All
Delete all changes that you have Applied to the Sandbox and revert to using the
master database settings, getting the latest Committed version of the items marked
with an asterisk.
Note: If there is nothing to Restore when you click Restore All, a dialog box will appear
telling you that there is nothing left to Restore.
Global Edit
Open the Global Editor, for when you want to change all network elements identified
by a filter. For more information on using the Global Editor, see Making Global
Changes to Network Elements on page 246.
About the Context Sensitive Menus in the Site Database Window
In the Site Database window, you can access commonly-used functions via context sensitive
menus, depending on:
 The view you have chosen in the Site Database Settings dialog box. For example, if you
choose to display Logical Links, you cannot cut paste and copy items in the Site Database
window.
 Which network element, if any, is selected in the left-hand pane.
To access context sensitive menus, right-click a network element.
63
ASSET User Reference Guide
About the Core Map View Window
The Map View window is a fundamental part of the ASSET suite in which you can view the different
data sets available within ASSET, including site data, connectivity and mapping data.
The Map View window and Site Database window are fully synchronised so that changes you
make in one are reflected in the other. In addition, when you click a network element on the map,
any open Site Database window will update dynamically to display that item.
At the left of the Map View window is the Layer Control Pane which has three tabs, Layer Order,
Legend and Data Types.
This picture shows an example of the Map View window:
Example Map View window
Notes:
 You can have multiple Map View windows open at the same time. To help distinguish them,
the title bar of each one will show "2D View - 1", "2D View - 2", and so on, representing the
order in which they were opened. In a new session (after closing and reopening the
project), the numbering will restart from "1".
 You can choose between the default Single View and the Tiled View. Using the Tiled View
you can see up to four maps within one window for comparison, or you can combine maps
with the Pixel Analyser and/or Graphs. For more information, see Using the Tiled View on
page 85.
About the Map View's Toolbar
This toolbar extends along the left edge and the top of the Map View.
Note: The toolbars and buttons that you see are always dependent on the products you have
installed. For specific information, see the relevant User Reference Guide.
64
About the Core User Interface
This table describes the tools available on the Map View toolbar:
Tool
Description
Individual object selection. Enables you to select any network element in the Map
View, and locate it automatically in the Site Database. This button is also useful
for deactivating any previously selected options (such as Zoom).
Selection Filter toolbox. For more information, see Adding to the Selection Filter
Using the Map View Window on page 295.
Clear the contents of the Selection Filter.
Distance toolbox. See About the Distance Measurement Toolbox.
Zooming options. See About the Zoom Options.
Quick Finder. See Searching the Map View Window with the Quick Finder on
page 106.
Jump to Location. See Using Jump To Location on page 108.
Display Site Tips. See Viewing Attribute Data as Site Tips on page 203.
Site Quick Edit. See 'Quickly Viewing and Editing Site or Cell Information' in the
ASSET Radio User Reference Guide.
Cell Quick Edit. See 'Quickly Viewing and Editing Site or Cell Information' in the
ASSET Radio User Reference Guide.
Show the Map Information pane. See About the Map Information Pane on page
71.
Create Arrays. See 'Creating Signal Coverage Arrays' in the section for the
required technology in the ASSET Radio User Reference Guide.
Launch the Simulator Wizard. See 'Using the Simulator Wizard' in the ASSET
Radio User Reference Guide.
Pixel Analyser mode. See About the Pixel Analyser on page 149.
Pixel select mode. See About the Pixel Analyser on page 149.
Launch ASSET Geo (if licensed). For more information, see the ASSET Geo User
Reference Guide.
Use the Vector Manager to create and manage vector file features. See About the
Vector Manager on page 251.
Use the Add Network Element toolbox to add Properties, and elements such as
sites and nodes.
Use the Move/Edit Network Element toolbox to move Properties, elements and
antennas. There is also a cloning option.
Use the Delete Network Element toolbox to delete Properties and elements such
as sites and nodes.
Use the Cell Associations toolbox to add and display neighbour relationships and
exceptions. Also displays carrier assignments.
Use the Candidate toolbox to make and break candidate relationships of a
Nominal Property, and show the candidates. Also sets, cancels and shows
Search Area.
65
ASSET User Reference Guide
Tool
Description
Use the Link toolbox to add or delete links, hubs and connections between
Properties.
You can add logical and cellular connections. There is also a 'Site Visibility' tool.
Favourite views. See About Favourite Map Views on page 101.
Switches between Single view and Tiled View.
Switches tile synchronisation on and off. It is on by default, and when it is on, any
panning or zooming of the selected tile is applied to all Map View tiles.
For information on panning around the Map View, see Repositioning (Panning) the Map on page
100.
Tip: For some of the above buttons, such as the Zooming options, you remain in that mode until
you press the Esc key or click the
button.
About the Distance Measurement Toolbox
The Distance Measurement toolbox contains the following buttons:
Distance Measurement Toolbox
This table describes the buttons:
This Button Enables You To
Measure the distances between points on a line, and the total length of the line.
Note: In the Map View, two connected points are referred to as a shape. One or more
(connected) shapes form a feature. More than one feature can be saved as one vector.
Click on the Map View to mark the first point. Drag and click to add further connected points.
Double-click to terminate the current line.
Show the coordinates of a point.
Click on the Map View to add a point.
Measure the size of an area.
Click on the Map View to establish the first point. Drag and click to add further points.
Double-click to close the area by automatically connecting the last point to the first.
66
About the Core User Interface
This Button Enables You To
Change the display properties of the tools described above:
In the Point pane, select the Point option to display points created by the point tool. In the
adjacent Coordinate Display pane, select what sort of coordinates are to be used.
In the Distance pane, select the Point, Shape Length and Feature Length options as
required to display the points, distances between points and total distance between first and
last points along the line created by the distance tool.
In the adjacent Coordinate Display pane, select what sort of coordinates are to be used.
In the Area pane, select the Point, Shape Length and Feature Length options as required to
display the points, distances between points, total distance of the area perimeter and the size
of the area created by the area tool.
In the adjacent Coordinate Display pane, select what sort of coordinates are to be used.
In the Coordinate Font pane, select the font, size and colour of the text and the background
colour to be used for the coordinate labels.
In the Shape Length Font pane, select the font, size and colour of the text and the
background colour to be used for the labels of distances between points.
In the Feature Length Font pane, select the font, size and colour of the text and the
background colour to be used for the labels of total distance.
In the Feature Area Font pane, select the font, size and colour of the text and the
background colour to be used for the area size labels.
Tracking cursor. This displays the coordinates as you move the cursor.
It may be useful to activate the tracking cursor when adding or moving network elements and
when moving or re-orientating antennas. You can also use it with the Map Grid and Pixel
Analyser.
You can switch it on and off by clicking the button or by pressing the F10 key.
Tips:
 If you want to enable panning while you are in one of the above modes, you need to press
the 'Ctrl' key.
 When you use a tool from the Distance Measurement toolbox in the Map View, it is shown
on the Map View only as long as the tool is selected. When you select another tool, the
lines, points or areas and their labels created with the first tool are lost. If you wish to
preserve the information displayed by these tools, you can do so by saving it as a vector
using the Vector Manager option from the Map View Tools menu. You can save multiple
points, lines and areas as a single vector. For more information on creating vectors, see
About the Vector Manager on page 251.
About the Zoom Options
There are various zooming options that you can use on the Map View window. These are available
as buttons on the Map View toolbar:
Zooming options on Map View toolbar
This table describes the buttons:
Button
Name
Brief Description
Zoom to point
Zoom In or Zoom Out at any point on the Map View. After clicking the
button, you can repeatedly left-click to zoom in and right-click to zoom out.
Tip: You can also use the mouse-wheel to zoom in and out.
67
ASSET User Reference Guide
Button
Name
Brief Description
Zoom from corner
Zoom from the corner of your initial mouse click (in any direction).
Zoom from centre
Zoom from the centre of your initial mouse click. Enables you to zoom to
the extent of a rectangle that you draw on the Map View.
Zoom to scale
This provides a list of scaling options.
Zoom to filters
Zoom to the network elements that are included in the currently selected
Filters in the Layer Control dialog box.
Zoom to filters
including radius
Zoom to the network elements that are included in the currently selected
Filters in the Layer Control Pane. The zoom level takes account of the
primary prediction radius that has been assigned to the relevant cells and
repeaters, or the global override setting (if selected) on the Predictions tab
of the Array Settings dialog box.
For more detailed information, see Zooming, Moving and Redrawing the Map on page 98.
Tips:
 The zoom options remain active until you press the Esc key or click the
button.
 If you intend to zoom into an area, it can help reduce memory resources if you start by only
displaying basic line data, such as coastline or roads. Once you are zoomed in, you can
then display layers such as heights and clutter data.
About the Add Network Element Toolbox
The Add Network Element toolbox contains buttons that enable you to use the Map View window
to add elements to the Site Database. Here is an example of the toolbox, which depends on your
technology licences:
Add Network Elements Toolbox
The network element buttons vary in colour and appearance, according to which technologies you
are using.
Tip: You can hover the cursor over each button to see which function it performs.
For information on each of the buttons, see 'About the ASSET Radio User Interface' section in the
ASSET Radio User Reference Guide.
68
About the Core User Interface
About the Move/Edit Network Element Toolbox
Immediately to the right of the Add Network Element toolbox is the Move/Edit Network Element
toolbox, which contains several useful buttons:
Move/Edit Network Elements Toolbox
This table shows the buttons in this toolbox:
This Button
Enables You To
Move a Network Element.
Move an Antenna.
Re-orientate an Antenna.
Move a Cell.
Move a Property.
Clone a Network Element.
The toolbars and buttons that you see are always dependent on the products you have installed.
For specific information, see the relevant User Reference Guide.
About the Cell Associations Toolbox
The Cell Associations toolbox contains the following buttons:
Cell Associations Toolbox
This table describes the buttons:
This Button
Enables You To
Add a Neighbour Cell.
Display Neighbours.
Add an Exception Cell.
69
ASSET User Reference Guide
This Button
Enables You To
Display Exceptions.
Display Co/Adjacent Carrier Assignments.
The toolbars and buttons that you see are always dependent on the products you have installed.
For more information on the above functions, see the ASSET Radio User Reference Guide.
About the Candidate Options Toolbox
The Candidate Options toolbox contains the following buttons:
Candidate Options Toolbox
This Button
Enables You To
Make a Candidate.
Break a Candidate.
Show Search Area.
Show Candidates.
Set Search Area.
Cancel Search Area.
Tip: When you click a button on the toolbar, you remain in that mode until you until you press the
Esc key or click the
button.
For more information on the above functions, see Using Nominal and Candidate Properties on
page 387.
About the Link Toolbox
The Link toolbox contains the following buttons if you have all of the tools installed:
Link Toolbox
70
About the Core User Interface
This table describes the buttons:
This Button
Enables You To
Add Point to Point Link.
Add Point to Multi-Point Link.
Add Point to Multi-Point Hub.
Move Point to Multi-Point Hub.
Add Back to Back Link.
Add Reflector Link.
Add Multi Radio Link.
Add Dual Polar Link.
Add Logical Connection.
Add Cellular Connection.
Use the Site Visibility tool.
Break Link.
Remove Logical/Cellular Connection.
Delete Point to Multi-Point Hub.
The toolbars and buttons that you see are always dependent on the products you have installed.
For specific information on the functions in the Link toolbox, see the ASSET Backhaul User
Reference Guide. Logical and Cellular connections are also described in the ASSET User
Reference Guide.
About the Map Information Pane
To get information about a particular point on the map, you can display the Map Information
window, either attached to the bottom of a Map View window or detached from it. When there is no
open Map View window, the Map Information window is automatically closed.
71
ASSET User Reference Guide
The Map Information window can display a variety of data about the Map View window. As you
move the mouse cursor over the map, the Map Information window displays information related to
the specific pixel under the cursor including location, height above sea level, the clutter category
building height and nearest cell.
Example of Map Information pane displaying pixel-specific information
To display this window:
In the Map View window:
From the View menu, click Show Map Information.
- or On the Map View toolbar, click the small arrow next to the
button, thenClick
.
(Tip: You can also use the toggling option by pressing Ctrl+G on the keyboard.)
For more information about the Map Information window, see Viewing Information about a Specific
Pixel on page 111.
About the Layer Control Pane
The Layer Control Pane appears at the left of the Map View. It enables you to choose which data
types you want to show, and to customise their display settings.
Here is an example:
Layer Control Pane
72
About the Core User Interface
You can close the Layer Control Pane by clicking on the X in the top right corner.
Alternatively, click
in the Map View toolbar.
You can then click the same button to open it again.
There are three tabs, each performing a different function:
 Layer Order:
Shows the currently selected data types in the order that they are displayed.
The layer ordering buttons enable re-ordering. There are also buttons for removing layers.
The display settings can be customised by double-clicking the appropriate item.
 Legend:
Shows information relating to the data types currently displayed, such as the display
symbols, colours and values assigned.
 Data Types:
Lists the different categories of data types that can be displayed. Includes items such as
vectors, heights, clutter, traffic arrays, coverage arrays, and network element filters.
The display settings can be customised by double-clicking the appropriate item.
For more detailed information, see Using the Layer Control Pane, and its associated topics.
About the Equipment Windows
The following sections provide a brief introduction to the various types of equipment in ASSET.
Their availability depends on which products are licensed and installed.
About the Cellular Antennas Dialog Box
This picture shows an example of the Cellular Antennas dialog box:
Cellular Antennas Dialog Box
For more information, see Using the Cellular Antennas Dialog Box on page 313.
73
ASSET User Reference Guide
About the Microwave Antennas Dialog Box
The Microwave Antennas dialog box has a similar structure as the Cellular Antennas dialog box,
but the parameters on the tabs are slightly different.
For more information, see Adding Microwave Antennas on page 344.
About the Feeders Dialog Box
This picture shows an example of the Feeders dialog box:
Feeders dialog box
For more information, see Creating Feeders on page 352.
About the Cell Equipment Dialog Box
This picture shows an example of the Cell Equipment dialog box:
Cell Equipment dialog box
For more information, see Creating Cell Equipment on page 351.
74
About the Core User Interface
About the BTS Equipment Dialog Box
This picture shows an example of the BTS Equipment dialog box:
BTS Equipment dialog box General tab
You can use this to keep track of different types of BTS equipment that might be used in your
network, including different vendors and different equipment models.
For more information, see Creating Site (BTS) Equipment on page 350.
About the Logical/Cellular Connection Database Window
In the Logical/Cellular Connection Database window, you can view and edit details of
logical/cellular connections (or interfaces) that you have created in the project network.
Every connection active in the selected filter is displayed in a list view, showing its end points and
the amount of traffic it carries. In the Connection Types column, the type of connection is shown.
An asterisk is shown if the connection has not been Committed.
The following picture shows an example of the Logical/Cellular Connection Database window:
Example Logical/Cellular Connection Database Window
75
ASSET User Reference Guide
For more information, see:
 Adding Logical and Cellular Connections on the Map on page 92
 Adding Logical and Cellular Connections in the Site Database on page 240
 Viewing and Editing Logical/Cellular Connections on page 395
 About the Buttons in Sandboxes on page 62
About the Message Log Window
The Message Log window opens automatically when a project is started and contains messages
and warnings:
Message Log
If any of the mapping directories are set incorrectly, the product cannot display that information. To
rectify this it is necessary to close the project and change the relevant directory before re-opening
the project.
This table shows the types of messages you might see:
Type of Message
For Example
Confirmation messages
You have opened a project.
Ready message
Login has been completed.
Messages relating to files
Incomplete map data.
Warnings
Failure to commit something to the database.
Out of sequence tasks
Committing a site which uses equipment which has not yet
been committed.
Permission warning
You do not have permission to perform the requested task.
About the Wastebasket
When you delete elements, they move to the Wastebasket. These elements have been deleted
only from your private area of the database, so other users will still be able to work on the "deleted"
item.
76
About the Core User Interface
This picture shows an example of the Wastebasket:
Wastebasket Showing a Variety of Deleted Items
About Add-Ins
You can access a number of utilities and third party tools by selecting Add-Ins from the File menu:
Note: Smart City Explorer and SpaceEyes will only appear on this menu if they are installed before
ASSET.
About the Licence Administrator
TEOCO provides a range of licences specific to the products, technologies and functionality that it
provides and supports.
The licensing system always starts after you have logged in to ASSET.
The Licence Administrator enables you to view and edit the licences that are available to you
after logging in to the database. Your access to them is primarily dependent on which licences your
organisation has purchased, but may be further controlled (on a user or group basis) by your
system administrator.
77
ASSET User Reference Guide
As an ASSET user, you can use the Licence Administrator to:
 Get licences
 Drop licences
 Check out (commute) licences for usage remote from the network server, based on a
specified number of days
 Edit the Startup option to determine your default licence configuration
To access the Licence Administrator:
From the Help menu, click Licence Administrator.
The Licence Administrator dialog box will show a list of licences, with the following information:
Column Name
Description
Possible Values
Name
The licence name can refer to a product licence,
technology licence, or functionality licence.
The list is dependent on
your organisational
purchases and your
system administrator.
Type
Whether the item is currently licensed to you, and if so, Network, Local, or
whether the licence is Network or Local.
Unlicensed
Expiry
The expiry date of the licence. If a licence has been
Date and Time
checked out (commuted), this will be a short-term date.
Allowed
Whether you can GET or DROP this licence.
Yes or No
Note: These options are not applicable to the ASSET
Product Suite licence.
Commute Allowed Whether you can check this item out for usage that is
remote from the network.
Yes or No
Note: This also depends whether your organisation
allows commutable licences.
For more information about how licensing configurations and permissions can be controlled by the
system administrator, and further licensing information, see the ASSET Installation and
Administration Guide.
Getting or Dropping Licences
To get or drop licences:
1. In the Licence Administrator dialog box, select the appropriate item(s). You can hold the
Ctrl or Shift keys down to multi-select.
2. Click the Get or Drop button, as appropriate.
Note: If your Startup option is currently set to 'User Configuration', the Overwrite
Existing (User) Configuration checkbox becomes active. You should select this option if
you want to use your modified configuration for future sessions. However, if you want your
changes to be temporary (that is, for this session only), you do not need to select this
option.
78
About the Core User Interface
3. Click Save.
The Licence Administrator dialog box closes.
Commuting Licences
To commute (check out) licences for usage that is remote from the network server:
1. In the Licence Administrator dialog box, select the appropriate item(s). You can hold the
Ctrl or Shift keys down to multi-select.
2. Click the Check Out button.
3. In the dialog box that appears, from the drop-down box, select the number of days that you
want to check out the licence for.
4. Click Continue.
5. The Save button will only be active if you have made any other changes that are not related
to commuting.
o
If the button is active, click Save. The Licence Administrator dialog box closes.
o
If the button is inactive, click Cancel to close the dialog box.
Tip: You can check licences back in at any time, using the Check In button.
Editing your Startup Option
By default, the licensing system attempts to obtain all the licences to which you are entitled. If
required, there are several other options.
To edit your Startup option in the Licence Administrator:
1. Click in the Startup Option drop-down box.
2. Select the required option:
Option
Description
All
Attempts to obtain all the licences to which you are entitled.
Note: The licences are dependent on the software your organisation has
purchased, and also on your system administrator.
Prompt
Displays the Licence Administrator dialog box immediately after you have
logged in to ASSET, so that you can select or deselect the licences you require.
When you click Start, this starts the licensing system, and all selected licences
will be requested automatically.
In most situations, this option is not normally necessary, because you can
access the Licence Administrator at any stage after logging in. But there may
be occasions where it is useful.
Note: This configuration will always overwrite your user configuration (see
below).
User
Configuration
This enables you to specify your own licence configuration. If you make
changes, the Overwrite Existing (User) Configuration enables you to save that
configuration for future sessions. Otherwise, the previous user configuration will
remain unchanged.
Group
Configuration
Obtains the licences determined by the user groups that are configured for
licence control by your system administrator. Your licence entitlement therefore
depends on which group(s) you belong to.
79
ASSET User Reference Guide
Note: All the above are dependent on any licensing configurations and permissions set by
your system administrator.
3. Click Save.
The Licence Administrator dialog box closes.
About the Distributed Task Agent Menu
If your ASSET installation has been set up so that your machine can be used as an agent for
processing distributed tasks, you can enable or disable this processing.
To do this:
1. Right-click on the Distributed Predictions
tray as applicable.
or Distributed Arrays
icon in your system
2. From the menu that appears, select Enable or Disable as required.
If you select enable, your machine will be used for distributed task processing according to a policy
set by your system administrator.
For more information on how this process operates, and how to set it up, see the 'Distributed Tasks'
chapter in the ASSET Installation and Administration Guide.
80
Viewing and Editing Networks on the Map
4 Viewing and Editing Networks on the Map
The Map View window is a fundamental part of the ASSET suite in which you can view all the
different elements of your network including site data, connectivity and mapping data.
As with all windows, the Map View and Site Database windows are synchronised so that changes
you make in one are reflected in the other. For example, when you click something in the map, the
Site Database window updates dynamically.
To open a Map View window:
On the main toolbar, click the New 2D View button
.
A blank Map View window opens.
Tips:
 You can open multiple Map View windows to display different kinds of data (or different
regions) simultaneously.
 You can include Map Views in workspaces. See About Workspaces on page 55.
 You can export map layers using the GIS Export facility. See Exporting Map Layers using
GIS Export on page 435.
Using the Layer Control Pane
The Layer Control Pane enables you to choose which data types you want to show in the Map
View window, and customise their display settings. It appears at the left of the Map View window.
There are three tabs, each performing a different function:
 Layer Order:
Shows the currently selected data types in the order that they are displayed.
The layer ordering buttons enable re-ordering. There are also buttons for removing layers.
The display settings can be customised by double-clicking the appropriate item.
 Legend:
Shows information relating to the data types currently displayed, such as the display
symbols, colours and values assigned.
 Data Types:
Lists the different categories of data types that can be displayed. Includes items such as
vectors, heights, clutter, traffic arrays, coverage arrays, and network element filters.
The display settings can be customised by double-clicking the appropriate item.
The tabs are described in the following topics.
You can click X at the top right of a Layer Control Pane to close it.
You can click
on the Map View's toolbar to re-open a Layer Control Pane.
At the bottom of the Layer Control Pane are the Redraw/Apply and Snap to View buttons.
81
ASSET User Reference Guide
When you have made changes on the Layer Order or Data Types tabs, the Redraw button
changes to Apply. Click Apply to update the Map View with your changes.
If you have moved the Layer Control Pane away from the left of the Map View window, you can
click Snap to View to restore its default position.
Selecting Data Types to View on the Map
You can use the Data Types tab of the Layer Control Pane to control which data types to view.
The data types available for display include vectors, text, backdrops, web maps, height data, clutter
data, network element filters, cell information, network connections and coverage.
To control which data types to view:
1. In the Map View, in the Layer Control Pane, click the Data Types tab.
Here is an example of this tab:
Tip: To modify the layer order of the selected data types, use the Layer Order tab.
2. To display a data type on the map, select the checkbox next to the data type.
If you are using the Tiled View, you can double-click the checkbox to display your chosen
data type on all the tiles. A c appears in the checkbox when you have done this. Doubleclicking again will remove the data type from all the tiles and the c from the checkbox.
Where data types are grouped by category and sub-category (such as clutter data) you can
select or deselect all child items by selecting or clearing the parent item.
3. When you have made changes, the Redraw button changes to Apply. Click Apply to
update the Map View window to display your chosen data types.
To customise how the items are displayed:
Double-click on the item to open the Display Properties dialog box, enabling you to
customise how items are displayed. For information on this, see Changing How Data
Appears on the Map on page 169.
82
Viewing and Editing Networks on the Map
Tips:
 If you intend to zoom into an area, it can help reduce memory resources if you start by only
displaying basic line data, such as coastline or roads. Once you are zoomed in, you can
then display layers such as heights and clutter data.
 This tab also includes a very useful Show Selected button, that automatically expands the
folders with items currently selected, and collapses the others. It is a quick way of seeing
which data types are currently active.
Changing the Display Order of the Layers
You can use the Layer Order tab of the Layer Control Pane to manage the order in which the
data types are displayed, so that one layer is not hidden by another. This is useful when you have
many items displayed simultaneously on the Map View window, and especially if you are viewing
coverage arrays.
To manage the order in which the selected data types are displayed:
1. In the Map View, in the Layer Control Pane, click the Layer Order tab.
This tab shows the currently selected data types in their display layer order, where the
highest item in the list is the one with the highest layer priority. Here is an example:
Tip: To select more data types for display, use the Data Types tab.
2. To move a data type up or down in the order, select the required layer and click the up or
down arrow buttons as required.
3. When you have finished, click Redraw to update the Map View window with your changes.
83
ASSET User Reference Guide
Other options:
 To delete data layers, select the data layer(s) that you want to delete, then click the
Remove Selected button. You can also click Remove All. Both these buttons are the
equivalent of clearing the checkboxes in the list of data types.
 Double-clicking an item opens the Display Properties dialog box, enabling you to
customise how items are displayed. For information on this, see Changing How Data
Appears on the Map on page 169.
Displaying and Changing Legend Information
The Legend tab of the Layer Control Pane shows the display symbols, colours and values
assigned to the data types currently on display. For example, it shows the signal coverage
schemas for any displayed arrays.
Here is an example:
Example of Legend tab
This tab also enables you to determine which items are shown in any printouts you make of the
Map View. For information on printing, see Printing from the Map View on page 125.
Selecting an Item on the Map to Find it in the Site Database
To select items in the Map View window, click the
button .
This enables you to select any network element in the Map View, and find it automatically in the
Site Database.
Tip: If you have performed functions that are repeatable, such as creating or moving sites, this
button is useful for stopping the repeatable functionality of the cursor, and returning to normal
mode.
84
Viewing and Editing Networks on the Map
Using the Tiled View
You can use the Tiled View to see up to four maps within one Map View window for comparison,
or you can combine maps with the Pixel Analyser and/or Graphs.
To select the Tiled View:
In the Map View window, from the View menu, select Tiled View
- or In the Map View's toolbar, click
.
The view previously displayed in the Single View appears by default in all four tiles of the Tiled
View, at the same magnification. This is because the Lock Tiles Pan Zoom option is on by default.
When this option is on, any zooming or panning of the selected tile is applied to the other Map
View tiles.
The Lock Tiles Pan Zoom option is accessible from the View menu or the
View's toolbar.
toggle in the Map
You can use the scroll-wheel on your mouse or the Zoom options from the View menu to change
the magnification. For more information, see Zooming on the Map on page 98.
This picture shows an example of the Tiled View with all four tiles in use:
To add a map view to a tile:
1. Click on the required tile to select it. A bold border indicates the selected tile.
2. Choose what you want to display in the same way as for the Single View. For more
information, see Selecting Data Types to View on the Map on page 82.
To add the Pixel Analyser to a tile:
In the Map View window, right-click on your chosen tile and from the menu that appears,
click Pixel Analyser.
The top two panes of the Pixel Analyser appears on the tile. At the top left of the Pixel Analyser
tile you can click Options to access available functions including Undock, Close, and Target
Graph Tile. If you click Target Graph Tile, the Graph and Pixel Analyser displays are combined
on the chosen tile. Only one tile at a time can be designated to display the Pixel Analyser. You will
need to undock the Pixel Analyser if you wish to access the Vector Analysis pane.
85
ASSET User Reference Guide
To add a Graph to a tile:
1. In the Map View window,right-click on your chosen tile and from the menu that appears,
click Target Graph.
2. On the Data Types tab of the Layer Control Pane, right-click on the required array under
Simulator or Array Clipboard.
3. Click Graphs.
Note: This option is only available on the right-click menu for array types for which the
Statistics option is also available.
The graph associated with your choice of array appears on the tile. You can click the Undock or
Close buttons on the tile to perform those functions. If you minimise the Map View window
sufficiently, the graph undocks automatically. Only one tile at a time can be designated to display a
graph.
Viewing Web Maps
Among the data types available for display are web maps, as shown in this example:
Example of Web Map displayed on Map View
Web maps are downloaded from the source specified in ASSET Administrator or, in the cases of
Bing Maps and OpenStreetMap maps, from a fixed source. For more information on how to specify
a web map source, how to group map sources, and on how to obtain a licence key to use Microsoft
Bing Maps, see the ASSET Installation and Administration Guide.
Web maps are downloaded to the cache folder specified on the Shared Data Directories tab of the
Project Settings dialog box. For more information on specifying the path to this folder and limiting
its size, see About the Shared Data Directories Tab on page 25.
86
Viewing and Editing Networks on the Map
Adding, Moving and Deleting Network Elements on the Map
You can add network elements by using the toolbar in the Map View window or by using the Site
Database window.
Note: Your ability to add items depends on the products you have installed and the permissions
you have been given by your administrator.
This section describes how to use the tools on the Map View toolbar that are common to more than
one product. Any buttons specific to only one product are described in the appropriate User
Reference Guide for that product.
Note: Before you start adding network elements:
 It is important to check that the default network is set correctly in the Site Database. See
Setting a Default Network on page 87.
 It is wise to specify parameters for all new network elements that you will be adding. You
can do this by using templates; for more information, see Using Templates for Network
Elements on page 222.
Setting a Default Network
When you have multiple networks (PLMN and/or Logical) in the project, it is important to set a
default network in the Site Database before you add any network elements manually in the Map
View.
To do this:
1. Ensure the Site Database Network Display Mode is set to either 'Logical Links' or
'Network View'.
2. In the left pane of the Site Database, select the network you want to make the default, for
example:
3. Right-click and select Set As Default Network:
A '+' sign will appear to the left of the network name, for example:
Any network elements that you add manually in the Map View will be added to the default network.
Important: When you perform an XML Export, this setting will dictate what happens at the later
stage when you perform an XML Import; the PLMN set as default in the exported file will be set as
default in the Site Database of the receiving project. Therefore, please pay attention to which PLMN
is set as the default network in the project that you are exporting from.
87
ASSET User Reference Guide
Adding Properties
In the Map View window, you can position different pieces of cellular equipment on the same
location called a Property. A Property is a technology-independent real estate location whereas a
site refers to the technology/equipment that is located at the Property on which it is parented.
You can add, delete and move Properties in the Map View window. For more information about
Properties, see About Properties on page 231.
To add a new Property to the current Map View window:
1. In the Add Network Element toolbox (top-left corner) click the Add Property button
.
2. Click in the map at the desired location for the Property.
The Property is automatically added and Applied to the Site Database but not Committed.
Tip: When you have selected the location of the new Property, press Esc to return to the
Select mode.
For information on how to add network elements (such as sites, nodes, MSC, BSC, RNC and so
on) to the Map View, see the 'Configuring Networks in ASSET Radio' chapter in the ASSET Radio
User Reference Guide.
Automatically Generating Sites/Nodes
To speed up the setting up of the nominal network in your project, you can automatically generate
sites or nodes onto selected Properties, based on a specific site or node template. By setting up a
Property-based filter, you can determine on which Properties the sites/nodes are to be created (the
Properties can either be empty or already have existing sites/nodes).
Important: Each time you run this feature, for non-GSM technologies, new nodes will be added to
the Site Database, under a newly created separate PLMN. Please ensure you have created your
required Property filter. For GSM, sites will always be added under the PLMN that has been set as
the default network.
To do this:
1. Click on the Utilities tab.
2. From the Tools menu, click Auto-Generate Sites/Nodes.
3. In the dialog box that appears, select the (Property-based) filter that you want to use.
4. Select the site or node template that you want to apply to the filter.
5. Click OK.
Tip: Remember to click back on the RADIO tab afterwards.
You have now applied an instance of the template (that is, a new site or node) to every Property in
the filter.
88
Viewing and Editing Networks on the Map
Adding Network Elements with a Selected Template
When you add network elements in the Map View window using the Add Network Element
toolbox, the template is always the one selected in the Templates dialog box. So, if you want to
use a different template, you would need to change this first in this dialog box.
However, if you need to frequently switch between different templates when adding a particular
type of network element, it may be easier to use the Tool Options dialog box from the Map View
menu.
To do this:
1. In the Map View window, from the Tools menu, click Options.
2. In the Tool Options dialog box, select the Add Element tab.
3. In the Object Type drop-down list, select the network element type.
4. In the Template drop-down list, select the template that you want to be active when you
add this network element type.
5. In the Property Template drop-down list, select the template that you want to be active in
the event of a new Property being required (only active when applicable).
Note: The Templates dialog box (under the Database menu) is automatically updated
with the new default. Therefore the same default will also operate when elements are
added in the Site Database.
6. Click in the map at the desired location of the object.
If the location is not on an existing Property, a new Property is added automatically
together with the object (they will only be visible if you they have been included in the
display properties for the filter).
The object and (if appropriate) Property are automatically added and applied to the
database.
Note: You need the correct privileges to be able to add and modify network elements. Contact your
administrator if you think your permissions need to be changed.
For more information about templates, see Adding Network Elements Based on Templates on page
237 and the 'Configuring Networks in ASSET Radio' chapter in the ASSET Radio User Reference
Guide.
89
ASSET User Reference Guide
Copying Network Elements
To copy a network element in the Map View window:
1. On the Map View window, click the down arrow on the Move Network Element toolbox,
and then click the Clone Object button
, as shown here:
2. In the Map View window, click the network element you want to copy. If multiple sites are in
close proximity, a list appears from which you can select the correct element.
3. Click at a new location to paste a copy of the network element. If the new location is not a
Property, a Property is created for this location.
The network element is copied and is shown in the Site Database.
Note: If you do not have group permissions to edit fields, the copy will have its fields reset
to their default values. Your administrator may also have configured the system so that all
copied elements have default field values. For more information on fields, see Viewing and
Editing Fields for Network Elements on page 274.
Deleting Network Elements
To delete objects from the Map View window:
1. Click the Delete Property button
to delete a Property or the Delete button
delete any other network element, then click the object you want to delete.
to
Warning: If you delete a Property, everything on the Property is deleted.
2. Click Yes to confirm the deletion.
The deleted item is sent to the Wastebasket from where it can be restored or deleted from
the master database.
If you make a mistake, and wish to restore items, use the Wastebasket.
90
Viewing and Editing Networks on the Map
Note: If you later want to create another object (of the same type) with the same name, you must
permanently delete the object from the Wastebasket.
Moving Network Elements
To move a Property (or all the network elements on a Property):
1. See the Important Information at the end of this topic.
2. Click the Move Property button
and click the required location.
To move any other type of network element in the Map View window:
1. Ensure that in the filter that you have selected, you have chosen a symbol and colour for
Properties, because it is easier to move items onto Properties when you can see them.
2. Click the down arrow on the Move Network Element toolbox, and then click the Move
Network Element button
.
3. Click the desired network element, for example a site.
Where more than one element is in the same location, you can select the required item
from the list that appears.
4. Click the new location. If the new location is not a Property, the network element and its
current Property will be moved.
The network element is moved and this is reflected in the Site Database.
5. Commit the change or restore the last Committed settings.
Important Information about Moving Properties:
When you change the location of a Property (whether by using the Map View or the Site Database),
you should be aware of the following:
 ASSET Backhaul users: If you have any links attached to a Property that you move, the
PtP Linkend Bearing and PtP Linkend Inclination values will not be updated in the
database. They will be incorrect in any reports that you generate directly from the database
(for example, using Crystal Reports®), but the correct values will be displayed elsewhere in
the tool.
 ASSET Radio and ASSET Backhaul users: When you change the location of a Property,
the behaviour of associated antenna locations depends on the Absolute/Relative setting in
the Site Database (this setting is individual to each antenna). This affects:
o
Cellular antennas assigned to cells (ASSET Radio)
o
Microwave antennas assigned to links (ASSET Backhaul)
The behaviour is as follows:
o
If the setting is Absolute, the antenna will remain in its original location, even after the
Property has been relocated. (You can subsequently change the antenna location, if
required.)
o
If the setting is Relative, the antenna will move in accord with the Property, maintaining
its relative distance from the new location of the Property (which means its absolute
coordinates will change).
91
ASSET User Reference Guide
So, in summary, the Absolute/Relative setting in the Site Database (ASSET Radio and
ASSET Backhaul) and Link Database (ASSET Backhaul) has a significant effect on the
above behaviour.
If you change the setting for an antenna in the Site Database or Link Database, ensure you
press Apply, because the behaviour as described above is only applicable when the setting
is Applied.
Adding Logical and Cellular Connections on the Map
If you want to route traffic across any supported network type, you must first connect the network
elements with logical and/or cellular connections. This table describes the two types of connection:
Connection Type Technology Description
Logical
All
Create logical paths to carry traffic between any two network
elements, irrespective of any network hierarchies.
Cellular
All
Create logical paths to carry traffic between network elements, based
on any network hierarchies in the Site Database.
Here are some examples:
GSM: You can only create cellular connections between MSCs and
BSCs, and between BSCs and Sites.
UMTS: You can only create cellular connections between
WMSCs/SGSNs and RNCs, and between RNCs and NodeBs.
Similar restrictions are in place for the other technologies.
Notes:

There are two exceptions to the hierarchy restriction for cellular
connections: (UMTS) RNC to RNC and (LTE) eNodeB to
eNodeB are also possible.

If you have manually created hierarchies in the Site Database,
the cellular connections are created automatically, and are
shown in the Logical/Cellular Connections Database.
You can create logical and cellular connections in two different ways:
 Using the Site Database. For more information on how to do this, see Adding Logical and
Cellular Connections in the Site Database on page 240.
Tip: If you use this method, you can create more than one logical/cellular connection at the
same time.
 Using the Map View.
To add a logical or cellular connection on the Map View:
1. Click the down arrow on the Make Link toolbox (in the toolbar on the left of the Map View
window), and then click either the Add Logical Connection button
Cellular Connection button
or the Add
, as required.
2. Click the starting network element for the connection.
Note: If you are creating a cellular connection, ensure that you follow the hierarchy rules
described above.
3. Click the destination network element for the connection.
92
Viewing and Editing Networks on the Map
A bi-directional connection is made between the two network elements:
The connection is automatically stored in the Logical/Cellular Connection Database:
In the Logical/Cellular Connection Database, you can view the traffic demand and add
routes and hops to logical/cellular connections. For more information, see Viewing and
Editing Logical/Cellular Connections on page 395.
Note: If you have ASSET Backhaul installed, you can route any of these connections
across links. For more information, see the ASSET Backhaul User Reference Guide.
About Displaying Site Visibility
Site visibility predictions are useful:
 For identifying possible connection points into the transmission network for new sites
 In assisting you when you are doing a frequency plan
93
ASSET User Reference Guide
You can display visibilities for a single site or multiple sites on the Map View. This picture shows an
example:
Displaying Site Visibility in the Map View window
This table shows the two ways in which you can predict site visibility:
Prediction
Description
Line of Sight only
Displays all areas within the defined calculation area, which have
been calculated to have a clear line of sight to the selected site.
Line Of Sight is a necessity when planning microwave transmission
links. In locations where LOS is not possible, you would need to
resort to different transmission media, for example satellite or fibre
link.
Line of Sight with Fresnel
zone clearance
When microwave planning, it is not just line of sight that is important,
but whether you have clearance in the zone around it, the Fresnel
Zone.
This prediction displays all areas within the defined calculation area
but uses user-defined clearance rules for the calculation instead of
straightforward line of sight.
Both of these methods are supported by the Site Visibility function in ASSET.
94
Viewing and Editing Networks on the Map
Displaying Site Visibility
To display the site visibility of a Property:
1. In the Map View window, click on the Make Link toolbox:
2. Click the Site Visibility button
.
The Site Visibility Settings dialog box appears:
95
ASSET User Reference Guide
3. Select the site visibility settings you require. This table describes the settings available:
Setting
Description
Use Clutter Heights
Select the height option(s), if any, that you want to include in the
visibility calculation. If you select to use Clutter Heights, you must
Use Building Raster Heights also specify a propagation model.
Use Building Vector Heights Note: If you select to use building vector heights, their position is
calculated based upon the position at which the vector line intersects
the profile.
K Factor
This geoclimatic factor is used to calculate the effective earth radius.
Tip: The usual geoclimatic factor is 1.333.
Start Antenna Height (m agl) The height of the 1st antenna, which is always above ground level.
End Antenna Height (m)
The height of the 2nd antenna.
Use End Antenna Height
Above Clutter Height
Select how the height of the receiving antenna will be calculated:

If you chose to use clutter heights, you can choose to calculate
the height of the end antenna using clutter. Here, antenna height
= DTM + Clutter + End Antenna Height.

If you chose to use building raster heights and/or building vector
heights, you can choose to calculate the height of the end
antenna using building heights. Here, antenna height = DTM +
Building Height + End Antenna Height.
Use End Antenna Height
Above Building Height
Fresnel Clearance (0-1.0)
and Frequency (GHz)
The Fresnel clearance required, used for microwave link planning.
Visibility Area (Degrees)
The extent of the visibility area that will be calculated. 360 degrees
represents a full circle around the property or site, 180 degrees a half
circle and so on.
Valid values are real numbers between 0.0 and 1.0 with a 'good'
value being the default of 0.6, although if planning at higher
frequencies, (over 36 GHz ) use 1.0.
Tip: Restricting the area of interest to particular angles reduces the
calculation time required and the amount of information shown in the
Map View window.
Preset Radius (Km)
You can choose a predefined radius of the area that will be checked
for visibility.
K
Note: It is suggested that e value exceeded for 99.9% of the time is used with between 0
and 100 percent first Fresnel clearance, depending on the frequency, geographical area
and atmospheric climate.
4. Click the desired Property or site.
5. If you used a Visibility Area of less than 360 degrees, angle the visibility area as required.
6. Drag the cursor outwards and, if you have not already defined a Preset Radius in the
Settings dialog box, click to specify the required radius.
Tip: If you select the wrong site, press Esc on your keyboard to select a different Property
or site.
7. If you have data of different resolutions, from the menu that appears, select the mapping
resolution you want to use in the calculation.
Tip: You can obtain more accurate results by using higher resolutions.
96
Viewing and Editing Networks on the Map
During visibility scanning calculations, measurements or "scans" are taken at a limited
number of points in each resolution section (a square of resolution which that visibility is
being calculated for). If an obstruction is found at any single point, then a report of no
visibility is made for that entire section.
The visibility of the site is shown in black by default. For example, here the site visibility is
good towards the coast, but poor towards the hills:
8. As with all items, to change the display properties and antenna height settings, select the
item required in the list of data types, which in this case, is will be under Site Visibility:
When site visibility has been created, it will automatically be refreshed using the existing
settings, if the site is moved to a new location.
Changing Antenna Heights Used in the Site Visibility Calculation
To change the antenna height settings used in the site visibility calculation:
1. In the Map View, in the Layer Control Pane, click the Data Types tab.
2. Under the Site Visibility category, double-click the appropriate Property.
3. On the Colour/Style tab, ensure the Use Default Settings checkbox is not selected.
4. Edit the transmitter height and receiver height as required.
5. If required, on the Parameters tab, edit the Fresnel zone clearance values.
6. Click OK.
7. Click the Redraw button.
97
ASSET User Reference Guide
Zooming, Moving and Redrawing the Map
There are several ways of zooming in and out on the map.
Zooming on the Map
This table describes how you can zoom in:
Option
Click the appropriate button and then
To zoom in or out by
a factor of two
Zoom In: Left-click on the map at the place where you want the zoom to be
centred.
Zoom Out: Right-click on the map at the place where you want the zoom to be
centred.
Tip: You can also use your mouse-wheel to zoom in and out.
To zoom in or out by
dragging to your
preferred zoom level
At the place where you want the zoom to be centred, hold the left mouse
button down while dragging the mouse downwards (zoom in) or upwards
(zoom out) on the map. Release the mouse button when finished.
Tip: You can also use your mouse-wheel to zoom in and out.
To zoom to an area
contained in a
rectangle (from a
corner)
At the place where you want the zoom to begin, hold the left mouse button
down while dragging the mouse outwards from the corner. You can do this in
any direction. Release the mouse button when finished.
To zoom to an area
contained in a
rectangle (from the
centre)
At the place where you want the zoom to be centred, hold the left mouse
button down while dragging the mouse outwards from the centre. Release the
mouse button when finished.
To zoom to a scale
factor or distance
Choose from the factor and distance options. You can also choose Last view
or Home view.
The aspect ratio of the region will match that of the current Map View.
The aspect ratio of the region will match that of the current Map View.
If this button is not initially visible, you need to click the small black arrow.
98
To zoom to the
network elements
belonging to the
selected Filters in the
Map View.
This will set the zoom area to show all the network elements that are included
in the currently selected Filters in the Layer Control Pane.
To zoom to the
network elements
belonging to the
selected Filters in the
Map View, including
the prediction radius.
This will set the zoom area to show all the network elements that are included
in the currently selected Filters in the Layer Control Pane. This zoom level
takes account of the primary prediction radius that has been assigned to the
relevant cells and repeaters, or the global override setting (if selected) on the
Predictions tab of the Array Settings dialog box.
If this button is not initially visible, you need to click the small black arrow.
If this button is not initially visible, you need to click the small black arrow.
Viewing and Editing Networks on the Map
Tips:
 To stop zooming, click the
button.
 For straightforward zooming in and out, you can just use the mouse-wheel, instead of using
the buttons.
 When using the Zoom buttons, you are in Zoom mode. You can hold down Shift to change
temporarily to Pan mode. This is useful for zooming and then scrolling and zooming again.
 If you want to zoom to an array that you have just displayed on the Map View, you can use
the 'Zoom to Array' option by right-clicking on the appropriate array in the Data Types list of
the Layer Control Pane.
This table describes additional zoom-related options:
Option
Do This
To zoom to the last
(previous) zoom level.
In the Map View window, from the View menu, point to Zoom and then click
Last. (Or use Ctrl-Z.)
To zoom to the home
zoom level
In the Map View window, from the View menu, point to Zoom and then click
Home. (Or use Ctrl-H.)
Tip: Also see Saving a Favourite (Home) Zoom Level on page 99.
To zoom to a region
defined by specified
coordinates
Right-click anywhere on the Map View window, and click Set 2D View
Region.
The Set 2D View Region dialog box appears. Specify the coordinates
defining the region you require and click Apply. If the area you have
specified is within the region defined by your project settings, the Map View
window is resized accordingly.
You can also capture the coordinates of the region currently displayed by
clicking the Get Current Coord button.
Note: This may be useful for defining a precise region for running coverage
arrays and simulations. But it is different from the 'Home' zoom level (see
Saving a Favourite (Home) Zoom Level on page 99).
To zoom all the tiles in
the Tiled View when
one tile is zoomed.
From the View menu in the Map View window, select Lock Tiles Pan
Zoom.
Saving a Favourite (Home) Zoom Level
You can set a level of zoom as your 'Home'. This performs two important roles:
 It acts as the default zoom level each time you open a new Map View window
 It acts as a zoom level that you can return to at any time
To do this:
1. In the Map View window, right-click and from the menu that appears click Set Home.
2. To return to this level of zoom, from the View menu of the Map View, point to Zoom then
click Home.
(Tip: You can also return to Home zoom level by pressing Ctrl+H on the keyboard.)
For information on setting up permanent favourite views, see About Favourite Map Views on page
101.
99
ASSET User Reference Guide
Shortcut Keys for Zooming
This table shows the shortcut keys (Ctrl, Alt or Shift) that you can press to switch from one mode to
another.
Note: You have to press and hold down these keys after selecting the mode and before clicking the
map.
Current Mode
Ctrl key held down
switches mode to
Alt key held down
switches mode to
Shift key held down
switches mode to
Zoom
Zoom Out
Zoom Box (from corner)
Pan
-
Zoom
Zoom Box (from centre) Zoom Box (from corner)
Repositioning (Panning) the Map
To reposition (pan) the map:
1. Click and hold down the left mouse button and drag the map to the required location.
2. You can continue to click and drag until you are happy with the position.
Note: If you are currently using one of the Distance Measurement toolbox modes (coordinate
points, distance, or area) you need to press the 'Ctrl' key to enable panning.
Redrawing the Map
When you have added or removed display items, you may need to redraw or refresh the
information shown in the Map View window.
To do this:
In the Map View window, right-click and, from the menu that appears, select Redraw.
About the GIS Export of Map Layers
The GIS Export facility can export any or all of the map layers (vectors, heights, clutter, coverage
arrays, network element filters and so on) that are currently displayed in the Map View.
You can export any of your map layers for use with:
 MapInfo
 Google Earth
 ESRI ArcGIS
For information on the GIS Export facility, see Exporting Map Layers using GIS Export on page
435.
100
Viewing and Editing Networks on the Map
About Favourite Map Views
When you are working on a particular Map View, you can save it as a Favourite. This means you
can easily return to a predefined working environment which can include:
 The Map Region
 The display list of items currently selected in the Layer Control Pane
 The layer ordering
 Various categories of array
 The Tiled View (except for Graph or Pixel Analyser tiles) if applicable
When you create a Favourite, you can choose which of the above items you want to save.
When you open a Favourite in the Map View, a Region Polygon vector is automatically created in
the Regions sub-folder of the User Vectors and Measurements folder on the Data Types tab of
the Layer Control Pane. This vector stores specific region coordinates for quick and easy usage
when you run any of the planning or array wizards. For more information, see Creating a Region
Polygon on page 262.
There are two possible storage/access locations for Favourites:
 User folder: Enables you to store and access your own Favourites, independently of other
users.
 System folder: Enables you to access a shared pool of Favourites. This depends whether
your administrator has set up a System Favourites folder. If so, and if you have the
'System Favourites' write permission, you can also save or copy any of your own
Favourites (new or existing) into this folder.
Favourites are stored in the folders that were defined in the project's settings. For information on
setting the paths to these folders, see About the Shared Data Directories Tab on page 25.
Here is an example of System Favourites and User Favourites available on the Map View:
Example of Favourites available on Map View
Tip: Favourites are very useful in the context of the Map View, but if you want to be able to set up
and reload several dialog boxes (Site Database, Map View, and so on) in chosen positions, you
can use Workspaces.
101
ASSET User Reference Guide
Here is a quick comparison:
 Use Favourites if you are only working with the Map View window. Additionally, in the
case of System Favourites, you can share them with other users of the project.
 Use Workspaces when you want to personalise the layout and positioning of several
dialog boxes, optionally including the Map View. See About Workspaces on page 55.
Saving a Favourite View
To save a Favourite view:
1. In the Map View window, right-click.
2. From the menu that appears, point to Favourites and click Save As:
Note: It is generally safer to choose Save As instead of Save, unless you want to modify
and save a previously loaded Favourite.
The Add New Favourite dialog box appears.
3. You may be able to choose between saving it as a User Favourite or as a System
Favourite. This depends whether your administrator has set up the System folder, and also
depends whether you have the 'System Favourites' write permission.
4. Type a meaningful name for the Favourite and any optional comments.
5. Select the appropriate checkboxes to determine the items you want to save in the
Favourite. The options vary according to what is currently available.
Important: When you save a new Favourite view, the Save Region option is always
enabled by default. You have this choice:
o
Leave this option selected if you want this Favourite, when loaded, to always return to
that recorded region, even if the map view you are currently viewing is in a different
region.
o
Deselect this option if you prefer this Favourite to be 'region-independent'. This can
offer more flexibility in the situation where you want to use the Favourite in different
map view regions, such that you only want it to remember the list of items currently
selected in the Layer Control Pane.
6. Click OK.
You can now access the Favourite at any time from the Map View drop-down box. If it was saved
as a System Favourite, other users will also be able to access it.
102
Viewing and Editing Networks on the Map
If you are using the Tiled View in the Map View window, two additional options are available from
the right-click menu under Favourites:
 Click Save All Tiles to save all the tiles currently displayed to the current Favourite name.
- or  Click Save All Tiles As to save all the tiles currently displayed to a new Favourite name.
Note: Only GIS tiles are saved to your Favourite, so Graph or Pixel Analyser tiles will not be
included.
The Save and Save As options will save the currently selected tile as a Single View Favourite.
Loading a Favourite View
You can load Favourite views from your own 'User' folder and also from a centralised 'System'
folder (if this is set up by your administrator).
To load a Favourite view:
Select the name of the view in the drop-down box at the top of the Map View window:
103
ASSET User Reference Guide
The Favourite appears in your Map View window. Here is an example:
Tip: Favourites are loaded when you open your project. Whenever there are new Favourites that
are centrally available (for example, your administrator or other users may add new Favourites into
the System folder), you can reload the Favourites without needing to close and reopen the project.
For information on the Organise Favourites dialog box, see Managing Favourite Views.
Managing Favourite Views
In addition to saving and loading individual Favourites, you can also perform several other useful
actions:
 Rename Favourites
 Delete Favourites
 Copy a Favourite from User to System folder
 Copy a Favourite from System to User folder
 Reload Favourites when new ones are available
 Check the usage history to help identify any Favourites that are no longer required
Note: The presence of the System Favourites (and the two Copy options) depends whether your
administrator has set up the System folder. Also, unless you have the 'System Favourites' write
permission, you cannot perform any save, copy, edit or delete actions in the System folder.
104
Viewing and Editing Networks on the Map
Here is an example of the Organise Favourites dialog box:
Organise Favourites dialog box
To open the Organise Favourites dialog box:
1. In the Map View window, right-click.
2. From the menu that appears, point to Favourites and click Organise:
The Organise Favourites dialog box appears.
To rename a Favourite:
1. If applicable to your set-up, select User Favourites or System Favourites from the dropdown box.
2. Select the specific item and then click Edit.
3. Rename the item and click OK.
To delete a Favourite:
1. If applicable to your set-up, select User Favourites or System Favourites from the dropdown box.
2. Select the specific item and then click Delete.
105
ASSET User Reference Guide
To copy one or more Favourites from one folder to the other:
1. If applicable to your set-up, in the Organise Favourites dialog box, select the specific item
or items (you can multi-select with Ctrl or Ctrl+Shift).
2. Click Copy to User or Copy to System, as appropriate.
When new Favourites are made available (for example, your administrator may add new Favourites
into the System folder), you can reload the Favourites without needing to close and reopen the
project.
To reload Favourites when new ones are made available:
Click Reload Favourites.
To check Favourite details:
 Look in the Created and Last Used columns to identify Favourites that are no longer
needed, so that you can delete them.
 Look in the Details column for any additional notes you have recorded with a Favourite,
and the View Mode column to see whether it is a Single or a Tiled view.
When you have finished using the Organise Favourites dialog box, click Close.
Searching the Map View Window with the Quick Finder
You can search the Map View window using the Quick Finder dialog box. This enables you to
locate items such as a location, Property, link or piece of text or attributes such as carried traffic.
This picture shows an example where any Property ID containing the number "70" is listed in the
Quick finder dialog box and highlighted with an arrow in the Map View window:
Using the Quick Finder with the Map View
106
Viewing and Editing Networks on the Map
To search the map using the Quick Finder:
1. Click the Quick Finder button
.
2. In the first drop-down field select the item that you wish to search for.
3. In the second drop-down field, if applicable, refine your search by selecting a parameter to
search for. The item and parameter that you have chosen are shown in "Look for" field.
4. If you have selected a parameter at step 3, click the
button by the "Where" field.
"Where" in this context is used to mean for example, find all cells where the cell ID includes
the text "site."
You can specify an expression to be applied to the search of your chosen item and
parameter by selecting an operator and a value.
Note: The operators available depend on the parameter selected and can include regular
expressions. For more information on these, see Examples of Searching by Regular
Expression on page 109.
You can also select the Not option to locate items that do not match the expression or
value chosen.
5. Optionally click the
button by the "Search in" field. For all items except text a dropdown list enables you to choose whether to search in a filter, a view, or in existing search
results.
If you choose to search in:
o
A filter, specify which filter
o
A view, use the Click View button to select one
o
Existing results, a subset of these that match your refined search criteria will appear in
the "Results" field after you click the Find button
For text items a drop-down field enables you to choose whether to search all text or just the
text currently displayed in the Map View window.
6. Optionally click on the
button by the "Highlight on view" field. You can use this to
determine how your search results are to be identified in the Map View window. You can
choose:
o
An arrow or a target symbol to highlight the item
o
The colour of the arrow or target
o
The colour of the surround (halo) around the arrow or target
o
The colour of the symbol (dot) representing the item
o
Whether or not text identifying the item is displayed
o
The colour of the text used
o
The size and transparency of the arrow or target used
7. Click Find. Your search results are shown in the Map View window and listed in the Quick
Finder dialog box under the "Results" field.
You can select the Append option if you want the current search results to be retained and
appended to the results of your next search. This table shows the options available if you
right-click on any of the results listed:
107
ASSET User Reference Guide
Select This Option
To Do This
Select All
Select all the items in the search results list and highlight all the
associated features in the Map View window.
Re-centre in view
For single selected items, position the item in the centre of the Map
View window.
Re-centre and zoom in view
For single selected items, position the item in the centre of the Map
View window and zoom in to 5km.
Quick Edit
Change the parameters associated with a GSM or UMTS item.
Generate report
Create a report including all the items shown in the list of search
results.
Save as selection filter
Create a selection filter that can subsequently be used to display the
items identified by the search in the Map View window. For more
information on filters, see Using Filters in ASSET on page 275.
Using Jump To Location
You can jump to a specified location in the Map View window. When you do this, that requested
location will be highlighted and will be centred in the window.
To do this:
1. On the Map View toolbar, click the small arrow next to the
button.
2. From the extra set of buttons that appear, click the Jump to Location button
Jump to Location dialog box appears. This picture shows an example:
. The
3. Select the type of coordinates you are going to use. You can choose from GRID
coordinates (in Eastings and Northings), LL (Longitude Latitude in degrees, minutes and
seconds) or DLL (Decimal Longitude Latitude).
4. Type your coordinates into the appropriate fields.
5. Click the Jump to button. Your chosen location is highlighted with an arrow in the Map
View window.
108
Viewing and Editing Networks on the Map
Examples of Searching by Regular Expression
Regular expressions allow complex search criteria to be defined and are used:
 In creating static filters in the Filter Wizard
 To add items to the Selection filter
 When searching on the map
 In the neighbour chooser dialog box
 In advanced antenna searches
 When enforcing naming conventions for network elements
For its regular expressions, ASSET uses the Perl engine. Perl is widely documented on the
internet. For example, you can read more about Perl at this location:
http://perl.org
This table gives some examples of regular expressions that you might use in ASSET:
Enter
To Find
.*
Everything.
^BSC.*
All BSCs beginning with BSC.
^PROPERTY.*
All Properties beginning with PROPERTY.
^CELL.*A$
All sector cell names beginning with 'CELL' and ending with the letter A
(sector A).
^CELL0001.
All the sectors for 'CELL0001' (A, B, C, …).
^SITE83(89|98)$j
SITE8389 and SITE8398.
^SITE_\d+\w$
SITE followed by an underscore, followed by at least one digit, followed
by only one letter. For example this would return SITE_102A,
SITE_01B and SITE_123123123A.
But it would not return SITE0102A, SITE_0123ABC or SITE__01A.
^Helier\d\d\.*A$
All elements beginning with Helier followed by two digits and an A.
.*[A-F]$
Elements with names ending in a,b,c,d,e,f or A,B,C,D,E,F unless you
have selected the Match Case checkbox, in which case it only returns
elements with names ending in A,B,C,D,E,F.
^(SITE|CELL)_[0-9]{4}[a-fA-F]{0,1}
SITE or CELL followed by an underscore, followed by exactly 4 digits,
optionally followed by one letter. For example, this matches SITE_3671
and CELL_3671C, but does not match CELL_031A or
SITE_0001TEST.
109
ASSET User Reference Guide
For example, this picture shows a search that has returned everything:
Searching Using a Regular Expression
This picture shows an example of using regular expressions in the Selection Filter. For more
information on this, see About the Selection Expert and Selection Filter on page 294.
Using Regular Expressions in the Selection Expert
110
Viewing and Editing Networks on the Map
Other Regular Expressions Examples
This table shows special meta-characters for use in regular expressions:
Item
Description
^
Matches the beginning of the line.
.
Matches any character (except newline).
$
Matches the end of the line (or before newline at the end).
|
Alternation.
()
Grouping.
This table shows character classes for use in regular expressions:
Item
Description
\w
Match a "word" character (alphanumeric plus "_").
\W
Match a non-"word" character.
\s
Match a whitespace character.
\S
Match a non-whitespace character.
\d
Match a digit character.
\D
Match a non-digit character.
This table shows standard quantifiers for use in regular expressions:
Item
Description
*
Match 0 or more times.
+
Match 1 or more times.
?
Match 1 or 0 times.
{n}
Match exactly n times.
{n,}
Match at least n times.
{n,m}
Match at least n but not more than m times.
Viewing Map Information in Other Windows
This section describes the other map-related windows where you can get further information about
what you are seeing on the Map View window.
Tip: You can also view the settings for a project while you are using the Map View window. To do
this, from the File menu, click View Project Settings. The Project Settings dialog box appears,
detailing information on the Map Data directories, Map Data Extents and so on.
Viewing Information about a Specific Pixel
To view information about a particular point on the map, you can show the Map Information pane,
which can be either attached to or detached from an open Map View window.
111
ASSET User Reference Guide
Here is an example:
Map Information pane displaying pixel-specific information
This pane displays the dimensions of the current view expressed as width and height in kilometres.
As you move the mouse cursor over the map, the pane displays information related to the specific
pixel under the cursor including location, height above sea level, the clutter category, building
height and nearest cell.
Important: You can also view pixel-specific information for all types of array (such as coverage
arrays and simulation arrays) in the Pixel Analyser window. For more information, see About the
Pixel Analyser on page 149.
To view the Map Information pane:
On the Map View toolbar, click the small arrow next to the
button, then click
.
(You can also use the toggling option by pressing Ctrl+G on the keyboard.)
The Map Information pane appears, attached beneath the Map View window.
If you have more than one Map View window open, you may prefer to use a detached pane. This
one pane will then display information about whichever Map View window is active.
To detach the pane from a Map View window:
1. On the Map View window, from the View menu, de-select the Pin Map Information option.
2. Drag the detached pane to the required location.
To reattach the pane, select the Pin Map Information option again.
You can decide which items to display in the pane.
To specify what you want to be displayed:
1. On the pane, click the Information Fields Selector button
.
2. Add and remove items as required, such as Location, Clutter, Nearest Cell and so on.
Tip: You can change how location and building height are displayed by double-clicking the
item in the Map Information window.
You can also do this for vector attributes. For more information, see Displaying Vector
Attribute Information for a Specific Pixel on page 113.
3. Click OK.
112
Viewing and Editing Networks on the Map
One of the options in the Information Fields Selector enables you to display the dimensions of the
current Map View and the scale:
For more information on this, see Viewing Scale Information Relating to the Current Map View on
page 113.
Viewing Scale Information Relating to the Current Map View
In the Map Information pane, one of the options in the Information Fields Selector enables you to
display the dimensions of the current Map View and also the scale:
Example of Dimensions and Scale in Map Information pane
To see this:
1. On the Map View window, from the View menu, ensure Show Map Information is selected.
2. On the pane, click the Information Fields Selector button
.
3. Add the item named '2D View Dimensions'.
4. Click OK.
Important: The scale value represents the ratio between the pixel size in ASSET and the screen
pixel size (in other words, it represents 'metres per pixel' based on the screen resolution). This
value can be a useful aid in deciding which resolution to specify against scanmaps in the index file.
For more information on scanmaps, see 'Configuring Map Backdrops' in the ASSET Technical
Reference Guide.
Displaying Vector Attribute Information for a Specific Pixel
To display vector attribute information in the Map View window:
1. On the Map Information pane, click the Information Fields Selector button
.
2. Add the 'Vector Attributes Display1' item.
3. Click OK.
4. Double-click the blank field:
In the example above, the blank space will represent Vector Attribute 1.
113
ASSET User Reference Guide
5. In the dialog box that appears, expand the vector which has the attribute(s) you want to
display:
6. Double-click each vector attribute that you want to display.
Each vector attribute will appear in the list on the right-hand side:
Tips:
o
You can include attributes from different vectors in the same Vector Attribute item. In
the example above, it would also be possible to include attributes from the CityCentre
or Pathway vectors in Vector Attribute 1.
o
You can add new attributes to the list, by right-clicking the list and from the menu that
appears, clicking Add.
o
To delete an attribute from the list, right-click the required attribute and from the menu
that appears, click Delete.
7. You can optionally set a number of display properties for these attributes:
o
If the attributes are used in more than one vector, you can choose which vector number
(the first, the second and so on) to display the map information for
o
Define the search radius in pixels
o
If you want to highlight the feature containing the attribute whose information you are
displaying, select the Highlight Feature option
o
If you want to display the attribute name in the information, select the Display attribute
names option
o
If you want to display the name of the vector associated with the attribute information,
select the Display vector name option
8. Click OK.
As you move the mouse cursor over the map, the pane displays the selected attribute
information related to the specific pixel under the cursor.
114
Viewing and Editing Networks on the Map
This picture shows an example, where the Highlight Feature, Display attribute names and
Display vector name options have been selected:
Viewing Information in the Height Profile Window
Use the Height Profile window to see a two-dimensional cross-section of the terrain between two
points (or Properties) on the map.
Important: The Height Profile window functionality can be used for ASSET Radio and ASSET
Backhaul. If you are using ASSET Backhaul, the Height Profile window provides additional
functionality related to microwave links. For more information, see 'Using Height Profiles' at the end
of the 'Designing the Physical Network' chapter in the ASSET Backhaul User Reference Guide.
115
ASSET User Reference Guide
This picture shows an example of a Height Profile window:
Example Height Profile Window
In the example:
 The closest obstruction to the line of sight is 16.4m
 The distance between the sites is 3.75km
 The bearing is 76.3 degrees
The set of options available depends on which tools you have installed.
About the Height Profile Toolbar
This section describes the functions of the buttons in the Height Profile window. Here is a picture
of the toolbar:
The Height Profile toolbar
Note: The Height Profile window functionality and choice of buttons available may vary according
to which ASSET products you have installed.
116
Viewing and Editing Networks on the Map
This table describes the buttons in this toolbar:
Button
Description
Toggle View
Save Profile
Print Title and Logo
Print Preview
Print Profile
Copy Profile
Profile Report Parameters
Select Link
Property to Point
Property to Property
Point to Point
Cancel Profile
Display Fresnel Zones
Toggle Display of Basic Reflections
Toggle Display of Specular Reflections
Reflection Analysis
Antenna Minimisation
Tilt Angle
Reverse Profile
Redraw Profile
Map Data Profile
User Defined Data Profile
User Defined Profile Generator
117
ASSET User Reference Guide
About the Height Profile Message Bar
This diagram shows the information on the Height Profile window message bar:
Tilt angles (cellular
antennas)
Line of sight
clearance
(or obstruction)
Distance
between points
or Properties
Bearing
Signal Loss (microwave
antennas)
Elevation
The Height Profile message bar
Note: The information available may depend on which tools you have installed.
What Does the Height Profile Window Show?
The Height Profile window shows:
 Line of sight (LOS) between the two points
 Clutter
 Clearance, or height of an obstruction
 Distance between the two points
 Bearing from due north of the end point from the start point
 Antenna tilts of cellular antennas
 Angle of elevation of the end point from the start point (a positive value means a downward
tilt, a negative value means an upward tilt)
 Any resultant signal loss
 Any obstructions, shown as vertical red lines
Note: You can get negative heights because the Height Profile window takes into consideration
earth curvature and represents this on a flat line from the start point, as illustrated here:
118
Viewing and Editing Networks on the Map
Displaying a Path in the Height Profile Window
To display a path between a Property and a desired point, two Properties, or two desired points:
1. From the View menu, click Height Profile.
2. In the Height Profile window, click the appropriate button, for example, Property to point
.
3. In the Map View window, click the Property (or point) then move the cursor to the desired
point (or Property) and click again.
Note: If you have chosen either Property to Property or Property to point mode, and
then click a particular point on the map, a list of the nearest Properties is displayed, from
which you can select the appropriate one.
If appropriate, the start and finish heights are set by the antenna heights of the selected
Property.
Note: If you select to view the profile along a link, the start and finish heights are set by the
heights of the microwave antennas.
4. If you have selected Property to Property or Property to point mode, you can select
which antenna from the Property is used. To do this, from the list of antennas that appear,
double-click the required antenna.
5. Click the Settings tab.
The appearance of this tab changes depending on the ASSET products you have installed.
For more information on using this tab, see Changing the Height Profile Settings on page
120.
6. On the Fresnel tab, ensure the correct clearance criteria are used. For more information on
the Fresnel tab, see Setting the Clearance Criteria for Height Profiles on page 121.
After you have created a height profile path:
 If you have ASSET Backhaul installed, you can view a report on the path along a link.
For more information, see the ASSET Backhaul User Reference Guide.
 You can check the clearance at specific points. For more information, see Checking
Clearance on Height Profile Paths on page 122.
 You can print a picture of the path for use in a report, for example. For information on how
to do this, see Printing Height Profiles on page 124.
119
ASSET User Reference Guide
Changing the Height Profile Settings
In the Height Profile window, to change what the height profile displays, click the Settings tab.
This picture shows an example Height Profile Settings tab:
Height Profile Settings tab
Note: Any changes that you make to the values in the Height Profile window will not be applied to
the Site Database or Link Database, unless you choose to click Apply.
In the Properties pane of the Settings tab, you can:
 Select the start and finish antenna heights for point to point mode. For Property to point and
Property to Property modes, this corresponds to:
o
The heights at the cellular antennas on the sites/nodes of the Property, if you have not
selected a microwave link.
o
The heights of the microwave antennas, if you have selected a microwave link.
 Edit the transmitter frequency at the start and end points.
 Where applicable, you can override the antenna inventory height with the antenna
prediction height, at the start and end points. This is only relevant if you have ASSET Radio
installed.
o
The antenna inventory height is the height of the antenna according to the antenna
inventory (this value is not used for cellular coverage predictions).
o
The antenna prediction height is the height of the antenna that is used for cellular
coverage predictions.
In the Map Data pane of the Settings tab, you can:
 Select which map or user data (if any) you want to include in the height profile calculation.
If you choose Building Vector Heights, click the Select button, and in the dialog box that
appears, ensure that the Building Vectors option is selected, and then click OK.
Note: If you select the Building Vector Heights checkbox, rather than display buildings
according to the pre-defined resolution, the Height Profile displays them based upon the
distance on which the profile line intersects the segments of the buildings, interpolating the
DTM height used to draw the buildings where the building falls between two profile points.
 Select the resolution to be used in the height profile calculation.
120
Viewing and Editing Networks on the Map
Setting the Clearance Criteria for Height Profiles
On the Fresnel tab of the Height Profile window, you can set the correct clearance criteria.
The amount of clearance required depends on the path length, the position of any obstruction along
a path and the frequency of the operation.
Note: If you have ASSET Backhaul installed, you can specify up to 6 clearance criteria with
corresponding Fresnel zone clearance requirements. If you do not have ASSET Backhaul installed,
you can only specify one clearance criterion.
For an example:
For each clearance criterion, you can specify the following:
Item
Description
K
The K factor – The factor by which the Earth's radius is multiplied to reflect the effective
Earth bulge.
F
The Fresnel factor – This is the amount of clearance that should be afforded in a particular
location, based on ITU-R recommendations. For example, for k=1.33, a clearance of 1.0
F1 should be obtained, but if k=minimum exceeded for 99.9% for the time, a clearance of
0.3 F1 should be obtained if the obstacle is rounded, or 0 F1 if there is a single sharp
isolated obstacle.
#
The number of the Fresnel zone – F1 is the 1st Fresnel zone, F2 is the 2nd Fresnel zone
and so on.
From and
The two antennas that connect the link. The height of the antennas will be considered in
To antennas the Fresnel zone calculations.
Colour
The display colour that you will use to visually identify the Fresnel zone.
To display a clearance criterion that you have defined, select its checkbox. You can display multiple
pairs on the same profile.
121
ASSET User Reference Guide
Changing the Clutter Settings in the Height Profile Window
To change which clutter settings are used for the height profile, click the Clutter tab. This picture
shows an example clutter tab:
On this tab, you can:
 Edit the clutter height and categories shown and choose a model to select which clutter
heights to use.
 View the colours and values assigned to the data types displayed in the open Height
Profile window.
Note: You cannot edit these colours here. To change them, double-click the clutter item in
the list of data types in the Map Information and Control dialog box.
 Choose to display clutter above the line of the height profile, below it, or both above and
below.
Checking Clearance on Height Profile Paths
After you have created a height profile path, you can look at specific points on it, and instantly see
the clearance between the line of sight (and/or the Fresnel zone) and any obstacles below.
To do this:
1. In the Height Profile window, click the Location Finder tab.
2. Select the Show Marker checkbox.
A vertical line appears on the height profile. The Marker Position pane shows the
geographical co-ordinates (in the format of your choice – LL, DLL or Grid).
122
Viewing and Editing Networks on the Map
This picture shows an example:
o
In the Line of Sight and Fresnel Zone panes, you can view clearance information
related to that specific point along the Height Profile path – clearance to the ground,
to clutter, to building vectors and to building rasters. The clearance values are based
on the specified K factor and/or the Fresnel Zone percentage.
o
In the Distance from pane, you can see the distance that the marker line is from either
end of the path.
o
In the Tilt Angle From and Effective Tilt from panes, you can view these angles from
either end of the path.
3. You can move the marker line along the height profile path in either direction, by:
o
Clicking on the marker line and dragging it from left to right as required
– or –
o
Clicking the Fine Tune left and right arrow buttons, for a more accurate location of a
point on a pixel by pixel basis
Tip: You can view the location of the marker on the Map View window, marked as a cross along
the path.
What Height is Used When Using Repeaters?
If you choose Property to Property and you are using a repeater, then ASSET assumes that you
are looking for how that repeater might receive a signal for repeating, so the Rx height is used.
If the profile mode is Property to point and are using a repeater, then ASSET assumes that you
are looking at how the repeated/transmitted signal is received by a mobile, so the Tx height is used.
123
ASSET User Reference Guide
Printing Height Profiles
You can print or copy the contents of the Height Profile window, using the Print toolbar buttons:
Print Toolbar buttons
Button
Description
Print Title and Logo
Print Preview
Print Profile
Copy Profile
To do this:
1. Click the Print Title and Logo button and specify any title, copyright, comments, headers
and footers that you require.
2. You can choose to:
o
Print a logo with the height profile, either the default logo or your own. As this is a
raster format, you may need to experiment with various image sizes to obtain the best
image on the hard copy printout. Any number of colours can be used (monochrome to
24-bit colour).
o
Print the time and date with the height profile.
o
Print the x and y axis labels for the height profile.
This picture shows an example dialog box:
3. Click OK.
4. On the Height Profile window, from the File menu, click Page Setup and specify details
such as page orientation, size, source and margins; change the printer, printer properties
and number of copies. These settings default to those assigned as default by the Windows
printer driver.
Important: You should set the number of pages to 1, unless your height profile contains a
Link Profile/Budget report.
5. Click the Print Preview button to verify your plots.
124
Viewing and Editing Networks on the Map
6. Click Print.
7. Check the details are correct, and click OK.
The height profile is printed.
About the Master View
The Master View window is a small-scale map, which indicates with a rectangle the position of any
currently opened map view.
To open the Master View window:
From the View menu, click Master View.
To choose what data is displayed on the Master View:
1. On the Master View, right-click and from the menu that appears, click Properties.
2. In the Data Types dialog box, select the data you require:
Tip: You can edit the display properties of a data type by double-clicking it.
3. Click OK & Redraw.
Tip: You can scroll your Map View using the Master View window. To do this, drag the rectangle to
the required position.
125
ASSET User Reference Guide
Printing from the Map View
In ASSET, you can print the whole contents of a Map View window, or specific areas of it. You can
also choose to print on paper, or to a file for archiving, including in reports and so on.
Tip: In the Map View, you can also export any of your map layers for use with MapInfo, Google
Earth and ESRI ArcGIS. See Exporting Map Layers using GIS Export on page 435.
Choosing the Legend Information for the Printouts
You can use the Legend tab of the Layer Control Pane to determine which items are shown in
any printouts you make of the Map View.
To do this:
1. In the Map View, in the Layer Control Pane, click the Legend tab.
2. Clear the Show as Print Preview checkbox at the bottom. The items are then shown in a
tree view.
3. Select the checkboxes next to the items in the list that you want to display in the printed
legend.
4. Select the Show as Print Preview checkbox to preview how the items will display on a
printout.
5. To view the layout of your printout, in the Map View, from the File menu, click Print
Preview.
6. When ready, click the Print button.
Customising the Page Layout for Printing
To set up how the contents of the Map View window will print:
1. On the Map View window, from the File menu, point to Print Setup and click Printer and
Page Layout.
The Page Setup dialog box appears; the settings default to those assigned by the
Windows printer driver.
2. Specify the page size, source and orientation and change the printer as required then click
OK.
Tip: Do not change the margins here as these are not used by ASSET.
3. From the File menu, point to Print Setup and click Legend and Title and specify any title,
copyright and comments that you require. The default title is Untitled or the last used title of
the current session.
4. Also choose whether to print the default logo or a different one. As this is a raster format,
you may need to experiment with various image sizes to obtain the best image on the hard
copy printout. Any number of colours can be used (monochrome to 24-bit colour).
5. Select the Print to Scale checkbox if you want to scale your mapping data appropriately.
For example, if a 1:100000 scale is used on the output, every centimetre on the printout will
represent 1 kilometre. The midpoints of the current view are used as the centre of this
printout.
126
Viewing and Editing Networks on the Map
6. Click OK.
7. From the File menu, click the Print Preview button to see what the printout will look like
and to choose where on the page you want the key, the map and the scale. For example:
8. When you are satisfied, either:
o
Print the whole map as shown in the Map View window
o
Print a defined area of the map
o
Print the map or area of map to file
Printing the Whole Map View
To print the whole contents as shown in the Map View window:
1. Set up the page layout as required.
2. From the File menu, click Print.
Printing a Specific Area of the Map View
To print a specific area of map rather than the whole contents of the Map View window:
1. Set up the page layout as required.
2. On the Map View window, from the File menu, click Print Area.
3. Using the cursor, click and drag to select an area of map that you want to print.
127
ASSET User Reference Guide
The Print Preview dialog box appears so you can check the map before printing. Note
that:
o
The scale used is that found in the current view
o
The region displayed may vary so that the scale may be maintained, based on paper
size, layout and so on
o
If you select the Print to Scale option in the Print Legend, only the centre point of the
area selected is used and also depending on paper size and the layout of the print, the
region will most likely be resized to maintain scale
Printing a Map View to File
As well as printing maps or partial maps on paper, you can print them to file. You can choose to
print maps as PDF, TIFF, JPEG, BMP, PNG, GIF, PCX or DCX files using a virtual printer driver
that is installed with ASSET. To do this:
1. Customize the page layout as required.
2. From the File menu, click Print.
3. In the Printer box, select the Universal Document Converter as shown here:
4. Click the Properties button and in the profile box, select the item you require, for example,
Document to PDF, to produce a PDF.
5. On the Image Settings tab, in the Color Depth box, select True Color (24 bit) so that
dithering does not occur and you can see transparency in your files.
6. On the Output tab, it is recommended that you select Prompt for Filename especially if
you are writing to a network folder.
7. For further help on using this printer driver, press F1 in the Properties dialog box.
8. When you are satisfied with your settings, click OK to print the plot.
Using Third Party 3D Visualisation Tools
If the visualisation tools Smart City Explorer and SpaceEyes have been installed, links to them
will be available under Add-Ins from the File menu.
128
Generating Arrays and Reports for Analysis
5 Generating Arrays and Reports for Analysis
This chapter describes how you can manage, display and analyse arrays, and generate statistical
reports, in ASSET Radio or ASSET Backhaul.
Example of array
About Arrays
An array is a pixel-by-pixel view of the predicted performance of a network in terms of coverage or
interference. An array helps to validate the suitability of your network design.
When an array is created, every pixel in the map view is analysed, therefore the size of the array is
directly proportional to the area you want to study. If you have various map data pixel resolutions, it
can be beneficial to produce overview studies of large areas using lower resolution map data, and
then study smaller areas using higher resolution map data.
Arrays can be created in ASSET Radio or ASSET Backhaul. This table provides some useful
information about the basic array types:
Product
Arrays
For Information on
Creating the Arrays
For Array
Descriptions
ASSET Radio
The simulation arrays (all
technologies) are generated either
from the signal coverage wizards or
from a full simulation. Simulations can
be saved as *.3gr files which contain
everything you need to run the
simulation again.
See the ASSET
See the 'Predicting
Technical Reference
Pathloss and Displaying
Coverage' and 'Simulating Guide.
Network Performance'
chapters in the ASSET
Radio User Reference
Guide.
Simulation arrays are generated as
individual Clipboard arrays, and can be
saved, which is useful for comparison
purposes. See About the Array File
Formats on page 130.
129
ASSET User Reference Guide
Product
Arrays
For Information on
Creating the Arrays
For Array
Descriptions
ASSET
Backhaul
MW coverage arrays for ASSET
Backhaul are generated as individual
Clipboard arrays, and can be saved,
which is useful for comparison
purposes. See About the Array File
Formats on page 130.
See the 'Planning
Microwave Links' chapter
in the ASSET Backhaul
User Reference Guide.
See the ASSET
Backhaul User
Reference Guide.
About the Array File Formats
Simulation arrays, coverage arrays and traffic rasters support the following formats:
 MapInfo Vertical Mapper (*.grd) or (*.grc) files, as appropriate to the array type (Float or
Enumerated, respectively).
 Array Clipboard (*.3ga) files
 MMR Array Clipboard (*.mmr) files
 ESRI BIL (*.bil) files
 Geo Tiff (*.Tif) files
For all technologies, the above formats are supported in both the Save and Load operations in the
Array Manager.
For information on the *.3ga format, see the ASSET Technical Reference Guide.
For information on saving and loading files, see Using the Array Manager on page 131.
Important:

The *.grd, *.grc and *.bil formats do not display metadata such as Memory, Resolution,
Region Size.

When using the Array Manager to load *.grd files or *.bil files, we recommend that you:
o
Use the Array Clipboard node when you load coverage arrays.
o
Use the Traffic node when you load traffic rasters.
If you do not follow this recommendation, the accuracy of the data in the loaded file cannot
be guaranteed.
For more information on these formats, see the 'Array File Information (ASC, BIL, GRD, GRC)'
topic in the 'Miscellaneous Vendor and Third Party File Formats' chapter of the ASSET Technical
Reference Guide.
About Large Array Support
If you frequently create large arrays, you can take advantage of the large array support provided in
ASSET. This is applicable to all types of array, for example: simulation arrays,
coverage/interference arrays, traffic arrays, and height or clutter rasters.
130
Generating Arrays and Reports for Analysis
ASSET enables you to set up support for large arrays on the local machine. The process uses a
swapping system, in which a swap folder is used to store the temporary files when more memory is
required. This can significantly increase the RAM available for array creation.
 For information on how to enable Large Array Support, see 'Allowing Large Array Support
on a Machine' in the ASSET Installation and Administration Guide.
 If Large Array Support has been enabled, you can still turn this on or off when working in an
open project. See Enabling or Disabling Large Array Support within a Project on page 46.
Warning: It is strongly recommended to turn off Large Array Support when not creating large
arrays. This is because it consumes a large amount of memory, and can be detrimental to the
general performance of ASSET. It is therefore recommended to only enable the feature when
required. You can contact Product Support for further advice.
Using the Array Manager
The Array Manager provides an array management facility, which enables you to perform memory
management on arrays and simulations. In addition, the Array Manager provides the ability to
retrieve archived arrays, allowing for the benchmarking of statistical changes over time.
The Array Manager is relevant to ASSET Radio and ASSET Backhaul, because arrays can be
created in both.
In the Array Manager, you can:
 View information relating to arrays currently in memory (such as Resolution, Region Size)
 View the progress of the array creation process
 View the number of any unqueued tasks, so that you know how many tasks are remaining
 Load arrays
 Save arrays
 Delete arrays (except Simulation arrays)
 View the data summary of a simulation
 Copy arrays to the Array Clipboard
 Rename Clipboard arrays
 Generate traffic rasters from generic rasters
For information on file formats, see About Arrays on page 129.
Note:
 You can also load arrays generated by ARRAYWIZARD, and perform all the functionality
within ASSET Radio, such as viewing the arrays, running statistics, and so on.
 You can export map layers from the Map View using the GIS Export facility. See Exporting
Map Layers using GIS Export on page 435.
131
ASSET User Reference Guide
To open the Array Manager:
From the Arrays menu, click Array Manager.
This picture shows an example of the Array Manager:
Example of the Array Manager dialog box
By default, all column information (File Name, Resolution, and so on) is displayed, but you can
customise which columns are included by right-clicking any of the column headings:
Example of customising displayed columns in the Array Manager dialog box
The Array Manager also provides colour control options for 'service area' arrays. See 'Service Area
Colouring' in the ASSET Radio User Reference Guide.
132
Generating Arrays and Reports for Analysis
Distributed Processing of Arrays
ASSET Radio enables you to speed up the process of generating predictions and arrays by
distributing them across a number of agent machines on the network. Optionally, multi-core
processors can also be used on the agent machines, for even faster results. For more information
on how this process operates, and how to set it up, see the 'Distributed Tasks' chapter of the
ASSET Installation and Administration Guide.
Saving Arrays
In the Array Manager, you can save arrays if they are currently in memory.
The simulation arrays (all technologies) are generated either from the signal coverage wizards or
from a full simulation. Simulations can be saved as *.3gr files which contain everything you need to
run the simulation again. Individual simulation arrays can be saved to the Clipboard (useful for
comparison purposes) in a variety of formats. See About the Array File Formats on page 130.
To save individual arrays:
1. From the Arrays menu, click Array Manager.
2. Expand the appropriate heading (for example Simulation or Array Clipboard) to find the
individual array(s).
Note: If the individual array is under the Simulation heading, you first need to right-click it
and click Copy to Array Clipboard.
3. Select an individual array that you want to save.
(For some of the file types, you can select multiple items by using the Shift key and/or the
Ctrl key.)
4. Click the Save button.
5. In the Array File Save dialog box:
a. Browse to the folder in which you want to save the file(s).
b. If appropriate, choose the required file type you want to generate.
c. Type a file name (unless you are overwriting an existing file).
6. If you have any planning comments that you want to add to the array header file, doubleclick the Comments field and type your comments.
7. Click the Save button.
This picture shows a scenario where an array has been saved, along with a newer array that has
been created in this session, but not yet saved:
Example of Array Manager, where one array is saved and one is only in memory
133
ASSET User Reference Guide
To save a whole set of arrays:
 For ASSET Radio:
If it is a simulation, select the Simulation heading:
If it is on the Array Clipboard, select the appropriate date-time stamp instance:
 For ASSET Backhaul:
Expand the Array Clipboard heading, and select the Microwave Coverage heading.
Then perform the same steps as above from Step 4 onwards.
Note: When saving an Array Clipboard instance containing many large arrays, it is more memoryefficient if, for each individual array you are interested in, you save it as a separate file, rather than
saving them all (including many unwanted arrays) into one enormous file.
Loading Arrays
In the Array Manager, you can load any arrays that you have saved previously.
To load arrays:
1. From the Arrays menu, click Array Manager.
2. Click the appropriate heading (for example Simulation or Array Clipboard).
3. Click the Load button.
4. In the Array File Selector dialog box, if more than one file type is listed, select the
appropriate type:
5. Select the file name of the appropriate array (or set of arrays), and then click Load.
The required array (or set of arrays) is loaded.
134
Generating Arrays and Reports for Analysis
Important:
 The *.grd, *.grc and *.bil formats do not display metadata such as Memory, Resolution,
Region Size.
 When using the Array Manager to load *.grd files or *.bil files, we recommend that you:
o
Use the Array Clipboard node when you load coverage arrays.
o
Use the Traffic node when you load traffic rasters.
If you do not follow this recommendation, the accuracy of the data in the loaded file cannot
be guaranteed.
(In relation to this, also see the note in 'About Compound Arrays' in the ASSET Radio User
Reference Guide.)
Tip: For most of the file types, you can load multiple files in one operation, by using the Shift key
and/or the Ctrl key.
Note: If you load an array which included a cell or cells that now no longer exist(s) in the database,
you can only use this array for statistical analysis and visualisation purposes. Also, some of the cell
information for the array will be undefined.
Loading Arrays Generated by ARRAYWIZARD
If you are licensed to use ARRAYWIZARD, you can use the Array Manager to load any of the
arrays generated within the ARRAYWIZARD parameter sets (these are automatically retrieved via
the index.text file in the 'Output array directory' specified in your Project Settings). You can then
perform all the functionality within ASSET Radio, such as viewing the arrays, running statistics, and
so on.
To do this:
1. From the Arrays menu, click Array Manager.
2. Click the Load button.
3. In the dialog box that appears, in the file type drop-down list, click the option named 'Array
Wizard Index File':
The Load ARRAYWIZARD Files dialog box appears, listing the items
135
ASSET User Reference Guide
4. Select the appropriate Parameter Set and Array Type from the drop-down lists. Here is an
example:
(The Resolution only needs to be chosen if there are multiple resolution files available.)
5. Click OK.
The required array is loaded.
Note: If you load an array which included a cell or cells that now no longer exist(s) in the database,
you can only use this array for statistical analysis and visualisation purposes. Also, some of the cell
information for the array will be undefined.
Deleting Arrays
In the Array Manager, you can delete any arrays from which are no longer needed, thereby freeing
some memory resources.
To do this:
1. From the Arrays menu, click Array Manager.
2. Either:
o
Click the appropriate heading (for example Simulation or Array Clipboard), if you
want to delete a set of arrays
- or -
o
Expand the heading, and select an individual array that you want to delete.
3. Click Delete.
Tip: For the signal coverage arrays, you can delete multiple items in one operation, by using the
Shift key and/or the Ctrl key.
Note: You cannot delete individual arrays that were produced by the Simulator. However, you can
use the Array Manager to delete the whole simulation from memory.
Viewing Array Progress and Aborting Arrays
In the Array Manager, in the case of Signal Coverage arrays for GSM, UMTS, LTE and 5G, you
can:
 View the progress of an array creation process
 View the number of any unqueued tasks, so that you know how many tasks are remaining
 Abort an array creation process
136
Generating Arrays and Reports for Analysis
To view the progress of an array creation process:
1. Create the array in the usual way.
The Array Manager opens automatically.
2. To see the progress percentage value, look under the Progress column, as in this example:
When the array creation process is complete, this value will become blank.
To abort an array creation that is already in progress:
1. Right-click on the appropriate item.
2. Click Abort, as in this example:
This will halt the array creation process, but will not completely remove the partially created
arrays from memory. To do this, see Deleting Arrays on page 136.
Viewing a Summary of Simulation Data
When you have run a simulation, or loaded a simulation from a file, you can use the Array Manager
to view a summary of the simulation data. To do this:
1. From the Arrays menu, click Array Manager.
2. Select Simulation and click the Properties button.
137
ASSET User Reference Guide
The Simulator Properties dialog box appears:
3. Values shown in blue are editable. To edit them, click Edit Values, make the required
amendments and click OK.
4. Click OK to close the Simulator Properties dialog box.
Displaying Arrays in the Map View
You can display arrays in the Map View. This picture shows an example:
Example of array
138
Generating Arrays and Reports for Analysis
Displaying Arrays
To display an array in the Map View:
1. Ensure the array is in memory. Arrays and simulation data can either be created by the
appropriate wizard, or from files loaded using the Array Manager.
For information on running a simulation or using the array creation wizards, see the ASSET
Radio User Reference Guide.
2. In the Map View, in the Layer Control Pane, click the Data Types tab.
3. In the Data Types list, expand the appropriate array heading, as follows:
o
Signal Coverage arrays for GSM, UMTS, LTE and 5G are listed under the Array
Clipboard heading:
o
Microwave Coverage arrays (ASSET Backhaul only) are also listed under the Array
Clipboard heading.
o
Simulation arrays (all technologies) are listed under the Simulator heading:
o
Signal Coverage arrays for Wi-Fi are listed under the Simulator heading.
4. Select the checkbox of the array you want to display.
5. Click Apply/Redraw.
The array will be displayed on the Map View.
Important: When running the Coverage Analysis wizards for GSM, UMTS, LTE or 5G, it is possible
to select and display the service area array before the processing is complete. When this happens,
the Layer Control Pane may show "no values or too many values" on the Legend tab. In this
situation, ensure you click the Redraw button when the Array Manager dialog shows that the array
is complete.
Tips:
 You can customise the appearance of the arrays. See Customising the Array Display
Properties on page 140.
 You can produce statistical reports from many of the arrays. See Generating Statistical
Reports for Arrays on page 162.
 If you want to zoom to an array that you have just displayed on the Map View, you can use
the 'Zoom to Array' option by right-clicking on the appropriate array in the Data Types list of
the Layer Control Pane.
 For brief descriptions of some of the different types of output arrays, see the ASSET
Technical Reference Guide or the appendix of the ASSET Backhaul User Reference Guide.
139
ASSET User Reference Guide
Customising the Array Display Properties
These instructions correspond to simulation arrays or clipboard arrays. Simulation arrays are
applicable to ASSET Radio, and clipboard arrays are applicable to both ASSET Radio and ASSET
Backhaul.
To customise the display properties of simulation arrays or clipboard arrays:
1. In the Map View, in the Layer Control Pane, click the Data Types tab.
2. In the Data Types list, double-click the appropriate array.
You will find the array either:
o
Under the Simulator heading:
- or o
Under the Array Clipboard heading (this includes Signal Coverage arrays for ASSET
Radio and Microwave Coverage arrays for ASSET Backhaul):
3. For the majority of the array types, the display properties are presented in a large dialog
box that includes a Colours tab with a Schemas button. If this is the case, you can either
customise the display properties specifically for each array type, or you can define your
own sets of display properties (known as schemas), and use them generically across other
array types.
On the Colours tab, you can either:
o
Customise the options by setting the ranges, choosing the colours and (if required)
adding labels. The simplest way to do this is to enter values for Min, Max, Step,
Ranges (you can fix any one of them) and then click Re-Calc. You can also add,
remove or sort ranges manually, using the appropriate buttons. You can then decide to
save this as a schema to be used by other arrays, as described in the following bullet
point.
- or -
o
Click the Schemas button to retrieve a schema that you have already defined, or to
save a schema that you have just created. The Schemas dialog box enables you to
create your own set of customised display schemas, and store them for future retrieval.
You can therefore utilise a small set of schemas across many array types. For more
information, see Defining Display Schemas for Arrays on page 143.
- or -
o
Utilise the Defaults buttons. The Make Defaults button enables you to make the
current display properties into a default, and the Use Defaults button enables you to
retrieve the default. These defaults affect all instances of a single array type. If a
default is overwritten by a new one, the old one cannot be retrieved unless it was
previously saved as a schema.
Note: For a few arrays, the first tab is named differently (for example, Parameters). For
these array types, the display options are more specific, and the Schemas and Defaults
buttons are unavailable.
140
Generating Arrays and Reports for Analysis
4. On the Visibility tab, you can select options for displaying the array only at a particular
zoom level threshold:
o
Use View Zoom Range to set the minimum and maximum distances within which the
array will be displayed according to Distance (North-South) or Distance (East-West).
o
Use Scale Range to set the minimum and maximum scale ratios within which the array
will be visible.
(You can show the scale range for the current Map View in the Map Information
Pane. See Viewing Scale Information Relating to the Current Map View on page 113.)
5. On the GIS Export tab, you can set the default content type for any subsequent GIS-based
exports of this array:
o
Raster Image (you can select from a range of output file types)
o
RLE Rectangles
o
Polygons
For more information on using GIS Export, see Exporting Map Layers using GIS Export on
page 435.
You can also choose between color and numeric pixel types to export. Choosing numeric
enables you to export value based rasters into formats that are compatible for import into
ASSET Web.
6. Click OK.
7. In the Layer Control Pane, click Apply/Redraw. The Map View will now display the array
with the new settings.
Note: The All Servers array display properties are customised in a totally different way, as
described in the following section.
Changing the Display Properties for the All Servers Array
The All Servers array is not a true array, since it is sensitive to the location of mouse cursor. It
displays information about which cells are "covering" each pixel based on the "All Servers" display
properties. A set of lines is drawn between all possible serving cells to the simulation pixel where
the mouse cursor is located. For pixels with more than one covering cell, the line thickness
increases proportionally.
For the All Servers array, you can change whether the display shows covering cells in order of best
server by quality or best signal strength. To do this:
1. In the Map View, in the Layer Control Pane, click the Data Types tab.
2. Double-click the All Servers array in the list of data types.
141
ASSET User Reference Guide
The All Servers Display Properties dialog box appears. Here is an example:
3. Choose the order that you want, and if you select signal strength, ensure you have set the
required threshold on the Array Settings dialog box.
4. Set a thickness for the line that is shown on the Map View. You can choose to display the
serving cells with:
o
Lines only
o
Numbered lines showing the best servers in order
o
Lines only, with the best server highlighted with a marker such as a circle or square
Displaying Outline Boundaries for Best Server Arrays
The enumerated array types, such as Best Server by RSRP, Best DL Cell, and so on, can be
displayed in block or outline mode.
 Block: The array appears in a similar way to most of the other arrays.
 Outline: The array only shows the boundaries of the array. This enables you to display a
separate signal strength array underneath the outline of the best server array, thereby
visualising the cell boundaries in combination with the signal strength.
Here are the Block and Outline options in the Display Properties dialog box:
Display properties for an enumerated array (such as best server)
In outline mode, you can either specify a fixed colour, or just use the same 'category colour' that is
used for the block mode array. For fixed colour, only a single boundary appears. For category
colour, a double (dual-colour) boundary appears, representing each one of the adjoining cell
boundaries.
You can also choose a line width.
142
Generating Arrays and Reports for Analysis
As an example, this picture shows a best server array in outline mode (fixed colour), together with
an underlying signal strength array:
Example of best server array in outline mode, together with signal strength array
Defining Display Schemas for Arrays
For the majority of the simulation arrays or clipboard arrays, a Schemas button is available on the
Display Properties dialog box. This activates a feature enabling you to define your own
customised set of display schemas, and save them for future retrieval for other arrays. This enables
you to utilise a small set of schemas across many of your array types.
Note: Display Schemas are applicable to both ASSET Radio and ASSET Backhaul.
Tip: Each of these array types also has hard-coded default display settings, which you can restore
at any time by clicking the Reset to Defaults button.
To define and save a new display schema at any time:
1. Customise the display properties of an individual array, as described in Customising the
Array Display Properties on page 140.
2. On the Colours tab, click the Schemas button.
143
ASSET User Reference Guide
3. In the Schemas dialog box that appears, right-click a folder, and from the menu that
appears, click Save as New Schema. Alternatively, you can click the Save as New
Schema button.
Tip: You can also create subfolders, if you wish to organise the schemas.
Note: If you want to simply update an existing schema, you can do this by selecting it and
using the Update Schema option.
4. Type a descriptive name for the schema, and click OK.
5. Close the Schemas dialog box. The new schema is now saved for future use, enabling you
to load it for any of the related array types.
Warning: Each time you save a new schema, the units are recorded and you will only be able to
load that schema into an array that uses the same units. For example, if you define and save a
schema for an array which uses % units, you will be unable to load it into an array that uses dBm
units.
Loading Display Schemas into the Array Display Properties
When you have defined and saved any display schemas, you can choose to load any of them into
the display properties of an array. To do this:
1. In the Map View, in the Layer Control Pane, click the Data Types tab.
2. In the Data Types list, double-click the appropriate array.
You will find the array under the Simulator heading:
Or under the Array Clipboard heading (this includes Microwave Coverage arrays for
ASSET Backhaul):
144
Generating Arrays and Reports for Analysis
3. In the Display Properties dialog box that appears, click the Schemas button.
Note: For a few types of array, the Schemas button is unavailable.
The Schemas dialog box appears, and displays a list of the schemas that you have
previously defined and saved:
4. Right-click the appropriate schema, and from the menu that appears, click Retrieve
Schema. Alternatively, you can click the Retrieve Schema button.
Tip: As an alternative shortcut, you can simply double-click the schema.
5. The selected schema is now loaded into the array's display properties (the Schemas dialog
box closes automatically).
6. In the updated Display Properties dialog box, click OK.
7. In the Layer Control Pane, click Apply/Redraw. The Map View will now display the array
with the selected settings.
Producing Delta Difference Plots
You can compare the effect of different arrays by producing delta difference plots manually if you
have not already generated them automatically with the Simulator Wizard (for more information,
see Using the Simulator Wizard in the ASSET Radio User Reference Guide).
To produce a delta difference plot:
1. Use the Coverage Wizard or Simulator to generate a set of arrays from which one can be
chosen as a baseline against which a comparison can be made.
2. In the Map View, on the Data Types tab of the Layer Control Pane, right click on the
required array and select Compare Baseline, then click Set Baseline.
Note: the Compare Baseline option is only available for arrays based on numerical values
such as Best SS-RSRP, and is not available for non-numerical arrays such as Best Server
by SS-RSRP.
The baseline coverage is shown on the Map View.
3. On the Data Types tab of the Layer Control Pane, right click on the array that you wish to
compare against the baseline and select Compare Baseline, then Delta Difference.
145
ASSET User Reference Guide
The difference in coverage between the baseline array and the comparison array is shown
in the Map View and a Delta node is added and shown as selected on the Data Types
tab.
Instead of selecting Delta Difference from the right-click menu at step 3, you can choose one of
four other options. This table describes them:
Option
Description
Combine (Max)
Plots the maximum combined effect of both baseline and comparison arrays. Like Delta
Difference, this is based on numerical values.
AND
Plots the effect of the AND logical operator on baseline and comparison arrays where
both are above threshold (TRUE).
OR
Plots the effect of the OR logical operator on baseline and comparison arrays where
either one or the other or both are above threshold (TRUE).
XOR
Plots the effect of the XOR logical operator on baseline and comparison arrays where
either one or the other but not both are above threshold (TRUE).
Note: The threshold referred to in the above table is the minimum value of the KPI category.
As with Delta Difference, if you select one of these options an additional node reflecting your
choice is generated on the Data Types tab.
Baseline Comparison
You can visualize the effect of network changes in the Map View by running the Coverage Wizard
or Simulator twice and comparing a baseline array from the first run with the equivalent delta array
from the second.
To compare arrays:
1. Generate a set of arrays from which one can be chosen as a baseline against which a
comparison can be made.
2. In the Map View, in the Data Types tab of the Layer Control Pane, right click on the
required array and select Compare Baseline, then click Set Baseline.
Note: the Compare Baseline option is only available for arrays based on numerical values
such as Best SS-RSRP, and is not available for non-numerical arrays such as Best Server
by SS-RSRP.
The baseline coverage is shown on the Map View.
3. Make your network changes and generate a modified set of arrays from which the
equivalent array to the baseline array can be selected for comparison.
4. On the Data Types tab of the Layer Control Pane, right click on the modified array and
select Compare Baseline, then Delta Difference.
The difference in coverage between the baseline array and the modified array is
automatically redrawn in the Map View and a Delta node is added and shown as selected
on the Data Types tab.
146
Generating Arrays and Reports for Analysis
Tip: Instead of selecting an individual array as the baseline, you can select the date-time stamp
indicating when the coverage wizard or simulator ran. This picture shows an example:
Having done this, when you subsequently select an array to compare against the baseline, the
equivalent baseline array is automatically allocated from those under the selected date-time stamp.
Instead of selecting Delta Difference from the right-click menu at step 4, you can choose one of
four other options. This table describes them:
Option
Description
Combine (Max)
Plots the maximum combined effect of both baseline and comparison arrays. Like Delta
Difference, this is based on numerical values.
AND
Plots the effect of the AND logical operator on baseline and comparison arrays where
both are above threshold (TRUE).
OR
Plots the effect of the OR logical operator on baseline and comparison arrays where
either one or the other or both are above threshold (TRUE).
XOR
Plots the effect of the XOR logical operator on baseline and comparison arrays where
either one or the other but not both are above threshold (TRUE).
As with Delta Difference, if you select one of these options an additional node reflecting your
choice is generated on the Data Types tab and the Map View is automatically redrawn.
Using Graphical Analysis
You can use histograms and Cumulative Covered Area line graphs to visualize data.
You can also make comparisons between graphs of the same array type.
To view a histogram or line graph for a generated array:
1. In the Map View, in the Layer Control Pane, right-click on the required array under
Simulator or Array Clipboard.
2. Click Graphs.
Note: This option is only available on the right-click menu for array types for which the
Statistics option is also available.
147
ASSET User Reference Guide
The Array Graph dialog box appears. This picture shows an example:
3. In the Types of Graph pane, the Histogram and Covered Area [km2] options are initially
selected by default.
You can choose to:
o
Select the No. Of Bins (pixels) option to change the y-axis for the Histogram
o
Clear the Histogram option and select the Covered Area [%] option to show the line
graph only
o
Select both the Histogram and the Covered Area [%] options as shown in the
example, in which case the y-axis for the line graph appears on the right
You can also compare graphs of the same array type that you have in the Array Clipboard.
Note: To compare a Simulator array with a Coverage array you must display the graph for the
Simulator array first.
To compare graphs:
1. Display the graph for the first array as described above.
2. Click the Choose button.
If you are using the Tiled View, you will need to undock the graph in order to see the
Choose button.
3. In the Select Multiple Arrays for Comparison dialog box, in the Comparison Sources
pane, use the checkboxes to select up to two of any available arrays.
Tip: You can click on Histogram Color and Line Color to change the representation of
the arrays.
4. Click Apply. The comparison plots are displayed as shown in the example.
148
Generating Arrays and Reports for Analysis
About the Pixel Analyser
The Pixel Analyser is a separate window that can be placed alongside a Map View window to help
with the analysis of all kinds of array information that has been generated during planning.
Note: The Pixel Analyser is relevant to ASSET Radio and ASSET Backhaul, because arrays can
be created in both. However, in ASSET Backhaul, not all of the options are relevant or available.
For ASSET Radio, this enables you to visually analyse network information (for any of the
technology types), such as signal strength or signal quality, or output from the Simulator.
For ASSET Backhaul, this enables you to visually analyse network information such as received
power, field strength or fade margin from the Microwave Coverage arrays.
In addition, you can also choose to view information relating to:
 Clutter and Heights map data
 Traffic arrays
 Clipboard arrays
The ability to read pixel-specific values from the Map View provides an invaluable resource for
analysis, planning, problem solving and improvement of the network performance. Here is an
example of the Pixel Analyser window:
Example of Pixel Analyser window
149
ASSET User Reference Guide
The Pixel Analyser can be used to perform two primary functions:
 Viewing pixel-specific information about arrays
 Exporting the pixel-specific information to a report or file
For information on how to set up and use the visual analysis functionality, see Using the Pixel
Analyser to View Information on page 150.
For information on exporting information to a report or file, see Using the Pixel Analyser to Export
Array Data on page 157.
Using the Pixel Analyser to View Information
You can use the Pixel Analyser to view information for any selected pixel in the Map View
window.
Note: The Pixel Analyser is available in both ASSET Radio and ASSET Backhaul. The options
available may vary depending on your product and technology licences.
To use the Pixel Analyser:
1. Depending on your particular requirements, ensure you have:
o
Simulation data in memory
- and/or -
o
Traffic arrays in memory
- and/or -
o
Clipboard arrays in memory
- and/or -
o
Clutter or Heights data shown on the map
Note: In the case of ASSET Backhaul, the created arrays are always equivalent to
clipboard arrays.
Tip: Simulation data and arrays can either be created by the appropriate wizard, or from
files loaded using the Array Manager.
2. In the Map View window, click one of the Pixel Analyser buttons
.
This Button
Or Key Press Enables you to
Pixel Analyser
Ctrl+T while on
the Map View
Dynamically view information about values for any pixel on the
Map View window by moving the mouse cursor over the map.
This mode operates dynamically with the mouse cursor.
Pixel Select
Ctrl+S while on
the Map View
Select a specific pixel by clicking on the Map View window. The
displayed values will not change until you click on another pixel
on the Map View.
This mode enables you to keep a pixel's values fixed in view if
you want to check values in other windows, such as in the Site or
Link Database.
Esc while on the Deactivate both the modes, whilst keeping the Pixel Analyser
Map View
window open.
150
Generating Arrays and Reports for Analysis
The Pixel Analyser window opens. Any of the arrays or data in memory and their values
per pixel can be displayed in the first pane. For ASSET Radio only, the available cells per
pixel and their values can be displayed in the second pane, and you can also choose to
display a vector analysis plot in the third pane.
3. To customise the content of the Pixel Analyser window, you can either use the Options
menu at the top of the window, or, in some cases, double-click on the relevant pane. This
table lists the options:
Option
Description
Applicable to
Array Row
Selection Details
See Selecting the Arrays to Display in the Pixel
Analyser on page 152.
ASSET Radio
ASSET Backhaul
Pixel Column
Selection Details
See Setting the Pixel Column Details in the Pixel
Analyser on page 153.
ASSET Radio
Vector Analysis
Plot Details
See Displaying Vector Analysis Plots on page 155.
ASSET Radio
Grid Export
See Exporting Array Data to a Report for a Single Grid
Location on page 158.
ASSET Radio
ASSET Backhaul
Point Export
See Exporting Array Data to a Report Based on Multiple ASSET Radio
Points on page 159.
ASSET Backhaul
Coordinate Display
Enables you to show the pixel location at the bottom of
the window as Long-Lat, Decimal Long-Lat or EastingNorthing.
ASSET Radio
ASSET Backhaul
4. When you are satisfied with the options you have set, place the cursor on the Map View,
and you will notice a
symbol appears.
5. To display the information per pixel in the Pixel Analyser window, either move the cursor (if
in Pixel Analyser mode) or click on a specific pixel (if in Pixel Select mode).
In the Pixel Analyser window, the pixel-specific values change as you move or click the cursor on
the Map View. Here is an example:
Example of Pixel Analyser window
151
ASSET User Reference Guide
Tips:
 If you want to list the arrays in a particular sequence (for easier network analysis), you can
drag and drop the rows in the top pane of the Pixel Analyser window.
 In the case of ASSET Radio, you can click any of the column headers in the second pane
to sort information in ascending or descending order. For example, to find the best server
using the Pixel Analyser, sort the cells by the Pilot Power column, which enables you to
compare the other cells with the best server.
 At the bottom of the Pixel Analyser window, the following useful data is displayed:
o
The pixel location (customisable via the Options menu)
o
The height data of that pixel
o
The clutter type of that pixel
o
The nearest cell to that pixel (ASSET Radio only)
The above items only update when you click or move the cursor on the Map View. Also,
height and clutter will only appear if you have displayed them in the Map View at least
once in the session, so that they are in memory.
 You can export pixel-specific information to a report or file. See Using the Pixel Analyser to
Export Array Data on page 157.
 There is an Options pane at the bottom of the window, providing extra functionality. See
About the Options Pane on the Pixel Analyser on page 156.
Selecting the Arrays to Display in the Pixel Analyser
Note: The selection of arrays to analyse is relevant to both ASSET Radio and ASSET Backhaul. In
both cases, the arrays available will be those that are currently in memory. (The example picture
below relates to ASSET Radio, but the principle is exactly the same for ASSET Backhaul.)
To select and customise the arrays (in the first pane) that you wish to analyse per pixel:
1. In the Pixel Analyser window, double-click anywhere in the first pane.
The Select Array Rows dialog box appears.
2. In the Available Arrays pane, expand the appropriate categories and then double-click the
arrays that you want to analyse.
Tip: You can limit the arrays listed in the Available Arrays pane to those used in the
Simulator by selecting the Restrict to sim enabled arrays checkbox.
3. Select the Chart checkbox for each array if you would like the chart to be displayed too.
Here is an example of a 'chart':
4. Set the Min and Max values for the chart by clicking the value boxes for the array, and then
entering values.
152
Generating Arrays and Reports for Analysis
Here is an example:
5. When you have finished, click OK.
Tip: After this, if you want to list the arrays in a particular sequence (for easier network analysis),
you can drag and drop the rows in the top pane of the Pixel Analyser window.
Setting the Pixel Column Details in the Pixel Analyser
Note: The selection of column details for cells/carriers is only relevant to ASSET Radio (not ASSET
Backhaul).
To select and customise the columns (in the second pane) that you wish to display for the
cells/carriers:
1. In the Pixel Analyser window, double-click anywhere in the second pane.
The Column Details dialog box appears.
2. If you are using more than one technology, click on the appropriate technology tab.
3. Select the columns you want to be displayed in the Pixel Analyser.
153
ASSET User Reference Guide
4. For some of the items, you can select or deselect the Chart checkbox. (To do this, you
must select the item first.) This allows you to display a chart in the Pixel Analyser, and set
the Max and Min values for the chart. Here is an example of a chart:
5. For some of the items, you can set the required threshold. (To do this, you must select the
item first.) Here is an example:
When a threshold is used in the Pixel Analyser, only cells with pixel values equal to or
greater* than the stated threshold will be displayed (*less than, in the case of link loss).
Note: In the Pixel Analyser window, you can only use one threshold at time. To turn one of
them on, you must right-click on the specific column header. To turn it off, you can rightclick on it again. The Options pane shows which threshold (if any) is currently applied see About the Options Pane on the Pixel Analyser on page 156.
6. When you have finished, click OK.
In the Pixel Analyser window, the second pane displays the column details according to what you
have specified. Here is an example:
Note: In the Pixel Analyser window, if you want to use one of the thresholds, you must right-click on
the specific column header. To turn it off, you can right-click on it again.
The values displayed for each of the columns are those derived from the simulation currently in
memory. Most of the column headings are self-explanatory. The following table clarifies the
purpose of some of the columns:
154
This Column
Displays
Relative
Difference between the Rx Pilot Power of the cell and that of the topmost sorted
item.
Distance
Distance of the cell from the selected pixel.
Bearing
Bearing of the antenna for the cell.
Neighbours
Yes/No to indicate whether the cell is a neighbour of the cell in the topmost sorted
item.
Generating Arrays and Reports for Analysis
This Column
Displays
Co Channel / Adjacent
Channels (GSM only)
Yes/No to indicate whether the cell has a cell or carrier layer that is the same as (or
adjacent to) that of another cell.
Line of Sight
Yes/No to indicate whether there is a clear line of sight between the pixel and the
cell.
Warning: This option may slow down the operation of the Pixel Analyser, so it is
recommended only to activate this when you need it.
Note: The exact combination of details will vary according to the technology.
Displaying Vector Analysis Plots
Note: Analysis of vectors is only relevant to ASSET Radio (not ASSET Backhaul).
You can use the Pixel Analyser to display analysis plots of any vector/polygon chosen from your
Map View.
To customise the vector analysis plot within the Pixel Analyser:
1. In the Pixel Analyser dialog box, double-click anywhere in the third pane. The Vector
Analysis Plot Details dialog box appears.
2. Select one of the radio buttons to choose which covering cell levels along the vector you
want to be plotted.
3. Enter the number of 'Best Values' to take into account (each will display its own coloured
plot line).
4. Enter a Step value for the X axis (this determines the plot intervals along the linear distance
of the vector).
5. Enter Min and Max values for the Y axis.
6. When you have finished, click OK.
To activate the vector analysis plot (in the third pane):
1. Ensure you have your required vector/polygon displayed in the Map View window.
2. If the Options pane at the bottom of the Pixel Analyser window is not already open, click
the
button.
3. Select the Vector Analysis checkbox.
4. Click the 'Select Vector On View' button.
5. On the Map View, use the cursor to select a vector/polygon. Here is an example:
155
ASSET User Reference Guide
6. When you have selected a vector/polygon, it becomes highlighted, and the
symbol
appears. You can then either move the cursor (if in Pixel Analyser mode) or click on a
specific pixel (if in Pixel Select mode) along the vector.
As you move (or click) along the vector, you can see the analysis plots in the third pane of
the Pixel Analyser. The display format depends how you chose to customise the analysis
plot. Here is an example:
Notes:
o
In Pixel Analyser mode, the cursor is sensitive exclusively to points along the
vector/polygon. Therefore, if you place the cursor away from the vector, the cursor will
simply react to the nearest point on the vector. This is true for both the analysis plot,
and for the pixel values in the first and second panes of the Pixel Analyser window.
o
If you wish to select a different vector/polygon, you must click the 'Select Vector On
View' button again. If you wish to zoom or pan in the Map View, you must also
reactivate the required mode.
About the Options Pane on the Pixel Analyser
The Options pane of the Pixel Analyser window enables you to do the following:
 Select the layer to view, if multiple technologies or carriers were included in the simulation.
This will display cells of that technology only, and/or using that carrier only.
 Compare cell values over two locations. See Comparing Cell Values over Two Locations.
 Activate the vector analysis plot. See Displaying Vector Analysis Plots on page 155.
 Quickly change the display precision (decimal places) shown for the arrays. This means
you can increase the precision when analysing full-precision array types (such as traffic),
but then easily revert to a lower precision for low-precision array types.
 Check whether one of the display thresholds is applied or not. See Setting the Pixel
Column Details in the Pixel Analyser on page 153.
156
Generating Arrays and Reports for Analysis
To view the Options pane of the Pixel Analyser window, click the
button.
Here is an example:
Example of the Options pane in the Pixel Analyser
Comparing Cell Values over Two Locations
When using the Pixel Analyser, you can see the effects on the same cells in two different
locations. This is useful for checking how any particular cell behaves in other pixels. To do this:
1. Set up the Pixel Analyser, as described in Using the Pixel Analyser to View Information on
page 150.
Note: This method requires that you start the process in Pixel Select
mode.
2. In the Pixel Analyser window, ensure the Options pane is displayed by clicking the Up
Arrow button
.
3. In the Pixel Data Update pane, choose to automatically display all cells per pixel, then click
the cursor on the map to a location whose cells you want to compare with another location.
4. In the Pixel Data Update pane, choose the Frozen option. This will retain the list of cells
shown for the current pixel.
5. Now click (or move the cursor if you have switched to Pixel Analyser mode) on another
location in the Map View, and the Pixel Analyser shows updated information for both the
original cells and for all the new cells relevant to the new pixel location.
6. You can click the Refresh button whenever you want to refresh the data so that only values
for the last clicked pixel are shown.
Using the Pixel Analyser to Export Array Data
You can use the Pixel Analyser to export pixel-specific array data to a report or file. There are two
different ways of exporting the data, a simple single grid location, and a more complex export
based on multiple points.
For more information, see:
 Exporting Array Data to a Report for a Single Grid Location on page 158
 Exporting Array Data to a Report Based on Multiple Points on page 159
157
ASSET User Reference Guide
Exporting Array Data to a Report for a Single Grid Location
When using the Pixel Analyser, you can export the pixel data to a report for a single grid location,
for comparisons with other results.
Note: The generated information depends on what you have enabled in the first and second panes
of the Pixel Analyser window.
To do this:
1. Set up the Pixel Analyser, as described in Using the Pixel Analyser to View Information on
page 150.
2. Select a pixel on the Map View by moving the mouse cursor or clicking.
(This depends on which button
mode is being used.)
3. From the Options menu of the Pixel Analyser window, select Grid Export:
4. In the dialog box that appears, select how you want to output the report.
Example Reports for a Single Grid Location
These pictures show examples of the reports that can be generated for a single grid location.
Note: The information for each selected array appears on a separate report or worksheet
(depending on your chosen output report format).
Example of information relating to the first pane of the Pixel Analyser window
158
Generating Arrays and Reports for Analysis
Example of information relating to the second pane of the Pixel Analyser window
Exporting Array Data to a Report Based on Multiple Points
ASSET Radio enables you to:
 Generate reports that provide coverage and quality analysis on a 'per subscriber' basis.
This may be particularly useful where networks are based on fixed subscribers, where the
location of the terminal/CPE is always known to the operator. Given that you can define
subscribers using 'points' within vector files, you can use the Pixel Analyser window to
select a single or multiple vector files containing point features, and then generate a report
or file containing the value for each of these point features from all your chosen arrays in
the Pixel Analyser.
Here is an example of some points displayed on the Map View:
 Generate reports or files that provide coverage and quality analysis along a line or around a
polygon, at a user-specified step interval. This may be particularly useful, for example, to
show the received power on a railway line, at 'walked' step points along the line. The
resulting report or file contains the pixel value for each of these step points from all your
chosen arrays in the Pixel Analyser. For each step point, the report displays the location
coordinates of the point, all feature attributes, and the corresponding value from the
reported array(s).
Here is an example of a line and a polygon displayed on the Map View:
In the case of multiple chosen arrays and/or multiple chosen vectors, these are reported on
separate pages, each headed with the array name and vector name.
For each point/line/polygon feature, the report displays the location coordinates, all feature
attributes, and the corresponding value from the reported array(s).
159
ASSET User Reference Guide
Notes:
 This option is specifically for use with vector files containing one or more point/line/polygon
features. If a selected vector file contains a mixture of features, only line, polygon or point
features are used for this functionality. For more information on using vector files, see
Using Vector File Features on page 251.
 The generated information depends on which arrays you have enabled in the first pane of
the Pixel Analyser window (the second pane is not applicable to this report).
 In the case of multiple chosen arrays and/or multiple chosen lines or polygons, these are
reported on separate pages, each headed with the array name and line/polygon name.
 An extra step point is always created at the end of the line or polygon edge, so the distance
between the last two step points may be less than the specified step interval.
To export array pixel data to a report based on points, or step points along a line or polygon
edge:
1. Ensure you have some vector files containing point, line or polygon features.
2. Set up the Pixel Analyser, as described in Using the Pixel Analyser to View Information on
page 150.
(However, for this process, you do not need to manually select pixels with the Pixel
Analyser buttons.)
3. From the Options menu of the Pixel Analyser window, select Point Export Options:
The following dialog box appears:
160
o
Select how you want the coordinate information to be displayed
o
Specify the step distance in the Scan Point Interval edit box (only relevant for lines or
polygons)
o
Click OK
Generating Arrays and Reports for Analysis
4. From the Options menu of the Pixel Analyser window, select Point Export:
5. In the Select Vectors dialog box that appears, select the required vector(s), and click OK.
6. In the dialog box that appears, select how you want to output the report.
Example Reports for Multiple Points
These pictures show examples of the reports that can be generated for points, lines and polygons.
Note: The information for each selected array appears on a separate report or worksheet
(depending on your chosen output report format).
Point Features Only
Example report:
Example of report showing ‘Point Features’ analysis data for an array selected in the Pixel Analyser
Point, Line and Polygon Features
161
ASSET User Reference Guide
The vector file used to produce this example included a line, a polygon and some points:
Example of report showing ‘Point, Line, Polygon edge’ analysis data for an array selected in the Pixel Analyser
Generating Statistical Reports for Arrays
Statistical reports enable you to produce area and percentage statistics for arrays. They can only
be generated after creating the relevant array.
Note: Statistical reports are available in both ASSET Radio and ASSET Backhaul. The options
available may vary depending on your product licences.
The report sections (that is, the rows) can show overall statistical summaries, comparing the area
satisfying the target level with the total area analysed, giving the result as a percentage of the total.
The area statistics can also be broken down by:
 Clutter type
 Individual cells (ASSET Radio)
 Individual carriers (ASSET Backhaul)
 Specific vectors
 Specific features (such as lines, polygons, roads) of a vector
Tip: For information on creating vectors, see Using Vector File Features on page 251.
Furthermore, you can incorporate distributional statistics (such as population), which appear as
additional columns in the report. These are obtained from traffic values which have been spread by
a traffic raster. If you wish to do this, check that the relevant traffic raster has already been saved to
file. For more information, see 'About Distributional Statistics' in the ASSET Radio User Reference
Guide.
162
Generating Arrays and Reports for Analysis
To create a statistical report for an array:
1. Ensure that the array is in memory. Arrays and simulation data can either be created by the
appropriate wizard, or from files loaded using the Array Manager.
2. Open a Map View (if not already open). Ensure that this includes the area for which you
want to generate statistics.
Note: If this view area is different from the one originally used to create the array, the
statistics will be based on the intersection of the two areas. It is also possible to focus the
statistics within selected vectors.
3. On the Map View toolbar, click the
button.
4. In the Layer Control dialog box, click the Data Types tab.
5. In the Data Types list, expand the appropriate array heading, as follows:
o
Signal Coverage arrays for GSM, UMTS, LTE and 5G are listed under the Array
Clipboard heading:
o
Microwave Coverage arrays (ASSET Backhaul only) are listed under the Array
Clipboard heading:
o
Simulation arrays (all technologies) are listed under the Simulator heading:
o
Signal Coverage arrays for Wi-Fi are listed under the Simulator heading.
6. Select the required array, right-click on it, and click Statistics. This picture shows an
example:
The Statistics dialog box appears. The options are described in the following section.
163
ASSET User Reference Guide
Using the Statistics Dialog Box
After the preparatory steps described in the previous section, the Statistics dialog box appears,
showing the area information for the rectangular area displayed in the current Map View.
You now have several options:
1. In the Analysis Area pane:
If you want to focus the statistics in a specific area or areas within the respective Map View
(rather than the whole rectangular area), enable the 'Restrict analysis area to within one
or more vectors' checkbox, and click Select. In the dialog box that appears, select one or
more vectors, and click OK. Here is an example where two vectors are selected:
If you choose not to do this, the statistics will be based on the whole rectangular area.
Note: If you have already used the 'Restrict Output Arrays to Vectors' option in the
Coverage or Simulator wizards, the report's analysis area will be automatically restricted,
as in this example:
Important: When this the case, you must only run these statistics on the most recently
created array.
2. In the Report Sections pane:
164
o
Choose which results you want to be displayed in the report. You can select any
combination of 'Statistics summary', 'Category summary', 'Per clutter' and 'Per
cell' (ASSET Radio) and 'Per carrier' (ASSET Backhaul) by selecting the appropriate
checkbox(es).
o
You can also show a breakdown of the results for selected vectors. To do this, select
the 'Per vector' checkbox, and click Select. In the Select Vectors dialog box, select
one or more of the available vectors, and click OK. You should ensure that chosen
vectors are within the area(s) chosen in the Analysis Area pane. The area of each
chosen vector will be treated independently of other vectors, and thus independently of
any overlapping areas, such that each pixel may be counted multiple times.
o
You can also show a breakdown for features within a specific vector. This may be
useful when your vectors contain multiple features, and also if you want to see attribute
values (such as road names) in the report. To do this, select the 'Per feature'
checkbox, and then click Select. In the Select Vector dialog box, select only one of
the available vectors, and click OK. You should ensure that this vector is within the
area(s) chosen in the Analysis Area pane. You must also ensure that the Attribute
Generating Arrays and Reports for Analysis
name columns are specified in the Vector Structure Editor (see Defining Attributes
for a Vector File Feature on page 264).
If you have selected the 'Per feature' checkbox, another checkbox named 'Use pixel
factoring' is available (only significant if the chosen vector contains more than one
feature). Select this option if, across all features, you want each pixel to be counted
only once. The feature that each pixel is assigned to is determined by the order of the
feature within the vector's *.tab file. De-select this option if you want each feature to be
treated independently of overlapping areas from other features, such that each pixel
may be counted multiple times.
3. In the Column Breakdown pane, you can choose the column information that you want to
incorporate in the report:
You must choose at least one of the following options:
o
If you want to report on the amount of area covered, select 'Area values'.
o
If you want to report on distributional statistics (such as population), select 'Raster
values', and then browse to the saved traffic raster from which you want these values
to be obtained. You can also type a name to appear on the headings for these extra
columns, so that the report clearly shows what the units represent.
Note: These distributional statistics are obtained from traffic values which have been
spread by a traffic raster. For this purpose, the traffic values are considered as
distribution 'units'. It is essential that the relevant traffic raster has already been saved
to file (rasters in memory cannot be used for this purpose).
4. In the Pixel Criteria Definition pane, choose the categories to base the report on:
Pixel Criteria option Description
Single category
(specific)
Reports on levels within a single category. Select a category from the
drop-down box. The options are in accordance with the schema
associated with the array.
Single category (low to
high)
Reports on levels that fall within the limits of two chosen categories.
Select a lower and higher category from the drop-down boxes. The
options are in accordance with the schema associated with the array.
Single category (low to
high) - absolute values
Reports on levels within a single category. Enter your own range using
absolute values, regardless of schemas.
Note: To prevent the inclusion of pixels representing "no data", avoid
having the value -200 within your range when using this method.
Multiple categories
Reports on levels for each and all of the categories, in accordance
with the schema associated with the array. You can choose to make
the reported values Cumulative or Non-Cumulative across the
categories.
Note: The availability of these options may vary according to the array type.
165
ASSET User Reference Guide
5. Click Generate.
6. In the Reporting dialog box that appears, choose how you would like to view the report.
7. Click OK.
Results of the Statistical Reports for Arrays
Depending on the options you select in the Statistics dialog box, the report you create can display
the following sections:
 The analysis parameters such as the coverage or quality level selected, and any area
restriction vectors selected
 Statistics and Category summaries
 Statistics broken down by:
o
Clutter type
o
Cell (ASSET Radio)
o
Carrier (ASSET Backhaul)
o
Chosen vector(s)
o
Feature within a chosen vector
The following tables describe the values that you can choose to include in the rows of the statistical
reports:
Statistics summary
Description
Total 2D View Area (km2)
The chosen area of analysis. This is either the area of the selected
Map view, or, if you selected to restrict the analysis area, the sum
of the area within the chosen vector(s).
Covered Area (km2)
The total area within the specified levels.
Covered Area (%)
The covered area as a percentage of the total displayed area.
Category summary
Description
Category information
Category names and ranges of values.
2
166
Covered Area (km )
The total area within the specified levels.
Covered Area (%)
The covered area as a percentage of the total area.
Per Clutter statistics
breakdown
Description
Total Area by Clutter category
For each clutter category, the area that exists in the chosen area of
analysis.
Covered Area (km2)
For each clutter category, the amount of its area within the
specified levels.
Covered Area (%)
For each clutter category, the percentage of its area within the
specified levels.
Generating Arrays and Reports for Analysis
Per Cell statistics breakdown Description
(ASSET Radio)
Total Area of the Cell coverage
(service area)
For each cell, the total of its (best server) service area that exists in
the chosen area of analysis.
Note: For each pixel, only the best serving cell is considered.
Covered Area (km2)
For each cell, the amount of its service area within the specified
levels.
Covered Area (%)
For each cell, the percentage of its service area within the specified
levels.
Per Carrier statistics
breakdown
(ASSET Backhaul)
Description
Total Area of the Carrier coverage
(service area)
For each carrier, the total of its (best server) service area that
exists in the chosen area of analysis.
Note: For each pixel, only the best serving carrier is considered.
Covered Area (km2)
For each carrier, the amount of its service area within the specified
levels.
Covered Area (%)
For each carrier, the percentage of its service area within the
specified levels.
Per Vector statistics
breakdown
Description
Total Area of each chosen vector
The total area of the vector that exists in the chosen area of
analysis.
Covered Area (km2)
The total area within the specified levels.
Covered Area (%)
The covered area as a percentage of the total area.
Per Feature statistics
breakdown
Description
Total Area of each feature* that is
contained in the chosen vector.
The total area of the feature that exists in the chosen area of
analysis.
(*roads, lines, polygons, and so on) Attribute values (road name, road number, building name, and so
on) can also be shown, depending on the configuration in the
vector's structure editor. See Defining Attributes for a Vector File
Feature on page 264.
Covered Area (km2)
The total area within the specified levels.
Covered Area (%)
The covered area as a percentage of the total area.
167
ASSET User Reference Guide
Distributional Statistics (such as population)
This is an optional further breakdown of the results into columns, giving values for distribution units.
Distributional statistics
Description
Distribution units covered
For each of the above (Summaries, Clutter, Cell and Attribute), the
distribution units within the specified levels.
Distribution units covered (%)
For each of the above (Summaries, Clutter, Cell and Attribute), the
percentage of the distribution units within the specified levels.
Note: ASSET Radio calculates its area statistics by counting pixels at the particular resolution.
MapInfo, in contrast, calculates the complete area of a polygon. This is the reason for any
discrepancy between corresponding areas in each program.
How Polygons are considered in the Statistical Analysis
The following information may be useful to clarify how ASSET calculates polygons for the statistical
analysis (reports).
 ASSET calculates the area statistics by counting pixels (at the chosen resolution). MapInfo,
in contrast, calculates the complete area of a polygon. This is the reason for any
discrepancy between corresponding areas in each program.
 The total area of the polygon is based on the total number of pixels within the rasterised
polygon. Only pixels that are completely inside the polygon are counted.
 The statistics are calculated with regard to the terrain heights, but the pixels are considered
as being on a flat surface.
168
Changing How Data Appears on the Map
6 Changing How Data Appears on the Map
This chapter describes how you can control the selection and appearance of the data displayed in
the Map View window.
Controlling the Selection and Appearance of the Data
In general, whenever you want to select which items to display on the map, or customise their
appearance:
1. In the Map View, in the Layer Control Pane, click the Data Types tab.
2. In the list of data types, select the checkbox next to each item that you want to display on
the map.
3. If you want to customise the display properties of an item, double-click the item name.
4. In the Display Properties dialog box, change the characteristics as required. The options
vary according to which item you have selected.
5. Click Apply/Redraw.
The following sections describe more specific customisation procedures.
Customising How Text is Displayed
The textual data that is available to you depends on the map data used but would typically include
classes such as Roads, Cities and Towns.
To customise how text appears in the Map View window:
1. In the list of data types, expand Text and double-click the item you want to customise.
2. In the dialog box that appears, enter the required information as shown here:
On this tab
You can
Font
Select the font and font size.
Background
Select the On option if you want to apply a background to your
text.
Overlap
Select options to automatically reduce overlapping text.
GIS Export
Select the content type for the GIS Export, and, in the case of
Raster image, the type of output file. For more information, see
Exporting Map Layers using GIS Export on page 435.
Visibility Settings
Select options for changing the visibility of the text:

Always

View Zoom Range - set the Min. and Max. distances within
which it will be visible. You can base this on Distance (EastWest) or Distance (North-South)

Scale Range - set the Min. and Max. scale ratios within which
it will be visible
Tip: You can show the scale range in the Map Information pane.
See Viewing Scale Information Relating to the Current Map View
on page 113.
169
ASSET User Reference Guide
Customising How Height Data is Displayed
To customise how height data appears in the Map View window:
1. In the list of data types, expand Height & Clutter Data and double-click the item you want
to customise (Height Block or Height Contour).
Important: If you want to display either of these items, ensure that the corresponding
checkbox in the list of data types is selected when you have finished customising. This is
the overall control for whether it shows in the Map View window.
2. In the dialog box that appears, enter the required information as shown here:
On this tab
You can
Height
Select the start colour from the palette, then specify the minimum height value
and the height step interval. If required, you can use the range value as a
display limit.
Select the Shading checkbox for a simple 3D effect to highlight the hill effects
(shading is not available for Contours).
Choose which resolution method you want to use.
Either:

Select a resolution from the drop-down list.
- or 
Specify a resolution (by typing any value in the box) and select the Multi
Res checkbox. A deterministic conversion process is used to display the
specified resolution. This may be especially useful if you want to visualise a
specific resolution that you have used for your pathloss predictions or
arrays. You can also select the Smooth checkbox to enable linear
smoothing, which helps to minimise any edge effects between different
resolutions.
Tip: You can also enable automatic selection of the best resolution as you vary
the zoom level, by selecting the Auto Res checkbox. See Using the Automatic
Map Resolution Option on page 172.
Minimum Height
Select a colour to indicate the minimum height on the map. This colour is used
to display areas up to and including the minimum height value that you have set
on the Height tab.
GIS Export
Select the content type for the GIS Export, and, in the case of Raster image,
the type of output file. For more information, see Exporting Map Layers using
GIS Export on page 435.
Note: You cannot perform this export if both Auto Res and Multi Res are
selected on the Height tab.
170
Changing How Data Appears on the Map
On this tab
You can
Visibility Settings
Select options for changing the visibility of the height data:

Always

View Zoom Range - set the Min. and Max. distances within which it will be
visible. You can base this on Distance (East-West) or Distance (NorthSouth)

Scale Range - set the Min. and Max. scale ratios within which it will be
visible
Tip: You can show the scale range in the Map Information pane. See Viewing
Scale Information Relating to the Current Map View on page 113.
Customising How Clutter is Displayed
To customise how clutter appears in the Map View window:
1. In the list of data types, expand Height & Clutter Data and double-click the Clutter item.
Important: If you want to display this item, ensure that the corresponding checkbox in the
list of data types is selected when you have finished customising. This is the overall control
for whether it shows in the Map View window.
2. In the dialog box that appears, enter the required information as shown here:
On this tab
You can
Clutter Properties
The available clutter categories depend on which map data you are using.
Typical categories are urban, suburban, industrial, airport, open areas, water,
vegetation and so on.
For each category, you can choose whether or not to display it, by using the
corresponding checkboxes under the 'Draw' column.
Tip: If you right-click anywhere on the rows or columns containing the
information, you can use the 'Select All' or 'Deselect All' options.
You can set your preferred colours to represent each category, by clicking the
corresponding boxes under the 'Colour' column.
The 'Default' button enables you to return to the basic default colours. It does
not affect any of the other settings.
There are two ways to choose the resolution you can either:

Select a resolution from the drop-down list.
- or 
Specify a resolution (by typing any value in the 'Resolution' edit box) and
select the 'Multi Res' checkbox. A deterministic conversion process is used
to display the specified resolution. This may be especially useful if you want
to visualise a specific resolution that you have used for your pathloss
predictions or arrays. You can also select the 'Modal' checkbox to simplify
the display of the boundary areas between different clutter types.
Tip: You can also enable automatic selection of the best resolution as you vary
the zoom level, by selecting the 'Auto Res' checkbox. See Using the Automatic
Map Resolution Option on page 172.
171
ASSET User Reference Guide
On this tab
You can
GIS Export
Select the content type for the GIS Export, and, in the case of Raster image,
the type of output file. For more information, see Exporting Map Layers using
GIS Export on page 435.
Note: You cannot perform this export if both Auto Res and Multi Res are
selected on the Style tab.
Visibility Settings
Select options for changing the visibility of the clutter:

Always

View Zoom Range - set the Min. and Max. distances within which it will be
visible. You can base this on Distance (East-West) or Distance (NorthSouth)

Scale Range - set the Min. and Max. scale ratios within which it will be
visible
Tip: You can show the scale range in the Map Information pane. See Viewing
Scale Information Relating to the Current Map View on page 113.
Using the Automatic Map Resolution Option
When you are customising the Map View display properties for height data or clutter data, you can
choose to use an automatic resolution (Auto Res) option.
The Auto Res option quickly re-evaluates which is the most appropriate resolution to display data
each time you zoom in or out. So, whether you are viewing a large region or zooming in to a city,
the Map View automatically selects the most appropriate resolution for you.
Note: This option is only for map visualisation purposes, and does not affect arrays or simulation outputs.
The Auto Res option operates slightly differently, depending on whether you also select the Multi
Res option.
Using Auto Res without Multi Res
If you select a resolution and then select the Auto Res checkbox (but not Multi Res):
The selected resolution becomes the highest quality resolution that will be displayed. For example,
if your project has available map data of 5m, 10m and 25m and 50m, and you specify a 10m Res.,
the Map View will never display the 5m data. This limit can save memory by avoiding displaying a
whole country at a high resolution. It will only display resolutions that are available in your map data
(if the zoom level is in between two levels of data, it will choose the higher resolution).
Using Auto Res with Multi Res
If you have already chosen to use the Multi Res option, and then also select the Auto Res option:
The Auto Res operates independently from the specified resolution (therefore the Res edit box
becomes irrelevant).
It can potentially display any resolution, even those not available in your map data. The displayed
resolution always depends on the current zoom level you are using, and reacts dynamically to it.
172
Changing How Data Appears on the Map
Customising How the Map Backdrop is Displayed
To customise how map backdrops (such as arial photographs) appear in the Map View
window:
1. In the list of data types, expand Map Backdrop and double-click the item you want to
customise.
2. In the dialog box that appears, on the Options tab:
o
Choose whether you want to display the backdrop item in colour or grayscale.
o
In the Style box, choose a percentage of opacity, if you want the backdrop to show
through other items that are simultaneously displayed on the map.
3. On the Visibility Settings tab, you can choose to always display this item when it is
selected, or to set the minimum and maximum map view dimensions at which the item will
then display.
For example, when zoomed in to a particular area of the network, you may want aerial
photographs or scanned maps to be displayed as a background, in order to verify the
positioning of a site. However, if you then zoomed out, this may clutter up the display, and
this can be avoided by choosing only to display the photographs at a particular zoom level.
o
Use View Zoom Range to set the minimum and maximum distances within which the
backdrop will be displayed according to Distance (North-South) or Distance (EastWest).
o
Use Scale Range to set the minimum and maximum scale ratios within which the
backdrop will be visible.
(You can show the scale range for the current Map View in the Map Information pane.
See Viewing Scale Information Relating to the Current Map View on page 113.)
Tip: If you have stored your aerial photographs in the recommended way, as detailed in
Map Data File Formats, when you set the Visibility settings for backdrops, you can choose
to display different resolution data at different map sizes, for example:
o
20m resolution data when the Map View size is between 5.01km and 100km
o
5m resolution data when the Map View size is between 1.01km and 5km
o
1m resolution data when the Map View size is between 0km and 1km
This picture shows how the 1m visibility settings would be specified, using the above
example:
4. On the GIS Export tab, choose the file format that you wish to use when exporting to GIS.
For more information, see Exporting Map Layers using GIS Export on page 435.
173
ASSET User Reference Guide
Customising How Web Map Data is Displayed
To select layers of web map data to display on the Map View:
1. In the list of data types, expand Web Maps and double-click on the subsidiary Web Maps
option.
2. In the dialog box that appears, on the Options tab, you can:
o
Select the required Web Map type from the Map Type drop-down list.
o
Choose whether you want to display the Web Map data in colour or grayscale.
o
In the Layers pane, select up to four layers to be displayed on the Map View. This
picture shows an example:
o
In the Internet access pane, if you want your Web Map data to be retrieved from your
cache folder rather than the internet, select the Do not access option. For more
information about your Web Maps cache folder, see About the Shared Data Directories
Tab on page 25.
o
Change how detailed the Web Map data appears by setting the Max Detail level.
o
In the Style box, choose a percentage of opacity, if you want the Web Map data to
show through other items that are simultaneously displayed on the map.
3. Click OK.
174
Changing How Data Appears on the Map
To see your chosen Web Map data layers on the Map View, select the Web Maps option under the
Data Types tab of the Layer Control Pane and click Redraw. If you have created groups of layers
in Administrator (for more information, see the ASSET Installation and Administration Guide), these
will be available for selection as sub-folders under the Web Maps folder.
Customising the Map Grid and Scale Bar
On the Data Types tab of the Layer Control Pane, there is an option to display:
 Map Grid
and/or  Scale
Example of Layer Control Pane
175
ASSET User Reference Guide
You can choose customise how these are displayed on the Map View:
Example of Map View window showing map grid and scale
To customise how the Map Grid appears in the Map View:
1. In the list of data types, expand Map Grid/Scale and double-click Map Grid.
2. In the Map Grid Display Properties dialog box, provide the required information as shown
here:
On this tab
You can
Options
Set the Grid Co-ordinate System to Longitude-Latitude or Easting-Northing.
Then set the Grid Type to Automatic or Manual. If you select Manual, you can
specify the grid spacings.
Choose to display either the Map Grid or the Ruler or both.
Choose to label a tile with the selected data types in the Tiled View.
Note: To limit the label length, common layers are automatically excluded.
Font
Select the font, font size and colour.
Style
Select the colour, line style, width and transparency for the grid.
GIS Export
Select the content type for the GIS Export, and, in the case of Raster image,
the type of output file. For more information, see Exporting Map Layers using
GIS Export on page 435.
Visibility Settings
Select options for changing the visibility of the map grid:

Always

View Zoom Range - set the Min. and Max. distances within which it will be
visible. You can base this on Distance (East-West) or Distance (NorthSouth)

Scale Range - set the Min. and Max. scale ratios within which it will be
visible
Tip: You can show the scale range for the current Map View in the Map
Information pane. See Viewing Scale Information Relating to the Current Map
View on page 113.
3. Click OK.
176
Changing How Data Appears on the Map
To customise how the Scale Bar appears in the Map View:
1. In the list of data types, expand Map Grid/Scale and double-click Scale.
2. In the Scale Display Properties dialog box, provide the required information as shown
here:
On this tab
You can
Display
Set the scale bar's colour, background, border, and its position.
Font
Select the font, font size and colour.
Visibility Settings
Select options for changing the visibility of the scale bar:

Always

View Zoom Range - set the Min. and Max. distances within which it will be
visible. You can base this on Distance (East-West) or Distance (NorthSouth)

Scale Range - set the Min. and Max. scale ratios within which it will be
visible
Tip: You can show the scale range for the current Map View in the Map
Information pane. See Viewing Scale Information Relating to the Current Map
View on page 113.
3. Click OK.
Customising How Filters are Displayed
You can change how filters appear in the Map View window and customise a wide variety of
display properties for filters.
For information on creating and using filters, see Using Filters in ASSET on page 275.
You can customise the display properties for:
 The All filter, which exists by default and displays all the network elements - sites, cells,
nodes and so on - that are contained in the database.
 The Selection filter (this is described in About the Selection Expert and Selection Filter on
page 294).
 Any additional filters that you create.
You can change the display properties of filters:
 When you create or edit a filter using the Filter Wizard
- and  In the Map View list of Data Types, by expanding Filters and double-clicking the required
filter
This table shows the things you can change for the different network elements in a filter:
For These Network Elements
You Can Change
Property, MSC, BSC, Distribution Node, Logical
Node, WMSC, SGSN, RNC, Node, PmP Hub
Symbol and label
Cell
Symbol, radial, label and service area
Repeater
Symbol, radial and label
Site, Node
Symbol, hexagon and label
177
ASSET User Reference Guide
For These Network Elements
You Can Change
Logical Connection, Logical Cellular Connection,
Link (PTP), Link (PMP), Passive Repeater Links
(Back to Back and Reflector), Multi-radio Links,
Dual Polar Links, Multi Band Links
Line 1, line 2 and label
The display properties dialog box for the selected filter opens. This picture shows an example:
In the dialog box that appears, you can:
 Choose to show all element types in the tree list, or only show the element types that exist
in the filter (a reduced list may help when you are customising the display properties of
those types).
 Quickly change various display properties, for example shape, size and line and fill colour,
using the Summary tab. For information on this, see Quickly Changing How Items in Filters
are Displayed on page 178.
 Make detailed and more complex changes using the individual tabs (Shape, Line, Fill, tab
and so on). Different tabs are available depending on the item you have selected. For more
information on this, see Making Detailed Changes to the Display of Items in Filters.
Quickly Changing How Items in Filters are Displayed
Each network element in a filter has a Summary tab that shows many of the display attributes that
you will want to change. As these are shown on one tab you can change them all quickly and
preview how the element will appear.
To change the appearance of network elements in a filter:
1. Change the items on the Summary tab as shown in this table:
Item
Description
Symbol - Shape
Select the size, font and shape required for the symbol for the network
element in the filter. You can edit the fixed point size to one decimal place by
typing over the value selected from the drop down box.
The default font is Standard.
178
Symbol - Line
Select a colour, line style and weight for the network element's symbol.
Symbol - Fill
Select a colour, fill style and percentage opacity for the fill of the symbol.
Changing How Data Appears on the Map
Item
Description
Background
Choose to accept the default of no background to the symbol, or to pick a
colour for a solid or halo background.
Label
Select which label you want to appear on the map.
You can also select a font, font size and colour.
2. Click OK.
3. To see your changes on the map, click the right mouse button and from the menu that
appears, click Redraw.
You can also make detailed changes using the individual tabs. For more information on this, see
Making Detailed Changes to the Display of Items in Filters.
Making Detailed Changes to the Display of Items in Filters
As well as changing various filters' display properties quickly using the Summary tab, you can
make detailed changes to how each network element in a filter will appear on the map. For
example, you might want to set up displays that:
 Show all cells on a particular MSC in one colour
 Highlight ground height over 50m
 Indicate all cells that will be on air in six months time, using fields
 Show in red all sites with traffic over a certain amount
 Use a different icon for different base station equipment types
To change the appearance of a network element in a filter:
1. In the Map View, in the Layer Control Pane, click the Data Types tab.
2. In the list of data types, expand Filters and double-click the required filter, for example All.
3. In the Filter Display Properties dialog box, expand the required network element so that
you can see the tabs for that element:
For all elements you can change the appearance of symbols and labels as described in
Changing the Shape of Symbols, Radials, Hexagons for Items in Filters on page 180.
For other items, this table shows the additional changes you can make:
For
You can also change the display of
Cells
Radial
Service Area
Sites, Nodes
Hexagons
Repeaters
Radials
179
ASSET User Reference Guide
For
You can also change the display of
Logical connections, logical cellular
connections, links (PTP and PMP), passive
repeater links (Back to back and reflector),
multi-radio links, dual polar links, multi band
links
Line1
Line2
4. Click OK.
5. To see your changes, right-click the map and from the menu that appears, click Redraw.
Changing the Shape of Symbols, Radials, Hexagons for Items in Filters
To change the appearance of a symbol, radial or hexagon for a network element in a filter:
1. Select and expand the required item, clicking Symbol, Radial or Hexagon.
2. On the Shape tab, you can change the size and shape for symbols, radials and hexagons.
All other items described refer to symbols and radials only.
This table shows what you can customise on the Shape tab:
To Change
Do This
Size
Select a fixed size or a variable parameter.
Shape
Select the font and the particular item you require from the lists.
Auto-Range
Settings
If you selected a variable size, you can customise the auto-range settings. For
each parameter, type a value in the Value column and select a colour by
clicking in the Colour column.
Size Step Options Choose Linear or Square Root.
Ranges
Click Add or Remove to customise the ranges.
Range Extents
Select a range extent.
Choosing a Fixed Size
Symbols and Radials
To set a symbol or radial to a fixed size:
1. Select and expand the required item, for example GSM Cell.
2. Click Symbol or Radial as required.
3. On the Shape tab, in the Size pane, select a fixed size in points from the list shown. Having
a fixed size symbol means that regardless of map size, symbols will not take up too much
of the screen.
Tip: You can type in a fixed size other than those shown, to one decimal place, by typing
over the value that you have selected from the list.
180
Changing How Data Appears on the Map
Hexagons
To set a hexagon to a fixed size:
1. Select and expand the required item, for example Cell Site.
2. Click Hexagon.
3. On the Shape tab, in the Size pane, select the required size.
4. In the Shape box, select a font and then a particular shape. The default font is Standard
and the shape, Hexagon.
Choosing a Size Based on a Variable
To resize a network element's symbol or radial using a variable:
1. Select and expand the required item, for example GSM Cell.
2. Click Symbol or Radial.
3. On the Shape tab, in the Size pane, select the Variable option and click the
button.
Note: If any of your antennas have multiple slots, you cannot set the symbol or radial to be
based on a variable antenna value.
4. Select the checkbox next to a variable parameter and choose either:
o
Match All.
o
Match based on Criteria and then click Values to choose those values required.
If needed, select the Not checkbox.
5. Click OK.
6. In the Shape box, select a font and a shape. The default font is Standard.
7. If you have selected a field as your variable, you need not do anything else. Click OK to
close the dialog box and skip these remaining instructions.
8. In the Auto-range Settings pane, select the box next to the parameters you want to use,
and enter the required values for both parameter value and corresponding symbol/radial
size.
Tip: If you want the value and size for a particular parameter (for example, Low) to be
automatically calculated, select its checkbox.
181
ASSET User Reference Guide
In this example, the symbol size will be determined by the building height:
If the Property has the minimum building height (0m), the symbol for it will be 4.9pt,
whereas if it has the maximum building height (8m), the symbol for it will be 14pt.
9. To calculate the values in between:
o
Ensure you have set the correct step size in the list of values.
o
In the Size Step Options pane, select Linear or Square Root.
Note: If you want to use Square Root to calculate the step sizes, you need to specify
the Low and the High size values.
o
Click Re-Calc.
The list of available ranges is displayed in the Ranges pane:
10. You can edit or remove those shown, or add new ones, and also select a range extent.
11. When you have set the required display options, click OK.
182
Changing How Data Appears on the Map
Changing the Line for Items in Filters
You can change the appearance of a line for a symbol, radial, hexagon line 1, line 2 or service area
for a network element in a filter
This table shows what you can customise on the Line tab:
To Change
Do This
Colour
Select a fixed colour or a variable parameter.
Line
Select a line style and weight.
Auto-Range
Settings
If you selected a variable colour, you can customise the auto-range settings. For
each parameter, type a value in the Value column and select a colour by clicking
in the Colour column.
Colour Options
If you chose Low or High as the automatically calculated option in Auto-Range
settings, you can choose one of these options:

Palette Step to use each distinct colour in the palette one by one

Colour Blend to use a gradual blend of toning colours starting with the first
colour chosen and ending with the second

Inflection to use a gradual blend of toning colours starting with the first colour
chosen, going via the inflected colour of your choice at the range number you
specify, and ending with the second colour chosen
Ranges
Click Add or Remove to customise the ranges.
Range Extents
Select a range extent.
For more information on how to use the variable colour option, see Changing the Colour Based on
a Variable on page 184.
Changing the Fill for Items in Filters
You can change the fill of a symbol, radial, service area or hexagon for a network element in a filter.
On the Fill tab, you can customise:
To Change
Do This
Colour
Either select a fixed colour or select a variable parameter.
Fill
Select a pattern and transparency.
Auto-Range Settings
If you selected a variable colour, you can customise the auto-range
settings. For each parameter, type a value in the Value column and select
a colour by clicking in the Colour column.
Colour Options
If you chose Low or High as the automatically calculated option in AutoRange settings, you can choose one of these options:

Palette Step to use each distinct colour in the palette one by one

Colour Blend to use a gradual blend of toning colours starting with the
first colour chosen and ending with the second

Inflection to use a gradual blend of toning colours starting with the first
colour chosen, going via the inflected colour of your choice at the
range number you specify, and ending with the second colour chosen
Ranges
Click Add or Remove to customise the ranges.
Range Extents
Select a range extent.
For more information on how to use the variable colour option, see Changing the Colour Based on
a Variable on page 184.
183
ASSET User Reference Guide
Changing the Colour Based on a Variable
To have the colour of a network element's symbol, radial or hexagon change according to
the value of a variable:
1. Select and expand the required item, clicking Symbol, Radial or Hexagon.
2. On the Line or Fill tab, in the Colour pane, select the Variable option and click the
button.
3. Select the checkbox next to the parameter you want to use - this can be any parameter, not
just those belonging to the particular element you have selected. For example, you could
choose the field values of a Property to display against BSCs on the map.
4. Choose All or choose Balder on Criteria together with an operator and the relevant
values, then click OK.
5. If under Auto-Range Settings you have Unique Colour Per Value specified, colours are
used automatically. Now go to step 7.
6. If under Auto-Range Settings you have Fixed Colour Per Value specified, in the Ranges
pane, choose the colour for each option you have selected. This picture shows an example:
7. If under Auto-Range Settings you have Auto-Range Values specified, select the box next
to the parameters you want to use, and enter the required values for both parameter value
and corresponding colour.
Tip: If you want the value and size for a particular parameter (for example, Low) to be
automatically calculated, select its checkboxes.
184
Changing How Data Appears on the Map
In this example, the Property symbol colour will be determined by the search radius:
If the Property has the minimum search radius (0m), the symbol for it will be a very light
colour, whereas if the Property has the maximum search radius (8m), the symbol for it will
be much darker.
8. To calculate the values in between, click Re-Calc.
The list of available ranges is displayed in the Ranges pane:
Here, a range of values are possible, with the Property darkening in colour as the search
radius increases.
9. If you want values outside the ranges to be coloured, select the checkbox and the colour
required.
10. Click OK.
185
ASSET User Reference Guide
Changing the Background of Items in Filters
You can change the background of symbols, radials, hexagons, line 1, line 2 and service areas for
network elements in a filter.
For example, using a Halo may enable you to see items on the map more clearly:
Where it might clash with the colour of displayed coverage, the halo colour is automatically
changed.
To add a background to your item:
1. Select and expand the required item, clicking Symbol, Radial or Hexagon.
2. On the Background tab, choose Solid or Halo background then select a colour from the
drop down menu.
Changing the Visibility of Items in Filters
You can change when a symbol, radial, hexagon, line 1, line 2, label and service area for a network
element in a filter appear on the map. For example, when zoomed in to a particular area of the
network, you may want items, such as aerial photographs, roads and so on, to be displayed as a
background, in order to verify the positioning of a site. However, if you then zoomed out, having all
this information displayed might clutter up the map. To avoid this, choose only to display items at a
particular zoom level.
On the Visibility tab, select the options for changing the visibility of the item:
 Always
 View Zoom Range - set the Min. and Max. distances within which it will be visible. You
can base this on Distance (East-West) or Distance (North-South)
 Scale Range - set the Min. and Max. scale ratios within which it will be visible
 Tip: You can show the scale range in the Map Information pane. See Viewing Scale
Information Relating to the Current Map View on page 113.
 Select what information will be visible on the Map Legend tab:
o
All of the values defined in the filter
o
Only the values that are used in the project
o
None of the values
Changing the Display of Labels in Filters
To change the appearance of labels for network elements in a filter:
1. Select and expand the required item, for example Property.
2. Click Label.
3. Change the information on the tabs as shown in the following table:
186
Changing How Data Appears on the Map
On this tab
You can customise
By doing this
Parameters
Label Default
Click Add to choose an item that you want to
display as a label on the map. Those shown in
the table are all displayed on the map, separated
by commas.
For any labels that you no longer want to display,
you should click in the list and choose Remove.
Select the font, font size and colour for the label.
Tip: To change the order in which the labels are
displayed, select the label that you want to move
and use the up and down buttons.
You can also add criteria to define under what
conditions this label is displayed. For example,
you may want to display the Property ID as a
label for a cell site, but only for those which also
contain particular RNCs.
To add a criteria:
Text Box
Visibility

Right-click the parameter.

From the menu that appears, click Add.

Select the required criteria and click OK.
Box Style
Select a fixed Height and Width for the text box.
If you do not select a fixed height and width, the
text box will automatically resize around the text.
Background
The background default is Off. If you select the
Solid or Halo option, select a colour from the
drop down menu.
Label Position
Select where you want the label to appear and, if
you wish, select an Offset distance between the
label and the network element.
Label Line
Select a Type, Width and Colour for the label
line. The line is drawn from the property location
to the centre of the text box. The Label Line
option is not available for cells.
How the label is shown
For more information, see Changing the Visibility
of Items in Filters on page 186.
Changing the Display of Service Areas in Filters
In the All Display Properties dialog box, you can change the appearance of a service area in a filter.
To do this:
1. Select and expand the required item, for example GSM Cell.
2. Click Service Area.
3. You can edit the following display properties:
On this tab
You can customise
By doing this
Line
The line style
For complete information on doing this, see Changing the
Line for Items in Filters on page 183.
Fill
The fill style
For complete information on doing this, see Changing the
Fill for Items in Filters on page 183.
187
ASSET User Reference Guide
On this tab
You can customise
By doing this
Service Array
How arrays in the
service area are
displayed
Select an Array Type from the drop down menu. All
available arrays are displayed, including the currently
selected one (if it is unavailable, this will be indicated).
If you try to set the display properties for an unavailable
array, you receive a warning in the message log.
Background
The background style
The background default is Off. If you select the Solid or
Halo option, select a colour from the drop down menu.
Visibility
How the service area is
shown
For full information, see Changing the Visibility of Items in
Filters on page 186.
Example of Displaying Properties According to Ground Height
This example shows how you can customise the display of Properties in a filter to show them
differently based on the variable of Ground Height.
1. In the list of data types shown in the Map View window, under Filters, double-click the
required filter.
2. In the dialog box that appears, expand Property and click Symbol.
3. Leaving the Shape and Line tabs showing Fixed size, click the Fill tab.
4. Choose Variable and select DTM (m).
5. In the Auto-Range Settings pane, select the checkbox for the item you want to be
automatically calculated, for example Range.
6. For the remaining three parameters, Low, High and Step, click in the Value column and
type in the required values in the units of the selected variable, so in this example, this is
metres.
7. In the Colour column, click to select a colour both for Low and High.
So far, the dialog box looks similar to this:
188
Changing How Data Appears on the Map
8. When you choose Range or Step as the automatically calculated option, Colour Blend is
automatically used as the colour option.
Note: You can try different colour options and click Cancel if you do not want to retain
them. However, if you change the variable, you may lose ranges and colour options you
have set up.
9. Click the Re-Calc button to update the Ranges pane and see the colour changes.
If you want to also colour values outside the currently used range, select the Values Not
Included By Ranges checkbox and choose a colour.
The dialog box now looks like this:
The Map View now displays the Properties like this, where the yellow Property is outside
the range specified:
189
ASSET User Reference Guide
The numbers shown indicate the Ground Height in metres as this has been added on the
Label, Parameters tab for Properties as shown here:
Example of Displaying Address Information for Properties in Filters
This example shows how you can label network elements based on certain criteria, and therefore
customise the display of the network element. In this example, we will modify Properties to show
their address information on the map. To do this:
1. In the list of data types shown in the Map View window, under Filters, double-click the
required filter.
2. In the tree, expand the Property element, and click the Label item.
3. On the Parameters tab, click Add to display a list of items to choose from.
4. Expand the Properties element, and choose the attribute or attributes that you want to
display. In this case, Address1 as shown here:
5. Click OK.
6. Click OK.
7. Click Redraw.
190
Changing How Data Appears on the Map
Now the address information displays on the map when we are displaying that filter as
shown here:
Customising How Vector File Features are Displayed
There are a number of ways you can change the display properties of vector file features (for
example, polygons and lines), whether it is from map data, such as coastline, or one you have
created yourself using the Vector Manager.
For information on creating, importing and using vectors, see Using Vector File Features on page
251.
To change how a feature appears in the Map View window:
1. If you want to change how a system vector feature appears on the map, contact your
administrator and ensure that you have Write permissions for System Vectors.
2. In the list of data types, expand System Vectors or User Vectors as appropriate, and
double-click the feature that you want to customise.
3. In the dialog box that appears, on the General tab, you can select to:
o
Use your own display properties, by selecting the 'Use this dialog to control settings'
option
o
Use the display properties defined by a GIS file, by selecting the 'Use GIS file's inbuilt
feature settings' option
191
ASSET User Reference Guide
4. If you select to override the GIS file's properties, you can either:
o
Make simple changes to the appearance of features, using the Summary tab
- or -
o
Make more extensive and detailed changes to the appearance of features, using a
number of different tabs
5. By default, ASSET uses settings that make the display of the vector file features appear
less cluttered on the map.
o
Initially, ASSET will only display the same unique string for a label on the first
occurrence.
This is particularly useful if you have two buildings with the same height, or a road
vector made up of many little line segments, instead of a single line. Each of these will
have multiple labels with the same value, which could potentially make the map appear
more cluttered.
o
Initially, ASSET will not overlap labels on the map. Instead, only the first overlapping
label is displayed.
For example, if Label A and Label B overlap, and Label A is drawn first, then Label B
will not get drawn at all.
However, both of these settings can be overridden, by selecting the 'Allow duplicate label
text' and 'Allow overlapping labels' options respectively.
Making Simple Changes to the Display of Vector File Features
Each vector file feature type has a Summary tab that shows many of the display attributes that you
will want to change. As these are shown on one tab you can change them all quickly and preview
how the feature will appear.
To change the appearance of a feature:
1. In the list of data types, expand System Vectors or User Vectors as appropriate, and
double-click the feature you want to customise.
2. Click the appropriate feature type (for example, polygon).
3. Change the items on the Summary tab as shown in this table:
Pane
Item
Description
Shape
Symbol
Select the font and the particular symbol you
require from the lists.
Fill
Select a pattern and a transparency.
Line (1 and 2)
Select a line colour, style and a weight.
Font (Text only)
Select a colour, font style and size for the text.
Background (Text only)
Select whether or not the text will be displayed with
a background, either a halo (a surrounding edge)
or a box (a solid shape).
Background colour (Text
only)
If you have chosen to have a background, then
select a background colour.
Opacity
Select the solidity of the shape.
Rotation
Select the angle of rotation, if you want to display
the symbol at a particular angle.
Font
Select a colour, font style and size for the label.
Label
192
Changing How Data Appears on the Map
Pane
Item
Description
Selected Attributes
N/A - this lists the attributes that you may have
chosen when making detailed changes to the
display of vectors.
4. Click OK.
5. To see your changes on the map, right-click and from the menu that appears, click
Redraw.
You can also make detailed changes using the individual tabs. For more information on this, see
Making Detailed Changes to the Display of Vector File Features.
Making Detailed Changes to the Display of Vector File Features
As well as changing various vector file features' display properties quickly using the Summary tab,
you can make more detailed changes.
For example, you might want to set up displays that:
 Show building vectors, with the building height attribute used as a label:
 Include textual annotations, verbally indicating for example, the suitability of locations for
cell sites, or areas of high density of users:
193
ASSET User Reference Guide
To change the appearance of a vector file feature:
1. In the Map View, in the Layer Control Pane, click the Data Types tab.
2. In the list of data types, expand the relevant vector file category (either System or User)
and double-click the required feature.
3. In the Display Properties dialog box that appears, expand the required feature type so that
you can see the tabs for that type:
For all features you can change the appearance of symbols and labels, on a different
number of tabs, depending on the feature type:
For This Feature Type
These Tabs Are Available
Point
Shape - Symbol, Fill, Line, Symbol Appearance
Label - Label, Label Properties
Polygon
Shape - Fill, Line 1, Line 2
Label - Label, Label Properties
Line
Shape - Line 1, Line 2
Label - Label, Label Properties
Text
Shape - Text Appearance, Fill
Label - Label, Label Properties
4. Click OK.
5. To see your changes, right-click the map and from the menu that appears, click Redraw.
Changing the Fill Colour or Pattern of Vector File Features
To change the fill colour or pattern for a vector file feature (for example, a polygon or point) in the
Display Properties dialog box:
1. Expand the required feature type, for example Polygon, and click Shape:
2. On the Fill tab, you can customise the fill of the feature shape. This table describes the
available options:
To change
Do this
Style
Select a pattern for the fill of the feature shape, for example dots or vertical
lines.
If you want to inset the lines for polygons so that they don’t overlap the lines
of other polygons, select the Erode Fill option. This is particularly useful if
you have several polygons with thick border lines close together.
194
Changing How Data Appears on the Map
To change
Do this
Foreground Colour
Either select a fixed colour or select the variable attribute that you want to
base the colour on.
If you choose the fixed colour option, for certain fill patterns you can select
more than one colour to show, for example, coloured stripes.
Auto-Range
Settings
Colour Options
Ranges
If you selected a variable colour, you can customise the auto-range settings:

You can select one of the settings to be automatically calculated, by
selecting its radio button

Type values for any of the settings in the appropriate boxes

For the min and max values, you can select a display colour
If you selected a variable colour, you can choose one of these options:

Palette Step to use each distinct colour in the palette one by one.

Colour Blend to use a gradual blend of toning colours starting with the
first colour chosen and ending with the second. You can additionally set
an inflection value. The range which contains this value will be the one
where inflection is applied.
Click Re-Calc to calculate the ranges based on the Auto-Range settings and
display them.
You can then add or remove individual ranges as required.
Values not included Select the colour that you want to use for any attribute value that does not fit
by range
within the min/max ranges that you have defined.
Range Extents
Select a range extent, either:
More than the minimum, and equal to or less than the maximum
- or Equal to or more than the minimum, and less than the maximum
Changing the Line Attributes of Vector File Features
To change the line attributes for a vector file feature in the Display Properties dialog box:
1. Expand the required feature type, for example Polygon, and click Shape:
2. Click the Line tab.
Note: For polygons and lines there are two Line tabs. This enables you to create more
complex visual effects (for example, stripes).
3. On the Line tab, you can customise how the line for a vector file feature is displayed. This
table describes the available options:
To change
Do this
Style
Select a pattern for the line, for example dots or vertical lines, and a
line width.
Colour
Either select a fixed colour or select the variable attribute that you
want to base the colour on.
195
ASSET User Reference Guide
To change
Do this
Auto-Range Settings
If you selected a variable colour, you can customise the auto-range
settings:
Colour Options

You can select one of the settings to be automatically
calculated, by selecting its radio button

Type values for any of the settings in the appropriate boxes

For the min and max values, you can select a display colour
If you selected a variable colour, you can choose one of these
options:
Palette Step to use each distinct colour in the palette one by one
Colour Blend to use a gradual blend of toning colours starting with
the first colour chosen and ending with the second. You can
additionally set an inflection value. The range which contains this
value will be the one where inflection is applied.
Ranges
Click Re-Calc to calculate the ranges based on the Auto-Range
settings and display them.
You can then add or remove individual ranges as required.
Values not included by
range
Select the colour that you want to use for any attribute value that
does not fit within the min/max ranges that you have defined.
Range Extents
Select a range extent, either:
More than the minimum, and equal to or less than the maximum
- or Equal to or more than the minimum, and less than the maximum
Changing the Visibility of Vector File Features
You can change the visibility of vector file features in the Display Properties dialog box. For
example, when zoomed in to a particular area of the network, you may want some items, such as
aerial photographs or roads, to be displayed in the background, in order to verify the positioning of
a site. However, when zoomed out, these items might obscure the other information on the map. To
avoid this, you can choose to display some items only within a particular zoom range.
To do this:
1. Double click the required data type.
2. In the Display Properties dialog box, click the Visibility tab.
3. On the Visibility tab, you can set when the vector file feature is displayed, either:
o
Always
- or -
o
196
Based on the Zoom Range, which are the minimum and maximum Map View
dimensions in which the item will be displayed, according to Distance (North-South) or
Distance (East-West)
Changing How Data Appears on the Map
Changing the Labels of Vector File Features
To change the appearance of labels for vector file features in the Display Properties dialog
box:
1. Expand the required feature type, for example Polygon, and click Label:
2. On the Label tab, you can customise the appearance of the feature label. This table
describes the available options:
On this Tab
You Can Customise
By Doing This
Label
Label Defaults
In the Attributes pane, click Add to choose an
attribute whose value you want to display as a
label on the map. Those shown in the table are
all displayed on the map, separated by commas.
For any labels that you no longer want to display,
select them in the list and choose Remove.
To change the order in which the labels are
displayed, select the label that you want to move
and use the up and down buttons.
Select the font, font size and colour for the label.
Select any additional effects for the label text, for
example underlining or making it bold.
Select any required vector metrics (point, shape
length, feature length, feature area). For more
information on creating vectors with these
metrics, see About the Distance Toolbox.
Label Properties
Label Position
Select the horizontal and vertical position of the
label and, if you wish, select an Offset distance
between the label and the vector.
Label Line
Select a Style, Width and Colour for the label
line. The line is drawn from the vector to the
centre of the text box.
Label Background
Select a background type and colour for the
label.
Line Label Repetition
Select if you want the label for a line repeated at
regular intervals along the line, and if so, at what
distance.
(for Line labels only)
197
ASSET User Reference Guide
Changing the Symbol of Points
To change the appearance of a symbol for a point in the Display Properties dialog box:
1. Expand the Point group and click Shape:
2. On the Symbol tab, you can change the symbol properties for points. This table describes
the available options:
To Change
Do This
Symbol
Select the font and the particular symbol you require from the lists.
Size
Select a fixed symbol size or select the variable attribute that you want to
base the symbol size on.
Auto-Range Settings
If you selected a variable symbol size, you can customise the auto-range
settings. For each parameter, type an attribute value in the first box and the
symbol size that you want to associate with the attribute value in the
second box type.
Size Step Options
Choose Linear or Square Root.
Note: For Square Root, you need to specify both the Min and the Max
values.
Ranges
Click Re-Calc to calculate the ranges based on the Auto-Range settings
and display them.
You can then add or remove individual ranges as required.
Values not included
by range
Select the symbol size that you want to use for any attribute value that
does not fit within the min/max ranges that you have defined.
Range Extents
Select a range extent.
Changing the Symbol Appearance of Points
To change the appearance of a symbol for a point in the Display Properties dialog box:
1. Expand the Point group and click Shape:
2. On the Symbol Appearance tab, you can change the how the symbol for points appears.
This table describes the available options:
Item
Description
Background
Change the background of points to see them on the map more clearly.
Choose either a halo round the point or a box, as well as a colour for this
background.
198
Changing How Data Appears on the Map
Item
Description
Effects
Add additional effects to enhance the appearance of the points.
Select a drop shadow (which adds a shadow behind the point) and/or make the
point bold.
Rotation
Rotate the point through a number of degrees.
Choose either:

The fixed value option, and then type the angle in the box, or use the up and
down buttons to change the angle. All points will be rotated by this angle.

The variable value option, and then click the Browse button to select which
attribute to base the angle on. Points will be rotated by different angles
depending on the value of the selected attribute.
Note: The selected attribute must use angle values for this option to be effective for example, an antenna azimuth attribute.
Changing the Appearance of (Vector) Text
To change the appearance of (vector) text in the Display Properties dialog box:
1. Expand the Text group and click Shape:
2. On the Text Appearance tab, you can set the display properties for the vector text that you
have created. This table describes the available options:
Item
Description
Font
Select the font and font size for the text.
Rotation
Rotate the text through a number of degrees.
Type the angle in the box, or use the up and down buttons to change the
angle. All points will be rotated by this angle.
Effects
Add additional effects to enhance the appearance of the text, for example
underlining it or making it bold.
Text Background
Change the background of the text to see it on the map more clearly.
Choose either a halo to surround the text or a box, as well as a colour for
this background.
199
ASSET User Reference Guide
Copying the Display Properties of Filters
To copy a filter's display properties:
1. Ensure you have set up display properties as required for your filter.
2. In the Map View, on the Data Types tab of the Layer Control Pane, right-click the filter
whose properties you want to copy, and from the menu that appears, click Copy
Properties.
3. Right-click the filter whose display properties you want to overwrite and click Paste
Properties.
For information on creating and using filters, see Using Filters in ASSET on page 275.
Using Visualisers
Visualisers are a way of creating multiple and varied display settings for the same filter when you
are using the Map View.
So, after you have set them up in the Data Types tab of the Layer Control Pane, you can quickly
and easily display the setting that suits your purpose at that particular time.
In addition to the benefit of multiple display settings, visualisers have some other advantages:
 They are not committed to the database, and therefore have no impact on processing
speed.
 You can customise and store your own visual requirements on the Map View, without
affecting any other users.
Examples of when using visualisers might be useful are:
 You need to present a monthly report, using the style of your organisation, which is different
to your own. So each month, for the same filter, you turn off your own display properties
and use different ones:
 You have set up the Selection filter to show Property IDs as labels. In a visualiser you
choose to change the label to show contact details instead. Or you may have a filter
showing all network elements and then create visualisers which each contain one network
element type, enabling you to separate out your displays as required:
Adding Visualisers
When you add a visualiser, it will inherit all the display properties of a filter, so ensure you have set
up the filter, assigning colours and symbols to each item as required.
To add a visualiser:
1. In the Map View, in the Layer Control Pane, click the Data Types tab.
2. Expand the Filters category and right-click the required filter.
3. From the menu that appears, select Add New Visualiser.
200
Changing How Data Appears on the Map
4. In the dialog box that appears, type the name for the new visualiser and click OK.
The new visualiser appears as a new item under the filter, and contains the filter properties
that you have copied:
Tip: Visualisers can also be included in Favourite Views (see About Favourite Map Views on page
101). This greatly speeds up the process of displaying the Visualisers with the minimum of effort.
Changing the Display Properties of Visualisers
You view and change the display properties of visualisers in the same way as you would do for
filters, that is, by:
 Double-clicking the visualiser in the list of data types
– or –
 Right-clicking the visualiser and from the menu that appears, selecting Properties
Copying and Resetting Display Properties of Visualisers
Copying Display Properties
You can copy display properties from one visualiser to another, overwriting existing display
properties. To do this:
1. Right-click the visualiser whose properties you want to copy and from the menu that
appears click Copy Properties.
2. Right-click the second visualiser and from the menu that appears click Paste Properties.
Resetting Display Properties
You can reset a visualiser's display properties to the original ones that you chose when you first
created the filter (not the visualiser).
To do this:
1. In the list of data types, expand Filters and browse to the required visualiser.
2. Right-click the required filter and select Reset.
201
ASSET User Reference Guide
Exporting and Importing Display Properties of Visualisers
To export the display properties of a visualiser and import them into another project:
1. Right-click the visualiser whose display properties you want to export, and from the menu
that appears, click Export Properties.
2. In the dialog box that appears, browse to the required location and type a name for the
settings file.
3. Click Save.
4. Click Export.
The display properties are exported.
5. In the second project, right-click the visualiser into which you want to import the display
properties.
From the menu that appears, click Import Properties.
6. In the dialog box that appears, locate the required settings file and click Open.
7. Click Import.
The display properties in the chosen file are imported.
Removing Visualisers
To remove a visualiser:
1. In the list of data types, expand Filters and browse to the required visualiser.
2. Right-click the required filter and select Remove Visualiser.
3. In the dialog box that appears, click Yes.
202
Changing How Data Appears on the Map
Viewing Attribute Data as Site Tips
In the Map View window, you can display network element data as Site Tips, which appear as you
hover over cells/repeaters in your network. This picture shows an example, where the carrier and
azimuth are displayed as screentips for the closest cell:
Viewing attributes on Map View as Site Tips
Note: The picture is just an example. The principle is the same for all technologies.
To display Site Tips:
1. On the Map View toolbar, click the small arrow next to the
button.
2. From the extra set of buttons that appear, click the Display Site Tips button
.
The Site Tip Attributes dialog box appears:
203
ASSET User Reference Guide
3. In the Available Attributes pane, expand the required network element, and:
o
Click the attribute that you want to display, and click the right arrow button
.
- or o
Select the checkboxes to the left of each attribute (this is quicker if you want to show
several attributes).
The chosen attributes are moved to the Selected Attributes pane.
You can deselect an attribute by clicking the left arrow button
checkbox.
, or by deselecting its
Tip: If you want to change the sequence in which the attributes will be displayed, click the
up
and down
arrow buttons to change the position.
4. When you have selected all of the required attributes, click OK.
The chosen attributes are then available as Site Tips when you hover the mouse over the
cell or repeater.
Note:
 Your chosen attributes are saved for future use. However, if you close and reopen the Map
View, or close and reopen the project, you will need to click the Display Site Tips button
and click OK to show them.
 If you want to stop displaying the Site Tips while the Map View is still open, click the
Display Site Tips button and click Cancel.
204
Saving Data to the Database
7 Saving Data to the Database
The ASSET database stores all the items needed to design a complete cellular network in a logical
hierarchy. This includes the parameter information that you add or edit in the various dialog boxes
(for example, network elements and equipment details).
Most of these dialog boxes (including the Site Database itself) contain an Apply button and a
Commit button. Some also contain a Commit All button. (A small number of dialog boxes only
contain a Commit option.)
Saving Your Changes to the Database
Comparison between Apply and Commit
In a project, when you make a change to some data and click Apply, the change you make is
saved to the database, but only visible to you. This provides the opportunity to make sure the
change is correct, or to experiment.
If you proceed (anytime later) to click Commit, then that change will be potentially visible to all
users of the project. For a clarification of when it becomes visible, please see Using Refresh to
Update Network Elements on page 211.
Important: All Applied changes will still be available (persisted) in the re-started project after you
close the project, log out or shut-down ASSET. The Apply action and the Commit action both save
the data, so there is no compulsion to Commit data before closing the project.
In summary, Apply and Commit both store data in the database, but Applied changes are only
visible to the individual who made the change whereas the Commit makes that changed data
potentially visible to all users.
Applying Your Data
To Apply your data:
1. In the current window or dialog box, select the network element that you have changed.
2. Click Apply
.
Changes are made to your personal area of the database, that is, only you will see the
changes you have made.
Note: If required, you can revert any Applied changes to the last Committed state, see Restoring
Your Data on page 207.
205
ASSET User Reference Guide
Committing Your Data
To Commit your data:
At any time after Applying the data, you can Commit that data.
1. Ensure that you want to make the change(s) visible to all users.
2. Click the Commit button
.
3. 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, a Database Warning message will prompt you to either cancel the Commit or to
continue, merging their Committed data with your own changes.
Committing All Your Data in the Dialog Box
To Commit all your data within the dialog box:
Depending on your user permissions, and depending whether this option is present, you can
collectively Commit all changes that you have made in a particular dialog box, by clicking the
Commit All button.
(This button is not available on all dialog boxes.)
Note: Where the dialog box contains a filter choice, the Commit All action is in accordance with the
currently selected filter.
1. Ensure that you want to make the collective change(s) visible to all users.
2. Click the Commit All button
.
3. 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, a Database Warning message will prompt you to either cancel the Commit or to
continue, merging their Committed data with your own changes.
Warning: When performing a Commit All, elements may fail to Commit under certain conditions.
Common reasons for failure are when a dependent element has never been previously Committed,
or the dependent element is not currently in a Committed state, or the dependent element is not in
the current filter. To avoid this, you should perform a Commit All on a filter that contains all the
dependent elements that have already been Committed at least once before. Alternatively, you
could use the Global Commit All option to commit all of the configuration elements and network
elements inside the current project.
Committing All Your Data in the Project
To globally Commit all your data within a project:
Depending on your user permissions, you can use the Global Commit All option to Commit all the
objects in your project in a single action. This automatically commits all the changes in the correct
sequence.
206
Saving Data to the Database
In other words, you can Commit all the changes that you have made, not just, for example, to the
Site Database, or Terminal Types, but throughout all the other dialog boxes, such as carriers,
equipment, antennas and so on.
Warning: You should use this option with extreme caution, because this action will Commit all your
Applied changes to the database.
To do this:
1. Ensure that you want to make the collective change(s) visible to all users.
2. From the Database menu, click Global Commit All.
3. 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, a Database Warning message will prompt you to either cancel the Commit or to
continue, merging their Committed data with your own changes.
Restoring Your Data
You can restore data from an Applied state back to its previously Committed state in a number of
ways. This assumes that the relevant data has already been Committed at least once before.
Note: This action reverts data back to its previously Committed state, so if any consecutive Applied
changes were made on the same object, all of them would be removed.
To restore the Applied changes for a single object to the last Committed state:
1. In the corresponding window or dialog box, select the object that you want to revert.
2. Click Restore
.
The object is reverted to its last Committed state.
To restore the Applied changes for all objects in a particular dialog box:
Click Restore All
.
(This button is not available on all dialog boxes.)
To restore the Applied changes for all objects in a project:
From the Database menu, click Global Restore All.
Examples of Using Apply and Commit
These three examples provide an idea of how the Apply and Commit process works in a multi-user
environment:
 Single user adding new objects
 Two users amending the same attribute of the same object
 Two users amending different attributes of the same object (merge)
207
ASSET User Reference Guide
Example 1: Single User Adding New Objects
This theoretical example demonstrates using Apply and Commit and the logical order in which
dependent objects need to be committed.
You are trying to improve the network service in an area and want to keep your changes to yourself
until you have verified that the changes are successful.
1. You add a propagation model and click Apply.
2. You add a three-cell site and specify that it uses that new model.
You do not need to Apply this as new items created in the Site Database window are
automatically Applied.
3. You change the name of each cell and click Apply.
At this stage, all these changes are visible to you only. That is, people simultaneously
accessing the same project will not see these changes; they will only see data that has
been Committed.
4. After testing, you decide to Commit these changes to the database.
Warning: You must do this in a logical order. For example, you cannot Commit the site
until the propagation model is Committed.
The order for Committing in the above example would be:
a. Commit the propagation model.
b. Commit the site.
c. Commit the cell.
Tip: Depending on your user permissions, you can use the Global Commit All option to Commit
all the objects in your project at once (this automatically commits all the changes in the correct
sequence). See Committing All Your Data in the Project on page 206.
Example 2: Two Users Amending Same Attribute on Same Object
This example demonstrates two users using Apply and Commit to amend the same attribute on the
same object.
Joan and Peter are connected to the same database and project and both will be working on the
same network element, a Property.
Their actions are as follows:
1. Joan amends the Building Height of Property X to 24, and then clicks Apply.
2. Peter amends the Building Height of Property X to 25, and then clicks Apply.
3. Peter clicks Commit.
208
Saving Data to the Database
4. Joan tries to click Commit. At this stage, a dialog box appears, alerting her that another
user has made a committed change, and prompts her to either continue or cancel:
5. After checking with Peter, Joan decides to Commit the change.
(The 'Refresh DB on Commit' option is only relevant when there is merged data, as
described in Example 3.)
The outcome of this is that Peter's committed value will be overwritten by Joan's committed value
because her Commit was the latest. When Peter next logs out and back into the project (or if he
performs a Refresh, as described in Using Refresh to Update Network Elements on page 211), he
will see Joan's new value.
Example 3: Two Users Amending Different Attributes on Same Object (Merge)
This example demonstrates two users using Apply and Commit to amend different attributes on the
same object.
David and Rafa are connected to the same database and project and both are working on the same
network element, a Property.
Their actions are as follows:
1. David amends the Property Code of Property Z to H000243, and then clicks Apply.
2. Rafa amends the Building Height of Property Z to 15, and then clicks Apply.
3. David clicks Commit.
209
ASSET User Reference Guide
4. Rafa tries to click Commit. At this stage, a dialog box appears, alerting him that another
user has made a committed change, and prompts him to either continue or cancel:
5. After checking with David, Rafa decides to Commit the change.
Note: The outcome of this is that a merge of the data takes place. In other words, changes to
Property Code and Building Height will be added to the Commit record for this object.
Assuming he left the 'Refresh DB on Commit' selected in the above dialog box, Rafa sees the
merged data after his Commit.
David will see the merged data when he next logs out in and back into the project (or if he performs
a Refresh, as described in Using Refresh to Update Network Elements on page 211).
Logging Out and Logging In Recommendation
Whenever you log out of the project, and then log back in, the data you see in your project is
automatically updated (refreshed) to include any Committed changes that other users have made.
After logging in, you will see network elements and any other objects in their currently Committed
state (including changes that were Committed while you were logged out), plus any changes that
you had Applied in your last session.
There are also two ways of refreshing the data while you are in a project session. See Using
Refresh to Update Network Elements on page 211.
Important: We recommend logging out of a project at regular intervals, preferably on a daily basis.
For more information about the reason for this, see About the Refresh Functionality and Database
Warnings on page 213.
210
Saving Data to the Database
Using Refresh to Update Network Elements
If you are one of several people simultaneously using the same database, you may want to update
your project to include any Committed changes that other users have made.
Whenever you log out of the project, and then log back in, the data is automatically updated
(refreshed). After logging in, you will see network elements and any other objects in their currently
Committed state (including changes that were Committed while you were logged out), plus any
changes that you had Applied in your last session.
However, there are also two ways of refreshing the data while you are in a project session:
 You can use Refresh to update specific objects, or Refresh All to update all the objects in
your project at once, as described below.
 You can select the Refresh DB On Commit option in the Preferences dialog box (under
the File menu), if you want your project to be automatically updated with changes made by
other users whenever you Commit an object that has had changes. For more information,
see Setting General Preferences.
Important: While the Refresh options are convenient and effective, we still recommend logging out
of a project at regular intervals, preferably once per day. Please see the Important note at the end
of Example of Using Apply, Commit and Refresh on page 212.
To check if a specific network element has had changes Committed by other users:
In the Site Database, or Link Database, select the appropriate network element and on
the Refresh tab, click Check for Changes.
Any Committed changes to this element are listed, giving details of the change, including
when and by which user.
If there are changes, and you wish to update (refresh) the network element to reflect them,
click Refresh.
To update (refresh) a specific network element:
Right-click any network element and from the menu that appears, click Refresh.
(You can do this regardless of whether you are aware of any changes by other users.)
To update (refresh) all network elements:
1. In the Site Database window, or Link Database, ensure you are displaying the correct
view for the network elements you wish to update.
2. Right-click in a blank area of the left hand pane, and from the menu that appears, click
Refresh All.
- or From the Database menu, click Refresh All.
3. If you are using the 'master project with sub projects' functionality, select to view changes
between:
o
This project and the master project
o
All projects that are shared with your master project
4. In the dialog box that appears, view the changes to network elements that have been
Committed by users since you started using the project.
5. Click Refresh All to refresh your project with the other people's Committed changes and
merge in your own, or Cancel.
211
ASSET User Reference Guide
Tip: You can also access this dialog box from the Database menu by clicking Refresh All.
Note: When you perform a Refresh, any items added and Committed by other users will be visible
to you. However, refreshing does not update any objects that have been deleted by another user.
Such objects (assuming they have also been emptied from the wastebasket) will still be visible to
you until the next time you log out and log into the project.
Example of Using Apply, Commit and Refresh
This example demonstrates two users using Apply, Commit and Refresh in order to work together
in the same project and be informed of each other's changes.
Steve and Maria are connected to the same database and project and both will be working on the
same cell. Steve's role is to choose the best antenna type for the cell, while Maria's role is to set up
the cell identity information.
In the Preferences dialog box, both Steve and Maria have the Refresh DB on Commit checkbox
selected. This enables both of them to see any changes the other person has made, whenever they
commit an object.
Their actions are as follows:
1. In the Site Database window, Steve selects a new antenna for the cell, and then clicks
Apply and then Commit.
At this stage, Maria does not know that Steve has made any changes.
2. Maria edits the cell identity and clicks Apply. When she tries to Commit, a Database
Warning dialog box appears, alerting her that another user has made a committed change,
and prompts her to either continue or cancel. She decides to cancel, in case this committed
change affects her work.
3. To update the cell to show the latest committed changes, she right-clicks the cell, and from
the menu that appears, clicks Refresh.
She sees that Steve has changed the antenna type, which will not affect her work.
4. Maria now edits the cell identity and clicks Commit.
5. Meanwhile, Steve has logged out of his computer and gone to lunch. When Steve returns
to his desk, he decides to see if any changes have been made by other users since he has
been away. To do this, he clicks Check for Changes on the Refresh tab.
6. Seeing that Maria has made some changes, he right-clicks the cell, and from the menu that
appears, clicks Refresh.
They both continue working.
Important: The above Refresh functionality is based on information stored in an event log. For
performance reasons, the event log does not indefinitely store information, and, by default, records
are regularly purged after a set amount of time (or when the user logs out of the project, at which
stage the information is no longer required). For this reason, it is recommended to log out and log
into projects at regular intervals. Failure to do this can result in situations where concurrent users
are unaware of changes to the same object, even if they have both chosen the 'Refresh DB on
Commit' option. Note that the final state of the committed record will not be affected by this purging
of data from the event logs. It is only the refresh logic that is affected, in the sense that users would
not be alerted by the interim Database Warning message box.
212
Saving Data to the Database
About the Refresh Functionality and Database Warnings
The Refresh functionality and the Database Warning dialogs (as described in the preceding
examples) are based on information stored in an event log. For performance reasons, the event log
does not indefinitely store information, and, by default, the event log information is regularly purged
after a set amount of time (or when the user logs out of the project, at which stage the information
is no longer required).
For this reason, it is recommended to log out and log into projects at regular intervals, ideally once
per day. Failure to do this can result in situations where concurrent users are unaware of changes
to the same object, even if they have both chosen the 'Refresh DB on Commit' option.
Important: The purging of information from the event log only affects the refresh logic, in the sense
that users would not be alerted by the interim Database Warning message box, nor would they be
able to use the Refresh options for changes that would have relied on that purged information.
The final state of the committed record is totally unaffected by this purging of information from the
event log. Users can always automatically update (refresh) their data by logging out and logging
back into the project.
Saving Sandbox Changes to the Database
If you have logged in to a Sandbox, you can choose whether changes you make are seen:
 Only by you and other users of this Sandbox (using Apply)
– or –
 By all other users (using Commit)
This means that you can test out your changes among your sandbox users before you make them
available to everyone else.
In summary, Apply and Commit both store data in the database, but Applied changes are only
visible to the Sandbox users whereas Commit makes that data visible to all users.
Note: Currently, Sandbox changes to the Site Database, the Link Database, Logical Connections,
and Filters are fully supported by the ASSET database. Sandbox Inserts and Updates are also
supported for terminals, bearers, carriers, services and propagation models. Changes to other
configuration data and equipment types are not supported, so if multiple Sandbox users attempt to
edit these simultaneously, or have references to them where other Sandbox users have edits on
them, this may result in database error messages.
Applying Data in a Sandbox
To save changes so that they are seen only by yourself and other users of this Sandbox:
In the current window or dialog box, click
.
Changes are made to the Sandbox.
213
ASSET User Reference Guide
If another Sandbox user has already clicked Apply after making a change to the same object that
you are changing, you are prompted to decide what to do with that user's change. The Required
Action pane gives details of the object affected:
If you have changed the same data (by making a change in the same field) as the other Sandbox
user, and you click Perform Action, your data is Applied.
Committing Data in a Sandbox
To make any changes you have made in the Site Database available to all users:
1. Ensure that you want to make the change(s) available to all users.
2. Click
.
Tip: Depending on your user permissions, you can Commit all changes that you have
made in the currently selected filter in one action, by clicking
.
3. 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, merging their
committed data with your own changes.
Warning: When performing a Commit All, elements may fail to Commit under certain conditions.
Common reasons for failure are when a dependent element has never been previously Committed,
or the dependent element is not currently in a Committed state, or the dependent element is not in
the current filter. To avoid this, you should perform a Commit All on a filter that contains all the
dependent elements that have already been Committed at least once before. Alternatively, you
could use the Global Commit All option to Commit all of the configuration elements and network
elements inside the current project.
214
Saving Data to the Database
Refreshing Data in a Sandbox
To see if other users have made changes, from the Database menu, click Refresh All.
For some types of configuration data, deletions are not supported. On clicking Refresh All, lines will
appear in the message log to identify such instances. The types for which deletions are supported
are:
 All Site Database types
 All Link Database types (except those that are part of Chains)
 Logical Connections
 Filters
Also see Logging In to a Database on page 17.
Checking Blocked Actions between Different Users
In a multi-user environment, there is always the chance that a user's attempted Apply action on an
object (such as a network element or equipment) will be blocked by an action on the same object
by a different user. In such cases, a warning will appear, prompting the user to check the Message
Log.
Typically, this may occur when one of the following actions occurs:
 A user attempts to insert a non-unique identifier for a Property, Site or Node in the
database.
 A user attempts to delete an object (such as an antenna) that is still being used on a
Property.
 A user attempts to update an object that has already been moved to the wastebasket by
another user.
 A user attempts to delete an element (such a service) that has already been assigned to
another element (such as a terminal type) by another user.
The Message Log, by default, reports detailed information explaining why the action is blocked:
 Date and time stamp
 Object (Type: 'Property', Type: 'Cell Site', Type: 'Antenna Device', and so on)
 Identity of object (Visible ID)
 Change history (Created by User / Last Modified by User)
 State of object according to each user: (Object View: 'Insert' / 'Committed' / 'Updated' /
'Wastebasket')
 Project Name (this is useful information for objects - such as antennas - that can be shared
between projects)
('Visible' and 'View' refer to the fact that different users may see different settings according to their
'Applied state' tables.)
215
ASSET User Reference Guide
Here is an example of a warning:
And here is an example of the corresponding reporting (additional detailed information) in the
Message Log:
Preferences
In your Preferences, under the File menu, on the General tab, the detailed reporting is enabled by
default, but you have the option to disable it (basic reporting is still retained). The option is named
"Report elements in use".
You can also set a limit to restrict the number of messages produced for each action that is
blocked. This is useful to prevent high volumes of messages (for example, an antenna might be
assigned to 1,000 Properties, which would potentially produce 1,000 messages).
Resolving Commit Failures
There are circumstances under which using Commit All or Global Commit All will result in a
database error. When this happens, the Commit All Failures dialog box appears
For example:
Joan and Peter are connected to the same database and project and both will be working on the
same network element, a Property.
Their actions are as follows:
Joan Creates a new Property ‘P1’ with no physical antennas, then Applies and Commits this
Property.
Peter Loads the same project and can see Property ‘P1’.
Joan Adds one physical antenna and Applies the Property only.
Peter Adds one physical antenna and Applies the Property only.
Both users are trying to add the "same" physical antenna, that is, for the same Property and the
same index. At this point both entries are in the DIFF table and owned by different user identities.
216
Saving Data to the Database
Peter then uses Commit All on the Site Database dialog. His Commit fails and the Commit All
Failures dialog box appears:
A summary of the Commit All failures is written to the Message Log, along with the recommended
action to take:
To Resolve Commit Failures:
1. Double click on the element to copy the identifier and then find it in the Site Database
dialog box,
- or Select individual elements by clicking on the checkbox,
- or Select multiple elements then right click and choose Check Selected.
2. Click the Add to Selection Filter button. You can then user the Selection Filter on the Site
Database dialog box to resolve the commit errors.
If the element is then committed successfully, deleted into the wastebasket, or restored from the
Site Database dialog box, then the same element is removed from the Commit All Failures dialog
box.
The Clear Selection Filter button clears the Selection Filter.
The Close button closes the Commit All Failures dialog box. To reopen it, select Commit All
Failures from the Database menu.
217
ASSET User Reference Guide
Generating Reports of Uncommitted Changes
You can produce a report that details all the changes (additions, modifications and deletions) which
you have made and Applied to network elements, but not Committed to the database. These
changes are therefore not visible to other users.
The network element, each field and the modified and previous values of each field are shown.
The report details additions, modifications and deletions to all elements in your networks as well as
items such as propagation models and equipment.
To produce a report of uncommitted changes:
1. From the Database menu, click Delta Report.
2. If there are a large number of differences, a message appears to warn you that this might
take time. You can choose not to continue by clicking No, otherwise click Yes to produce
the report.
Tip: You can reduce the time taken to generate the report by clearing any orphaned DB
entries that exist in the 'Applied state' tables for the project. (Otherwise, any such entries
will be included in the Delta report as inserts or updates.) To do this, click on the Utilities
tab, and from the Tools menu, click Clean DB Orphans.
A message also appears if there are no differences.
The 'Applied state' tables in the database are analysed and a report appears.
The left pane displays each item, its type and a state showing if the element has been
added, deleted or updated. This picture shows an example:
218
Saving Data to the Database
Tips:
o
To sort the data in any of the columns in the left-hand pane, click the column heading
o
To find a particular network element ID, type the name in the Find ID box. ASSET
highlights the item with then name (or the nearest alphabetical/numerical match) that
you have entered.
3. Click the Info button to display the right hand pane which will show all fields associated with
any element that you select and its value:
In the right hand pane:
o
A red symbol appears next to an item with applied changes, for example,
o
A green symbol appears next to an item that has not been changed, for example,
o
To view any additional information, double-click the
symbol beside the name of an
attribute, then click the Back button to return to the previous list
o
If no information is available, the symbol is green
o
If the item is an addition, the 'Previous Value' is marked as '-'
o
If the item is a deletion, the 'Modified Value' is marked as '-'
Note: If you use the Delta Report to review the Neighbour Upper Limits, note that this cannot report
on any changes to generic values set in ASSET Administrator. It can only report on cell-specific
values in the Site Database.
Using the Version Reporter
Provided that you have the necessary permissions (for more information on user and group
permissions see the ASSET Installation and Administration Guide), the Version Reporter gives
you a bulk view and limited rollback capability for committed data only. It allows you to sort data
using the following parameters:
 Object Type
 Name
 Version
 User
 Time
 Filter
To open the Version Reporter:
1. Click on the Database menu.
2. Click Version Reporter.
219
ASSET User Reference Guide
This picture shows an example of the Version Reporter:
Example Version Reporter Dialog Box
If you have just used the Show History button on the History tab for an object in the Site
Database (for more information see 'About the History Tab' in the ASSET Radio User Reference
Guide), then details of changes to that object will be visible in the Version Reporter dialog box,
otherwise the dialog box will be blank.
To view changed objects:
1. Click Find. The Find dialog box appears.
2. Select the options you require to limit the objects included in your search.
Warning: Do not use the filter option for object types that cannot be filtered, or when
looking for version information for configuration data, since filters do not contain such data.
Note: If you select All from the Type drop-down list and select the Filter option, Find will
identify filterable object types only.
3. Click Find. Objects matching your search criteria are listed in the Version Reporter dialog
box.
To view the details associated with a particular object:
Select the row representing the required object and click the Details button.
The rollback facility allows you to revert a group of objects to their previous state. To do this:
Select the row representing the required object and click the Rollback button.
Note: The previous state reverted to is the latest previous state only.
To clear the Version Reporter dialog box and the cache memory of search results:
Click Clear Cache.
220
Viewing and Editing the Site Database
8 Viewing and Editing the Site Database
The ASSET database stores all the items needed to design a complete cellular network in a logical
hierarchy. This includes the parameter information that you add or edit in the various dialog boxes
(for example, network elements and equipment details).
The Site Database contains all the network elements for the project, including their identities,
parameters, locations, and so on.
It can contain elements for multiple technologies, all of which can be viewed at the same time. The
Site Database can follow the same hierarchy as the real network.
You can view and edit any of the elements and their parameters, either individually or on a global
basis, using your customised filters.
To open the Site Database window, do one of the following:
 From the Database menu, click Sites.
 From the ASSET main toolbar, click
.
The left pane contains your network hierarchy and when you select an item in this pane, related
information appears in the right pane. The information changes depending on your selection. This
picture shows an example:
Site Database Window showing parameter information for selected item
Note: If required, you can maximise the Site Database window, and/or you can extend the right
border or the bottom border of the dialog box. You can then resize the left pane and/or right pane
according to your needs. This also enables you to use the splitter bar in the middle to expand the
left pane and adjust the relative size of each pane. When you close or reopen the dialog box, or the
project, the size and position will be remembered.
221
ASSET User Reference Guide
The left pane contains the overall network structure details, and the right pane contains the detailed
parameters of each network element.
If you only see the left pane, and you want to see the right pane:
Click the right arrow button
.
You then click the same button if you want hide the right pane.
To view the sites within a particular filter, select the filter from the Filter drop-down list.
Tip: When you close and reopen the Site Database window, or the project, the last selected filter
will be remembered.
For some more information, see About the Site Database Window on page 60.
Using Templates for Network Elements
When planning a network, it is very likely that many network elements, for example sites or nodes,
will have the same characteristics. Instead of setting each attribute on each of these sites to the
same value, you can create and define templates. These templates will contain default attributes
that you set up and then these can be used as the basis for any new network elements.
Templates can be defined for various network elements; the most significant template is the MUNode because it represents the sites and nodes. (MU stands for 'Master Unit'.) Depending on
which technologies you are using in your project, you can decide whether you want the MU-Nodes
in your project to contain cells of a designated specific technology or cells of any technology. For
more information, see 'About MU-Nodes' in the 'Configuring Networks in ASSET Radio' chapter in
the ASSET Radio User Reference Guide.
You create templates in the Templates dialog box. This picture shows an example:
Templates dialog box
The types of template that you can create depend on the products you have installed.
222
Viewing and Editing the Site Database
You can maximise the Templates dialog box, or you can extend the right edge outwards or the
bottom edge downwards. If you extend it outwards, this enables you to use the splitter bar in the
middle to adjust the relative size of the left and right panes.
Note: Although you can create as many templates as you want, only one template for each network
element type can be active at any one time. You determine this by selecting one of the (mutually
exclusive) checkboxes for that network element type.
Project Defaults
In order to make a project easy to use right from the start, the following default objects, with pre-set
parameters, are provided each time a new project is created in ASSET:
 Antenna default
 Propagation model defaults (450, 900, 1800 and 2100 MHz)
 MU-Node Template defaults (with sites/nodes and cells for each single technology and for
some multiple technology combinations)
 Terminal type default (for each technology)
These default objects represent the minimum parameters required to create sites/nodes and
generate coverage arrays.
Creating a Template for a Network Element
Please read the information in Using Templates for Network Elements on page 222.
You can either create an entirely new template, as described below, or create a template from an
existing network element (as described in the subsequent topic).
To create a new template:
1. From the Database menu, click Templates.
– or –
In the Site Database window, from the View menu, click Templates.
2. In the dialog box that appears, the tree pane lists the network elements and below them,
the available templates for each type. You can either modify the default template or add a
new one.
3. To add a new template, right-click on the type of template you want to add, and click Add
Template:
223
ASSET User Reference Guide
4. Specify a meaningful name for the template and click OK.
5. On the tabs for the new template, set the required parameters.
6. Click Apply to save the changes.
7. Ensure the checkbox of your new template is selected, if you want to activate it as the
default template for the network element.
8. Click Close.
Note: For more information on completing templates for specific network elements such as MUNodes, see the 'Configuring Networks in ASSET Radio' chapter in the ASSET Radio User
Reference Guide.
Important: You cannot Commit templates, you can only Apply them. This means that they are only
visible to you, and cannot be shared directly with other users logged into the same database. The
only way to make them available to other users is by exporting them as an XML file. For more
information, see Exporting XML Data on page 424.
Creating a Template from an Existing Network Element
Instead of creating an entirely new template, you can also create a template from an existing
network element. This is recommended if you have worked on a configuration of an existing
network element and want to make it available for re-use elsewhere in your network.
You can do this in either of these places:
 Map View
 Site Database
Creating a Template in the Map View Window
You may have worked on a configuration of an existing network element that you want to save as a
template for use elsewhere in your network.
To do this in the Map View Window:
1. Right-click the required element.
2. From the menu that appears, point to Make Template From and then click the object for
which to make a template.
3. In the dialog box that appears, enter a name for your template.
4. If you want this template to be used by default whenever you add a new element to your
network, select the Set as default checkbox.
5. Click OK.
224
Viewing and Editing the Site Database
Creating a Template in the Site Database
You may have worked on a configuration of an existing network element that you want to save as a
template for use elsewhere in your network.
To do this in the Site Database:
1. In the Site Database window, ensure you are displaying the correct view. For more
information about this, see Viewing and Editing the Site Database on page 221.
2. Right-click the network element whose attributes you want to use in a template and from
the menu that appears select Create Template.
3. In the dialog box that appears, enter a name for your template and click OK.
4. If you want this template to be used by default whenever you add a new element to your
network, select the Set as default checkbox.
5. Click OK.
Note: For information on completing templates for specific network elements such as sites, nodes
and cells, see the relevant User Guide (for example, ASSET Radio).
Editing and Copying Templates
You can edit a template to change its attributes or duplicate it to start configuring a new template
based upon the settings of the original template.
To change the attributes of a template:
In the Templates window, select a template and on the tabs available make changes as
required.
For more information on the different template attributes, see Creating a Template for a
Network Element on page 223.
To copy a template:
1. In the Templates window in the Templates pane, right-click the template you want to
duplicate.
2. From the menu that appears, select Duplicate.
Deleting a Template
You can delete a template, providing that it is not the only one for a particular network element.
To delete a template:
1. In the Templates window, in the Templates pane, right-click the template you want to
delete.
2. From the menu that appears, click Delete.
225
ASSET User Reference Guide
Choosing the View in the Site Database
Using the View menu in the Site Database, you can change how the Site Database displays the
network elements:
 Logical Links View:
This shows the network elements listed as a hierarchy under their PLMN.
Note: In ASSET, network hierarchies under elements such as MSC, BSC, RNC, MME
(and so on) are optional.
 Network View:
This shows the network elements listed (regardless of hierarchies) under the appropriate
PLMN or logical network.
 Location View:
This shows a list of Properties (locations), and shows the network elements at each of
those locations.
226
Viewing and Editing the Site Database
 Cell-Antenna View:
This shows the Properties (locations) containing the antennas from which each cell is
physically transmitting. These locations may be the same as or different from the location
of the cell. For more information, see 'Assigning Antennas to Cells' in the ASSET Radio
User Reference Guide.
 Physical Links View:
This shows a list of Properties, showing how each of them is physically linked if you use
ASSET Backhaul.
Refreshing the Display of Network Elements in Site Database
To reconstruct the tree and refresh the information shown in the tree pane of the Site
Database:
1. In the Site Database window, ensure you are displaying the correct view for the objects
you wish to reconstruct.
2. Right-click in a blank area of the left hand pane and from the menu that appears, click
Reconstruct Tree.
– or–
From the Site Database View menu, click Reconstruct Tree.
Selecting Which Tabs to Display in Site Database
In the Site Database, the information for each network element is divided across a number of tabs.
Depending on your role, or the particular task that you are performing, not all of the information will
be relevant.
Tip: There are also general ways of displaying the networks elements. See Choosing the View in
the Site Database on page 226.
227
ASSET User Reference Guide
To choose to display only those tabs in which you are interested:
1. In the tree pane of the Site Database, right-click the network element for which you want to
customise the tab display.
2. From the menu that appears, click Customise.
The Choose Pages to Display dialog box appears. Here is an example:
3. In the Page Title pane, select the tabs that you want to display. You must choose at least
one tab.
Tip: If you want to undo a selection or ordering of tabs, and revert to all tabs being
displayed in their original order, click the Default button.
4. To define the order in which the tabs will be displayed, use the Move Up and Move Down
buttons.
The tab order in the Site Database is from left to right, so the higher up the list you move a
tab, the further left it will appear.
This picture shows an example, where only four tabs have been selected, and the 'Grid
Constraints' tab has been moved up one place from its original position:
228
Viewing and Editing the Site Database
5. Click OK.
The chosen tabs are displayed, in the defined order.
For our example selection described above, the Site Database would look like this:
Opening the Site Database at a Particular Site
To open the Site Database at a particular site:
1. On the General tab of the Preferences dialog box, ensure you select the Site Database
checkbox. For information, see Setting Up Your Preferences on page 38.
2. Hold down the Ctrl button and click the site in the Map View window.
The Site Database appears with the chosen site selected.
3. If the Site Database is not already expanded, click the >> button to display information
about this site.
Using the Map View to Find Elements in Site Database
To use the Map View for selecting elements that you want to highlight in the Site Database:
1. In the Site Database, select the filter containing the network element that you want to
highlight.
2. Click near a site in the Map View window and from the menu that appears, click the
element you want to be highlighted in the Site Database.
To select an element in the Site Database through Best Server arrays:
1. Ensure you have a Best Server array in memory or copied to clipboard.
2. In the Site Database, select the filter containing the network element that you want to
highlight.
3. In the Map View window, from the Tools menu, click Options.
4. In the Tool Options dialog box, select the Best Server tab.
5. Expand each category and select a Best Server.
6. To close the Tool Options dialog box, click the X button in the top right hand corner.
7. Using the mouse cursor, click pixels in the map view that you are interested in and the
element that the Best Server relates to is highlighted in the Site Database.
229
ASSET User Reference Guide
Creating a PLMN Network or Logical Network
You can add a PLMN or logical network in the Site Database and define all the attributes of its
elements.
To create a PLMN network:
1. In the Site Database, from the View menu, click Network View.
2. Click the right mouse button on All Networks and from the menu that appears, click Add
PLMN Network.
The PLMN network appears, and network elements can be added to it.
To create a Logical network:
1. In the Site Database, from the View menu, click Network View.
2. Click the right mouse button on All Networks and from the menu that appears, click Add
Logical Network.
The logical network appears, and logical nodes can be added to it.
When you have multiple networks (PLMN and/or Logical) in the project, it is important to set a
default network in the Site Database before you add any network elements manually in the Map
View. To do this:
1. Ensure the Site Database Network Display Mode is set to either 'Logical Links' or
'Network View'.
2. In the left pane of the Site Database, select the network you want to make the default, for
example:
3. Right-click and select 'Set As Default Network':
A plus sign will appear to the left of the network name, for example:
Any network elements that you add manually in the Map View will be added to the default network.
Important: When you perform an XML Export, the default network setting will dictate what happens
at the later stage when you perform an XML Import; the PLMN set as default in the exported file will
be set as default in the Site Database of the receiving project. Therefore, please pay attention to
which PLMN is set as the default network in the project that you are exporting from.
230
Viewing and Editing the Site Database
About Properties
A Property refers to a real estate location that is technology-independent. Its primary purpose in
ASSET is to hold details of the location co-ordinates.
Note: Another important function of the Property is that it stores the details of the antennas
available for the network elements residing on it. For more information, see the 'Configuring
Networks in ASSET Radio' chapter in the ASSET Radio User Reference Guide.
Each network element must always be parented to a Property, and inherits the same location coordinates as that Property.
ASSET can add multiple elements to the same Property. This flexibility enables you to co-locate
elements where necessary.
Tip: If you are in the Location View, and right-click the network, you can add a Property and Site or
Node simultaneously, rather than doing this in two stages. For more information on how to do this,
see Adding Properties and Sites/Nodes Simultaneously on page 235.
Viewing Properties in the Site Database
To select a Property and change information on its tabs, you first need to be able to see the
Property in the left pane of the Site Database window. To do this:
1. In the Site Database window, from the View menu, choose Location View or Physical
Links.
2. If you have chosen Location View, click the required Property.
- or If you have chosen Physical Links, click the required Property, then select the Property in
the menu that appears:
231
ASSET User Reference Guide
Tip: You can quickly view the Property details of a network element while remaining in the Logical
Links or Network View mode, by right-clicking the appropriate element and selecting View
Property. This will enable you to view (and, if appropriate, edit) the Property details for that
element. Here is an example:
Viewing and Changing Address and Contact Details
Property addresses and information about contacts are stored in the ASSET database. You add an
address for a Property on the Address tab of the Site Database:
Site Database - Address Tab
232
Viewing and Editing the Site Database
This tab also shows any contacts from those that you enter in the Contacts window:
Contact Persons
Details of how to add both addresses and contact details are described below.
Adding and Editing Property Details
To add or edit Property details:
1. In the Site Database window, from the View menu, ensure Location View is selected.
2. In the left-hand pane, select a Property.
3. On the Address tab, enter the address information you require.
4. If you have created any contacts, you can also choose a contact for this Property.
To view Property details from a site:
1. Select a site in the left-hand pane of the Site Database.
2. Click the Address tab to view addresses and contacts that are currently set for the
Property on which the site is situated.
Tip: If you want to quickly view the Property details of a network element while remaining in the
Logical Links or Network View mode, you can do this by right-clicking on any element and selecting
View Property. This will enable you to view (and, if appropriate, edit) the Property details for that
element.
233
ASSET User Reference Guide
Adding, Editing and Exporting Contact Details
To add or edit contact details:
1. From the Database menu, click Contacts and click the Add New Contact
Contact Details
or Edit
button.
2. Enter the details you wish to record then click OK.
To export selected details to file:
1. In the Contacts dialog box, select the person or persons whose details you want copied.
2. Click the Export the Selection to Excel button
.
3. In the dialog box that appears, select the required report format, and if required, browse to
the folder in which you want to store the exported details.
4. If you want to add date and time information to the file, select the Prepend with Date/Time
Stamp option.
5. In the Open With pane, select to save the contact details to file only or select an
appropriate editor - either the one registered for the file format or another one of your
choice.
6. Click OK.
The selected details are exported to the chosen file format, and (if applicable) open in the
chosen editor.
Adding and Deleting Network Elements in the Site Database
This section describes adding and deleting network elements in the Site Database window. You
can also use the toolbar in the Map View window to add elements.
To add network elements in the Site Database window:
1. In the Site Database, from the View menu, ensure you are displaying the network by
Logical Links, Location or Network View.
2. If you want to follow a hierarchical structure in the Site Database, in the left pane, right-click
the element above the one you wish to add. For example, to add a GSM site, right-click the
relevant BSC, or to add a UMTS Node B, right-click the relevant RNC.
Note: If you are adding a cell, you must follow the hierarchical structure by right-clicking
the relevant site or node.
- or If you do not want to follow a hierarchical structure (and you are not adding a cell), you can
just right-click on the relevant PLMN.
Tip: If you are in the Location View, and right-click the network, you can add a Property
and Site (for GSM) or a Property and Node (for UMTS) simultaneously, rather than adding
a Property and then a site or node. For more information on how to do this, see Adding
Properties and Sites/Nodes Simultaneously on page 235.
234
Viewing and Editing the Site Database
3. From the menu that appears, do one of the following:
o
Click Add <Item>, for example Add Cell
o
If the element you are adding can be based upon a template, follow the steps in Adding
Network Elements Based on Templates on page 237
Tip: When displaying the network by location, you can also add various network elements directly
to Properties, by right-clicking on the Property.
Note: You can also use the Map view to add or delete network elements. See Viewing and Editing
Networks on the Map on page 81.
Adding Properties and Sites/Nodes Simultaneously
In the Site Database window, in the Location View, you can add Properties and sites or nodes
(depending on your network technology) simultaneously, rather than having to create each element
separately.
To do this:
1. From the View menu in the Site Database, click Location View.
2. Right-click on the 'Base Network' category, and from the menu that appears, click the
option appropriate to your technology. For example, for LTE, click 'Add Property &
eNodeB':
235
ASSET User Reference Guide
3. For the site or node, click either the default template (the template that is currently selected
to be used) or another template from those you have created. For more information about
creating and using templates, see Using Templates for Network Elements on page 222.
The Specify Property and Cell Site (or Node) Information dialog box appears. This
picture shows an example:
4. In the Property Information pane, you can choose to create a new Property for the new
site/node or associate it with an existing Property:
o
If you select a New Property, select the required template and location co-ordinates
o
If you select to associate it with a Specific Property, click the Browse button and use
the Property Chooser to find the required Property
5. If you are creating a new Property, select the method for generating an ID for it:
o
If you select Auto generate new ID, a new ID is automatically generated for the
Property
o
If you select Specify new ID, type the required Property ID
Note: You cannot use spaces in the chosen ID; these are converted into underscore
characters as spaces are not allowed for unique identifiers.
6. In the Cell Site (or Node) ID Generation pane, select a method for generating IDs for the
cell site (or node):
o
If you select Auto generate new ID, a new ID is automatically generated for the cell
site/node
o
If you select Specify new ID, type the required cell site/node ID
Note: You cannot use spaces in the chosen ID; these are converted into underscore
characters to avoid database errors.
o
If you select to link it to the Property ID, the new cell site or node will take its name from
its parent Property
7. Click OK.
236
Viewing and Editing the Site Database
Adding Network Elements Based on Templates
Use the following steps to add a network element in the Site Database that is based on a
template:
1. In the Site Database, from the View menu, ensure you are displaying the network by
Logical Links, Location or Network View.
2. In the tree pane, right-click the PLMN or the network element to which you want to add
something, and from the menu that appears, point to the relevant Add <Item>.
For example, to add a site, you can right-click the relevant BSC and from the menu that
appears, point to Add Site.
3. Click either the default template (the template that is currently selected to be used) or
another template from those you have created. For more information about creating and
using templates, see Using Templates for Network Elements on page 222.
4. In the dialog box that appears:
If you are adding a Property
If you are adding any other type of network element

If you want to use your own ID, in
the Identity box, type the name
that you require.

Choose to parent the new element with an existing Property
or a new Property.


If you want to use the default
name that will be generated, leave
the Identity box empty.
If you have chosen to create a new Property, select to
generate the ID automatically, or type the name that you
require.


Click OK.
Select to generate the ID for the network element type
automatically, based on the parent Property ID, or type the
name that you require.

Click OK.
The new network element will appear in the left pane of the Site Database.
Deleting Network Elements in the Site Database
To delete network elements you need to have certain permissions. If you find you cannot delete
elements, see your administrator.
 When displaying network elements in the Logical Links view of the Site Database window:
To delete any network element:
In the left pane, right-click the element that you want to delete and from the menu that
appears, click Delete <Item>.
237
ASSET User Reference Guide
Deleted items, apart from uncommitted cell layers, are sent to the Wastebasket from
where they can be restored or deleted from the master database.
Warning: If a cell has neighbours or exceptions, these will be deleted with the cell.
Restoring the cell will not restore any of these.
 When displaying network elements in the Location view of the Site Database window:
To delete a Property as well as any MSC, BSC, site and equipment on that Property:
In the left pane, right-click the Property you want to delete and from the menu that appears,
click Delete Property.
 When displaying network elements in the Network view of the Site Database window:
To delete an entire Network (and any element and equipment on it), or an individual
network element:
In the left pane, right-click the network or network element that you want to delete and from
the menu that appears, click the appropriate Delete option.
Tip: It also possible to use the Selection expert to delete items. See Deleting Network Elements
using the Selection Expert on page 301.
Deleting Empty Properties
Empty Properties may exist in the Site Database because:
 Each time you create an MSC that is not already associated with a Property, a new
Property is created for you. If you then move the MSC to a different Property, you leave
behind an empty Property.
 You may have deleted an MSC, attached to a Property, leaving behind the empty Property.
To view empty Properties, ensure you are in Location view (see Choosing the View in the Site
Database on page 226). Empty Properties appear in the tree with no elements beneath them; in
this example, Property01 is an empty Property:
To delete a Property:
Right-click the network and from the menu that appears click Delete Empty Properties:
238
Viewing and Editing the Site Database
Deleting Items from the Wastebasket
You cannot create a new item with the same name as something in the Wastebasket, so you may
want to delete an item permanently.
Warning: Deleting items from the Wastebasket affects all users, as the item is deleted from the
database.
To permanently delete an item from the database:
1. From the Database menu, click Wastebasket or click
on the toolbar.
2. Select the checkbox next to each item you want to delete permanently then click Delete.
Tip: For multiple items, hold down Ctrl and select the names of items, right-click and
choose Select.
When other users next reload the project, they will notice the changes.
You can also delete the entire contents of the Wastebasket by clicking the Empty button. You do
not have to select any checkboxes by items to do this.
Restoring Deleted Items
Use the Wastebasket to restore deleted items to the database.
Note: You can only restore deleted items if the objects on which they depend are still in use or
have been restored first ('top-down' principle). For example, to restore BSC1 that belongs to MSC1,
you may first need to restore MSC1. If the Property itself was deleted, you would need to restore
that before anything else.
You can restore items such as physical elements of the network, cell layers and carrier layers, cell
and site equipment, terminal types and links.
To restore a deleted item:
1. From the Database menu, click Wastebasket.
2. Select the checkbox next to each item that you want to restore then click Restore.
Your item is restored in the Committed state that it was prior to any Applied changes that
you made. An exception to this is when you restore a newly added item that has not yet
been Committed when the Wastebasket will preserve its original contents.
239
ASSET User Reference Guide
Adding Logical and Cellular Connections in the Site Database
On the Connections tab for a network element in the Site Database, you can view and add logical
and cellular connections. This picture shows an example Connections tab:
Site Database - Connections tab
If you want to route traffic across any supported network type, you must first connect the network
elements with logical and/or cellular connections.
You can create logical and cellular connections in a number of different ways:
 Using the Map View. For more information on how to do this see Adding Logical and
Cellular Connections on the Map on page 92.
 Using the Connection Creation dialog box in the Site Database.
Tip: If you use this method, you can create more than one logical/cellular connection at the
same time, for example, to connect multiple NodeBs to an RNC or multiple SGWs and
MMEs to an eNodeB.
 By cutting and pasting 'lower' network elements onto 'higher' network elements in the Site
Database (Cellular connections only). For example, cutting and pasting a Site onto a
different BSC, or a Node B onto a different RNC.
To add logical or cellular connections using the Connection Creation dialog box:
1. From the Database menu, click Sites.
2. Select the network element for which you want to create logical/cellular connections.
3. Right-click, and from the menu that appears, click Add Logical/Cellular Connection.
4. In the Connection Creation dialog box that appears, you can set any of the following
selection criteria:
Item
Description
Filter
This enables you to filter the network elements that you want to be included in
the Find operation for potential connections. The All filter is the default.
Site/Node
You can use this edit box to type the ID of the potential connecting network
element, using a type of expression to assist the search: Substring, Regular
expression or Exact (case-sensitive or otherwise). You can also type a commaseparated list of IDs, if you want to find a multiple set of network elements.
Tip: When using the Site/Node option, it may be wise to set the Filter to 'All'.
Connection
240
The connection type that you want to create, either logical or cellular.
Viewing and Editing the Site Database
Item
Description
Technology
The technology used on the potential connecting network element.
Distance
The maximum distance from the potential connecting network element. (In other
words, the maximum length of the connection that you want to consider).
5. When satisfied with your selection criteria, click Find.
6. A list of potential connections that meet the criteria appears.
This picture shows an example, where three potential connections have been found for
SGSN0, to SITE0, SITE1 and SITE3 respectively:
7. Choose the connections that you want to create by selecting the required Site/Node IDs.
Note: The search may find connections that have already been created. If you choose
these, these connections will not be 're-created'.
8. Click OK.
The connections are created, and appear on the Connections tab:
The top pane displays a summary of all of the connections (per technology), and the lower
pane displays further information on each connection.
9. Apply and Commit your changes.
241
ASSET User Reference Guide
Making Changes to Network Elements in Site Database
In the Site Database, you can change various attributes, some of which are common to all network
elements and some of which are specific to particular network elements. Any changes you make in
the Site Database window are synchronised with the Map View window and reflected there.
In general, to make changes in the Site Database window:
1. In the Site Database window, select the element whose attributes you wish to change.
2. Ensure you have clicked the >> button so that the window is expanded and show tabs on
the right-hand side containing information related to the element that you selected.
3. Make the required changes on the tabs on the right-hand side.
Tip: To instantly expand the whole of your network hierarchy in the left-hand pane, press the * key
on your numeric keypad. Similarly, to hide most of the hierarchy, press the / key on your numeric
keypad.
Note: For information on where to find descriptions of each of the tabs, see About the Tabs in the
Site Database Window on page 242.
About the Tabs in the Site Database Window
The tabs displayed in the Site Database window vary according to the item you have selected and
the type of network you are designing.
To see the tabs on the right hand side of the Site Database window, ensure you have clicked the
>> button to expand the window.
Important: This section covers the tabs (such as Filters, Admin, Refresh) that are common to
several of the ASSET products. However, the majority of the tabs in the Site Database are specific
to the ASSET Radio product, which is covered by the ASSET Radio User Reference Guide. Within
that guide, you should look at the following locations:
 For information on tabs that are generic to all technologies, such as: Status,
Measurements, Neighbours, Carried Traffic, Physical/Logical Antennas:
o
Find the 'Configuring Networks in ASSET Radio' chapter and start with the topic named
'About the Tabs and Parameters in the Site Database'.
 For information on tabs that are technology-specific, such as: Antennas, Carriers, Cell
Parameters (powers, thresholds, load levels):
o
242
Find the technology-specific chapters appropriate to your network(s), and start with the
topic about setting parameters in the Site Database. So, for example, within the
chapter 'Using ASSET Radio with LTE', you would look under the heading 'Setting LTE
Parameters in the Site Database'.
Viewing and Editing the Site Database
About the Filters Tab
On the Filters tab in the Site Database, you can add (or remove) a network element into any static
filter, including the Selection Filter.
To do this:
1. On the Filters tab, click Display.
This shows all filters (static and dynamic) that currently contain the element.
2. Click Change.
3. Select (or de-select) the static filter(s) in which you would like the element to be included (or
excluded).
4. Click OK.
5. Click Update.
About the Admin Tab
The Admin tab appears for all elements in the Site Database and enables you to set write and read
permissions for the selected element.
On this tab, you can:
 For the Object Write Permissions, choose who has permission to make changes to the
element. To do this, select the required checkboxes (if appropriate, you can choose a group
from the drop-down list).
Note: You can only make changes to the permissions for the element if you are the current
owner.
 For the Object Read Permissions, choose who has permission to view the element. To do
this, select the required checkboxes (if appropriate, you can choose a group from the dropdown list).
Tip: You can also change this information on the basis of filters using the Global Editor.
For full information on permissions, see the ASSET Installation and Administration Guide.
About the Refresh Tab
The Refresh tab appears for all elements in the Site Database and enables you to see if any
committed changes have been made by other users working on the same project, and update your
element to include their changes.
On this tab, you can:
 Check to see if any committed changes have been made by other users to the network
element since you started your project. To do this, click Check for Changes.
 Update your element, to include committed changes that have been made by other users
since you started your project. To do this, click Refresh.
243
ASSET User Reference Guide
About the History Tab and Button
If your system administrator has activated ASSET's Version History feature (for information on
how to do this, see the ASSET Installation and Administration Guide), the History tab appears in
many ASSET windows. For some dialog boxes there is a History button. You can use the History
tab or button to access information on the changes to, and previous parameter settings associated
with, database objects. You can also use it to perform a rollback on objects so that they are
returned to an earlier state. This picture shows an example of a History tab in the Site Database
window:
History Tab for a Property in the Site Database window
When you first click a History tab, it is blank (unless you have set the automatic display preference for more information see Setting Filter and History Preferences on page 44).
Note: The timestamp shown in the History Tab is the time when you actually Commit the object into
the database. The 'Last Modified' timestamp shown on the General tab is the time when you last
edited the object. Therefore there can be a difference between them, if some time elapses before
you decide to Commit. In addition, the timestamp in the History tab is derived from the local
machine that hosts the database. This is to ensure consistency for users working in multiple
locations.
To see what changes have been made to the selected object:
Click Show History (for Filters and for Propagation Models, click the History button first).
A list of committed versions of the object appears. The highest version number represents
the most recently committed version of the object. The number of versions retained before
the oldest is overwritten by the newest is set by your system administrator. The maximum
is 100. For more information on how this number is set, see the ASSET Installation and
Administration Guide.
244
Viewing and Editing the Site Database
To compare the parameter settings of a committed version of the object with those currently
held in memory:
Select a single committed version of the object from the list on the History tab and click
Details. A dialog box appears showing the settings for the selected committed version in
the Previous column, and the settings currently held in memory in the Current column).
Rows with differences are highlighted in red except for the currently selected row which is
blue. You can click Next to jump to the next row with changes and Previous to jump to the
previous one. This picture shows an example:
To return to the History tab, click Close.
To change an object back to the state represented by a previous version, select the required
version on the History tab and click Rollback. The parameters are restored to their former settings.
To compare the parameter settings of two previously committed versions of the selected
object:
1. Hold down the Ctrl key and select the two versions that you want to compare from the list
on the History tab.
2. Click Details. A comparative list of parameters appears with those belonging to the more
recent of the two versions selected being shown in the Current column, and those
belonging to the older of the two versions being shown in the Previous column. Rows with
differences are highlighted in red except for the currently selected row which is blue. You
can click Next to jump to the next row with changes and Previous to jump to the previous
one.
About Web Enabled Site Data (External Data Tabs)
If your ASSET Administrator has configured any external data pages, you may see additional data
tabs for particular network elements. These tabs enable you to view external web-enabled content
from within the Site Database.
245
ASSET User Reference Guide
The name and number of tabs depends on how they have been defined in the ASSET
Administrator.
This picture shows an example, where an external data tab has been set up to display a useful
website for reference information:
Example external data tab
To refresh the information shown on an external data tab, right-click on the page and from the
menu that appears, click Refresh.
Any errors or load failures are described in the Message Log.
Important: To be able to use any hyperlinks on the external data pages, you must have the
appropriate permission. Contact your Administrator for more information.
Note: The information displayed on external data tabs is read-only, and cannot be used to modify
information in ASSET.
Making Global Changes to Network Elements
Changing information for a large number of sites can be a very lengthy process when performed
manually. To avoid this, you can use the Global Editor to change all sites identified by a filter.
Important:
 It is strongly recommended that you perform a Commit All on the Site Database
immediately before using Global Edit, so that you can subsequently use the Restore All
option if the changes do not match your requirements.
 Depending on which other products/licences are installed, there are many technologyspecific tabs. For information on these tabs, see 'Using the Global Editor in ASSET Radio'
in the technology-specific chapter in the ASSET Radio User Reference Guide.
246
Viewing and Editing the Site Database
To use the Global Editor:
1. In the Site Database window, click Global Edit.
2. Select the appropriate filter.
3. Select the items that you want to change for all the network elements in this filter.
The Global Editor consists of several tabs corresponding to different network elements. Not
all tabs are relevant to every network element type.
Tip: When you are trying to find a tab, it may be easier to use the Quick Page Selection
list on the left of the dialog box.
This picture shows an example of the Global Editor:
4. After you have made all the required modifications, you can then Apply them to the
database by clicking Apply.
This process may take a while depending on the number of changes being made. A
progress dialog box will be displayed.
When the changes have been Applied, the Global Editor dialog box closes.
Tips: You can:
o
Stop the Apply process at any time by clicking Abort. If you do this, it does not undo
any Applies the Global Editor has already performed.
o
Revert any Applied change to its previously Committed state by selecting the
appropriate network element in the Site Database and then clicking Restore.
o
Revert all Applied changes to their previously Committed state by right-clicking
anywhere in the left pane of the Site Database and then clicking Restore All.
5. If you want all other users to see the changes made, you must Commit each element
individually or Commit All. For more information on Committing changes, see Saving Your
Changes to the Database on page 205.
247
ASSET User Reference Guide
What Data Can You Edit Globally?
The following table lists some of the general items that you can modify using the Global Editor.
On this tab
You can modify
Status
Any of the fields that have been set up in the project.
Admin
Which users have write permissions (owner, group) to objects in the selected filter (this
can also be the All filter).
Note: You can only make changes to the write permissions for objects if you are their
current owner. That is, anything you select to change on this tab will affect only the items
that you own in the filter that you have selected.
Properties
Set Search Area Radius, Prevent Changes to Search Area, Override Mean Time To
Repair (only relevant to the ASSET Backhaul tool), Override DTM Height, Contact details,
Town, County, State.
For Override Mean Time To Repair, the 'Use Global Value' option is useful where you
have previously set the override with a 'User Define' value, and want to revert to 'Use
Global Value' for a group of Properties.
For Override DTM Height, the 'Use DTM Height' option is useful where you have
previously set the override with an 'Actual Height', and want to revert to 'Use DTM Height'
for a group of Properties.
For detailed information on the Physical Antennas, Logical Antennas and Antenna Ports
tabs in the Global Editor, see the 'Configuring Networks in ASSET Radio' chapter in the
ASSET Radio User Reference Guide.
Note: Depending on which other products/licences are installed, there are many additional
technology-specific tabs. For information on those tabs, see 'Using the Global Editor in ASSET
Radio' in the technology-specific chapter in the ASSET Radio User Reference Guide.
If you want to perform bulk reparenting of network elements (nodes to RNCs, for example), you
cannot do this using the Global Editor. But you can use the XML Editor, under the Logical Cellular
Connections drop-down item (dependent on your XML Editor version). To do this, you would create
a filter containing the appropriate nodes, modify the RNC column, and then re-import the XML file
with the correct option selected. For more information on the XML Data Editor, see Using the XML
Data Editor on page 437.
For information on reparenting in general, see Reparenting Network Elements on page 249.
248
Viewing and Editing the Site Database
Reparenting Network Elements
You can reparent network elements in the Site Database in a number of ways.
To reparent a single network element:
1. In the tree view, right-click the network element that you want to reparent and from the
menu that appears, click Cut <Item>:
2. Right-click the network element that you want to be the new parent, and from the menu that
appears, click Paste <Item>.
The reparented item appears beneath the parent item, in the Applied state.
You may, for example, want to reparent multiple nodes to a different RNC, or multiple sites to a
new BSC.
To do this using the Selection Expert with the Site Database (recommended):
1. Use the Selection Expert to either select an existing filter or to create a temporary filter
containing the items that you want to reparent. For more information on how to do this, see
About the Selection Expert and Selection Filter on page 294.
2. In the left-hand pane, select the items that you want to reparent.
3. From the Edit menu, click Cut from Database:
249
ASSET User Reference Guide
4. In the Site Database, in the tree view, right-click the network element that you want to be
the new parent, and from the menu that appears, click Paste <Item>:
The reparented items appear beneath the parent item, in the Applied state.
To do this using the Hierarchy tab in the Site Database:
1. In the tree view, select the parent of the items that you want to reparent.
2. On the Hierarchy tab for the parent element, click the Display button (or the Refresh
button if you have previously clicked it).
3. On the tab, select the required items and right-click:
From the menu that appears, click Cut.
4. In the tree view, right-click the network element that you want to be the new parent for the
items that you have cut.
5. From the menu that appears, click Paste <Item>.
In the tree view, the reparented items appear beneath the parent item, in the Applied state.
250
Using Vector File Features
9 Using Vector File Features
In ASSET, you can create and display your own vector file features, which are saved with the
project.
There are a number of different types of vector file feature, which are described in the following
table:
Feature Type
Description
Polygon
A set of points connected by lines that form a closed shape.
Line
Two or more points connected by lines that form an unclosed shape.
Point
A geometric element that has no dimensions, and whose position is based on its
coordinates.
Text
A set of words or letters.
This picture from the Map View window shows an example of vector file features (polygon, line,
point and text):
Example of vector file features
251
ASSET User Reference Guide
About the Vector Manager
You can create and manage vector file features in the Vector Manager.
To open the Vector Manager:
1. If not already open, open a Map View window.
2. In the Map View toolbar, click the Vector Manager button
.
This picture shows an example of the Vector Manager:
Vector Manager dialog box
The Vector Manager has a versatile toolbar. This table describes the button functions:
Button
Description
Create a new vector.
Select a shape.
Draw a point.
Draw a line.
Draw a polygon.
252
Using Vector File Features
Button
Description
Create a region polygon.
Tip: This is a very useful feature, enabling you to:

Set up a viewing region and subsequently return to that
region at any time.

Share that region with other users.

Store specific region coordinates for quick and easy
usage when you run the planning or array wizards.
For full details, see Creating a Region Polygon on page 262.
Add text.
Append an existing line.
Append an existing polygon.
Move a point within a shape.
Insert a point within a shape.
Move a shape.
Delete a point within a shape.
Delete a shape.
The usage of the buttons is described in the sections within Creating Your Own Vector File
Features on page 259 (in particular, Editing Lines and Polygons on page 268).
Tips:
 You can also open the Vector Manager from the Tools menu of the Utilities tab, without an
open Map View window. If you do this, you can perform some options (such as imports or
renaming) but you need a Map View if you want to use the drawing functionality.
 To hide the vector tree and show only the toolbar, from the Options menu click Hide
Vector Tree. To show the vector tree again, click Show Vector Tree.
Configuring Vector Files
To display a new MapInfo *.tab file you must first register it for use within ASSET . You only have to
do this once, because the details are remembered between sessions.
You can do this in three ways:
 Import the vector files one by one, using the Vector Manager. This is the most
straightforward and recommended method. For more information on how to do this, see
Importing Vector File Data.
 Ask your map data supplier to provide an index.xml file for the tab files that you have.
 Modify the index.xml file yourself, either manually or by using a power tool.
Important: For the second and third methods, you must ensure that the coordinates in the tab files
are in metres, and they are using the same projection system as the ASSET project that you want
to use them in. However, for the importing method, this is not necessary.
253
ASSET User Reference Guide
For more information on the index.xml file format, see the ASSET Technical Reference Guide. To
help you or your map data supplier create the index.xml file, Product Support can supply the
required xml schema and sample files on request.
Importing Vector File Data
You can import selected vector file data from a range of formats into the database at any time.
Important: For all the formats, if the imported vector is in a different projection system to that of the
current project, it will be automatically converted during import. This is also true for 'Mapinfo (*.tab)'
vector files, but there is an additional option to import 'Unconverted Mapinfo (*.tab)' vector files if
you do not want conversion to take place. (The subsequent section provides more information.)
To import vector file data:
1. In the Vector Manager, right-click a folder or top level node and from the menu that
appears, click Import Vector File:
2. You can choose from any of the following supported formats:
Notes:
o
You can define CPE (Customer Premises Equipment) FWA Terminal height and
azimuth values with the Table Browser. For more information, see Setting Values for
the Attributes on page 265.
o
You can import point vectors using the CSV format. Doing this requires the .csv file and
accompanying .prj and .csvt files to be available for import.
A new vector file feature is created and the vector data file is imported. If the vector file
feature consists of a single TAB file, the import is complete.
3. If the vector file feature is made up of multiple TAB files, you should now right-click the new
vector file feature name and from the menu that appears, click Import Vector File.
The vector file feature is updated with the additional TAB file.
254
Using Vector File Features
4. Continue to add files, until all of the files have been imported.
Note: If the vector file feature has any missing files, it is still loaded and the missing files
marked with a red cross.
MapInfo Vectors - Coordinate System Conversion
Before version 8.1, the Import Vector File process ignored any difference between the coordinate
system of the imported vector and the coordinate system of the project. From 8.1 onwards, you
have the choice of selecting:
 MapInfo with conversion (which converts the imported vector file’s coordinate system to
match the project)
- or  MapInfo without conversion (which leaves the imported vector file's coordinate system
unchanged)
Note: The original TAB file is not changed by either option.
In 8.1 onwards, when using the Import Vector File process, the default type of file is MapInfo (with
conversion):
If you use this option, a <VECTORNAME>_conv.TAB fileset will be created when the vector file is
imported, and the message log confirms the conversion.
This conversion may cause the area and perimeter of the new converted file to differ from the
original TAB file. You can check this by opening the _conv file and the original file in MapInfo and
comparing them. Any differences will probably produce a difference in ASSET’s Array Statistical
Reports for total area between a polygon vector imported in 7.0 and the same polygon vector
imported in 8.1 onwards.
Note: The conversion only occurs within the vector import process; any polygon vectors upgraded
to 8.1 onwards will not show a difference between 7.0 and 8.1 onwards.
In light of the above, in situations where you are importing a vector file in 8.1 onwards, and require
backward compatibility regarding the array area and perimeter, you can choose the non-conversion
option:
255
ASSET User Reference Guide
Warning: Importing a vector in a different system without conversion may lead to incorrect results.
Therefore we generally recommend that you do not use the Unconverted MapInfo importing option
unless you are sure that the vector and the project already have matching coordinate systems.
Exporting Vector File Data
You can use the Vector Manager to export selected vector file data.
Tip: You can export the files as they are (TAB files) or in MID/MIF format.
To export vector file data:
1. In the Vector Manager, right-click the appropriate vector (includes all its files) or an
individual vector file.
2. From the menu that appears, click:
Export to Folder
- or Export to MID/MIF format
3. Choose a folder and click OK.
The appropriate files are output to the chosen folder.
Troubleshooting Vector Files
Depending on your current situation, you can set up your vector files to work correctly in different
ways:
Scenario
Solution
You have created a new database
based on an import, and have a set of
old format vector files and an index.txt
file.
You can convert your vector files into the new format, and
create an index.xml file from the index.txt file, using the
index2tab power tool. To obtain this power tool, contact
Product Support.
You have created a new database
based on an import and have a set of
new format (*.tab) vector files.
You can import these vector files into your project, and create
an index.xml file, using the Vector Manager. For more
information on how to do this, see Importing Vector File Data.
You have created an entirely new
database
You need to purchase a set of MapInfo format (*.tab) files for
the geographical area that you require, and then import these
files.
Classifying User Vector Files
You can classify your user vectors so that you can subsequently search for and display only those
vectors that belong to the classification you are currently interested in. This is achieved by
assigning classifications to sub-folders in the Vector Manager and then moving vectors into the
appropriate sub-folders.
256
Using Vector File Features
The ability to classify user vectors can be particularly beneficial when using the following items in
ASSET:
 Layer Control Pane - Data Types tab (Map View window)
 Select Vectors dialog box (Statistics dialog box)
 Select Exclusion Polygons dialog box (Measurements toolbox)
 Vector Attribute properties in the Map Information Pane (Map View)
This table shows the available classifications and the vectors that should be associated with them:
Use This Classification
For Sub-folders Containing Vectors That
Building

specify building heights

display only polygon properties

contain only lines

display only line properties

are non editable

contain only point features

display only point properties (the display variable is preset to show
power)

display x and y coordinates, and power, in the Table Browser

contain only point features

display only point properties

display x and y coordinates in the Table Browser

contain only polygons

display only polygon properties
Line
Measurement
Point
Polygon
Note: Region polygons are a special case and will normally be
classified under Region as described below.

specify postal codes

display only point properties

display x and y coordinates in the Table Browser
Region

are generated by favourites, or by dragging existing regions, or,
for existing vectors, by clicking the Create Region Polygon
button. For more information, see Creating a Region Polygon on
page 262.
Text

contain only text

display only text properties

do not fit any other classification
Postal Code
Unclassified
To create a sub-folder in which to place, for example, all your Roads vectors:
1. In the Map View window, from the Tools menu, select Vector Manager.
2. Right-click on User Vectors and Measurements.
3. Click on Add Folder. A new folder called New Folder 1 appears on the vector tree.
4. Right-click on New Folder 1.
5. Click on Rename and type an appropriate name such as Roads.
257
ASSET User Reference Guide
You should ideally have sub-folders for each of the classifications shown in the table, ensuring that
each one has the appropriate classification.
To assign a classification to a sub-folder:
1. In the Vector Manager, right-click on the sub-folder in the vector tree to which a
classification is to be assigned.
2. Click Classifications. A submenu appears. This picture shows an example:
3. Click on the required classification. The classification is assigned to the sub-folder such that
any vectors placed in that sub-folder belong to the sub-folder's classification.
To re-classify a user vector file:
1. In the Vector Manager, right-click on the vector file to be re-classified.
2. Click Cut.
3. Right-click on the sub-folder representing the classification to which you want the vector to
belong.
4. Click Paste. The vector file appears under the chosen sub-folder in the vector tree and
inherits the classification assigned to that sub-folder.
258
Using Vector File Features
For an example of how useful the vector classifications can be, here is a picture of the Select
Vectors dialog box that is displayed when you are producing a Statistics Report for an array, and
wish to restrict the statistics to one of more vectors. Notice how you can use the Advanced pane to
limit the types (classifications) of vector that are listed for selection:
Example of Select Vectors dialog box
Creating Your Own Vector File Features
To create your own vector file features:
1. Ensure you have specified a system vector folder and user vector folder in your project. For
more information, see About the Map Data Directories Tab on page 25 and About the
Shared Data Directories Tab on page 25.
Note: It is recommended that you set these directory paths to be unique per project (if you
have multiple projects). If the user vector folder is shared between users, you should be
aware that any folder deletion will impact other users trying to use that folder until they
restart that project.
2. Ensure you have a Map View window open with the required area displayed.
3. In the Map View toolbar, click the Vector Manager button
.
The Vector Manager appears. This picture shows an example:
259
ASSET User Reference Guide
4. In the toolbar of the Vector Manager, click the Create New Vector button
.
The vector file features can be organised in separate sub-folders (for example Buildings,
Postal Codes, Unclassified).
When you use the Create New Vector button
, the new vector file feature is added to
the uppermost sub-folder that has its classification set as 'Unclassified' (for more
information, see Classifying User Vector Files on page 256). If no such sub-folder exists,
then a 'New Folder' is automatically created.
Here is an example:
Tip: You can also create a new vector from the Options menu in the Vector Manager. To
do this:
o
In the Vector Manager, click the folder under which the new folder is to be created.
o
In the Options menu, click Add Folder. A new folder is created and can be renamed.
o
With the new folder selected:
Click Add Vector if you want to create a new vector and store the tab file in the folder
defined for User (line) vector data on the User data directories tab of the Project
Settings dialog box. For more information, see About the Shared Data Directories Tab
on page 25.
- or Click Add Vector to Folder if you want to create a new vector and store the tab file in
a different folder.
5. In the Vector Structure Editor, type a name for the new vector.
6. Click Add to add an initial attribute to the vector:
260
o
Enter an attribute name, for example 'Population'
o
Choose whether you want the value to be a float, integer or string
o
Click OK
Using Vector File Features
For a full description of attributes, see Defining Attributes for a Vector File Feature on page
264.
7. If you selected the Add Vector to Folder option, then in the Browse for Folder dialog box
that appears, select the folder in which you want to store the vector:
- or If you clicked the Create New Vector button
or the Add Vector menu option (or you
clicked Cancel in the Browse for Folder dialog box), the tab file is stored in the folder
defined for User (line) vector data on the Shared Data Directories tab of the Project
Settings dialog box. For more information, see About the Shared Data Directories Tab on
page 25.
A new blank vector tab file with its own sub-folder in the User Vectors folder is
automatically created.
8. To rename the folder, right-click and select Rename, type the required name and then click
OK.
9. To create the new vector file feature, for example the path of a new road or an area that
you want to define, select the new vector tab file and select the required button, depending
on what you want to create. The following table describes the available options:
Click this button
To create
A line, or set of lines, in a vector.
A polygon (a closed shape).
A point.
A text item.
For more information on the different types of vector file features, see Using Vector File
Features on page 251.
261
ASSET User Reference Guide
10. In the Map View window, follow the appropriate instructions depending on which feature
you are creating:
If you are creating a
Do this
Line
1. Click the start point and all the subsequent points, as required.
2. Double-click the final point to complete the line.
Polygon
1. Click the start point and all the subsequent points.
2. Double-click the final point to complete the polygon.
Point
Click the location at which you want to add the point.
Text item
1. Click the location on the Map View window at which you want to add
the text.
2. In the dialog box that appears, type the required text.
3. Click OK.
11. You can now add attributes to the vector or polygon. For more information on how to do
this, see Defining Attributes for a Vector File Feature on page 264.
In the Vector Manager, you can save your vector file feature changes. To do this:
From the Options menu, click Save All.
For more information on saving and exporting vectors, see Saving Vectors on page 271.
In the Vector Manager, you can also delete vectors. To do this:
1. Select the vector that you want to delete.
2. From the Options menu, click Remove Vector.
Creating a Region Polygon
A Region Polygon vector can be extremely useful in various ways. You can:
 Set up a viewing Region and subsequently return to that Region at any time, because it will
be retrievable from your vectors on the Data Types tab of the Layer Control Pane.
 Share that region with other users, simply by making it available in the system vectors
(permission-dependent), rather than user vectors.
 Store specific region coordinates for quick and easy usage when you run any of the
planning or array wizards, without the need to precisely position the view every time you
run a wizard. You can use this method for the majority of the wizards in ASSET Radio, such
as Coverage Analysis, Simulator, Traffic, Neighbour Planner, and so on. This also means
you can remain looking at your current Map View when you run one of these wizards,
without having to zoom in or out of your current Map View. Instead, you can just continue
with your original view.
For more information, see 'Using Selected Vectors in the Planning or Array Wizards' in the
ASSET Radio User Reference Guide.
There are three ways to create a Region Polygon, using the Vector Manager, using a Favourite,
and using Drag Region.
To create a region polygon using the Vector Manager:
1. Perform the same initial steps as described in Creating Your Own Vector File Features on
page 259.
2. In the toolbar of the Vector Manager dialog box, click the Create Region Polygon button
.
262
Using Vector File Features
The Add Region Polygon dialog box appears:
3. In the Add Region Polygon dialog box, enter the required co-ordinates.
4. If you want to obtain a precise region which will match a specific map resolution, you can
achieve this by entering a 'Normalise to resolution' value and clicking Apply.
5. Click OK.
To create a Region Polygon from a Favourite
Simply open the required Favourite by selecting it from the Favourites drop-down in the
Map View toolbar.
When you do this, a Region Polygon vector is created automatically. The vector is added to those
listed in the Regions sub-folder of the User Vectors and Measurements folder on the Data Types
tab of the Layer Control Pane. It will also appear under the Regions node in the Vector Tree of
the Vector Manager dialog box. These pictures show two such vectors:
In the Layer Control pane, the newly created Region Polygon vector will be shown in blue text as
is Net1 in the above example. This indicates that it is the currently selected Region for the Map
View. To clear this selection you can right-click in the Map View and then click Clear Region. To
select another Region as current for the Map View, right-click on the Region name in the Layer
Control pane then click Select as Region. Only the currently selected Region is saved as part of a
Favourite.
To Create a Region Polygon Using Drag Region
1. Right-click in the Map View window and select Drag Region. The cursor changes to a
hand icon.
263
ASSET User Reference Guide
2. Left-click and drag the hand icon to the extent of the region you require, then release the
left mouse button. The Add Region Polygon dialog box appears with the coordinates of
your region filled in. You can use Normalise to resolution to adjust these if necessary.
The dialog box now contains an additional field: Name of Region.
3. In the Name of Region field, type a name for your new Region.
4. Click OK. The new region is added to those listed in the Regions sub-folder of the User
Vectors and Measurements folder on the Data Types tab of the Layer Control Pane. It
will also appear under the Regions node in the Vector Tree of the Vector Manager dialog
box.
Defining Attributes for a Vector File Feature
When you are creating a vector file feature, you can use the Structure Editor to add attributes to
it. Attributes can include such information as salary, quality of area, population data and so on, that
you can assign a value to.
If your vector file feature contains more than one feature (for example, two polygons), they will
share the same attributes.
To add an attribute:
1. In the Vector Manager, right-click the required vector file feature and click Structure.
2. In the Vector Structure Editor dialog box, click Add.
3. In the dialog box that appears:
o
Enter an attribute name, for example 'Population'
o
Choose whether you want the value to be a float, integer or string
4. Click OK and the attribute is added to the list.
5. To specify which columns are used in statistics reports, in the Attribute name columns
pane, type the required row numbers, each separated by a comma. In this example,
'CountyName' and 'Population' will be displayed in statistics reports:
For information about setting values for the attributes, see Setting Values for the Attributes on page 265.
For information about changing the display of vector file features, see Customising How Vector File
Features are Displayed on page 191.
264
Using Vector File Features
Setting Values for the Attributes
After you have created vector file features, and defined attributes for them, you can use the Table
Browser to:
 Set values for the attributes
 Highlight specific features within a vector in the Map View window
 Search for details of specific features within a vector
 Create a new vector using a searched sub-set
To do this:
1. Right-click the required vector file.
2. From the menu that appears, click Table Browser:
265
ASSET User Reference Guide
The Table Browser dialog box appears. This picture shows an example:
The top pane lists all of the features (polygons, appended polygons, lines, points and so on) that
belong to the vector file feature. Each feature is individually numbered (in the Feature# column)
based on its sequence of creation within the vector file feature.
The associated attribute columns correspond to the attributes already defined for the vector file
feature.
To set the attribute values:
1. In the top pane, select the required feature, and double-click the attribute value that you
want to edit.
2. Type the required value and press Enter.
This picture shows an example:
266
Using Vector File Features
To highlight specific features in the Map View window:
1. In the Display selection pane, choose whether you want to have the selected feature:
o
Highlighted in the Map View window
- or -
o
Highlighted and focused in the centre of the Map View window
2. In the top pane, select the required feature from the list.
The selected feature is highlighted (and if applicable, centred) in the Map View window:
To search for specific details of features:
1. In the Search pane, select the item(s) on which you want to search - you can search on the
feature 'number', and/or any number of the attributes.
2. To define the search criteria for one of the items, double-click the corresponding
Expression row, and in the dialog box that appears, select the required options and click
OK.
If you are searching based on more than one item, you should do this for each item.
3. Click Search.
The Table Browser highlights the features and attribute values that match the chosen
search criteria. This picture shows an example:
267
ASSET User Reference Guide
Tips:
o
If you just want to see search results, select the Display search results only
checkbox.
o
To highlight each of the search results in order, click the arrow buttons
.
To create a new vector containing a sub-set of the features displayed in the search results:
1. Ensure that the Display search results only checkbox is selected.
2. Select the checkboxes for the required features under the Feature# column:
3. Click Create Vector.
A new vector is created in the Vector Manager, and its name is displayed in the Message
Log.
Editing Lines and Polygons
In the Vector Manager, you can edit lines and polygons in a number of ways:
 To move a particular point in the line/polygon to another location, click the Move Point
button
, click the point that you want to move, and then click the new location
 To move an entire line/polygon (including any holes or islands) to another location, select
the line/polygon that you want to move (using the Select Shape button
Move Shape button
), click the
and then click the new location
 To delete a particular point in the line/polygon, click the Delete Point button
the point that you want to delete
and click
 To delete a line/polygon, select the polygon/line using the Select Shape button
then click the Delete Shape button
.
 To append an existing line with another line:
o
Select the line using the Select Shape button
o
Click the Append Existing Line button
o
Add the new line as required.
.
 To add a point to an existing line/polygon:
o
Select the line/polygon using the Select Shape button
o
Click the Insert a Point within a Shape button
o
Add the new point as required.
.
.
For information on how to save your changes, see Saving Vectors on page 271.
If you do not want to save your changes, right-click the required vector and click Undo All
Changes.
268
, and
Using Vector File Features
You can also create holes in polygons, or islands (two or more separate shapes that are still treated
as the same polygon). For more information on how to do this, see Creating Holes or Islands for
Polygons on page 269.
Creating Holes or Islands for Polygons
After you have created a polygon, you can add a hole to represent a sub-section within it. For
example, your polygon may encompass the whole of a city, but you may want to have a centre
section representing the densely-populated city centre, with the outer section representing the less
densely-populated suburbs:
Suburban Area of
a City
City Centre
Example Hole in Polygon
In this way, you can, for example, generate population statistics based on the suburbs only or the
centre only, and plan separate strategies accordingly.
Alternatively, you may want to represent certain sub-sections of one area, but not the area as a
whole. To model this, you can create separate islands for a main polygon. For example, blocks of
flats spread across a wide area:
Example Island for a Polygon
269
ASSET User Reference Guide
To add a hole or island to a polygon:
1. In the Vector Manager, right-click the required vector file feature and click Structure.
2. In the Vector Structure Editor dialog box, click Add.
3. Click the Select Shape button
, and in the Map View window, select the polygon to
which you want to add the hole or island.
4. From the Vector Manager toolbar, click the Append Existing Polygon
button.
5. In the Map View window, click the start point and all subsequent points of the polygon,
either inside an existing one (which would make it a hole) or somewhere else on the Map
View (which would make it an island).
Important: All points of the hole must be within the same polygon.
6. To link up the two ends of the polygon, double-click.
7. To save the polygon, from the Options menu, click Save.
For more information on how vectors can be saved, see Saving Vectors on page 271.
When you select the hole or island, the main polygon should be selected too, and vice
versa.
This picture shows a polygon with a smaller island to its right:
You can add extra lines to existing lines or sets of lines in a similar way:
1. Click the Select Shape button
, and in the Map View window select the line or set of
lines that you want to add an extra line to.
2. From the Vector Manager toolbar, click the Append Existing Vector button.
3. In the Map View window, click the start point and all subsequent points of the line.
4. To finish the line, double-click.
5. To add the line to the database, from the Options menu, click Save.
270
Using Vector File Features
Saving Vectors
After you have created or edited the vectors in your project, you can:
 Save them locally with the current MapInfo projection setting included, so that you can use
the vector data in other tools (for example, MapInfo).
 Save them to the default vector folder.
Tip: To check where this is, from the File menu, click View Project Settings. On the Map
Data Directories tab, the default vector folder is defined as the Line (Vector) Data folder.
To save vectors to a local folder:
1. In the Vector Manager, select:
o
The vector name, if you want to save a vector and all of its associated files
o
The individual vector file, if you want to save a single file as a vector
2. Right-click, and from the menu that appears, click Save Copy As.
3. In the dialog box that appears, browse to the folder in which you want to save the vector file
feature.
If you are saving an individual vector file, you must also specify the TAB filename.
4. Click OK.
The selected file(s) are saved to the chosen location, using the MapInfo projection setting
defined in the project settings.
To save vectors to the default vector folder:
In the Vector Manager:
o
Right-click the required vector name and from the menu that appears, click Save
- or -
o
Select the required vector, and from the Options menu, click Save
The selected vector is saved to the default vector folder.
Tip: If you want to save all of the vectors that you have created, from the Options menu, click
Save All.
Also see Exporting Vectors on page 271.
Exporting Vectors
After you have created or edited the vectors in your project, you can export them to TAB/DAT file or
to MID/MIF file formats. You can:
 Export vectors locally, without the current MapInfo projection setting, to a TAB file.
 Export vectors locally, without the current MapInfo projection setting, to a MIF file.
Note: Export to MID/MIF format does not currently support polygons with holes.
271
ASSET User Reference Guide
To export vectors to a TAB/DAT file in local folder:
(Saves an exact copy of the original file without including the current MapInfo projection setting.)
1. In the Vector Manager, select:
o
The vector name, if you want to export a vector and all of its associated files
o
The individual vector file, if you want to export a single file as a vector
2. Right-click, and from the menu that appears, click Export to Folder.
3. In the dialog box that appears, browse to the folder to which you want to export the vector
file feature.
4. Click OK.
The selected file(s) are exported to the chosen location.
To export vectors to a MID/MIF file in local folder:
(Saves an exact copy of the original file without including the current MapInfo projection setting.)
1. In the Vector Manager, select:
o
The vector name, if you want to export a vector and all of its associated files
o
The individual vector file, if you want to export a single file as a vector
2. Right-click, and from the menu that appears, click Export to MID/MIF format.
3. In the dialog box that appears, browse to the folder to which you want to export the vector
file feature.
4. Click OK.
The selected file(s) are exported to the chosen location.
Also see Saving Vectors on page 271.
272
Using Filters and Fields
10 Using Filters and Fields
Filters enable you to group elements logically according to their attributes and/or functions, which
enables you to divide your network into more manageable sections for analysis, diagnosis and
display.
As well as filtering on network element type, hierarchy, owner and so on, you can define fields and
use them as the basis for a filter.
To make the management of filters easier they can be stored at two levels:
 At the system level in the System folder, making them available to all users on a system
 At the user level in the User folder, making them available to a single user only
The level at which you can store filters is controlled by the permissions that you have been granted.
Tip: On the Filters tab of the Preferences dialog box under the File menu, you can choose from a
variety of options to determine which user filter folders to display. For more information, see Setting
Filter and History Preferences on page 44.
Using Fields in ASSET
Status fields are primarily used to enable project managers to manage and oversee the network
engineering cycle, from initial design to the rollout phase.
ASSET enables you to set up any number of fields in your project, so that they can provide
information about individual network elements (such as sites, cells or microwave links) in the Site
Database. Fields may be used for a variety of reasons, for example, to track the rollout phase of a
site, or record its equipment, or its region, or perhaps the name of the planner in charge.
Fields can serve as a useful way of creating filters. This means that you can, for example, display
"In Build" sites in the Map View, or generate a coverage array for "On Air" cells, or generate an
interference analysis for microwave links which are "Live", and so on.
At the initial stage of setting up these fields, they must be associated with specific network element
types. After this has been done, the fields appear on the associated network elements in the Site
Database. This enables you to assign the appropriate field option for individual network element
types (such as site, cell, link or Property).
Note: You define status fields within the ASSET Administrator module, in the Field Definer dialog
box. For more information, see the ASSET Installation and Administration Guide.
It is generally advised that fields be set up as early in the project as possible, so that they are
available for the planner to assign the relevant option to the relevant network elements in the Site
or Link Database, or in the Templates.
273
ASSET User Reference Guide
This picture shows an example of the Field Definer:
Example of Field Definer dialog box
Examples of Field Definitions
Some examples of fields that could be created are:
Field
Type
Options
Rollout Phase
Picklist
unset, Planned, Acquired, In-Build, On-Air
Vendor Equipment
Picklist
unset, Nokia, Ericsson, Siemens
Region
Picklist
unset, North, South, East, West
Equipment Costs
Float
any decimal number
Planner's Name
String
any text
Visit Due
Boolean
True or False
Phase Number
Integer
0,1,2,3,4...
Established
Date and Time
date and time limits and timezones
Important: When defining fields, it is important that you associate each field with the appropriate
network element object type(s), such as Properties, sites, cells or microwave links. For more
information, see the ASSET Installation and Administration Guide.
Tip: For picklists, it is strongly recommended that the first option in each group is named “unset”,
"unknown", or similar, so that this can be the default when no particular option has yet been
assigned.
Viewing and Editing Fields for Network Elements
When the fields have been defined in the ASSET Administrator module and committed to the
database, you can view and edit the fields within the Status tabs of the Site Database, listed
against the relevant network elements, and, in the case of the Link Database, against each link.
274
Using Filters and Fields
To view the status of the parent elements on this tab:
1. In the Site Database window, in the tree pane, click the required element.
2. Click the Status tab to see a list of the fields for this network element, and for any parent
elements that it may have.
Note: Fields displayed in grey are read-only - you do not have permissions to edit these.
The group permissions for the currently selected field are displayed in a panel at the
bottom of the status tab.
3. To change an associated field:
o
For Picklist or Boolean types, click in the field value column and select the required
value from the drop-down list, as shown here:
- or o
For Float, String or Integer types, double-click in the field value column, and type or
edit the value.
- or -
o
For Date and Time type fields, click > to expand the editable rows, then edit the values
in them as required.
Tip: Any fields that you have edited - but not yet Applied - are displayed in bold.
In the case of the Link Database, you can find the Status tab under the General tab for a
microwave link.
Note: Fields in the Site Database operate independently of network hierarchy level or technology.
For example, if you have the same field associated for the Property, site and cell object types, an
individual field assignment in the Site Database at the site level will not affect or update the other
levels. For more information, see the ASSET Installation and Administration Guide.
Using Filters in ASSET
Filters provide a logical grouping of network elements according to their characteristics or functions.
They enable you to sub-divide the network into more manageable sections for analysis, diagnosis
and display, and they therefore represent a powerful way of selecting a subset of items such as
Properties, sites, links or cells, from the ASSET database.
You can create your filters according to many different criteria, including element type, hierarchy,
fields and polygons, as well as attributes such as antenna type, frequency band, carried traffic, and
so on. For example, you could create a filter to display all operational sites within a geographical
region which are using a particular vendor’s equipment.
275
ASSET User Reference Guide
Filters can be defined as either Static or Dynamic, and there is an additional Selection Expert filter.
This table summarises each type:
Filter Type
Description
Static Filters
These are static lists of objects specified by the user. These filters can only be
changed by the user adding or deleting objects from the list.
There are various ways of adding and removing objects.
Dynamic Filters
The lists of objects in dynamic filters will constantly update as the network
evolves. These filters select network elements based on criteria such as:

Object type (for example, BSC, Site, Cell, Link)

Status Field assignment

Cell Layers assigned

Parenting

Geographical Location (for example, within a polygon)
These filters are 'dynamic' because the inclusion list will automatically be updated
whenever a change is made to any of the parameters forming the filter definition
criteria.
Selection Expert
There is also an 'on-the-spot' memory filter which can swiftly and powerfully select
items from the 2D View or Site/Link Database. Also, the memory filter can
optionally be saved as a static filter for future use.
Note: In the Filters Database, static filters always appear as RED, and dynamic filters always
appear as BLUE. This helps you to quickly identify the filter type.
Purpose and Uses of Filters
Filters are a very important feature in ASSET Radio.
You can use filters to:
 Limit the list of network elements displayed in the Site Database
 Determine which combination of network elements appear in the Map View
 Vary the customised appearance of different filters in the Map View
 Control which items are to be included in the various wizards
 Limit which items will be included in any global edits in the Site Database
 Limit which items to include in the various reports
 Limit which items to include an XML Export
Note: Created filters can either be stored in a System folder (for everyone to use) or in the User
folder, which means that they are not available to other users (unless they expressly choose to
'show all user filters' on the Filters tab of the Preferences dialog box under the File menu). The
Apply and Commit principles are the same as for any other object saved to the database. The
general recommendation is to make sensible usage of the system and (personal) user folders, and
only commit filters that are essential to all users.
276
Using Filters and Fields
Creating a Dynamic Filter using the Filter Wizard
To create a dynamic filter:
1. On the main toolbar, click the Filters button
.
2. The Filter Database dialog box appears, displaying any folders and filters which have
already been set up:
Note: The Selection Filter is a special filter which is used by the Selection Expert, and is
described in a subsequent section.
3. Select the folder in which you want to store the new filter and then click Add. This will
launch the Filter Wizard, which guides you through the creation process.
Tip: You can create sub-folders, if required, by right-clicking on the System folder or on
your individual User folder.
4. Step 1 of the Filter Wizard prompts you to give the filter a meaningful name (this can be
modified later if required):
If your new filter has similar selection criteria as an existing filter, you can choose the option
to use an existing filter as a template and select it from the drop-down menu.
Click Next.
5. Step 2 of the Filter Wizard displays a list of Available Attributes. Move each required
element type to the Selected Attributes pane by double-clicking it, dragging it, or selecting
it and using the right arrow button. This will define which objects are to be considered in the
filter.
For example, one method would be to expand one of the items in the Available Attributes
pane to reveal the selection of fields already set up for the project in ASSET
Administrator. The required field can then be selected as an attribute for the filtering
criteria.
Polygons represent another way in which network elements can be filtered. All available
polygons can be displayed by expanding the Property element in the Available Attributes
pane.
277
ASSET User Reference Guide
In this example, the Cell Site element has been expanded, and the 'Rollout Phase' field has
been selected as an attribute to be considered in the filtering process:
You can specify the logical operators by right-clicking on them to toggle between the two
types:
o
If you choose OR, a value will be returned if any of the attributes are present
o
If you choose AND, a value will be returned only if all the attributes are present
Tip: It is also easy to modify these operators on the next screen, and to dynamically
preview the resulting item selection. (In this particular example, this will make no
difference, since there is only one attribute selected.)
Note: You can group attributes together with their own logical operator, and create rules
within rules. The easiest way to do this is to drag and drop the attributes into their logical
groupings. The Selection Rules will be activated from top to bottom, branching where
specified. For some ideas on how to create 'faster' filters, see Making Your Dynamic Filters
More Efficient on page 306.
When you have all the element types and criteria that you want to filter on, click Next.
6. Step 3 of the Filter Wizard prompts you to set the definitive rules and criteria for the filter
and enables you to modify the logical operators using the associated radio buttons.
Important: On this screen, you must click on each of the selected attributes to ensure that
the appropriate options appear on the right-hand side.
Define the exact rule for each element type or criterion by selecting it in the 'Selected
Attributes' pane, and:
278
o
Selecting a rule definition (for example, 'Equals'). You can also reverse the rule
definition (for example, 'Not Equal To') by selecting the 'Not' checkbox.
o
Typing a value in the box or, if applicable, clicking the 'Values' button to select the
value(s) that you are interested in (for example, when selecting Field values).
Using Filters and Fields
In this example, click the 'Values' button, and select the ON AIR option:
Then click OK.
You can click Preview to see a list of all the elements that are included in the filter
according to your latest definitions. This will help you to refine the filter further if necessary.
When satisfied with your criteria, click Next.
7. Step 4 of the Filter Wizard displays the list of elements currently included in your filter. The
filter will be 'Dynamic' (unless you now decide to switch it to 'Static' - but if you want to
create a static filter, it is easier to carry out the steps in the following section).
Note: In this example, we have used the simple approach of using only the Field attribute;
notice that all items associated with the filtered sites are also included in the filter, in other
words, their related objects, such as Properties, MSC, BSC, cells, and so on. If we had
selected the cell site AND its field attribute in Step 2, we would only have the cell sites in
the filter, and not the related objects.
Click Next.
8. Step 5 of the Filter Wizard enables you to set up the customised display settings for the
items which are included in your filter. If you selected the “Use existing filter as template”
option in Step 1, this screen will default to those settings. You can also easily modify these
later in the Map View.
Click Next.
279
ASSET User Reference Guide
9. Step 6 of the Filter Wizard (the final step) enables you to modify the name of the filter, and
also to establish which other users, if any, will be able to modify this filter in the future
(assuming it is committed, and assuming they have the appropriate permissions).
10. When satisfied, click the Finish button to complete the Filter creation process.
The newly created filter appears in the Filters Database, in the folder you selected at the start of
the process. As a Dynamic filter, it will appear with a BLUE symbol, as in this example:
Example of Dynamic Filter
In the Filters Database, any of the filters may be committed, modified or removed, and also moved
or copied between folders.
If you want this filter to be available for use by other users, you can Commit the filter. Otherwise, it
will only be available locally on your machine.
All created filters are available for use in various parts of ASSET, such as the Site Database, Link
Database, Map View, Coverage Arrays, Wizards, Reports, and so on.
Grouping Attributes in Dynamic Filters
When you are creating dynamic filters, you can group attributes together with their own logical
operator, and create rules within rules.
To do this:
1. In the Selected Attributes pane, right-click the first attribute.
2. From the menu that appears, click Group.
3. Click the element you want to group it with.
- or –
280
Using Filters and Fields
1. In the Selected Attributes pane, select the first element you want to group.
2. In the Available Attributes pane, select the element that you want to group it with.
3. Click the right arrow button
.
- or 1. In the Selected Attributes pane, click the first element you want to group.
2. While still holding the mouse button, move to the element that you want to group it with.
This picture shows an example, in which the filter is set up to find all Properties or MSCs within the
coastline vector:
Creating a Static Filter using the Filter Wizard
To create a static filter:
1. On the main toolbar, click the Filters button
.
2. The Filter Database dialog box appears, displaying any folders and filters which have
already been set up.
Note: The Selection Filter is a special filter which is used by the Selection Expert, and is
described in a subsequent section.
3. Select the folder in which you want to store the new filter and then click Add. This will
launch the Filter Wizard, which guides you through the creation process.
Tip: You can create sub-folders, if required, by right-clicking on the System folder or on
your individual User folder.
4. Step 1 of the Filter Wizard prompts you to give the filter a meaningful name (this can be
modified later if required):
If your new filter has similar selection criteria as an existing filter, you can choose the option
to use an existing filter as a template and select it from the drop-down menu.
Click Next.
5. Steps 2 and 3 of the Filter Wizard are not applicable to static filters, so ignore both steps by
clicking Next.
281
ASSET User Reference Guide
6. In Step 4 of the Filter Wizard, select the 'Static' option. This picture shows the tabs that
become visible:
You can now manually select whichever elements you require by using the tabs and
methods described in this table:
Tab
Description
How to Add Items to the Filter
Identifier
Use exact
matches or
regular
expressions

Select the element type that you want to add.

Type the element ID, either defining an exact match or defining the
match with a regular expression. For more information on using
regular expressions, see Examples of Searching by Regular
Expression on page 109. You can make this case-sensitive by
selecting the Match case option.

Click Add, and all of the elements matching this identifier will be
displayed in the Active Elements box.
Note: You can also remove items from the filter. To do this, in the
Active Element pane, right-click the elements(s) and from the menu
that appears, click Remove. You can also select the item(s) in the
Active Element pane and then click the Remove button that appears in
the Identifier tab.
File List
Filters
282
Browse to a text
file listing the
identifiers on
separate lines
Use a
combination of
chosen filter and
element types

Select the element type that you want to add.

Type in a file name or click the Browse button and locate the
correct file.

The file format of this text file is a list of site identifiers each on a
separate line.

Click Add, and all of the elements matching this identifier will be
displayed in the Active Elements box.

Select the element type that you want to add.

Choose the filter from which you want to add elements of the type
selected, and click Add.
Using Filters and Fields
Tab
Description
How to Add Items to the Filter
Location
Choose all or

selected network
elements in a

particular Map
View
Open a Map View window displaying the area and items you want
to add or remove from the filter.
On the Location tab, select the element type, for example
Property.

In the Select Map View pane, click the appropriate button, for
example, Add Element.

In the Map View window, click the required network element.

Repeat for all of the elements that you want to add to or remove
from the filter.

Click the Stop Adding or Stop Removing button.
Tip: You can use the Add Element or Remove Element buttons with
multiple Map Views if required. The element selection is controlled
automatically, depending where you click.
Add or remove

all of the

elements of a
selected element
type


Hierarchy
Include or
exclude
hierarchical
elements
Open a Map View window.
On the Location tab, select the element type, for example
Property.
Click the required Map View (it is important to do this first when
using the Add or Remove All buttons)
In the Select Map View pane, click the appropriate button, for
example, Add All Elements.
For items that already exist in the filter, you can add or remove parent
elements, child elements or neighbours. The functionality is the same
as for the Selection Filter. See Editing the Selection Filter using the
Element Hierarchy on page 303.
Click Next.
7. Step 5 of the Filter Wizard enables you to set up the customised display settings for the
items which are included in your filter. If you selected the “Use existing filter as template”
option in Step 1, this screen will default to those settings. You can also easily modify these
later in the Map View.
Click Next.
8. Step 6 of the Filter Wizard (the final step) enables you to modify the name of the filter, and
also to establish which other users, if any, will be able to modify this filter in the future
(assuming it is committed, and assuming they have the appropriate permissions).
When satisfied, click the Finish button to complete the Filter creation process.
All newly created filters appear in the Filter Database, in the folder you selected at the start of the
process. Static filters appear with a RED symbol, as in this example:
Example of Static Filter
In the Filters Database, any of the filters may be committed, modified or removed, and also moved
or copied between folders.
283
ASSET User Reference Guide
If you want this filter to be available for use by other users, you can Commit the filter. Otherwise, it
will only be available locally on your machine.
All created filters are available for use in various parts of ASSET, such as the Site Database, Link
Database, Map View, Coverage Arrays, Wizards, Reports, and so on.
Editing and Deleting Filters
To edit an existing filter:
1. In the Filter Database dialog box, select the filter you want to edit.
2. Click Edit.
3. Use the Filter Wizard to modify the filter.
Tip: To rename a filter, in the Filters dialog box, right-click the required filter and then click
Rename. In the dialog box that appears, type the new name and click OK.
To delete an existing filter:
1. In the Filter Database dialog box, right-click the required filter.
2. From the menu that appears, click Remove.
- or Select the filter you want to delete and click the Remove button.
The filter is moved to the Wastebasket. To ensure other people cannot use it, you will
need to remove it from the Wastebasket. Until you do this, the filter is still available to
others.
Organising Filters
Using Folders
To enable you to store and organise your filters effectively, two filter folders called System and
User are provided. If you have the required permissions you can set up sub-folders within one or
both of these and store your filters in them.
Example of Filter Database dialog box
Important: On the Filters tab of the Preferences dialog box under the File menu, you can make
various choices of which user filter folders to display. For more information, see Setting Filter and
History Preferences on page 44.
284
Using Filters and Fields
To create a new folder for filters:
1. In the Filter Database dialog box, right-click the filters folder for which you wish to create a
sub-folder - either System or User.
2. From the menu that appears, click New Folder. A new folder appears in the tree view and
you can change this name if you wish.
Tip: You can create further folders within folders by right-clicking a folder, and then from the menu
that appears, clicking New Folder.
Moving Filters
When you are organising your filters, you may want to move them between folders. To do this:
1. Right-click the filter that you want to move, and from the menu that appears, click Cut.
2. Right-click the folder that you want to move the filter to, and from the menu that appears,
click Paste.
– or –
1. Select the filter you want to move, and while still holding the left mouse button down, drag
the filter onto the required folder.
2. Release the left mouse button to place in the folder.
Copying Filters
As well as adding new filters, you can also copy a filter and then modify it.
For example, if you have created a complex filter to show all BSCs owned by John Smith that are
also in the South region and have one antenna, you can copy this filter and then modify it to show
the same information but for BSCs owned by Pat Taylor.
Copying in the Filter Database
1. In the Filter Database dialog box, right-click the filter that you want to copy, and from the
menu that appears, click Copy.
The filter and its display properties are copied.
2. Right-click the folder that you want to copy the filter to, and from the menu that appears,
click Paste.
Selecting to Use an Existing Filter as a Template
When adding a new filter you can choose to base it on an existing filter.
285
ASSET User Reference Guide
To do this:
On the first page of the Filter Wizard, select the "Use an existing filter as a template"
option:
The rules and display properties are copied from the selected filter, and appear on the
subsequent pages of the wizard.
Note: If you choose the All filter, only the display properties are copied.
Copying Display Properties Between Filters in the Map View Window
1. In the list of data types, right-click the filter whose display properties you want to copy, and
from the menu that appears click Copy Properties.
2. Right-click the filter whose properties you want to overwrite, and from the menu that
appears click Paste Properties.
Example Filters
The examples in this section represent some of the typical filters that you may want to create.
Example of Filtering Sites under a Specific MSC/BSC
You may want to filter sites and so on based on their parent BSCs. For example, you may want to
filter all cell sites that have BSC1 as their parent.
To do this:
1. Begin creating your filter in the usual way.
2. In the Available Attributes pane, expand the BSC category.
3. Select Hierarchy and then click the right arrow button
.
4. In the Available Attributes pane, select Cell Site and then click the right arrow button
.
286
Using Filters and Fields
5. Ensure that the logical operator is set to AND , since you want to filter on everything that is
a cell site and has a parent BSC. This picture shows an example:
6. Click Next.
7. Ensure that the rule definition for BSC Hierarchy is Is Under, and the rule definition for
Cell Site is Is Equal To.
8. Click the Values button for BSC Hierarchy and select the parent BSC(s) you want to filter
on. Click OK when you are satisfied.
9. Complete the pages of the Filter Wizard, and then click Finish.
Example of Filtering on a Field
You may want to filter a particular network element based on its field assignment. For example, if
your administrator has set up a group named 'Region', with East, West, North, South picklist
options, you may want to filter all Properties whose Region field assignment is 'South'.
To do this:
1. Begin creating your filter in the usual way.
2. In the Available Attributes pane, expand the Property category.
3. Expand the Fields category, select the Region group and then click the right arrow button.
In this simple example, the logical operator can be either AND or OR.
4. Click Next.
5. Ensure that the rule definition is 'Equals'.
6. Click the Values button and select the field value of 'South'. Click OK.
7. Complete the pages of the Filter Wizard, and then click Finish.
Warning: If your administrator deletes a field from the Field Definer in ASSET Administrator, any
filters that include rules based on that field will be automatically modified, by having the
corresponding rule(s) removed from the filter.
287
ASSET User Reference Guide
Example of Filtering on a Field from a Parent Property
You may want to filter a particular network element on a field assigned to the parent element. For
example, you may want to filter all MSCs whose parent Property's Region field assignment is 'North'.
To do this:
1. Begin creating your filter in the usual way.
2. In the Available Attributes pane, expand the Property category.
3. Expand the Fields category, select the Region group and then click the right arrow button.
4. In the Available Attributes pane, select MSC and then click the right arrow button.
5. Ensure the logical operator is set to AND, since you want the filter to match both of the criteria.
6. Click Next.
7. Ensure that the rule definition for the Property Region Field is 'Equals' and that the rule
definition for the MSC is 'Is Equal To'.
8. Click the Values button for the Property Region Field and select the field value of 'North'.
Click OK.
9. Complete the pages of the Filter Wizard, and then click Finish.
Example of Filtering on a Polygon
You may want to filter Properties, sites and so on based on a polygon that you have created. You
can select sites to be included in a filter based on geographic regions defined by the vector data.
In this example, if you wanted to filter all cell sites in a North Region polygon, you would do the
following:
1. Begin creating your filter in the usual way.
2. In the Available Attributes pane, expand the Property category.
3. Expand the Polygons category, select the North Region polygon and then click the right
arrow button.
4. In the Available Attributes pane, select Cell Site and then click the right arrow button to
move it.
5. Ensure the logical operator is set to AND, because you want to filter on everything that is a
cell site and in the North Region polygon. This picture shows this example:
6. Click Next.
7. Ensure that the rule definition for Cell Site is Is Equal To, and the rule definition for North
Region polygon is Within.
8. Complete the pages of the Filter Wizard, and then click Finish.
A filter for that polygon is created.
Note: If you edit the polygon at a later date, the filter is updated automatically.
288
Using Filters and Fields
Example of Filtering on Web Feature Services
You may want to filter properties, sites and so on based on associated Web Feature Services. This
example assumes that the WFS attribute NAM, belonging to the WFS feature Airport, has been
mapped to the ASSET Property network element (object) as shown in the ASSET Installation and
Administration Guide.
To set up a filter that will find a Property for which the wfs:Airport/NAM attribute is equal to
JERSEY:
1. Begin creating your filter in the usual way.
2. In the Available Attributes pane, expand the Property category:
3. Ensure that the logical operator is set to AND, because you want to filter on everything that
is a property and has the specified WFS attribute.
4. Expand the WFS Services category and the required WFS feature:
5. Select the WFS attribute - wfs:Airport/NAM then click the right arrow button.
Important: While it is the NAM attribute that has been associated with the Property
network element in Administrator, you will see that all the attributes of the WFS Airport
feature are listed. If you select an attribute other than NAM to include in your filter, the filter
first identifies those elements which match the NAM attribute and then those that match
the selected attribute.
6. Click Next.
7. In the Selected Attributes pane at Step 3 of the Filter Wizard, click Property:
wfs:Airport/NAM is Equal To "". The parameter entry fields in the right pane become
available.
289
ASSET User Reference Guide
8. In the Operator drop-down field, select the required Operator. Since this is a text attribute,
the available Operators are Equal To, Like, and Null. Select Equal to and type JERSEY in
the text box:
You can click Preview to see what network elements will be identified by your filter:
Notes:
o
To filter for elements with attributes that do not match the specified Operator, select the
Not option.
o
If you select the Like Operator, you can define and include a Wildcard character, a
Single unknown character or an Escape character in your search text string.
For example:
If You Use the Default
The Filter Returns
Wildcard character * and type JER*
All element names beginning with JER.
Single character ? and type JERSE?
All six character element names beginning with JERSE.
Escape character ! and type XY!*
Any element with a name of XY*.
o
290
When filtering for elements having attributes with a numerical value, the available
Operators are Equal To, Less Than, Greater Than, Less Than or Equal To, Greater
Than or Equal To, Null, and Between. A default value of 0.000000 can be changed
by clicking on the attribute at Step 3 of the Filter Wizard. This picture shows an
example in which the Between Operator has been chosen for the Airport/ID attribute
and the values have not yet been typed in:
Using Filters and Fields
o
Using the Native XML Query Operator, you can create your own customised query
based on any filtering criteria that the server supports. You can use criteria such as
line or shape geometry that ASSET does not support. To do this, type an XML string
into the text box:
Example 1:
<ogc:Filter xmlns:ogc="http://www.opengis.net/ogc">
<ogc:PropertyIsEqualTo>
<ogc:PropertyName>ZV3</ogc:PropertyName>
<ogc:Literal>59</ogc:Literal>
</ogc:PropertyIsEqualTo>
</ogc:Filter>
Example 2:
<ogc:Filter xmlns:ogc="http://www.opengis.net/ogc"
xmlns:gml="http://www.opengis.net/gml">
<ogc:BBOX>
<ogc:PropertyName>GEOM</ogc:PropertyName>
<gml:Box
srsName="http://www.opengis.net/gml/srs/epsg.xml#4326">
<gml:coordinates>-2.16666698,52.29777908 3.16666698,53.29777908</gml:coordinates>
</gml:Box>
</ogc:BBOX>
</ogc:Filter>
Any text string that you add must comply with the standard set out in the OpenGIS
Filter Encoding Implementation Specification version 1.0.0. This document can be
downloaded from http://www.opengeospatial.org/standards/filter.
9. Complete the pages of the Filter Wizard, and then click Finish.
A filter based on the selected Web Feature Service attribute is created and can be used to find
matching elements in the Map View window. This picture shows an example:
291
ASSET User Reference Guide
Example of Filtering on Different Attributes in More Than One Vector
You may want to filter on more than one vector, but based on different attributes. For example, you
may have two vectors and you want to filter on Cell Sites from Vector 1, and MSCs from Vector 2.
To do this:
1. Begin creating your filter in the usual way.
2. In the Available Attributes pane, expand the Property category, then the Polygons
category, under User Vectors, select Vector1 and then click the right arrow button.
3. Repeat this to include Vector2.
4. In the Selected Attributes pane, select Vector1.
5. In the Available Attributes pane, select Cell Site and then click the right arrow button.
A new logical rule tree is created, containing Vector1 and Cell Site:
6. In the Selected Attributes pane, select Vector2.
7. In the Available Attributes pane, select MSC and then click the right arrow button.
A new logical rule tree is created, containing Vector 2 and MSC.
8. Ensure that the logical operator for the whole filter is set to OR, but the logical operators for
each logical rule tree are set to AND.
This picture shows this example:
9. Click Next.
10. Ensure that the rule definitions for the two vectors are set to Within, and the rule definitions
for Cell Sites and MSCs are set to Is Equal To.
11. Complete the pages of the Filter Wizard, and then click Finish.
292
Using Filters and Fields
Filtering Objects by their Technology and Activity Settings
Within your filters, you may want to use the criteria that consider the Fixed and Variable technology
settings on an MU-Node, and the Active and Not Active settings on a cell. There are various
options, depending on the filter attributes.
Note: For information on the Fixed and Variable technology settings on an MU-Node, and the
Active and Not Active settings on a cell, see 'About MU-Nodes' and 'About Cells' in the ASSET
Radio User Reference Guide.
Here are some examples of the attributes and their purpose:
Object
Attribute
Selectable Values
Description
MU-Node
'Subtype Mode Active'

True

False
Relates to the Fixed Technology
checkbox on the General tab of the
MU-Node. 'True' will filter the MUNodes which have the checkbox
selected, 'False' will filter the MUNodes which have the checkbox not
selected.

One or more of the
listed technologies

Multiple Technology

Undefined

One or more of the
listed technologies

Multiple Technology

Undefined
Cell
Cell
Cell
'Supported Technologies'
'Active Technology Mode'
'Owner'
(These options are in
addition to the basic
(this is just an example of one 'Operator' criteria such
particular attribute to
as 'Equals' and 'Value')
demonstrate how the
additional criteria can be
 Technology
used)
 Active

Not Active

Supported
Relates to filtering cells which have
one or more of the chosen
technologies supported on the cell.
You can choose one or more of the
technologies (OR basis). Or choose
'Multiple Technology' if you want to
filter any technology. Or choose
'Undefined' if you want to filter cells
which have no technology supported.
Relates to filtering cells which have
one or more of the chosen
technologies active on the cell.
You can choose one or more of the
technologies (OR basis). Or choose
'Multiple Technology' if you want to
filter any technology. Or choose
'Undefined' if you want to filter cells
which are not active.
Relates to filtering cells for which you
not only want to satisfy the basic
criteria of the attribute, but also meet
this additional optional criteria.
You can choose one or more of the
technologies (or All), and you can
further specify that the chosen
technology(s) is in Active mode, or
Not Active mode, or Supported
(which means that as a minimum, it
only has to be supported on the cell).
293
ASSET User Reference Guide
Object
Attribute
Selectable Values
Description
Cell
'Antenna Type'
(These options are in
addition to the basic
'Operator' criteria such
as 'Equals' and 'Value')
Relates to filtering cells for which you
not only want to satisfy the basic
criteria of the attribute, but also meet
this additional optional criteria.

Technology

Active

Not Active

Supported

Not Applicable
You can choose one or more of the
technologies (or All), and you can
further specify that the chosen
technology(s) is in Active mode, or
Not Active mode, or Supported
(which means that as a minimum, it
only has to be supported on the cell).
(this is just an example of an
antenna-related attribute to
demonstrate how the
additional criteria can be
used)
There is also a Not Applicable option,
which means that you do not want the
filter to take the Active/Not
Active/Supported state into
consideration (this extra option is for
antenna-related attributes only).
About the Selection Expert and Selection Filter
The Selection Expert is a powerful and flexible feature. The main feature within it is the Selection
Filter. Here is an example:
Example of Selection Expert
The following explanations may help to define the terms used:
The Selection Expert:
 Is a powerful way of creating a filter. Using it, you can select any subset of items by
choosing them individually in the Site Database or Map View, or by creating in the Map
View a polygonal, circular or rectangular area that contains the sites you want. Then you
can perform operations, such as globally editing and then re-predicting the coverage, for
only the sites in this Selection filter.
 Acts as a handy clipboard - to easily allow you to cut and paste network elements between
different parents, cells between sites and so on.
 Acts as a viewing window for all filters - you can quickly review all filters, (static, dynamic
and Selection) and edit the static and Selection filters.
 Reparenting network elements (for example, reparenting multiple nodes to a different RNC,
or multiple sites to a new BSC). For more information, see Reparenting Network Elements
on page 249.
294
Using Filters and Fields
The Selection Filter:
 Is the main feature within the Selection Expert.
 Is an extremely useful method of selecting groups of objects in a quick and easy way.
 Is a static filter that exists only in memory. It is not stored in the database and therefore
cannot be Applied or Committed.
 Can be renamed and saved as a normal static filter.
 Can be used as the basis for creating a static filter in the Filter Wizard.
 Can be used to store, check and review the created/modified objects from an XML Import
or Grid Data Loader Import. See Saving the Contents of an Import into the Selection Filter
on page 305.
Tip: There is a shortcut button
in the ASSET toolbar, which opens the Selection Expert.
Adding to the Selection Filter Using the Map View Window
To add items to the Selection Filter using the Map View window:
1. Ensure the Map View window shows the area and elements from which you will be
selecting.
2. If required, choose to limit the element types that are added. See Choosing Which Types of
Network Elements are Added to the Selection Filter on page 296.
3. On the main toolbar, click the 'Selection Expert' button
.
4. In the Map View window, click the down arrow on the Selection Filter toolbox
the options:
To
Do This
Select individual network
elements
Click the Single Select
to see
button.
Hold down Shift and click each network element that you want to include in the
Selection filter.
Warning: If you click an element that already exists in the Selection filter, it will
be removed from the filter. That is, holding down Shift while clicking will toggle
an item in and out of the Selection filter.
Tip: You can also replace the contents of the Selection filter with your new
selection by clicking without holding down Shift.
Select network elements
in a rectangular area that
you will draw
Click the Rectangular Select
button and hold down Shift.
Click where you want a corner to be and then drag to create a rectangle. The
elements within the rectangle are added to the Selection filter.
As you do this, the width and height dimensions are displayed, along with the
units that you chose in the Preferences dialog box.
Tip: You can also replace the contents of the Selection filter with your new
selection by clicking and dragging without holding down Shift.
295
ASSET User Reference Guide
To
Do This
Select network elements
button and hold down Shift.
in a circular area that you Click the Circle Select
will draw
Click and hold down the mouse button where the centre of the circle will be,
and drag outwards to set the radius of the circle. The currently selected
elements inside the circle are added to the Selection filter.
Tip: You can also replace the contents of the Selection filter with your new
selection by clicking and dragging without holding down Shift.
Select network elements
in a polygon that you will
draw
Click the Polygon Select
button and hold down Shift.
Click where the first point of the polygon will be, then click to create more
points as required. To close the polygon, double-click anywhere in the Map
View window.
The currently selected elements inside the polygon are added to the Selection
filter.
Tip: You can also replace the contents of the Selection filter with your new
selection by clicking and dragging without holding down Shift.
Clear Selection filter
Click the Clear Selection filter
Selection filter.
button to empty all objects from the
Important: Hold down Shift when using any of the above buttons to add a current
selection to the filter. If you do not hold down Shift, the filter contains ONLY the current
selection, replacing what was there.
The selected elements appear in the Selection Expert and you can edit the items shown, and save
or export the filter.
Choosing Which Types of Network Elements are Added to the Selection Filter
When creating the Selection Filter, by default, all network element types are added. However, you
can choose to limit what network element types are added.
Tip: This limit applies when you are adding items to the Selection Filter using the Map View
window. When clicking items on the Site Database Hierarchy tab, you can add all types of items
here regardless of what is selected in the Selection Expert Options dialog box.
To select which items you want to add to the Selection Filter when using the Map View:
1. In the Map View window, from the Tools menu, click Options.
In the dialog box that appears, the Selection tab lists all of the network element types that
can be added to the Selection Filter.
2. Clear the checkboxes next to element types that you want to exclude from future Selection
filters.
Tip: Hold down Shift to select multiple types, then click one of the checkboxes to clear all
those selected.
3. When you have made your selections, close the dialog box.
296
Using Filters and Fields
Adding Items to the Selection Filter Using the Site or Link Database
You can add items to a Selection filter using the Site or Link Database in various ways.
Adding Items to the Selection Filter by Right-clicking
In the Site or Link Database, right-click the network element that you want to add to the Selection
filter and from the menu that appears, click Add to Selection Filter.
Tip: In the Cellular Antennas dialog box, you can add antennas to the Selection filter in a similar
way.
Adding Items to the Selection Filter using the Filters tab
To add to the Selection filter using the Filters tab of the Site or Link database:
1. In the Site or Link database, select the required object that you want to add to the
Selection filter.
2. On the Filters tab, click Display to reveal the current filters that the object belongs to.
3. Click Change (if in Site database) or Add (if in Link database) to reveal the list of available
filters.
4. Select the Selection checkbox, and click OK.
5. Click Update.
The Selection filter will then be automatically updated.
You can use the Remove button in a similar way.
Adding Items to the Selection Filter on the Hierarchy tab
You can use the Hierarchy tab of the Site Database to add to a Selection filter. For example, you
might want to create a filter containing the multiple items that are parented to the same Property.
Note: This method is applicable to the Site Database only.
To add to the Selection Filter using the Hierarchy tab:
1. In the Site Database, select the parent of the item that you want to add to the Selection
filter.
2. On the Hierarchy tab for that element, click the Display button (or the Refresh button if
you have previously clicked it). For example:
297
ASSET User Reference Guide
The items parented on this element now appear on the tab, as shown here:
3. Select one or more of the network elements shown on the tab and click the Add button to
add them to the Selection filter.
Tip: Similarly, to remove an item from the Selection filter, select the item on the tab and
click the Remove button.
Adding Items to the Selection Filter Using an Existing Polygon Vector
To add items to the Selection filter using a polygon vector that has already been imported or
created in the Vector Manager:
1. On the main toolbar, click the 'Selection Expert' button
.
2. On the Location tab:
o
Select 'All Types' to add all appropriate types to the Selection filter
- or -
o
Choose a specific element type, for example Property.
3. In the Select Polygon Vector(s) pane, click the Select Polygon Vectors button.
298
Using Filters and Fields
4. In the Select Polygon Vector(s) dialog box that appears, select the polygon vectors that
contain the items that you want to add to the selection filter:
Tip: If you have classified your vectors, you can use the Filter By Vector Class pane to
restrict which classifications are available for selection. Any polygons contained within
them (which may not just be the Polygon classification) will be listed for selection. For more
information, see Classifying User Vector Files on page 256.
5. Click OK.
The Selection Expert displays the number of vectors that have been selected:
6. Click the Add All Elements button.
299
ASSET User Reference Guide
All of the items of the selected element type that are contained within (or overlap) the
selected polygon vectors are added to the selection filter:
- or To remove the elements that are contained within (or overlap) the selected polygon
vectors, from the selection filter, click the Remove All Elements button.
Using the Selection Expert to Count the Sites in an Area
To count the sites in an area:
1. On the main toolbar, click the 'Selection Expert' button
.
2. Select the sites you wish to count using any of the methods already described in this
section.
You can view the number of sites:
 In the Object Count box of the Selection Expert
 At the bottom of the Site Database
Selection filter selected.
.
when you have the
Tip: You can configure which network element types appear in the object count in the Site
Database. See Customising the Object Count in the Site Database on page 49.
300
Using Filters and Fields
Deleting Network Elements using the Selection Expert
Warning: You should use this option with extreme caution. This deletion option will move the
chosen items into the Wastebasket.
To use the Selection Expert to delete items contained in the Selection Filter from the Site
Database:
1. On the main toolbar, click the 'Selection Expert' button
.
2. Perform the filtering operations to compose the contents of the Selection Expert (as
described in the preceding sections).
3. In the Selection Expert, select the items that you want to delete. You can use the Shift and
Control keys to select multiple elements.
4. Right-click the selected items, and from the menu that appears, click Delete From
Database.
5. Confirm you wish to go ahead with the deletion(s).
The selected network elements are deleted from the Site Database (moved into the
Wastebasket).
Editing the Selection Filter
This section describes the ways in which you can edit the contents of the Selection filter.
To open the Selection Expert, on the main toolbar, click the 'Selection Expert' button
.
Removing Items from the Selection Filter
To remove items from the Selection Filter:
1. In the Selection Expert, select the items that you want to remove from the Selection
Filter. You can use the Shift and Control keys to select multiple elements.
2. Right-click the selected items, and from the menu that appears, click Remove From Filter.
The selected network elements are removed from the Selection filter.
Editing the Selection Filter using an Identifier
To add or remove specific network elements in the Selection filter based on an identifier:
1. In the Selection Expert, on the Identifier tab, select the element type that you want to add
or remove, for example BSC, and enter either an exact element ID, or a regular
expression.
2. In the Match pane, ensure you have selected the correct type - either Exact or Regular
Expression - for what you have entered above. You can also choose whether or not to
make this case-sensitive by selecting the checkbox.
3. Click the Add or Remove button as required.
301
ASSET User Reference Guide
Editing the Selection Filter using a File
To edit items currently in the Selection filter by using the contents of a file:
1. In the Selection Expert, on the File List tab, select the required element type, for example
BSC.
2. Type in a file name or click the Browse button and locate the correct file.
Notes:
o
The file format of this text file is a list of site identifiers each on a separate line
o
File imports for patterns need DeviceID\PatternID to recognise patterns, as PatternID
on its own is not unique
3. Click Add.
All of the elements of the required type that exist in the file are displayed in the Selection
Filter. You can then remove any individual items, if required.
Editing the Selection Filter using the Map View
To add or remove items in the Selection filter using the Map View window:
1. In the Selection Expert, on the Location tab, select the element type, for example Property.
2. In the Select Map View pane, click the appropriate button, for example, Add Element.
3. In the Map View window, click the required network element.
4. Repeat for all of the elements that you want to add to or remove from the Selection filter.
5. In the Selection Expert, click the Stop Adding or Stop Removing button.
Tip: You can use the Add Element or Remove Element buttons with multiple Map Views if
required. The element selection is controlled automatically, depending where you click.
To add or remove all of the elements of the selected element type:
1. In the Selection Expert, on the Location tab, select the element type, for example
Property.
2. Click the required Map View (it is important to do this first when using the Add or Remove
All buttons)
3. In the Select Map View pane, click the appropriate button, for example, Add All Elements.
Editing the Selection Filter using Other Filters
To add items from other filters to your Selection filter:
1. In the Selection Expert, select the required element type.
2. From the list of folders shown, select the filter that contains the required network elements.
3. Click Add.
All of the elements of the required type that exist in the file are displayed in the Selection Filter.
4. Remove any unwanted items as required, by selecting the item and clicking Remove.
302
Using Filters and Fields
Editing the Selection Filter using the Element Hierarchy
You can edit which items currently exist in the Selection filter based on their position within the
element hierarchy. For a selected item that already exists in the Selection filter, you can add and
remove the following items to the Selection filter (if applicable):
 Parent elements
 Child elements
 Any neighbours that it may have
 Any connections (logical and/or cellular) that it may have
Note: To use this method, the items that you want to add must already exist in the Site Database;
the Selection Expert cannot create them.
To use the element hierarchy to add to the Selection filter:
1. Ensure you have added at least one item to the Selection filter.
2. In the left hand pane, select the item whose related elements you want to add/remove.
Tip: You can select more than one network element.
3. In the Filter modification options pane of the Selection Expert, click the Hierarchy tab.
4. In the Element Type pane, select the type of element that you want to add/remove. You
can choose 'All Types' if you want to add all appropriate element types to the Selection
filter.
5. Click the appropriate button, depending on what you want to do:
o
If you want to add the logical/physical parent(s) of the selected element type for the
selected filter item(s), click the Add Parent(s) button.
In this example, the parent Property of SITE11 will be added to the Selection filter:
- or To remove the logical/physical parent(s) of the selected element type for the selected
filter item(s), click the Remove Parent(s) button.
o
If you want to add the logical/physical child (or children) of the selected element type
for the selected filter item(s), click the Add Child(ren) button.
303
ASSET User Reference Guide
In this example, the child GSM cells of SITE11 will be added to the Selection filter:
- or To remove the children of the selected element type for the selected filter item(s), click
the Remove Child(ren) button.
o
If you want to add the neighbour(s) of the selected item(s) (inward, outward and
mutual), click the Add Neighbour(s) button.
The type of neighbour added to the Selection filter will depend on the technology of the
selected element type; selecting All Types will add neighbours from all available
technologies.
In this example, the GSM neighbours of SITE11A will be added to the Selection filter:
- or To remove the neighbour(s) of the selected item(s), click the Remove Neighbour(s)
button.
304
Using Filters and Fields
Notes:
o
You can only add items that are one hierarchy level above or below the selected item.
For example, if you choose to add the child elements for an RNC, the UMTS NodeBs
will be added but not their associated cells or repeaters.
o
When removing items, selected items in the left-hand pane can still be removed if they
are a parent, child or neighbour of a related item.
For example, if you select a parent RNC and a Node B in the left-hand pane, and you
choose to remove UMTS Cell children, only the cells are removed. But if you choose to
remove children of all types, then the selected Node B will be removed as well.
Locating Selection Filter Items in Other Windows
You can choose an item in the Selection Filter and quickly find it in one of the following windows:
 Site Database
 Map View
 Link Database
 Logical/Cellular Connection Database
To do this:
1. Ensure you have the appropriate window open with a view (for example, filter) that includes
the item you have selected.
2. In the Selection Expert, in the list of items, click the identity of the item you want to locate.
3. From the Tools menu, point to Locate and click the window you want to use.
The window you have chosen becomes the current window with the item indicated.
Saving the Contents of an Import into the Selection Filter
ASSET enables you to import created or modified objects into the database in various ways.
Sometimes, after performing an import, or a series of imports, it can be difficult to identify the
created or modified items in the Site Database (unless you had done a Commit All just before the
import, so that you can see the asterisked items).
However, ASSET provides a useful way of identifying, checking and reviewing created or modified
objects from recent imports. You can achieve this by using an option to automatically save these
created/modified objects into the Selection Filter.
To see these options:
In your Preferences, under the File menu, on the Filters tab, you can choose from three
options:
o
No changes will be made to Selection Filter contents after an import
o
Selection Filter contents will be aggregated with objects affected by an import
o
Selection Filter contents will be replaced by objects affected by an import
This automatic saving option is applicable to imports from the XML Import and the Grid Data
Loader Import.
(For information on these, see Importing XML Data on page 411 and About the Grid Data Loader
on page 457, respectively.)
305
ASSET User Reference Guide
Notes and Tips:
 If you want to accumulate the created/modified objects from a series of imports, the
Aggregate option may be useful.
 The Selection Filter is a filter that exists only in memory, so each user's Selection Filter is
individual to each user.
 You can use any of the functions in ASSET that use filters. For example, using the contents
of the Selection Filter, you can generate a site report, or you can display the contents in the
Site Database.
 At any time, you can easily clear the Selection Filter.
 At any time, you can easily rename and save the contents of the Selection Filter into a
normal static filter.
Saving the Selection Filter
To save network elements that currently exist in the Selection Filter:
1. From the Database menu, click Selection Expert.
2. From the File menu of the Selection Expert, click Save As.
3. In the Filter Name box, type a name and click Save.
4. Now, if you view the Filter Database, (from the Database menu, click Filters) your filter
has been added, and has a red symbol next to it, indicating that it is a static filter.
You can now modify the filter from the Filter Database as usual, and then use it, as you would
any filter, to limit lists of network elements in the Site Database window, reports and so on.
Making Your Dynamic Filters More Efficient
When creating dynamic filters, the selection rules will be activated from top to bottom.
The sequence of these rules can therefore affect the speed of your filters.
You can make your dynamic filters run faster by:
 Eliminating the largest number of unwanted objects first.
 Using as few rules as possible - the number of evaluations affects the speed at which a
filter runs.
 Placing the rules in a sensible order in step 2 of the Filter Wizard - some types of rule are
faster than others. For example, to test if an object is a particular element, the filter wizard
compares two integers to see if they are equal or not. However, to test to see if a Property
is within a vector, the filter wizard uses a complex algorithm to compare the location of the
Property with every point that makes up the vector.
This table lists the rules from quickest to process to the slowest:
Fastest
Slowest
306
Weighting
Rule Type
1
Element
5
Hierarchy
8
Field
5-15
Attribute
50-10000+ depending on the number of points in the polygon
Polygon
Using Filters and Fields
The examples below show how performance is affected by good and bad use of rules.
 Example of reordering a simple filter
 Example of making filters faster by using fewer rules
Example of Making Filters Faster by Reordering a Filter
Imagine there is a GSM network where the sites and cells are evenly distributed under each
MSC/BSC. The network consists of:
 400 Properties
 2 MSC
 8 BSCs
 400 sites
 1000 cells
If you wanted a filter that included all the sites under ‘MSC1’, you would need two rules:
 An element type rule saying you only wanted sites
 A hierarchy rule saying anything under MSC1
The following diagrams show the difference in processing if you run these rules in different orders:
Example 1: With the ‘Element Type’ rule first:
Processing example - Element Type rule first
307
ASSET User Reference Guide
Example 2: With the ‘Hierarchy Type’ rule first:
Processing example - Hierarchy Type rule first
Even in this simple example, the filter must process 23% more objects.
It is even more important to optimise filters if they are complex as the difference in speed will be
dramatic.
Example of Making Filters Faster by Using Fewer Rules
This example shows how performance is improved by restructuring filter definitions to use fewer
rules and by making the faster rules run first. The two filters below provide identical outputs but the
performance of the second filter will far exceed the first.
In the first filter, every object is compared first with the Node field and then the Node element type.
Items that do not fulfil these criteria are then compared with the cell field and then the cell element
type:
First Filter Showing Time Consuming Process
308
Using Filters and Fields
The second filter, however, compares every object with the Node element type followed, if needed,
with a comparison against the cell element type. Only if an object is of the correct element type
does it do a field comparison and it only does it once, unlike the first filter which had all cells doing
two field comparisons:
First Filter Showing Faster Process
Displaying Filters
To show selected sites that have been defined in a filter:
In the Filter box, click the required filter.
To show a specific network element:
1. Ensure the selected filter includes the required element. If in doubt, use the All filter.
2. Type the element name in the Find box.
When you have both a Map View window and the Site Database window open, you can also
select an element on the map and the Site Database window scrolls to select that element
automatically. For this to work, the filter that is selected must include the selected element.
Tip: For information on what you can do with the display settings of filters, see Copying the Display
Properties of Filters and Using Visualisers.
309
ASSET User Reference Guide
Exporting Filters using XML Export
If you want to take a copy of your filters (for example for backup) you can use the XML Export
functionality. See Exporting Filters on page 431.
310
Managing Antennas and Equipment
11 Managing Antennas and Equipment
This chapter explains how to create and manage the main equipment types, including antennas.
Note: There is some important information on the antenna-related definitions used. See 'Overview
of Antenna Concepts in ASSET Radio' in the ASSET Radio User Reference Guide.
Managing Antennas and Equipment using Folders
You can manage antennas and other equipment in two main types of folder:
 All projects - the equipment will be available in all projects within the current database
 The current project - the equipment will only be available in the project that is currently
open
Here is an example relating to antennas:
Example of using folders to store antennas
If required, you can add subfolders to any of these two main folders, to organise your equipment in
a more structured way. To do this:
1. Select the appropriate main folder for which you want to add subfolders (either 'All Projects'
or the specific project).
2. Right-click, and from the menu that appears, click New folder.
A new folder is added to the list, which you should name as appropriate.
Tip: If required, you can also add subfolders to subfolders.
To move subfolders and equipment within folders:
1. Select the equipment/subfolder that you want to move.
2. Right-click, and from the menu that appears, click Cut.
3. Select the folder/subfolder into which you want to move the equipment/subfolder.
4. Right-click, and from the menu that appears, click Paste.
311
ASSET User Reference Guide
To rename equipment or subfolders:
1. Select the required equipment or subfolder.
2. Right-click, and from the menu that appears, click Rename.
3. Type the new name as required, and then press Enter.
To delete equipment or subfolders:
1. Select the required equipment or subfolder.
2. Right-click, and from the menu that appears, click Delete.
The selected equipment or subfolder is removed.
Note:
 You cannot move, rename or delete the All Projects or current project folders, and you
cannot delete folders that contain items that are assigned in the Site Database. However,
you can delete a folder containing items that are unassigned; in such cases, the items (but
not the folder) can be restored from the wastebasket.
Storing Antennas in the Database
Antennas are stored in the database. These types of antennas are supported:
 Cellular antennas are used in ASSET Radio, TEOCO's radio planning product. They are
designed by manufacturers with fixed gain, directivity and radiation pattern. When installed
on a network they only have one pattern, which carries all of the uplink and downlink traffic.
See Using the Cellular Antennas Dialog Box on page 313.
Note: There is some important information on the antenna-related definitions used. See
'Overview of Antenna Concepts in ASSET Radio' in the ASSET Radio User Reference
Guide.
 Microwave antennas are used in ASSET Backhaul, TEOCO's microwave link planning
product.
See About the Microwave Antennas Dialog Box on page 74.
312
Managing Antennas and Equipment
Using the Cellular Antennas Dialog Box
This picture shows an example of the Cellular Antennas dialog box:
Cellular Antennas Dialog Box
This displays all the antenna devices and patterns that have been added or imported for your
project(s).
The antennas are presented at two levels: Device (parent level) and Pattern (child level).
For more information, see About the Tabs on the Cellular Antennas Dialog Box on page 314.
As antennas are important elements of a network, many parameters can be stored for each
antenna in the database including:
 Antenna Gain
 Frequency Band
 Manufacturer name
 Physical dimensions (such as weight)
 Horizontal and vertical radiation patterns (masks)
For the following parameters, you can either enter your own values, or click the Calculate buttons
to derive the values from the antenna pattern:
 Electrical Downtilt
 Azimuth Offset (see About the Azimuth Offset).
 Horizontal Beamwidth
 Vertical Beamwidth
313
ASSET User Reference Guide
Important:
For all propagation models except MYRIAD and Volcano:
o
The Electrical Downtilt and Azimuth Offset values influence the predictions.
For MYRIAD and Volcano models:
o
The Electrical Downtilt and Azimuth Offset values do not influence the predictions.
Instead, these models read these values directly from the antenna mask file.
For all propagation models:
o
The Horizontal and Vertical Beamwidth values do not influence the predictions.
For more information, see 'Antenna Tilt and Masking Calculations' in the ASSET Technical
Reference Guide.
Normally you would not create antennas, but import them using an antenna definition file supplied
by a manufacturer. However, depending on your permissions, if you do want to create or edit an
antenna, you can do so.
In ASSET, cellular antennas consist of an 'antenna device' and one or more 'patterns' belonging to
that device. Here is an example:
Tips:
 You can create folders and sub-folders in which to store your antennas. See Managing
Antennas and Equipment using Folders on page 311.
 You can perform an XML Import or XML Export of all the objects in the Cellular Antennas
dialog box by using the Import or Export buttons.
 You can perform folder-specific or antenna-specific XML Exports from the Cellular
Antennas dialog box. See About the Context Menu on the Tree Tab on page 330.
 You can easily organise your antenna devices and patterns by grouping together variants
of a device. For example, if you have a variable electrical tilt antenna type, you can store
each of its antenna patterns under a common device. You can use the same principle for
multi-mode antennas, for example GSM900 / GSM1800 / UMTS antennas. See Maintaining
Your Antenna Lists Efficiently on page 336.
 You can perform searches for antennas, using one of two methods:
314
o
Basic searches using the Tree tab (see Using the Basic Search for Cellular Antennas
on page 326).
o
Rule-base searches using the Advanced Search tab (see Using the Advanced Search
for Antennas on page 331).
Managing Antennas and Equipment
About the Tabs on the Cellular Antennas Dialog Box
There are two tabs in the left pane of the Cellular Antennas dialog box:
 Tree
 Advanced Search
The antennas comprise two levels: antenna device (parent level) and antenna pattern (child level).
Note: The tabs in the right pane of the Cellular Antennas dialog box are mentioned at the end of
this topic.
The Tree tab displays all the antenna devices and patterns that have been added or imported for
your project(s). There are various display options for how you want these to be shown.
The Advanced Search tab enables you to perform detailed searches using customised rules. It also
provides a useful way of regrouping patterns to devices, and helps you to efficiently maintain your
antenna lists.
The following table describes the actions you can perform on each tab:
On This Tab
You Can
For More Information See
Tree
Add antenna devices.
Adding Antenna Devices on page 317
Add antenna patterns.
Adding Patterns to an Antenna Device
on page 323
Find antenna devices and patterns (basic
search).
Using the Basic Search for Cellular
Antennas on page 326
Edit and move antenna devices and patterns.
Editing or Moving Antenna Devices and
Patterns on page 328
Delete antenna devices and patterns.
Deleting Antenna Devices and Patterns
on page 327
View the pathloss at different angles for a
pattern.
Viewing Pathlosses for Patterns on page
329
Display two patterns simultaneously to compare Comparing Two Patterns on page 329
them.
Use the Context Menu to make changes.
Advanced
Search
About the Context Menu on the Tree Tab
on page 330
Perform detailed searches for antenna devices Performing the Advanced Search on
and patterns, by constructing search rules base page 333
on specific attributes.
Fine tune the results of the advanced search
results using extra inclusion/exclusion options.
Fine Tuning the Results of the Advanced
Search on page 335
Maintain your antenna lists efficiently by
grouping patterns under appropriate devices
and deleting empty devices.
Maintaining Your Antenna Lists
Efficiently on page 336
Use the Context Menu to make changes.
About the Context Menu on the
Advanced Search Tab on page 338
315
ASSET User Reference Guide
There are also sets of tabs in the right pane of the Cellular Antennas dialog box:
 When you click an antenna device, you can access the information on these tabs:
General, Hierarchy, Antenna Usage.
See Adding Antenna Devices on page 317.
 When you click an antenna pattern, you can access the information on these tabs:
General, Mask.
See Adding Patterns to an Antenna Device on page 323.
About the Filter Option in the Cellular Antennas Dialog Box
The Tree tab of the Cellular Antennas dialog box contains a Filter drop-down box that enables
you to view only the antennas that exist in your chosen filter. This is only appropriate if you use
filters that are based on antenna objects.
Filter drop-down box on Tree tab
Important: The Filter selection only operates when you are viewing the Tree tab. It has absolutely
no effect when you are viewing the Advanced Search tab.
About the Display Options in the Cellular Antennas Dialog Box
There are two sets of display options in the Cellular Antennas dialog box, available by clicking the
Options menu:
Note: These options are available on both the Tree tab and the Advanced Search tab. In the case
of the Tree tab, the selected filter will also influence which antennas are shown.
316
Managing Antennas and Equipment
Firstly, you can choose one of the display options described in this table:
Select This Option To Display
Show Pattern ID
The Pattern ID, for example:
Show Unique Pattern
ID
The Unique Pattern ID (device\pattern) in the list, for example:
Tip: This may be useful if you use the Unique ID override option for your
patterns.
Secondly, you can choose one of the display options described in this table:
Select This Option To Display
Show All Devices
All antenna devices, irrespective of their usage in the Site Database (all of
their patterns are displayed).
Show only Used
Devices
Only antenna devices that have one or more of their patterns in use in the
Site Database (all of their patterns are displayed).
Show only Unused
Devices
Only antenna devices that do not have any of their patterns in use in the
Site Database (all of their patterns are displayed).
Note: In the case of the ‘Show All/Used/Unused' options, the display affects all the projects in the
tree list.
Tip: If you make changes to the antenna assignments in the Site Database while using the Used or
Unused display option, you can use the Refresh button to refresh the list of antennas.
Adding Antenna Devices
In ASSET Radio, antenna patterns are parented to an antenna device. The following information
describes the parameters on the antenna device, and also describes how you could manually add a
device.
Note:
 There is a power tool for converting Planet Antenna files (*.txt / *.msi) into Antenna XML
files so that multiple antennas and patterns can be converted into ASSET XML format. It is
available from Add-ins under the File menu (see Using the Planet Antenna Utility on page
343), but can also be run independently of ASSET. If you require further details, please
contact your regional Product Support centre.
 There is also a Planet PAFX Antenna Import feature that supports the direct import of
*.pafx antenna files, where the Antenna Device and multiple Antenna Patterns that are
contained in the *.pafx file are imported directly into ASSET. No intermediate steps or
manual intervention are required. See Using the Planet PAFX Antenna Import on page 342.
317
ASSET User Reference Guide
You can add cellular antenna devices to the antenna inventory in a number of ways:
 If you have the required antenna information stored in a file that uses one of the supported
formats, you can import them. For more information, see Importing and Exporting on page 411.
Tip: You can also perform an XML Import/Export to/from the Cellular Antennas dialog box.
See About the Context Menu on the Tree Tab on page 330.
 If you have the antenna manufacturer's datasheets, or know the parameters (dimensions,
masks and so on), you can add them manually.
To add an antenna device manually:
1. From the Equipment menu, click Cellular Antennas.
2. In the dialog box that appears, right-click the project folder that will contain the antenna.
Note: You need the correct privileges to add antennas to all projects.
3. From the menu that appears, select New Antenna Device.
4. Select the new antenna and add the required information on the tabs:
On This Tab
You Can
General
In the Device ID box, type the user-defined name of the selected antenna device.
In the Manufacturer box, type the name of the manufacturer of your antenna.
In the Description box, type a description for your antenna device.
The Beam Patterns box shows the number of patterns on the device.
In the Antenna Type drop-down list, you can select one one of the following:

Passive

Beam-Switching
Coloured icons in the user interface help you to distinguish each type:
Switched Beam Antennas:
If the device's antenna type is set to Switched Beam, the behaviour is different from
non-Switched Beam antennas. For more information about Switched Beam
antennas, see 'About Switched Beam Antennas' in the ASSET Radio User
Reference Guide.
For more information about configuring antennas in the Site Database, see 'About
the Physical Antennas and Logical Antennas tabs' in the ASSET Radio User
Reference Guide. (This includes a section 'Configuring 5G Switched Beam
Antennas'.)
Important: The behaviour of the physical and logical antenna parameters in the Site
Database differs significantly according to the antenna type. You should only set the
Beam-Switching type for use with 5G cells or for digital splitting with other
technologies.
ASSET automatically updates the Created and Modified boxes when a new antenna
device is created or modified.
Costing: Select one of the manufacturers from the list of suppliers that you have
entered, and add a unit cost for the antenna.
Device details: Specify information about the device’s physical dimensions.
318
Managing Antennas and Equipment
On This Tab
You Can
Antenna Beam Sets (Switched Beam): This pane is only relevant If the device's
antenna type is set to Switched Beam. A beam set is a defined group of patterns
that will be used by an assigned antenna. For a description of how to use this tab,
see Creating Beam Sets on page 320.
Hierarchy
View a list of the antenna patterns that belong to the currently selected antenna
device. To view the details, click the Display button.
Antenna Usage
Run a report showing which objects are using the device or pattern. This might be
useful in various ways, for example when you want to perform cleanups.
You can choose to report on all objects or limit it to Properties, cells or repeaters.
Where antennas are used by all projects, you can select to limit the report to the
current project. When ready, click Run Report. Afterwards, you can double-click on
any column header to re-order the data, and/or use the Find functionality.
5. Click Apply (and Commit, as required) to save the changes to the antenna device.
About Switched Beam Antennas
Switched Beam antennas are only relevant for 5G, except when used for digital splitting with LTE.
Operationally, a switched beam antenna allows the signal to be steered in both the horizontal axis
and vertical axis to give directional coverage to a mobile. For example, a switched beam antenna
may have 136 patterns formed from a grid of beams which results in many horizontal and several
vertical tilts. This means the azimuth can be electronically changed in small steps, and likewise the
vertical tilt.
These effects can be considered in ASSET Radio, using the Pathloss Predictor, Signal Coverage
Analysis, or Simulator.
Important: To use beam switching, Switched Beam antennas must be present in the Cellular
Antennas dialog box (Equipment menu), with the device's antenna type set to ‘Beam Switching’,
and with defined Beam Sets. For full information on the Cellular Antennas dialog box, see the
'Managing Antennas and Equipment' chapter in the ASSET User Reference Guide.
Each Switched Beam device must (in addition to traffic patterns) have at least one control pattern. If
there are multiple frequencies, there must be one control pattern (in addition to traffic patterns) for
each frequency.
Switched Beam antennas typically comprise large numbers of patterns, therefore their configuration
in ASSET Radio is different from other antennas.
Notes:
 ASSET Radio provides a utility to create switched beam antennas that can partially model
full dimension (FD) beamforming for 5G, with beams in the horizontal and vertical
directions. This can increase the overall spectral efficiency of the cell and help to plan
coverage for users at different heights. Once created, they can then be assigned to
Properties and cells and used in the normal way for coverage analysis. See 'Using the
Switched Beam Antenna Utility' in the ASSET User Reference Guide.
 You can also use digital splitting on switched beam antennas. For more information, see
Digitally Splitting Antennas in the ASSET User Reference Guide.
319
ASSET User Reference Guide
Creating Beam Sets
If the antenna device type is Switched Beam, you must define at least one beam set for it. A beam
set is a defined group of patterns that will be used by an assigned antenna. The beam set
information should be in the antenna definition file supplied by the antenna manufacturer.
Important:
 Copy and Paste functionality can be used to help to set up the data rows in the grid. So you
may prefer to prepare the information in an external spreadsheet, and use it to populate the
beam set definitions.
Any data pasted into the grid will automatically create the required rows (there are also
'Add Row' and 'Remove Row' options which may be useful when making manual entries).
The instructions below describe how the column information needs to be defined.
 Validation rules must be met, otherwise the set will not be accepted when you click the OK
button. Appropriate error messages are provided in the user interface.
To add a beam set:
1. Refer to the initial steps in Adding Antenna Devices on page 317.
2. In the Cellular Antennas dialog box, select the appropriate antenna device, and click the
General tab.
The Antenna Beam Sets (Switched Beam) pane lists any sets that have already been
defined for the antenna device.
3. Click the Add Set button.
4. In the Add New Group dialog box, name the set, and click OK.
5. Ensure the appropriate set is selected, and click the Edit Set button.
The Beam Set Editor appears:
320
Managing Antennas and Equipment
This table provides descriptions for each column in the grid:
Column Name
Description
Pattern Beam Index
This is the number that corresponds to the Pattern Beam Index value
specified at the pattern level (Info tab). See Adding Patterns to an Antenna
Device on page 323.
There must only be one instance of each pattern beam index in this column.
SSB Index
If the row does not represent a control beam, the SSB Index must be set to
'-1'.
If the row represents a control beam, this index must be set to an
appropriate value, as explained here:
The total number of unique SSB Indexes within the beam set (Number of
SSB Beams) is specified on right side of the dialog box, and the validation
rules will expect this number to be matched by the corresponding entries in
the SSB Index column.
For example, if Number of SSB Beams is set to '3', then the validation rules
will expect one (or more) index of '0', one (or more) index of '1' and one (or
more) index of '2' in the SSB Index column, but no other index values.
A valid configuration can involve several control beams being grouped
under the same SSB index value. For that reason, the SSB Index value
does not have to be unique within the column.
Is Control Beam
'1' = True; '0' = False.
Is Traffic Beam
'1' = True; '0' = False.
Note: A beam can be set to '1' for both Control and Traffic, to represent the
fact that it supports both.
Control Beam Index
This can be any number from '0' upwards, and it must be unique within the
column.
If it is not a control beam, this must be set to '-1'.
Traffic Beam Index
This can be any number from '0' upwards, and it must be unique within the
column.
If it is not a traffic beam, this must be set to '-1'.
Tip: On the right side of the dialog box, there is an 'Auto Set Indexes'
button. This can be useful for setting the Control Beam Index and Traffic
Beam Index columns with incremental numbers.
Antenna Pattern Info
This shows the Frequency, Electrical Tilt and Azimuth Offset that
correspond to the pattern of that particular Pattern Beam Index. If the same
index is used for more than one frequency, then multiple details are
displayed.
6. On the right side of the dialog box, specify the Number of SSB Beams. This represents the
total number of unique SSB Indexes within the beam set, and the validation rules will
expect this number to be matched by the corresponding entries in the SSB Index column
on the left. For example, if Number of SSB Beams is set to '3', then the validation rules will
expect one (or more) index of '0', one (or more) index of '1' and one (or more) index of '2' in
the SSB Index column, but no other index values.
The following simplified examples show beam sets that would satisfy the validation rules.
This first example shows three different SSB Index values of '0', '1' and '2', which
successfully matches the Number of SSB indexes ('3'):
321
ASSET User Reference Guide
This second example shows two identical SSB Index values of '0'. This represents a
'grouped' control beam. The only SSB Index value in this set is '0' (albeit with more than
one instance), and so this successfully matches the Number of SSB indexes ('1'):
Note: There is also a way of creating a beam set based on frequency. See Creating a
Beam Set Based on Frequency on page 322.
7. When you have finished, click OK.
If the validation fails, you will see a message. Otherwise, the changes will be accepted.
8. In the Cellular Antennas dialog box, click Apply (and Commit, as required) to save the
changes to the antenna device.
Creating a Beam Set Based on Frequency
When creating a beam set for Switched Beam antennas, you may want to do so by adding all the
patterns that operate at a requested frequency.
Important:
 This method guarantees that you add all the patterns (from the device's original set of
patterns) that operate at the requested frequency, that is, the frequency that is specified on
the Info tab of the antenna pattern.
Each of those patterns will have a Pattern Beam Index, and that index may also support
other frequencies. For this reason, the resulting beam set can in fact be used on those
other frequencies. This is indicated in the 'Antenna Pattern Info' column in the Beam Set
Editor.
This is a useful way of checking that the details in the beam set are as expected. It also
has the advantage that where you have the same antenna patterns that can operate at
different frequencies, you only need one beam set, instead of several sets.
The frequency itself is assigned on the logical antenna on the Property in the Site
Database, so only one frequency will be used when on that antenna when predictions are
run.
When you use this method, you must subsequently manually amend the rows that
represent control beams, as this information will not be known by the Beam Set Editor. You
can, of course, manually amend the beam set in any other way, as required.
 If you consecutively press the 'Add Patterns at Frequency' button, it will overwrite anything
previously in the beam set.
To creating a beam set based on frequency:
1. Refer to the initial steps in Creating Beam Sets on page 320.
2. In the Beam Set Editor, on the right side, you will see this option:
322
Managing Antennas and Equipment
3. In the Frequency drop-down list, select the required frequency.
4. Click Add Patterns at Frequency.
This example shows part of a beam set where patterns that support 37000MHz were
added, but where they also support 40000MHz:
Note: All the SSB Index values show '-1', which means that you must subsequently
manually amend the rows that represent control beams, as this information will not be
known by the Beam Set Editor. The SSB Index for traffic beams should, of course, remain
as '-1'.
5. When you have finished, click OK.
If the validation fails, you will see a message. Otherwise, the changes will be accepted.
6. In the Cellular Antennas dialog box, click Apply (and Commit, as required) to save the
changes to the antenna device.
Adding Patterns to an Antenna Device
In ASSET Radio, antenna patterns are parented to an antenna device. The following information
describes the parameters on the antenna pattern, and also describes how you could manually add
a pattern.
Note: In ASSET Radio, from a 5G perspective, the terms 'pattern' and 'beam' can be considered to
be the same thing.
To add patterns to an antenna device:
1. In the Cellular Antennas dialog box, ensure you have added an antenna device to the
antennas database.
2. Right-click the antenna device for which you want to add a pattern and click New Pattern.
3. Add the required information on the tabs:
On This Tab
You Can
General
In the Options menu, you can choose to show the Unique Pattern ID, if you want to
have a unique name for the pattern, independent of the device/pattern name. This is
primarily intended for use with legacy imports and exports (PlaNet) as these tools
will not recognise the new device\pattern format generated by ASSET. To manually
set this ID, select the Override checkbox and enter the required new ID. If you
choose to import PlaNet format antennas, this field is auto-completed with the
antennas name contained in the file, enabling PlaNet sites to reference the correct
antenna on import.
In the Description box, type a description for your pattern.
323
ASSET User Reference Guide
On This Tab
You Can
ASSET automatically writes the Created and Modified boxes when a new pattern is
created or modified.
Define the gain for the selected pattern, referenced to either an isotropic (dBi) or
dipole (dBd) antenna.
Note: Ensure you select the correct reference antenna (dBi or dBd). There is no
conversion of the gain value in this dialog box when you switch from one to the
other. With respect to the cells in the Site Database, this gain value will be added to
the transmit power to determine the EiRP (if dBi chosen) or the ERP (if dBd
chosen).
Specify the polarisation used in this pattern: Horizontal, Vertical or Cross Polar.
Specify the Frequency of the pattern, the Front to back ratio, and, if appropriate, the
Cross polar antenna discrimination.
For Element Array Indicator, you can set this to '0', '1' or '2' to indicate the
capabilities of the antenna: 0 = single; 1 = dual band; 2 = tri band.
For Lever/Parameter Config ID, you can specify the lever/parameter configuration of
the antenna (such as the mounting or downtilt kit type).
Switched Beam Antennas
If the parent device is set to Switched Beam, you must specify the Pattern Beam
Index. This value must be unique per frequency.
You must define one or more Beam Sets so that you can create groups of patterns,
and specify the Control and/or Traffic beams. See Creating Beam Sets on page
320.
You can select the Composite Pattern option if you wish to use digital splitting on
the antenna. This will enable you to select beams on the Logical Antennas tab for a
property for the purpose of digital splitting. For more information, see
Logical Antennas Tab - Parameters in the ASSET Radio User Reference Guide.
When the Composite Pattern option is set and the pattern has been assigned to a
Logical Antenna, if you then de-select the Composite Pattern option, a warning that
the pattern is associated with a Logical Antenna appears.
Mask
In the Edit Primary Mask pane, click the required mask type (either Horizontal or
Vertical) to view and edit a table of losses in dB for different values of the pattern
azimuth (or elevation). These losses are the reduction in antenna gain from the
antenna pattern's point of maximum gain. Any changes you make are shown in the
corresponding diagram on the mask tab.
You can enter degree values up to 1 decimal place.
Note: The diagrams only display path losses of 40 dB or less.
For the Electrical Downtilt, Azimuth Offset*, and Horizontal and Vertical
Beamwidths, you can either enter your own values, or click the 'Calculate' buttons to
derive the values from the antenna pattern.
* See About the Azimuth Offset.
Important:
For all propagation models except MYRIAD and Volcano:

The Electrical Downtilt and Azimuth Offset values influence the predictions.
For MYRIAD and Volcano models:

The Electrical Downtilt and Azimuth Offset values do not influence the
predictions. Instead, these models read these values directly from the antenna
mask file.
For all propagation models:

The Horizontal and Vertical Beamwidth values do not influence the predictions.
4. When finished, click Apply (and Commit, as required) to save the changes to the pattern.
324
Managing Antennas and Equipment
About the Azimuth Offset
This topic provides a clarification of the Azimuth Offset, which is one of the antenna pattern
parameters that can be configured on the Mask tab of the Cellular Antennas dialog box.
This parameter is the angle, expressed in degrees, between the Physical Azimuth bearing of an
installed antenna and the maximum of its main beam in the azimuth plane. Azimuth Offset can be
positive or negative. For example, a positive value means that the antenna beam is directed to a
compass heading numerically greater than the Physical Azimuth bearing.
Whilst the Physical Azimuth bearing is fixed by the geometry of the antenna installation, in general
the Azimuth Offset is remotely controllable and variable. This antenna capability is also known as
Remote Azimuth Steering or RAS.
The 'Effective Azimuth' bearing is defined as the sum of the Physical Azimuth bearing and the
Azimuth Offset (Effective Azimuth = Physical Azimuth + Azimuth Offset).
Displaying the Azimuth Offset on Map View
When you display cells on the Map View, you can choose to show the azimuths so that they
consider Azimuth Offset.
To do this:
1. In the Map View, in the Layer Control Pane, click the Data Types tab.
2. In the list of data types, select the checkbox next to the required network element filter
under the Filters heading.
3. Double-click on the name of the network element filter.
4. In the Display Properties dialog box that appears, select the 'Consider Azimuth Offset'
checkbox in the Radial section for cells.
5. Click Apply/Redraw.
Here is an example giving a comparison:
'Consider Azimuth Offset'
not selected
'Consider Azimuth Offset'
selected
Ant 1: Physical Azimuth = 0 deg
Ant 1: Azimuth Offset = 10 ; Effective Azimuth = 0 + 10 = 10 deg
Ant 2: Physical Azimuth = 120 deg
Ant 2: Azimuth Offset = -10 ; Effective Azimuth = 120 - 10 = 110
deg
Ant 3: Physical Azimuth = 240 deg
Ant 3: Azimuth Offset = 5 ; Effective Azimuth = 240 + 5 = 245 deg
Example result:
Example result:
In addition, when you click on an antenna object in the Map View using either the 'Re-orientate
antenna' option or 'Move antenna' option, the Effective Azimuth bearing is displayed (where
appropriate) next to the Physical Azimuth bearing.
325
ASSET User Reference Guide
Using the Basic Search for Cellular Antennas
On the Tree tab of the Cellular Antennas dialog box you can search on device and pattern IDs
using the Find drop-down list.
Tip: If you have Show Unique Pattern ID selected in the Options menu, you can also search on a
unique pattern ID.
To make a basic search:
1. In the Find box, type one or more characters which you know are contained in the device
or pattern. In this example, the first two characters have been typed. The first item
matching these characters in the tree list is highlighted and a list of other matching items
becomes available in the drop-down list:
2. If the first item is not the one you require, either select the one you require from the dropdown list, or click the Find button to highlight the next matching item in the tree view.
If you want to search for antennas by setting customised rules, you can use the Advanced Search
tab.
Using the Hierarchy Tab to View, Delete or Reparent Patterns
You can use the Hierarchy tab of an antenna device to view the patterns that belong to it. To view
or refresh the details, click Display/Refresh.
You can use this tab to remove multiple elements to the Wastebasket. To do this, select the
required elements, then right-click and select Delete.
You can also reparent multiple patterns to a different device. To do this, select the required antenna
patterns, then right-click and select Cut. Then select a different antenna device in the left pane of
the dialog box, right-click, and select Paste.
You can also perform the Hierarchy tab functionality when you click on a folder (Tree tab only).
For more information about the Hierarchy tab, see:
 Deleting Antenna Devices and Patterns on page 327
 Editing or Moving Antenna Devices and Patterns on page 328
326
Managing Antennas and Equipment
Deleting Antenna Devices and Patterns
Provided that you have write access to the Cellular Antennas dialog box, you can delete antenna
devices and patterns. You can either do this individually, or you can use the Hierarchy tab to
perform multiple deletions.
Note: You will not be allowed to delete antenna devices or patterns that are currently assigned to
nodes/cells in the Site Database.
To delete a single antenna or pattern:
1. From the Equipment menu, click Cellular Antennas.
The Cellular Antennas dialog box displays a tree list of folders.
2. Extend the tree to view the antenna devices and patterns available.
3. Right-click the device or pattern you want to delete and from the menu that appears, click
Delete.
Warning: If you delete a device, all of its associated patterns will be removed to the
wastebasket.
To delete multiple antenna devices:
1. From the Equipment menu, click Cellular Antennas.
The Cellular Antennas dialog box displays a tree list of folders.
2. Select the folder from which you wish to delete antenna devices.
3. Select the Hierarchy tab.
4. Click the Display button.
A list of the antenna devices stored in this folder is displayed.
5. Hold down the Ctrl key and click the devices you want to delete, so that they are highlighted.
6. Right click and, from the menu that appears, select Delete.
All the highlighted antenna devices are deleted.
To delete multiple patterns:
1. From the Equipment menu, click Cellular Antennas.
The Cellular Antennas dialog box displays a tree list of folders.
2. Expand the folder from which you wish to delete antenna patterns.
3. Select the antenna device from which you wish to delete patterns.
4. Select the Hierarchy tab.
5. Click the Display button.
A list of the patterns stored for this antenna device is displayed.
6. Hold down the Ctrl key and click the patterns you want to delete, so that they are highlighted.
7. Right click and, from the menu that appears, select Delete.
All the highlighted patterns are deleted.
327
ASSET User Reference Guide
You can restore antenna devices and patterns by selecting them from the Wastebasket. For more
information on how to do this, see About the Wastebasket on page 76.
Tip: There is also a powerful 'Delete All' option that can be used on the Advanced Search tab.
See Maintaining Your Antenna Lists Efficiently on page 336.
Editing or Moving Antenna Devices and Patterns
Provided that you have write access to the Cellular Antennas dialog box, you can edit and move
antenna devices and patterns.
To edit an existing antenna or antenna pattern:
1. From the Equipment menu, click Cellular Antennas.
2. In the Cellular Antennas dialog box, click on the antenna or pattern you wish to edit.
3. Edit the required information on the tabs.
4. When finished, click Apply and, if required, Commit.
To move an existing antenna or antenna pattern in the antennas database:
In the Cellular Antennas dialog box, select and drag the antenna or the pattern to the
desired location.
(Antenna patterns can only be moved to antenna devices.)
Tip: Alternatively, you can use the Cut and Paste options from the Right-Click menu.
Warning: If you move antennas between projects, you cannot restore them to their original
project by clicking the Restore button.
To move multiple antennas or antenna patterns in the antennas database:
1. In the Cellular Antennas dialog box, select the folder containing the antennas that you
want to move, or the antenna containing the patterns that you want to move.
2. Select the Hierarchy tab.
3. Click the Display button.
Depending on the item you selected, a list of the cellular antennas stored in this folder or a
list of patterns stored on this antenna is displayed.
4. Hold down the Ctrl key and click on the antennas or patterns you want to move so that they
are highlighted.
5. Right click one of the highlighted antennas or patterns, and select Cut.
6. Right-click the folder or antenna to which you want to move the antennas or patterns, and
select Paste.
The antennas or patterns are moved to the new location.
328
Managing Antennas and Equipment
Viewing Pathlosses for Patterns
In the Cellular Antennas dialog box, on the Mask tab, you can view the precise path loss
(measured to 1 decimal place) at a particular angle on a pattern.
Important: The diagrams in the Horizontal and Vertical panes only display path losses of 40 dB
or less.
To do this:
1. In either the Horizontal or Vertical pane, click on the angle for which you want to view the
path loss.
The path loss at this particular point appears in the lower left corner of the beam pattern
pane. This picture shows an example, in which the path loss at 327° for the primary pattern
is 29.1 dB:
Tip: If you are comparing two patterns, you can view two pathloss values at the same
angle - one for the primary pattern (in red) and one for the secondary pattern (in blue).
2. To view the path loss at another angle, click the mouse button and drag the cursor to the
required angle.
Comparing Two Patterns
If you have more than one pattern available, you can compare different patterns with each other to
enable you to select the most appropriate one for your requirements.
To do this:
1. In the Antennas Database, on the Tree tab, select the required antenna device, and the
first pattern that you want to view:
329
ASSET User Reference Guide
2. Click the Mask tab. The first pattern will be displayed on both horizontal and vertical masks
in red.
3. From the Secondary pattern drop-down list, select the second pattern that you want view:
4. Ensure that the Both patterns option is selected:
The second pattern is displayed on the same diagrams in blue:
Tip: To view just one of the patterns at any time, select the Primary or Secondary pattern
option.
You can now compare the two patterns. You can make changes to the primary pattern, but
the secondary pattern is read-only.
Tip: As part of your comparison, you can view pathloss information for both patterns at
specific angles. For more information, see Viewing Pathlosses for Patterns on page 329.
330
Managing Antennas and Equipment
About the Context Menu on the Tree Tab
An extensive context menu is available on the Tree tab of the Cellular Antennas dialog box, by
right-clicking on an object.
The options are as follows:
If You Want To
Right-click This Level And Click This Option
Create a new folder.
Folder
New Folder
Create a new antenna device.
Folder
New Antenna Device
Create a new antenna pattern.
Device
New Pattern
Add the item to the list in the Advanced Search tab. Device or pattern
Note: If the selected item is a pattern, the parent
device is also added. If it is a device, only the
device is added.
Include in Advanced
Search
Add the device or pattern to the Selection Filter.
Device or pattern
Add to Selection Filter
Delete the item from the database.
Device, pattern, or folder
Delete
Rename the item.
Device, pattern, or folder
Rename
Cut the pattern, and paste it onto a different device, Device, pattern, or folder
or cut the device, then paste it into a different
folder.
Cut and Paste
Tip: You can also use the 'drag and drop' method.
Produce a report showing which objects are using
the device or pattern.
Device, pattern, or folder
Report Antenna Usage
Perform an XML Export directly from the Cellular
Antennas dialog box.
Device, pattern, or folder
XML Export
Note: You can perform an XML Import or XML
Export of all the objects in the Cellular Antennas
dialog box by using the Import or Export buttons.
Apply, Commit or Restore a change.
The exported object(s)
correspond to which level
of the tree is right-clicked.
Device will include child
pattern(s); Pattern will
include parent device;
Folder will include all its
devices and patterns.
Device or pattern
Apply
Commit
Restore
Using the Advanced Search for Antennas
If you want to search for antennas using customised rules, click on the Advanced Search tab of
the Cellular Antennas dialog box. Here you can:
 Create detailed search rules to enable you to locate specific antennas
 Perform a search using the rules you have created
 Edit and remove search rules
 Fine tune the search results
 Add chosen items to the Selection Filter
 Maintain your antenna lists efficiently
331
ASSET User Reference Guide
Creating Rules for Advanced Searches
The first step towards performing an advanced search for antennas with particular attributes is to
create your search rules.
To add a search rule:
1. On the Advanced Search tab of the Cellular Antennas dialog box, click the Add Rule
button:
2. Select an attribute from the Antenna Search Rule dialog box:
3. From the drop-down list for the Operator field, select an operator (not relevant for all
attributes).
4. If you want your search to exclude antennas described by the operator, select the 'Not'
checkbox.
332
Managing Antennas and Equipment
5. Type a value (or for some attributes select a value from a drop-down list, or for range-type
attributes you would need to type two values). For example you could search for antennas
with a Frequency equal to 37000:
Tip: For some attributes you can use a Regular Expression as an operator. For further
information see Examples of Searching by Regular Expression on page 109.
6. Click Add.
The rule appears in the Search Rules pane. You can add additional rules for your search in the
same manner. Once you have created your search rules you can perform your advanced search.
Performing the Advanced Search
Once you have created your antenna search rules, you can perform your advanced search. To do
this:
1. On the Advanced Search tab, select AND or OR (as required) in the Search Rules pane:
333
ASSET User Reference Guide
If you have only a single rule, the operator is insignificant. But for multiple rules, you need
to choose:
o
AND, if you want all of the rules to be satisfied
o
OR, if you want any of the rules to be satisfied
2. Click Search.
After you have done this, the results appear in the Search Results pane:
Note: The object count appears under the Search Results pane. If you subsequently use any of the
Exclude/Include options (see Fine Tuning the Results of the Advanced Search on page 335), this
changes to:
Editing and Removing Search Rules
To edit a search rule that you have added:
1. In the Search Rules Pane of the Advanced Search tab, right-click the rule that you want
to edit, and from the menu that appears click Edit.
- or Double click the rule to be edited.
The Antenna Search Rule dialog box appears.
2. Edit the entries in the Attribute and Operator boxes.
3. Click the Update button to save the entries.
To remove a search rule:
1. In the Search Rules Pane of the Advanced Search tab, select the rule to be removed.
2. Click the Remove Rule button.
The rule is deleted from the Search Rules pane.
334
Managing Antennas and Equipment
To remove all search rules:
1. In the Search Rules Pane of the Advanced Search tab, right-click any of the rules.
2. Select Remove All.
All the rules are deleted from the Search Rules pane.
Fine Tuning the Results of the Advanced Search
The Advanced Search tab provides some extra options that help you to fine tune the results of the
Advanced Search. These are:
 Exclude from Search Results (right-click)
 Include All Associated Patterns (right-click)
 Include Patterns for All Devices (button)
This table describes them:
If You Want To
Do This
Remove the antenna device (with all its patterns), or remove an individual
pattern, from the Search results.
Right-click on a device or
pattern,
then select 'Exclude from
Search Results'
Ensure all patterns for the selected device are included in the Search results.
Right-click on a device,
then select 'Include All
Associated Patterns'
Ensure all patterns for all the currently listed devices are included in the Search
results.
Click the 'Include Patterns
for All Devices' button
Tip: For a table listing all the context (right-click) menu options, see About the Context Menu on the
Advanced Search Tab on page 338.
Adding Searched Items to the Selection Filter
The Advanced Search tab also enables you to add any of the items in the list to the Selection
Filter.
You can do this for:
 Individual items one at a time, by right-clicking and selecting 'Add to Selection Filter'
 All the items currently in the list, by clicking the 'Add Search Results to Selection filter'
button
Tip: For a table listing all the context (right-click) menu options, see About the Context Menu on the
Advanced Search Tab on page 338.
Report of the Search Results
You can also generate a report in text format for the search results, by clicking the the 'Text
Export' button.
335
ASSET User Reference Guide
Maintaining Your Antenna Lists Efficiently
The Advanced Search tab provides options that help you to efficiently maintain the antenna lists
that are stored in your projects. These options are:
 Find All Empty Devices
 Delete All (from the database)
 Group Antennas by Device
This table describes them:
If You Want To
Do This
Find all antenna devices that do not contain any antenna patterns. This may be Click the 'Find All Empty
useful if you want to delete these devices, either individually by right-clicking, or Devices' button
using the Delete All button.
(positioned top-left)
Perform a database removal of all the devices currently listed in the Search
Results.
Notes:

The deletion process operates at the device level: an antenna device is
either deleted as a whole (with all its patterns) or it is not deleted at all.

If the deletion process encounters a device with one or more of its patterns
currently assigned in the Site Database, or encounters a device that does
not have all its patterns currently listed in the Search results, it skips that
device and sends an appropriate message to the Message Log. It then
continues processing other items in the list.
Group together selected patterns under a particular antenna device.
Click the 'Delete All'
button (positioned bottomright)
See Grouping Antennas
by Device on page 336
Grouping Antennas by Device
In the Cellular Antennas dialog box, the cellular antennas consist of an antenna device and one or
more beam patterns that belong to that device. Here is an example:
Example of Cellular Antennas - Device and Patterns
(Typically, the pattern name starts with the same string as the device name, but this may not be the
case if you use the Unique Pattern ID override option.)
It may be that your tree structure of antennas needs tidying from time to time. If so, you can use the
'Group by Antenna Device' functionality to group together selected patterns under a particular
antenna device.
Note: This grouping functionality is only available from the Advanced Search tab. The operations
on this tab are not affected by any filters selected on the Tree tab.
To use the grouping functionality:
1. From the Equipment menu, click Cellular Antennas.
2. Click on the Advanced Search tab.
336
Managing Antennas and Equipment
3. Perform your search as described in Using the Advanced Search for Antennas on page
331. (You can fine tune the list it if necessary.)
This enables you to produce a working list of antennas with which to perform the grouping.
For example, you may want to search all antennas of a particular manufacturer. However,
later in the process, you have the flexibility to manually add/remove other antennas to/from
the working list.
4. Click the Group Antennas by Device button.
This will launch a dialog box that shows three panes of information:
o
The middle pane ‘Search Results’ initially shows the same list that was present in the
Advanced Search results
o
The left pane ‘Device/Pattern List’ initially shows all other devices/patterns that were
excluded from the Advanced Search results
Note: The contents of the middle pane and the left pane are always mutually
exclusive.
o
The right pane ‘Select Target Device’ shows all the parent devices for the patterns
currently present in the ‘Search Results’ pane.
All three panes are organised with the same hierarchical structure (Folder, Device,
Pattern).
5. If required, you can refine the working list. You can move devices or patterns or folders
from the ‘Device/Pattern List’ (left) pane to the ‘Search Results’ (middle) pane, and vice
versa, by selecting the item and then using the left/right arrow buttons.
If you select and move a pattern, only that pattern is moved (not any sibling patterns). If
you select and move a device, all of its patterns are moved. If you select and move a
folder, all of its contents are moved.
Tip: If you want to find something in the left pane, you can type some characters in the
search string, and click Find.
6. When you have finished refining the list in the middle pane, you can move (group) all the
antenna patterns in the middle pane under one of the antenna devices listed in the right
pane. To do this, select one of the devices in the right pane, and then click the Group
Patterns under Device button. Then click OK.
The list structure in the middle pane now updates to show the patterns grouped under the selected
device, and the list structure is automatically updated in the Cellular Antennas dialog box.
337
ASSET User Reference Guide
Tip: If you want to, you can create a new device in the right pane, by right-clicking on a folder,
clicking New Device, and then naming it. You then need to Commit the new device. After that, you
can then use this new device to group the antennas in the same way as described above.
When you have finished with the Group by Antenna Device dialog box, you can close it. If you
made any changes to the antenna groupings, this is reflected in the Cellular Antennas dialog box,
both on the Tree tab and the Advanced Search tab.
About the Context Menu on the Advanced Search Tab
A context menu is available on the Advanced Search tab of the Cellular Antennas dialog box, by
right-clicking on an object.
The options are as follows:
If You Want To
Right-click on
And Select This Option
Create a new pattern for the device.
Device
New Pattern
Remove the antenna device (with all its patterns),
or remove an individual pattern, from the Search
results.
Device or pattern
Exclude from Search results
Include all patterns for the selected device in the
Search results.
Device
Include All associated Patterns
Add the device (without its patterns), or add a
pattern, to the Selection Filter.
Device or pattern
Add to Selection Filter
Delete the item from the database.
Device or pattern
Delete
Rename the item.
Device or pattern
Rename
Cut a pattern and paste it onto a different device
Device or pattern
(on either of the tabs) or cut a device and then click
the Tree tab to paste it into a different folder.
Cut and Paste
Produce a report showing which network elements
are using the device or pattern.
Device or pattern
Report Antenna Usage
Perform an XML Export.
Device or pattern
XML Export
Apply, Commit or Restore the change.
Device or pattern
Apply
Commit
Restore
Searching Antennas from the Site Database
When selecting antenna devices/patterns, you can search for antennas directly from the Site
Database.
To perform a simple search:
1. From the Database menu, click Sites.
2. From the View menu in the Site Database window, select Logical Links.
3. In the left pane, right-click the required network element and select View Property from the
drop-down menu.
4. Click the Physical Antennas tab.
338
Managing Antennas and Equipment
5. In the Device ID column, click at the right end of the cell on the required row. (If you click
elsewhere in the cell a drop-down arrow appears at the right end of the cell and you can
click on that to achieve the same result, which is that the Antenna Search dialog box
opens).
6. In the Search field of the Antenna Search dialog box, type your search criteria.
7. Click Find.
8. Click the required device in the Match List pane. The Antenna Search dialog box closes
and your chosen antenna appears in the Device ID column of the Physical Antennas tab
in the Site Database window.
To perform an advanced search:
1. Follow steps 1 to 5 of the simple search above.
2. In the Antenna Search dialog box, click the Advanced Search button. the Antenna
Search dialog box closes and the Cellular Antennas dialog box opens.
3. Carry out your advanced search as described under Using the Advanced Search for
Antennas on page 331.
Using the Switched Beam Antenna Utility
ASSET Radio provides a utility to create switched-beam antennas that can partially model full
dimension (FD) beamforming for 5G. This is sometimes referred to as FD MIMO.
The purpose of this utility is to create a switched-beam antenna with a large number of beams
(directions) to approximate a beamforming antenna (which can dynamically steer a beam in any
direction).
The role of FD beamforming is to cover the 3D space in both directions: Azimuth (or Horizontal)
and Elevation (or Vertical).
This will increase the overall spectral efficiency of the cell, with an increase in MU-MIMO, and also
help to plan coverage for users at different heights.
The utility can create a switched-beam antenna with a large number of traffic beams. Once created,
these multi-beam antennas can be saved as XML files and then imported into your project where
they will appear in the Cellular Antennas dialog box. There they will correspond with the usual
rules for switched beam antennas (see About Switched Beam Antennas on page 319), such as the
need to set up one or more beam sets (see Creating Beam Sets on page 320). They can then be
assigned to Properties and cells and used in the normal way for coverage analysis.
To use the utility:
1. From the File menu, click Add-ins.
2. Click Switched-Beam Antenna Utility.
339
ASSET User Reference Guide
3. A dialog box appears, as in this example:
4. Set the parameters and options, which are as follows:
Pane
Parameter or Edit Box
Values or Comments
Element Array Configuration
Elements
Horizontal
Vertical
Spacing (wavelengths)
Horizontal
Vertical
Min Angle (°)
Horizontal
Vertical
Max Angle (°)
Horizontal
Vertical
Output Beam Array Configuration
Number of Directions (*)
Horizontal
Note: Before you set these
Vertical
values, see the description of the
Auto-Calculate option below)
Freq (MHz)
Single Element Pattern (3GPP 38.901)
Antenna Name
This will be the Device ID
Output XML file
File name and location
Beamwidth (°)
Horizontal
Vertical
Amax (dB)
Horizontal
Vertical
Gain (dBi)
Visualise Beam Pattern
340
Angle (°)
Horizontal
Vertical
Beam Index
Incremental buttons
Managing Antennas and Equipment
Note: In this particular dialog box, the keyboard editing functions ENTER and TAB work
differently:
o
Pressing the ENTER key will update the value in the edit box, and the cursor remains
in the same box.
o
Pressing the TAB key will update the value in the edit box and then move the cursor to
the next edit box or button on the dialog box.
5. The 'Visualise Beam Pattern' pane enables you to view individual patterns by using the
Beam Index arrows (this has no effect on what gets written to the XML file).
6. Optionally, click the Auto-Calculate button (see description below).
7. After all the parameters have been specified:
a. Select the 'All Projects' checkbox if that is how you want the file to be imported at a
later time. If this is not selected, then the file will be imported (at later time) to your
currently logged-in project only.
b. Click the Write Antenna XML File button.
8. The file is saved to the specified location, ready for import into your currently logged-in
project or all projects, as appropriate.
Automatically Calculating the Number of Directions
As stated above, the purpose of this utility is to create a switched-beam antenna with a large
number of beams (directions) to approximate a beamforming antenna (which can dynamically steer
a beam in any direction).
However, using too many beams in a small range means that adjacent beams will overlap
significantly and cause SINR to be over-estimated in the Simulator.
Therefore ASSET Radio provides an option in the utility to automatically populate the numbers of
vertical and horizontal beams based on the other parameters. This calculates the number of beams
(directions) that would minimise the error in SINR, and makes the process of creating the beams
much less complicated.
If you want to do this, ensure you set all the other parameters and options first, and then click the
Auto-Calculate button.
The sole purpose of the Auto-Calculate button is to set the two values in the 'Number of
Directions' boxes:
It does not edit any other parameter in the Switched-Beam Antenna Utility.
341
ASSET User Reference Guide
Digitally Splitting Antennas
Antennas that use digital splitting to expand network capacity can be accommodated on LTE and
5G cells.
To use digital splitting:
1. Add single beams as composite patterns to an antenna device. For more information - see
Adding Patterns to an Antenna Device on page 323.
2. In the Site Database, using the Location view, select the cell to be split.
3. Using the right-click menu, create two clones of the cell.
4. On the Property, select the physical antenna.
5. Using the Add button, add two more logical antennas.
6. In the Single Beam column, select the two new logical antennas.
7. In the Pattern ID column, use the drop-downs to set the two new logical antennas to
different single beams.
8. In the Prediction Model column, use the drop-downs to add prediction models to the two
new logical antennas.
9. Click Apply.
10. In the Child Ids column, deselect the original logical antenna and select the two new ones.
11. Click Apply.
The split sites will now be available for selection in the Pathloss Prediction Generator. For more
information, see Using the Pathloss Prediction Generator in the ASSET User Reference Guide
Using the Planet PAFX Antenna Import
ASSET Radio supports the direct import of Planet PAFX (*.pafx) antenna files.
This means that the Antenna Device and multiple Antenna Patterns that are contained in the *.pafx
file(s) are imported directly into ASSET. No intermediate steps or manual intervention are required.
Note:
 The import supports any technology or type of antenna that exists in *.pafx format.
 You can import a single file or multiple files.
 Only the data related to Patterns is imported; data related to Ports, Electrical Controllers
and Beamforming is not imported.
To perform the import:
1. From the Equipment menu, click Cellular Antennas.
2. At the top-left of the Cellular Antennas dialog box, from the File menu, click Import Planet
Antenna File.
342
Managing Antennas and Equipment
A dialog box appears, as in this example:
3. Select the 'Add to All Projects' checkbox if you want the imported antenna device/pattern to
be added under All Projects. If not selected, then it will be imported to your currently
logged-in project only.
4. Select 'Import as Switched Beam' if you want to import the antenna into ASSET as a
switched-beam antenna. When you select this, the Pattern Beam Index will be sequenced
for patterns that have the same Frequency (from 0 onwards) and the Antenna Type on the
device will be set to 'Beam-Switching.'
If this option is not selected, the antenna will be imported as a normal 'Passive' antenna
type.
5. In the Import Conflicts pane, select how you want conflicts to be handled during import.
You can be prompted on an individual basis, or (for all conflicts), you can leave the existing
data as it is, merge the data, or replace the data in the project with the imported data.
6. In the Import File box, select the required *.pafx file(s) to be imported into ASSET, by using
the
button. If required, you can select multiple files.
7. Click OK.
Your selections are persisted for the next time you use this import dialog box.
Using the Planet Antenna Utility
ASSET Radio provides a utility that can convert Planet Antenna files (*.txt / *.msi) into Antenna
XML files so that multiple antennas and patterns can be converted into ASSET XML format.
It enables you to combine multiple antennas into single devices, or combine them all into one single
device. This second option is especially useful when, for a given switched-beam antenna, you have
multiple files representing different beam patterns and the aim is to have all of those files anchored
under a single switched beam antenna device.
(The utility can also be run independently of ASSET. If you require further details, please contact
your regional Product Support centre.)
Important: There is also a Planet PAFX Antenna Import feature that supports the direct import of
*.pafx antenna files, where the Antenna Device and multiple Antenna Patterns that are contained in
the *.pafx file are imported directly into ASSET. No intermediate steps or manual intervention are
required. (The Planet PAFX Antenna Import feature has no interaction or dependency on the Planet
Antenna Utility.) See Using the Planet PAFX Antenna Import on page 342.
343
ASSET User Reference Guide
To use the utility:
1. Check first where your Planet Antenna files are stored.
2. From the File menu, click Add-ins.
3. Click Planet Antenna Utility.
A dialog box appears, as in this example:
4. From the folder where the Planet Antenna files are stored, drag and drop any or all of the
required files into the main area of the dialog box.
5. If you want to force all patterns into one device, select the appropriate checkbox.
Otherwise, the combining will only occur where the patterns have a common device name,
so that this may result in several devices.
6. Specify the output folder, by typing the path or using the
button.
7. Click Generate XML.
The file or files are saved in the specified folder.
Adding Microwave Antennas
You can add microwave antennas to the antenna inventory in a number of ways:
 If you have the required microwave antennas stored in a file that uses one of the supported
formats, you can import them. For more information, see 'Importing Microwave Antennas' in
the ASSET Backhaul User Reference Guide.
 If you have the manufacturer's datasheets, or know the parameters (dimensions, masks
and so on) that the antennas should have, you can add them manually.
To add an antenna manually:
1. Ensure you have write permissions for equipment and that you have the Backhaul tab
selected.
2. From the Equipment menu, click MW Antennas.
344
Managing Antennas and Equipment
The Microwave Antennas dialog box appears:
3. Select the project folder in which you want to store the new antenna(s). You need the
correct privileges to add antennas to the All Projects folder.
4. Right-click and from the menu that appears, select New MWAntenna Device.
5. Add the required information on the General tab including:
In This Pane
Do This
General
Information
In the Device ID box, type the user-defined name of the selected antenna device
to a maximum length of 31 characters.
Click Photo to display a photograph of the component or to search for and
assign a photograph.
In the Description box, type in a description for your antenna device.
ASSET automatically writes the Created and Modified boxes when a new
antenna is created or modified.
Costing
Information
Select one of the manufacturers from the list of suppliers that you have entered.
Add a unit cost for the antenna.
6. Click Apply.
7. Click Commit.
8. Click Close.
You can then add a pattern to your microwave antenna.
Adding Microwave Antenna Patterns
To add a microwave antenna pattern:
1. In the left pane of the Microwave Antennas dialog box, right-click the microwave antenna
you wish to add a pattern to and from the menu that appears, select New MW Antenna
Pattern.
345
ASSET User Reference Guide
2. Add the required information on the tabs, including:
On This Tab
Do This
General
Define the gain for the selected beam pattern, referenced to either an
isotropic (dBi) or a dipole (dBd) antenna.
Specify the physical dimensions of the antenna - its diameter and weight.
Specify the frequency band of the beam pattern, the minimum and
maximum operating frequencies and the front to back ratio.
Type the manufacturer's name in the appropriate box.
Specify which type of polarization is used in this beam pattern - either single
polarization (which can be horizontal, vertical or both (crosspolar)) or dual
polarization.
Tip: If you want the antenna to be used in dual polar links, select dual
polarization.
The polarization type that you choose will affect the number of masks you
have to define on the Mask tab.
Select the required mask style, depending on your link type:

If you are defining an antenna for a PtP link, a symmetrical mask is
appropriate. In a symmetrical mask, the horizontal and vertical planes
share the same mask.

If you are defining an antenna for a PmP link, a non-symmetrical mask
is appropriate. In a non-symmetrical mask, different masks are used for
the horizontal and vertical planes.
If you are using NSMA format antennas, define:
Mask

The FCC/ETSI ID - the ID number issued by the Common Carrier
Branch of the FCC. For services that do not issue ID numbers, insert
NONE to ensure the antenna can be exported correctly.

The Pattern ID - The reverse pattern FCC ID number. The reverse
pattern is generally obtained by inserting the feed in an opposite
manner in order to reverse the pattern.

The Half Power Beam Width - This is the included angle centered on
the main beam of the antenna and defines the angle where the antenna
response falls below -3dB.
Select the pattern that you want to view. The number of patterns available
will be based on the polarization type selected on the Info tab. For more
information on the available types, see below this table.
A graphical illustration of the chosen pattern is displayed, along with the
3dB beamwidth.
You can edit the mask data to show losses for different values of antenna
azimuth (or elevation). For more information on how to do this, see Editing
the Mask Data for Microwave Antennas on page 347.
Note: Symmetrical patterns are indicated by an asterisk (*) next to the
angle.
On the Mask tab for a microwave antenna pattern, the patterns are listed using
abbreviations:
o
V stands for vertical and H for horizontal
o
The first letter shows the polarization that the antenna transmits
o
The second letter shows the polarization of the signal being received
For example, a VH pattern transmits on the vertical plane and receives on the horizontal
plane.
346
Managing Antennas and Equipment
Depending on the polarization type you have selected on the Info tab, you should define
the following patterns:
Polarization Type
Masks
Required
Single Horizontal
HH
HV
Single Vertical
VV
VH
Single Horizontal and Vertical
HH
HV
VV
VH
- or Dual
3. Click Apply.
4. Click Commit.
5. Click Close.
Editing the Mask Data for Microwave Antennas
On the Mask tab for a microwave antenna, you can click Edit Mask Data to see a table listing
losses for different values of antenna azimuth (or elevation). These losses are the reduction in MW
antenna gain from the MW antenna pattern's point of maximum gain.
This picture shows an example:
Example mask data for an antenna
You can add and change data in the table and this is then shown in the illustration on the Mask tab.
347
ASSET User Reference Guide
For the angle, you can enter values to 2 decimal places.
Tip: The mask that you want to add may be symmetrical - that is, have matching loss values for
both sides of the mask (from 0° to 360° and from 360° to 0°, but not including 0° and 180°).
To quickly add a symmetrical mask:
1. Add one side of the mask (either the angle from 0 to 360 degrees, or the angle from 360 to
0 degrees) and the accompanying loss, and then click Add.
2. Click the Mirror button.
The other side of the mask, and its corresponding row, are created automatically. If you
subsequently update one of the rows, this is reflected in the corresponding row.
Symmetrical masks are indicated by the word 'Symmetrical', and an asterisk (*) next to the
angle in the list.
Important: Make sure that you have entered all the required antenna radiation patterns (VV, VH,
HV and HH). Lacking one antenna radiation pattern might affect interference calculation results.
Editing, Moving and Deleting Microwave Antennas
Provided that you have write access to the Microwave Antennas dialog box, you can edit, move or
delete MW antennas.
To edit an existing MW antenna:
1. From the Equipment menu, click MW Antennas.
2. In the Microwave Antennas dialog box, click on the antenna you wish to edit.
3. Edit the required information on the tabs.
4. When finished, click Apply and, if required, Commit.
To move an existing antenna to a different folder in the Microwave Antennas dialog box:
1. In the Microwave Antennas dialog box, select the antenna you want to move.
2. Drag and drop it to the appropriate folder.
Tip: Alternatively, you can use the Cut and Paste options from the right-click menu.
Warning: If you move antennas between projects, you cannot restore them to their original
project by clicking the Restore button.
348
Managing Antennas and Equipment
To delete a single antenna or antenna beam pattern:
1. In the Microwave Antennas dialog box, right-click the antenna that you want to delete.
2. From the menu that appears, click Delete.
Note: You cannot delete antennas that are currently assigned to links in the Link
Database, nor when the project has been opened in Partial Load or Region Load.
Tip: You can restore antennas by selecting them from the Wastebasket.
Storing Equipment in the Database
ASSET not only stores the logical configuration of the cellular or fixed network but also the physical
configuration by storing the various types of equipment used. Storing 'libraries' of equipment details
in ASSET has a number of benefits:
 Network component details are easily accessible
 There is no need for a separate database
 Detailed parameters can be held against each equipment component, reducing the chance
of error
 Photographs can be attached to components, to make identification easy
When you have added an equipment type to ASSET, it becomes available in the relevant dropdown lists in the Site Database:
Choosing equipment types in the Site Database
You can then choose to Apply it to the required network element.
The default type for all equipment types is Unknown, which uses default parameters for any
calculations that require equipment data.
You should ensure your data is accurate; review it regularly so that the most up-to-date agreed
values are being used for the network design.
349
ASSET User Reference Guide
Creating Site (BTS) Equipment
To create and edit site (BTS) equipment:
1. Ensure you have write access to the BTS database.
2. From the Equipment menu, click BTS Equipment.
The BTS Equipment dialog box displays the site equipment available to the current
project.
3. Click Add.
A BTS with a default name appears in the list.
4. Select the new BTS and add the required data on the tabs:
On this tab
Do this
General
In the Part ID box, enter the user-defined name of the selected equipment to a
maximum length of 128 alphanumeric characters.
Click Photo to display a photograph of the BTS equipment or to search for and
assign a photograph.
If required, add a description of the mast head amplifier as well (up to 256
characters)
ASSET automatically writes the Created and Modified boxes when new BTS
equipment is created or modified.
Costing
Select one of the manufacturers from the list of suppliers that you have entered. See
Viewing and Changing Equipment Suppliers Details on page 355 for more
information.
Add a unit cost.
Parameters
Specify the maximum and minimum output power of the BTS equipment.
If the value for the PA output is set in the Site Database to a value outside the
allowed range for the appropriate transmitter, the value is adjusted by ASSET to the
maximum or minimum as required, and the Message Log informs you of this
change.
Specify the Minimum and Maximum carrier spacings allowed between carriers on
the same site (Site Spacing) and between carriers on the same cell (Cell Spacing).
5. Click Apply or Commit, as required.
To edit a BTS:
1. Select the BTS and change the required data on the tabs.
2. When finished, click Apply or Commit, as required.
To remove a BTS:
Click the BTS in the list, then click Remove.
Note: This cannot be done if the project has been opened in Partial Load or Region Load.
350
Managing Antennas and Equipment
Creating Cell Equipment
To model equipment such as hybrid combiners and attenuators which do not come under any of
the predefined categories, use the Cell Equipment dialog box.
To create cell equipment:
1. Ensure that you have write access to the cell equipment database.
2. From the Equipment menu, click Cell Equipment.
The Cell Equipment dialog box displays the cell equipment available to the current project.
3. Click Add.
A cell equipment with a default name appears in the list.
4. Select the new cell equipment and add the required data on the tabs:
On this tab
Do this
General
In the Part ID box, enter the user-defined name of the selected equipment to a
maximum length of 128 alphanumeric characters.
Click Photo to display a photograph of the cell equipment or to search for and
assign a photograph.
If required, add a description of the mast head amplifier as well (up to 256
characters).
ASSET automatically writes the Created and Modified boxes when new cell
equipment is created or modified.
Costing
Select one of the manufacturers from the list of suppliers that you have entered.
See Viewing and Changing Equipment Suppliers Details on page 355 for more
information.
Add a unit cost.
Info
Specify equipment loss (dB), which is the insertion loss for the component. The
default value for equipment loss in the Unknown cell equipment type is zero.
5. Click Apply or Commit, as required.
To edit a cell equipment:
1. Select the cell equipment and change the required data on the tabs.
2. When finished, click Apply or Commit, as required.
To remove a cell equipment:
Click the cell equipment in the list, then click Remove.
Note: This cannot be done if the project has been opened in Partial Load or Region Load.
Creating Cabins
As for other equipment, you can add and edit cabins:
1. Ensure you have write access to the cabin database.
2. From the Equipment menu, click Cabins.
The Cabins dialog box displays the cabins available.
3. Select the folder to which you want to add the cabin, either the current project or All Projects.
351
ASSET User Reference Guide
Note: You need the correct privileges to add cabins to the All Projects folder.
4. Right-click, and from the menu that appears, click New Cabin.
A cabin with a default name appears in the list.
5. Select the new cabin and add the required data on the tabs:
On this tab
Do this
General
In the Part ID box, enter the user-defined name of the selected cabin to a
maximum length of 31 characters.
Click Photo to display a photograph of the cabin or to search for and assign a
photograph. ASSET automatically writes the Created and Modified boxes when
new cabin is created or modified.
Costing
Select one of the manufacturers from the list of suppliers that you have entered.
See Viewing and Changing Equipment Suppliers Details on page 355 for more
information. Add a unit cost.
Dimensions
Specify the dimensions of the cabin - length, width, height, weight.
Tip: You can create subfolders, and you can move, delete and rename cabins. For more
information, see Managing Antennas and Equipment using Folders on page 311.
Creating Feeders
Feeder equipment is relevant to both ASSET Radio (cellular antennas) and ASSET Backhaul
(microwave antennas). It is important to define your feeders as accurately as possible, because
they incur losses which will affect the performance of your network.
To define feeders:
1. From the Equipment menu, and click Feeders.
The Feeders dialog box displays the feeders available, to all projects and just the current
project as well.
This picture shows an example:
352
Managing Antennas and Equipment
2. Select the folder to which you want to add the feeder, either the current project or All
Projects.
Note: You need the correct privileges to add feeders to the All Projects folder.
3. Right-click, and from the menu that appears, click New Feeder.
A feeder with a default name appears in the list.
4. Select the new feeder and add the required data on the tabs:
On this tab
Do this
General
In the Part ID box, type the user-defined name of the selected feeder to a
maximum length of 31 characters.
Click Photo to display a photograph of the component or to search for and
assign a photograph. ASSET automatically writes the Created and Modified
boxes when a new feeder is created or modified.
Costing
Select one of the manufacturers from the list of suppliers that you have
defined.
Add a unit cost for the feeder.
Losses
Specify the frequency band that the feeder is valid for.
Specify the feeder loss on a per metre basis (not dB/100 m).
The total loss of all connectors (around 0.5-1 dB per station) should also be
included.
Specify the feeder weight, in kg per metre.
Tip: You can create subfolders, and you can move, delete and rename feeders. For more
information, see Managing Antennas and Equipment using Folders on page 311.
Creating Masts
To create and edit masts:
1. Ensure you have write access to the mast database.
2. From the Equipment menu, click Masts.
The Masts dialog box displays the masts available.
3. Select the folder to which you want to add the mast, either the current project or All
Projects.
Note: You need the correct privileges to add masts to the All Projects folder.
4. Right-click, and from the menu that appears, click New Mast.
A mast with the default name appears in the list.
5. Select the new mast and add the required data on the tabs:
353
ASSET User Reference Guide
On this tab
Do this
General
In the Part ID box, enter the user-defined name of the selected equipment to a
maximum length of 31 characters.
Click Photo to display a photograph of the mast or to search for and assign a
photograph. ASSET automatically writes the Created and Modified boxes when
a new mast is created or modified.
Costing
Select one of the manufacturers from the list of suppliers that you have entered.
See Viewing and Changing Equipment Suppliers Details on page 355.
Add a unit cost.
Dimensions
Specify the mast's dimensions - structure height, section length and weight.
Specify how the mast is mounted - for example, from a rooftop.
Constraints
Optionally, set available mast heights. In this version of ASSET, this tab is for
information only, and has no other impact.
Tip: You can create subfolders, and you can move, delete and rename masts. For more
information, see Managing Antennas and Equipment using Folders on page 311.
Creating Mast Head Amplifiers
For the appropriate technologies, you can use mast head amplifiers on some cells to improve the
receiver performance. They have a noticeable beneficial effect when there is considerable feeder
loss between the antenna and the transceiver.
To create and edit a mast head amplifier:
1. Ensure you have write access to the Mast Head Amplifier database.
2. From the Equipment menu, click Mast Head Amplifiers.
The Mast Head Amplifier dialog box displays the mast head amplifiers available to the
current project.
3. Click Add.
A mast head amplifier with a default name appears in the list.
4. Select the mast head amplifier and add the required data on the tabs:
On this tab
Do this
General
In the Part ID box, enter the user-defined name of the equipment.
Click Photo to search for and assign a photograph of the equipment.
If required, add a description.
ASSET automatically writes the Created and Modified boxes when a new mast
head amplifier is created or modified.
Costing
Optionally, select one of the manufacturers from the list of suppliers. See Viewing
and Changing Equipment Suppliers Details on page 355 for more information.
Add a unit cost.
Amplifier
Specify the Mast Head Amplifier parameters:
The Uplink Noise Figure, the Uplink Maximum Gain, and the Downlink Insertion
Loss.
5. Click Apply or Commit, as required.
354
Managing Antennas and Equipment
To edit a mast head amplifier:
1. Select the mast head amplifier and change the required data on the tabs.
2. When finished, click Apply or Commit, as required.
To remove a mast head amplifier:
Click the mast head amplifier in the list, then click Remove.
Note: This cannot be done if the project has been opened in Partial Load or Region Load.
Viewing and Changing Equipment Suppliers Details
You can enter the names, addresses and other contact details for equipment suppliers:
Adding Equipment Suppliers
To add a new equipment supplier:
1. From the Equipment menu, click Suppliers.
2. Click Add and enter the required details then click OK.
355
ASSET User Reference Guide
356
Using Propagation Models
12 Using Propagation Models
Propagation models are mathematical attempts to model the real radio environment as closely as
possible. Most propagation models need to be tuned (calibrated) by being compared to measured
propagation data, otherwise you will not be able to obtain accurate pathloss predictions.
Carrier Wave measurements (survey data) help you produce an accurate propagation model that
functions correctly. No model could be applied with accuracy to every situation, and the choice of
model is not as important as the fine tuning for the particular environment. Normally this calibration
process is carried out by a specialist. The validity of a propagation model will depend on the validity
and significance of the survey data.
A number of Application Programming Interfaces (APIs) are also available, enabling you to create
custom propagation models. For more information, see the 'ASSET Interfaces' chapter in the
ASSET Technical Reference Guide.
Note: Information about propagation models can be found in the ASSET User Reference Guide,
because it is generic to both ASSET Radio and ASSET Backhaul. However, information about
model analysis and model tuning, which are both specific to ASSET Radio, is here in the ASSET
Radio User Reference Guide.
How Many Propagation Models are Required?
There are two extreme ways in which you can use propagation models:
 You can have a large number of models, each pertaining to a particular area or city. This
has the advantage of having accurate models for specific areas or cities. The disadvantage
is that it may not be feasible or economical to achieve and maintain that accuracy, given
the time and cost incurred for the model tuning process.
 You can have one generic model which can be used for all areas. This has the advantage
of making the choice much simpler for the planner. Also, the model tuning process would
be more economical both in terms of cost and time. However, the disadvantage is that the
model is just an average case, and its accuracy may be limited.
A more realistic approach is to use a small number of different models for generic environments, for
example, urban, rural and so on. The number of models will depend on:
 The resources available, in terms of time, finances, manpower and skills
 The available mapping data: resolution, number of clutter classes, building raster and
building vector information
 The diversity of area or country to be modelled
 The accuracy required
Project Defaults
In order to make a project easy to use right from the start, the following default objects, with pre-set
parameters, are provided each time a new project is created in ASSET:
 Antenna default
 Propagation model defaults (450, 900, 1800 and 2100 MHz)
 MU-Node Template defaults (with sites/nodes and cells for each single technology and for
some multiple technology combinations)
 Terminal type default (for each technology)
357
ASSET User Reference Guide
These default objects represent the minimum parameters required to create sites/nodes and
generate coverage arrays.
About the Accuracy Required for a Propagation Model
Propagation model accuracy is always important. This table shows how the accuracy of a
propagation model can affect each of the planning processes:
This planning
process
Is affected by the accuracy of propagation model in this way
Best Server
The better the model accuracy (that is, the lower the standard deviation), the
more representative the values are at each pixel in the Best Server array to real
life values.
Service area calculation
This has implications for the spreading of traffic within cells. Typically, for a
densely planned area of the network, the accuracy of the model will have
minimal impact on this calculation of service area. For a less densely planned
network, where cell service areas are limited by minimum signal thresholds,
inaccuracies in the model will have a greater effect.
Neighbour analysis
Typically, for a densely planned area of the network, the accuracy of the model
will have minimal impact on this calculation of nearest neighbours. For a less
densely planned network, where cell service areas are limited by minimum
signal thresholds, inaccuracies in the model will have a greater effect upon the
calculation of neighbours.
Interference table
generation
The greatest effect of accuracy of the model is in the interference table
generation process. If, for example, the propagation model is accurate to 8dB
standard deviation, then for each individual C/I calculated the standard
deviation will be 11.3dB. If the model is accurate to 10dB standard deviation,
the standard deviation of the C/I will be 14.1dB. The accuracy of an
uncalibrated model may be significantly less than this.
Resulting interference
arrays
The more accurate the model, the less errors are involved in the carrier to
interference arrays.
About the Supplied Propagation Models
These propagation models are supplied and supported in the ASSET suite:
Model
Brief Description
Recommended Usage
Standard
Macrocell 3
General Purpose macrocell
model that accounts for the
different elements of
propagation in the wireless
channel.

Can be typically calibrated to
less than 7dB standard
deviation.
Models 1 and 2 are only
supported for customers who
still want to use them, and
upgrade from previous
versions of ASSET (these
models cannot be added).
358
Recommended Mapping
Data
Sites in environments

where the distance from
the site is greater than

approximately 500m

Base station antenna
heights in the range of
15-200m

Receiver heights in the
range of 1-10m

Multiple height
capability: see About
Multiple Height Pathloss
Predictions
Terrain DTM height raster data
Terrain clutter - raster
data
Clutter and Height data
should be of the same
resolution(s). Although there
is no minimum resolution,
recommended pixel sizes for
this data are between 20m
and 200m.
Using Propagation Models
Model
Brief Description
DHM model
Same as the Standard
As above, but especially
Macrocell 3 model but with the suited to built-up areas.
additional ability to include
building height rasters (digital
height maps) in the calculation.
As for Standard Macrocell 3
but with additional building
raster layer.
Enhanced
Macrocell
In the pathloss calculation

parameters for this model, you
can specify the slope and
intercept parameters (k1 and
k2) independently for LOS and
NLOS. These parameters are 
used dynamically during the
propagation calculations.
It is advantageous to
use this model in
environments with hilly
terrain
As for Standard Macrocell 3.

It has several
advantages over the
Standard Models, as
described in About the
Enhanced Macrocell
Model on page 364
Free Space
Loss Model
Recommended Usage
Recommended Mapping
Data
Multiple height
capability: see About
Multiple Height Pathloss
Predictions
Simulates the signal strength
Best used when you have
loss across a line-of-sight path LOS connections.
in which the transmit and
receive antennas operate in an
otherwise empty environment.
As for Standard Macrocell 3,
but you can also use building
vectors.
Note: The Free Space Loss
model is only available in
ASSET Backhaul.
MYRIAD
model
The MYRIAD model is the
successful result of several
years of research in
propagation, modelling,
optimisation and algorithms.
All cell sizes (micro,
mini, small, and macro
cells)

The model can automatically
adapt itself to all engineering
domains, radio environments
and systems.
All radio environments
(dense urban, urban,
suburban, mountainous,
maritime, open)

It relies on highly realistic
modelling of the propagation
channel.
All systems (DVB-H,
GSM, (E)GPRS, UMTS,
Wi-Fi, LTE, 5G, NB-IoT)

Frequencies from 400
MHz to 5 GHz

Multiple height
capability: see About
Multiple Height Pathloss
Predictions
MYRIAD is a separately
licensed TEOCO propagation
model.
Volcano
(Rural)

Suitable for transmitters
located whether in rural or
suburban environments.
Specifically adapted for
dominant sites, with
antennas located above
surrounding building
A deterministic propagation
rooftops, typically in rural
model based on 'multiple knife- environments.
edge' diffraction.
Volcano models are separately
licensed.
As for Standard Macrocell 3.
For full information on how to
use this model, refer to the
MYRIAD Help or MYRIAD
User Reference Guide.
ASSET map data files:

DTM/Heights/Altitude

Clutter data
Optionally:

Clutter heights in raster
and/or vector format

Building outlines in vector
format
359
ASSET User Reference Guide
Model
Brief Description
Recommended Usage
Recommended Mapping
Data
Volcano
(Urban)
Suitable for any transmitters
located whether in denseurban urban or suburban
environments.
Depending upon the site
configuration, ray-tracing
options can be activated,
which permits users to
benefit from a full multipaths calculation or a smart
time optimized one.
Specifically adapted for
urban environment in the
presence of a dense small
cell distribution.
ASSET map data files:
A deterministic propagation
model based on 'over rooftop'
diffraction and on 'multipath
component modelling', that is,
2D or 3D ray-tracing.

DTM/Heights/Altitude

Clutter data

Clutter heights in raster
and/or vector format
(optional but
recommended in urban
environments)

Building outlines in vector
format for ray-tracing
Optionally:

Volcano
(Maestro)
SUI model
SLR model
Maestro is an adaptive “smart” Coherent and high precision
model manager which
nationwide planning and
automatically selects the best management.
propagation model to be
applied to the environment and
frequency under study.
The SUI (Stanford University
Interim) model is one of the
recommended models for use
in analysing fixed wireless
broadband communication
networks at frequencies below
11GHz.
The SLR model in ASSET is
partly based on the ITU-R
P1546-2 recommendation. The
model can be used for DVB-H
planning or for other
applications that require longrange calculations (1-1000km).

Cells with radius <10km

Can be used for various
terrain and tree density
types

Base station antenna
heights in the range of
15-40m

Directional antennas (210m) at the CPE
receiver, installed on or
below rooftops or
windows
Point cloud LiDAR data
Same as for the Volcano
Rural and Volcano Urban
models.
For full information on the
Volcano models, refer to the
Volcano User Guide.
As for Standard Macrocell 3.
Point-to-Area model that can As for Standard Macrocell 3.
be used to make predictions
for terrestrial services in the
frequency range of 100 to
2000 MHz.
Restricted to 50% time
variability and to a land path.
Note: All the supplied propagation models are distributable and can be multi-threaded (locally and
remotely).
About the Standard Macrocell Models
There are three Standard Macrocell models: 1, 2, 3.
It is recommended to use model 3, because it is more accurate than the older models.
Note: The models 1 and 2 are only supported for customers who still want to use them, and
upgrade their databases from previous versions of ASSET. Only model 3 can be added (see
Configuring a Standard Macrocell Model on page 372).
360
Using Propagation Models
The Standard Macrocell models incorporate an optimal dual slope loss model with respect to
distance from the base station. They also incorporate algorithms for effective base station heights,
diffraction loss, and the effects of clutter.
Standard Macrocell model 2 has the following benefits compared to Standard Macrocell model 1:
 It handles clutter effects differently by using a through-clutter loss effect
 It is faster
Standard Macrocell model 3 has the following benefits compared to Standard Macrocell model 2:
 The interpolation of the horizontal and vertical antenna masking gives a more accurate
representation of the antenna mask
 The quantisation of masking loss for the angle of calculation divides the vertical and
horizontal antenna masks into 0.01 degree increments (36000 discrete angle and gain
values)
 The lookup table of sin and cos values has been replaced with functions to generate the
true values
 It has multiple height capability (see About Multiple Height Pathloss Predictions)
Path Loss Formula for the Macrocell Models
In the Propagation Models dialog box for the Standard or Enhanced Macrocell models, the Path
Loss tab shows the equation for pathloss. The general pathloss formula for the Macrocell models is
as follows:
Path Loss (dB)  k1  k 2 log( d)  k3(Hms )  k 4 log( Hms )  k5 log( Heff )
 k 6 log( Heff ) log( d)  k 7(diffn )  C _ Loss
Where:
d
Distance from the base station to the mobile station (km).
Hms
Height of the mobile station above ground (m). This figure may be
specified either globally or for individual clutter categories.
Heff
Effective base station antenna height (m).
diffn
Diffraction loss calculated using either the Epstein-Peterson, Bullington,
Deygout or Japanese Atlas knife edge techniques.
k1 and k2
Intercept and Slope. These factors correspond to a constant offset (in
dB) and a multiplying factor for the log of the distance between the base
station and mobile.
k3
Mobile Antenna Height Factor. Correction factor used to take into
account the effective mobile antenna height.
k4
Multiplying factor for Hms.
k5
Effective Antenna Height Gain. This is the multiplying factor for the log of
the effective antenna height.
k6
Multiplying factor for log(Heff)log(d).
k7
Multiplying factor for diffraction loss calculation.
C_loss
Clutter specifications taken into account in the calculation process.
The propagation model can be tuned by modifying the k-factors. For improved near and far
performance, dual slope attenuation can be introduced by specifying both near and far values for
k1 & k2 and the crossover point.
361
ASSET User Reference Guide
How Signal Strength is Calculated
For the Macrocell models, the received signal strength is calculated using the following equation:
PRX (dBm)  EiRPTX  LMASK ( ,  )  LP
Where:
PRX is the received power in dBm.
EiRPTX is the maximum Effective Isotropic Radiated Power of the cell in dBm (that is, at the peak
gain point of the antenna).
LMASK ( , )
is the antenna mask loss value for azimuth and elevation angles,  and  respectively,
in the direction of the path being calculated, in dB. When the received signal is directly on the main
beam of the antenna, this value will be zero.
L P is the path loss in dB.
Calculation of EiRP
EiRP = PAPower - cellEquipmentLoss - feederLoss + antennaG + antennaCorrectionFactor +
cellCorrection
where:
feederLoss = (feederLength * feederLossPerMetre) + feederConnectionLoss
antennaG = antennaGain (+ 2.14 if the gain is in dBd)
About Through-Loss for Clutter
Some of the supplied propagation models can be set up to use through-clutter loss and throughloss distance.
For these model types, on the Clutter tab of the Propagation Models dialog box, each clutter
category may be given an associated through-clutter loss (dB/km). The total through-clutter loss for
a prediction point is calculated by examining the clutter lying between the mobile station and the
base station.
d
A through-loss distance (referred to as through ) must also be set. Only points lying within this
distance from the mobile station contribute to the total through-clutter loss.
362
Using Propagation Models
This diagram shows an example:
Diagram showing through-loss distance
When calculating the total through-clutter loss, the individual through-clutter losses are weighted so
that the clutter nearest the mobile station has the highest effect. The weighting is linear with a
maximum weight of 1 (at the mobile station) and a minimum weight of zero (for clutter at distances
>=
d through
).
The formula is as follows:

d 

Weight  max  0, 1 
d through 

Where:
d
is the distance of the clutter pixel (resolution-dependent) from the mobile station.
d through
is the through-loss distance.
The formula ensures that when
d
is greater than
d through
, the weight always becomes zero.
d through
In the case where the distance between the mobile and base station is less than
clutter lying between the mobile station and the base station is taken into account.
, only the
About the DHM Model
The DHM model is fundamentally the same as the Standard Macrocell model 3, but with the
following distinct characteristic:
363
ASSET User Reference Guide
On the diffraction options for the model, you can also activate the parameter that considers
building height rasters (digital height maps) in the diffraction calculation:
It is therefore advantageous to use this model where you have map data that includes a building
height raster layer, so that the diffraction calculation will use this information in all pixels where this
data is available.
In the model parameters, you can optionally define clutter heights which are added to the terrain
height to incorporate them into the diffraction calculations. If this is the case, the diffraction
calculation will only use the clutter height data in pixels where building height raster data is not
available (clutter heights are described in Configuring a Standard Macrocell Model on page 372).
For information on how to add a DHM model, see Configuring a DHM Model on page 374.
About the Enhanced Macrocell Model
The Enhanced Macrocell model, like the Standard Macrocell models, incorporates an optimal dual
slope loss model with respect to distance from the base station. It also incorporates algorithms for
effective base station heights, diffraction loss, and the effects of clutter.
It also has multiple height capability (see About Multiple Height Pathloss Predictions).
The Enhanced Macrocell model has the following distinct advantages compared to the Standard
Macrocell models:
 On the pathloss calculation parameters for the model, you can specify the slope and
intercept model parameters (k1 and k2) independently for LOS and NLOS. The appropriate
parameters are used dynamically during propagation calculations by identifying where there
is LOS and NLOS.
 This model is able to produce LOS/NLOS information for each predicted location. In the
case of LTE networks, this can provide improved MIMO modelling when you use the
Simulator, by enabling you to deactivate MIMO in areas that have LOS to the serving cell.
(MIMO schemes rely on a low correlation between the signal paths to the transmit elements
of an antenna; locations that have LOS to an antenna are more likely to have a high
correlation.) You can also generate a 'Line Of Sight' array.
 On the effective antenna height for the model, an extra Knife-Edge based option is
available for selection.
 On the diffraction options for the model, you can also specify a maximum number of knifeedges to consider, and an extra option (Giovaneli) is available for selection.
 It is advantageous to use this model in environments containing hilly terrain.
 The model tuning process for this particular model has been improved, and is more userfriendly.
For the above reasons, it is generally recommended that you use the Enhanced Macrocell model
rather than the Standard Macrocell models.
Note: For the purposes of this model only, the definitions of LOS and NLOS are as follows:
 A point is considered to be LOS if there are no obstructions in the direct path between the
transmitter and receiver. However, it is still possible to have some diffraction loss if any
terrain falls within the first Fresnel zone of the transmitted ray
 A point is considered to be NLOS if it suffers any diffraction loss, that is, one or more points
along the transmit/receive path are inside the first Fresnel zone
364
Using Propagation Models
For information on how to add this model type, see Configuring an Enhanced Macrocell Model on
page 375.
About the Free Space Loss Model
The Free Space Loss propagation model - if no other parameters are set - simulates the signal
strength loss across a line-of-sight path in which the transmit and receive antennas operate in an
otherwise empty environment, unaffected by the earth surface reflections or other atmospheric
influences. Antenna gain is important to the model, because it has a significant impact on the
transmitted/received power.
Note: The Free Space Loss model is only available in ASSET Backhaul, where it can be useful
when planning the backhaul connections for Small Cells.
In the model parameters, you can optionally define settings for clutter heights, building vectors,
diffraction loss, reflection loss and so on. See Configuring a Free Space Loss Model on page 377.
About the MYRIAD Model
The MYRIAD Model is a sophisticated and versatile propagation model. It is the successful result of
several years of research in such domains as propagation, modelling, optimisation and algorithms.
This model is able to automatically adapt itself to:
 All cell sizes (micro, mini, small, and macro cells)
 All radio environments (dense urban, urban, suburban, mountainous, maritime, open)
 All systems (DVB-H, GSM, (E)GPRS, TETRA, UMTS, Wi-Fi, LTE, 5G, NB-IoT)
 A wide range of frequencies, from 400MHz to 5GHz
The model relies on highly realistic modelling of the propagation channel, and therefore achieves
synergy of the three vital physical elements:
 Diffraction in the vertical plane
 Guided propagation in the horizontal plane
 Reflections from hilly or mountainous terrain
In addition, this model can produce LOS/NLOS information for each predicted location.
For information on how to use this model, refer to the MYRIAD Help or MYRIAD User Reference
Guide.
Important: In ASSET, for the MYRIAD model, the Electrical Downtilt, Azimuth Offset and
Beamwidth values on the Mask tab of the antenna pattern in the Cellular Antennas dialog box do
not influence the propagation predictions. Instead, the model reads these values directly from the
antenna mask file.
Note: MYRIAD is a separately licensed TEOCO propagation model.
365
ASSET User Reference Guide
About the Volcano Models
Volcano comprises state-of-the-art, high-performance and multi-platform propagation models, used
by operators for many years to design their networks.
Compliant with all environments and topologies, from rural dominant to dense urban small cell sites
and fully 5G compatible, Volcano is the ideal propagation model to be used for large scale and
nationwide operational network design and optimization.
Volcano efficiently addresses mmW propagation simulations, leveraging High Definition GIS data
thanks to industry-leading 3D ray-tracing capabilities. Volcano models are suitable for any
environment or technology being therefore ideal for the advanced design and optimization of
telecommunications networks. In addition, the comprehensive outputs and advanced analysis
capabilities (such as accurate massive MIMO and beamforming calculation capabilities) help to
improve network design quality for new wireless technologies such as 5G mmW.
Volcano software could either be installed during the installation of ASSET or from standalone setup programs. Licences to use the Volcano models should be requested from TEOCO (in the same
way as all other licences for the ASSET tools).
All Volcano models are fully integrated with ASSET suite. Volcano propagation models can be
accessed in the same way as other models, using the Propagation Models dialog box.
For information on how to use these models, refer to the Volcano User Guide.
Key features summary:
Model
Brief Description
Recommended Usage
Mapping Data Needed
Volcano
Rural
Suitable for transmitters
located whether in rural or
suburban environments.
Specifically adapted for
dominant sites, with
antennas located above
surrounding building
rooftops, typically in rural
environments.
ASSET map data files:
A deterministic propagation
model based on 'multiple
knife-edge' diffraction.
Volcano
Urban
Suitable for any transmitters
located whether in denseurban urban or suburban
environments.
A deterministic propagation
model based on 'over
rooftop' diffraction and on
'multipath component
modelling', that is, 2D or 3D
ray-tracing.
Depending upon the site
configuration, ray-tracing
options can be activated,
which permits users to
benefit from a full multipaths calculation or a smart
time optimized one.
Specifically adapted for
urban environment in the
presence of a dense small
cell distribution.

DTM/Heights/Altitude

Clutter data
Optionally:

Clutter heights in raster
and/or vector format

Building outlines in vector
format
ASSET map data files:

DTM/Heights/Altitude

Clutter data

Clutter heights in raster
and/or vector format (optional
but recommended in urban
environments)

Building outlines in vector
format for ray-tracing
Optionally:

Volcano
Maestro
366
Maestro is an adaptive
“smart” model manager
which automatically selects
the best propagation model
to be applied to the
environment and frequency
under study.
Point cloud LiDAR data
Coherent and high
Same as for the Volcano Rural
precision nationwide
and Volcano Urban models.
planning and management.
Volcano models are separately
licensed.
For full information on the Volcano
models, refer to the Volcano User
Guide.
Using Propagation Models
Important: In ASSET, for the Volcano models, the Electrical Downtilt, Azimuth Offset and
Beamwidth values on the Mask tab of the antenna pattern in the Cellular Antennas dialog box do
not influence the propagation predictions. Instead, these models read these values directly from the
antenna mask file.
Key benefits:
Operational Configurations: With more than 20 years in the market and cutting-edge technical
developments, Volcano is a mature, robust and well-proven tool dedicated for large scale
nationwide operational design and optimization projects.
3D network performance analysis: Volcano capabilities could be employed for several
applications, including Fixed Wireless Access network design, counting on 3D coverage analysis,
with a fully scalable approach to assess performance levels for a specific height or a specific side of
a building/window (see illustration below).
3D coverage map in New York City, with Volcano predictions
GIS modelling management: Depending on the level of detail in the GIS data, the application, and
the frequency (for both Sub-6GHz and mmW frequency bands), Volcano can manage standard low
and high resolution data (e.g. 3D City high accuracy buildings and accurate foliage modelling), as
well as point cloud LiDAR data.
Massive MIMO (MaMIMO) analysis capabilities: As a key issue for precise network planning,
Volcano is capable of simulating antenna behaviour with MIMO arrays larger than 64 elements.
Indoor Calculation Method: Volcano models use a specific deterministic calculation method to
estimate the signal level incoming or inside buildings providing accurate predictions for indoor multifloor receivers.
367
ASSET User Reference Guide
Reception Above Clutter: In addition to regular reference for receiver height above the ground,
Volcano models could consider a receiver as being above clutter (such as buildings). This feature
may be especially suited for FWA applications.
Received power distribution above clutter
Clutter optimization: For an accurate mmW analysis, an optimization in propagation through
clutter has been set.
About the Volcano Rural Model
Volcano Rural is dedicated to predictions in rural and suburban environments based on 2D lowresolution geographical data maps (for example, a raster resolution greater than or equal to 20m).
Volcano Rural is suitable for radio predictions related to dominant sites, whether located in rural or
suburban environments. In this case, a "dominant site" can be understood as a radio site with
transmitting antennas predominantly located well above the surrounding environment (such as
building rooftops, vegetation).
Coverage example with the operational Volcano Rural Model (London UK)
368
Using Propagation Models
About the Volcano Urban Model
Volcano Urban is dedicated to predictions in dense urban, urban and suburban environments
based on 2D low-resolution (that is, a raster resolution greater than or equal to 20m) or 3D highresolution geographical data maps (that is, a raster resolution less than or equal to 10m and/or 3D
vector representation).
Volcano Urban is suitable for radio predictions related to micro-cellular or mini-cellular sites in
urban environments. A "mini-cellular site" is here understood as a radio site with antennas above
rooftops or against building facade at a lower position than some surrounding buildings. A "microcellular site" is here understood as a radio site with antennas placed in open areas at small height,
that is, below rooftops.
Depending on the site configuration, the Volcano Urban model takes advantage of direct path and
multiple path contributions (the multiple path component option can be activated in the user
interface).
Volcano Ray Tracing Principle
Leveraged by massive MIMO (MaMIMO), propagation through clutter optimization and small cells
analysis, Volcano offers unique 5G network planning capabilities.
About Maestro
Maestro is an adaptive “smart” model manager which automatically selects the right propagation
model to be applied to the environment, frequency and site topology under study. Maestro is a
major asset for managing large national networks, as it improves the accuracy, reduces time and
reduces risks.
Principal key benefits of Maestro:
 Model selection based on environment, frequency and topology – provides higher accuracy
 Automatic assignment – reduces time compared to manual assignment
 Automatic assignment – reduces risks of assigning the wrong model
369
ASSET User Reference Guide
About the SUI Model
The SUI (Stanford University Interim) propagation model is one of the recommended models for
use in analysing fixed wireless broadband communication networks at frequencies below 11GHz.
ASSET enables you to set up propagation models based on the SUI standard. For information on
this, see Configuring a SUI Model on page 377.
Note: The SUI model (IEEE 802.16 SUI Model V1) does not support point predictions.
Path Loss Formula for the SUI Model
The SUI model is an empirical model governed by the basic path loss equation as follows:
For
:
Where
For
d
is the distance in metres
d0
= 100 metres
s
is the shadow fading factor with a normal distribution
the following equation is applicable:
Path Loss Formulae adjusted for Diffraction and Clutter Loss
The SUI model can also account for diffraction loss and clutter loss. Therefore the above equations
can be modified as follows:
For
370
:
Using Propagation Models
For
:
Where
Ld
is the Diffraction Loss Scale Factor.
About the SLR Model
In line with the suggestions of the DVB-H standard, the SLR (Standard Long-Range) model in
ASSET is partly based on the ITU-R P1546-2 recommendation for the purpose of calculating the
received signal strength of the DVB-H signal. The model is not an exact match of the ITU
recommendation, but it has sufficient capabilities to be used for DVB-H planning or for other
applications that require long-range calculations (1-1000km).
This table describes the differences between ASSET and the ITU-R P1546-2 recommendation:
Item
ITU-R P1546-2
ASSET
Frequency range supported
30-3000MHz
100-2000MHz
Time Variability supported
1%, 10% and 50%
50%
Propagation paths supported
Land, Sea and Mixed
Land
Adjustments for different climatic regions
Yes
No
For information on how to add a SLR model, see Configuring an SLR Model on page 379.
For extra information, see 'Using ASSET with DVB-H' in the ASSET Radio User Reference Guide.
Adding and Editing Propagation Models
ASSET enables you to add, edit or view propagation models.
To add a propagation model:
1. If you are using ASSET Radio, from the Configuration menu, click Propagation Models.
- or If you are using ASSET Backhaul, from the Arrays menu, click Propagation Models.
2. In the dialog box that appears, click the Add button.
Tip: If you want to use an existing model as a template for a new model, rather than
creating a completely new one, select the required model and then click Duplicate. You
should then follow the instructions in the following sections to modify the model as
required.
3. Choose the required model type, and click the Add button.
4. Specify a name for the model, and any required comments.
5. If you want the prediction system to perform bilinear smoothing on the height data when
predictions are created, select the 'Smooth height data when predicting' checkbox. This is
useful if you sometimes predict at a resolution for which height data is not available (for
example, you may be predicting at 25m resolution, with available height data of 10m, 20m
and 50m).
371
ASSET User Reference Guide
6. If you use Distributed Predictions, you may want to specify a 'Bytes Per Pixel' value. This
value can be used when estimating the prediction memory usage, and can help to distribute
predictions more evenly to agents which have enough spare resources, and therefore
achieve more overall efficiency.
When the Distributed Task Coordinator distributes prediction tasks, it can potentially
distribute them to any agent machine, regardless of memory or resources to perform those
tasks. Therefore, in an attempt to distribute predictions more evenly to agents which have
spare resources, the coordinator needs an estimate of the memory for the predictions,
based on the number of pixels and the bytes per pixel for the prediction model.
If you use distributed predictions, we recommend a sensible starting value of ‘7’, but you
can set the value as required to suit your requirements.
If you do not use distributed predictions, you can just leave the value as ‘0’.
Note: The setting is a temporary workaround. It is planned that in a future release, the
memory usage will be derived automatically, and the manual setting on the propagation
model dialog box will be removed.
7. Click the View/Edit Model Parameters button.
Configure your model as required; instructions for each type of model are described in the
following sections.
To edit a propagation model:
1. If you are using ASSET Radio, from the Configuration menu, click Propagation Models.
- or If you are using ASSET Backhaul, from the Arrays menu, click Propagation Models.
2. Select the appropriate propagation model and click the View/Edit Model Parameters
button.
3. Follow the instructions in the following sections to modify the model as required.
Project Defaults
In order to make a project easy to use right from the start, the following default objects, with pre-set
parameters, are provided each time a new project is created in ASSET:
 Antenna default
 Propagation model defaults (450, 900, 1800 and 2100 MHz)
 MU-Node Template defaults (with sites/nodes and cells for each single technology and for
some multiple technology combinations)
 Terminal type default (for each technology)
These default objects represent the minimum parameters required to create sites/nodes and
generate coverage arrays.
Configuring a Standard Macrocell Model
To configure a Standard Macrocell Propagation Model:
1. Complete the initial steps as described in Adding and Editing Propagation Models on page
371.
2. On the General tab, you can specify the frequency, mobile receive height, effective earth
radius and standard deviation of interference.
372
Using Propagation Models
Optionally, if the model type is Standard Macrocell 3, you can set up values for multiple
height pathloss predictions. See About Multiple Height Pathloss Predictions (this includes a
section on how to specify the additional heights).
3. On the Path Loss tab, set the various model parameters, sometimes referred to as the kvalues. For suggested values, see Recommended Starting Parameters for the Standard
Macrocell Models on page 374.
4. On the Eff Ant Height tab, choose the effective site antenna height calculation method to
be used.
For more information, see the ASSET Technical Reference Guide.
5. On the Diffraction tab, choose the diffraction loss calculation method to be used.
For more information, see the ASSET Technical Reference Guide.
6. On the Clutter tab, you can specify clutter-based correction values to the pathloss
calculation.
Important: Although it is possible to use any or all of the Clutter tab options, we generally
recommend that you only use the Offset-loss values.
You can:
o
Specify Offset-loss correction values. To do this, click each required category and edit
the value, using the 'Offset-loss' edit box.
Offset-loss considers the clutter in which the mobile station is located. Values can be
positive or negative, but should always be considered as 'fine tuning' of the main kvalues of the pathloss formula. The fundamental focus should always be on the main
k-values.
o
Optionally, specify a Through-loss (dB/km) correction value for each clutter type. To do
this, click each required category and edit the value, using the 'Through Loss' edit box.
You also need to specify a generic Through Loss Distance, under the Clutter Options.
Through-loss considers all clutter on the path between the mobile station and the base
station (see About Through-Loss for Clutter on page 362). Values can be positive or
negative, but should always be considered as 'fine tuning' of the main k-values of the
pathloss formula. The fundamental focus should always be on the main k-values.
o
Optionally, add clutter heights to the terrain height to incorporate them into the
obstruction loss calculations, by specifying a height and a separation for each clutter
category. The separation value models the reduction in the diffraction effect at the
mobile, by separating the mobile from the surrounding clutter, in order to prevent the
mobile from being swamped by high diffraction losses. Clutter lying within this distance
from the mobile is considered as having a clutter height of zero. The clutter height is
added to the terrain height along the profile except for the specified separation
distance at the start and end of the profile. To activate these added heights in the
model, you need to select the Use Clutter Heights checkbox.
Note: Using clutter heights and separations will slow down the model. You do not need
to use them if you can tune your model satisfactorily.
7. Click OK.
8. Apply and Commit your changes as required, then click Close.
373
ASSET User Reference Guide
Recommended Starting Parameters for the Standard Macrocell Models
These tables provide suggested default parameters for the Standard Macrocell models. These
values need to be entered in the Propagation Models dialog box.
Important: These values only represent typical starting values based on an urban environment,
and they may not be suitable for all types of map data. For your live projects, you must tune
(calibrate) the pathloss values in accordance with the real environment.
Common Parameters
Mobile Rx Height
1.5
Earth Radius
8493
Effective Antenna Height (Heff)algorithm
Relative
Diffraction Loss algorithm
Epstein Peterson
Merge knife-edges closer than: 0.00
Clutter parameters
Leave unaltered (0.00)
K values
450 MHz
900 MHz
1800 MHz
2000 MHz
2500 MHz
3500 MHz
k1
142.3
150.6
160.9
162.5
164.1
167
k2
44.9
44.9
44.9
44.9
44.9
44.9
k1 (near)
129.00
0.00
0.00
0.00
0.00
0.00
k2 (near)
31.00
0.00
0.00
0.00
0.00
0.00
d<
0.00
0.00
0.00
0.00
0.00
0.00
k3
-2.22
-2.55
-2.88
-2.93
-3.04
-3.20
k4
-0.8
0.00
0.00
0.00
0.00
0.00
k5
-11.70
-13.82
-13.82
-13.82
-13.82
-13.82
k6
-4.30
-6.55
-6.55
-6.55
-6.55
-6.55
k7
0.4
0.7
0.8
0.8
0.8
0.8
If you are using frequencies that are not in the above tables, you can deduce the starting values
from those of the nearest frequency.
Configuring a DHM Model
The process to add or edit a DHM model is almost exactly the same as for a Standard Macrocell
Model, with the one difference that on the Diffraction tab you can activate the parameter to include
building height rasters (digital height maps) in the diffraction calculation:
Building Height Raster parameter on Diffraction tab of DHM model
374
Using Propagation Models
Configuring an Enhanced Macrocell Model
To configure an Enhanced Macrocell Propagation Model:
1. Complete the initial steps as described in Adding and Editing Propagation Models on page
371.
2. On the General tab, you can specify the frequency, mobile receive height, effective earth
radius and standard deviation of interference.
Optionally, you can also set up values for multiple height pathloss predictions. See About
Multiple Height Pathloss Predictions (this includes a section on how to specify the
additional heights).
3. On the Path Loss tab, set the various model parameters, sometimes referred to as the kvalues. For suggested values, see Recommended Starting Parameters for the Enhanced
Macrocell Model on page 376.
4. On the Eff Ant Height tab, choose the effective site antenna height calculation method to
be used.
For more information on the available methods, see the ASSET Technical Reference
Guide.
5. On the Diffraction tab, choose the diffraction loss calculation method to be used.
For more information on the available methods, see the ASSET Technical Reference
Guide.
Tip: You can also set the knife-edge parameters.
6. On the Clutter tab, you can specify clutter-based 'Correction' values to the pathloss
calculation. To do this, click and edit the required values for each clutter category.
The values can be positive or negative, but should always be considered as 'fine tuning' of
the main k-values of the pathloss formula. The fundamental focus should always be on the
main k-values.
If required, you can specify a generic 'Correction Distance', which limits how far from the
mobile station the correction values are applicable. The total clutter loss for a prediction
point is calculated by examining the clutter lying between the mobile station and the base
station. Only points lying within the specified distance from the mobile station contribute to
the total clutter loss. You can choose either:
o
Distance Weighting: When calculating the total clutter loss, the individual clutter losses
are weighted in a similar way to through-loss in other models. For more information,
see About Through-Loss for Clutter on page 362.
o
Uniform Weighting: When calculating the total clutter loss, the individual clutter losses
are equally weighted.
Important: We generally recommend that you leave the Correction Distance at 0.00, so
that the correction value is only considered based on the clutter at the pixel location of the
mobile station.
7. Click OK.
8. Apply and Commit your changes as required, then click Close.
375
ASSET User Reference Guide
Recommended Starting Parameters for the Enhanced Macrocell Model
These tables provide suggested default parameters for the Enhanced Macrocell model. These
values need to be entered in the Propagation Models dialog box.
Important: These values only represent typical starting values based on an urban environment,
and they may not be suitable for all types of map data. For your live projects, you must tune
(calibrate) the pathloss values in accordance with the real environment.
Common Parameters
Mobile Rx Height
1.5
Earth Radius
8493
Effective Antenna Height (Heff)algorithm
Relative
Diffraction Loss algorithm
Giovaneli
Merge knife-edges closer than: 0.00
Maximum number of knife-edges: 10
Clutter parameters
Leave unaltered (0.00)
K values
450 MHz
900 MHz
1800 MHz
2000 MHz
2500 MHz
3500 MHz
k1 for LOS
142.3
150.6
160.9
162.5
164.1
167
k2 for LOS
44.9
44.9
44.9
44.9
44.9
44.9
k1 (near) for LOS
129.00
0.00
0.00
0.00
0.00
0.00
k2 (near) for LOS
31.00
0.00
0.00
0.00
0.00
0.00
d < for LOS
0.00
0.00
0.00
0.00
0.00
0.00
k1 for NLOS
142.3
150.6
160.9
162.5
164.1
167
k2 for NLOS
44.9
44.9
44.9
44.9
44.9
44.9
k1 (near) for NLOS 129.00
0.00
0.00
0.00
0.00
0.00
k2 (near) for NLOS 31.00
0.00
0.00
0.00
0.00
0.00
d < for NLOS
0.00
0.00
0.00
0.00
0.00
0.00
k3
-2.22
-2.55
-2.88
-2.93
-3.04
-3.20
k4
-0.8
0.00
0.00
0.00
0.00
0.00
k5
-11.70
-13.82
-13.82
-13.82
-13.82
-13.82
k6
-4.30
-6.55
-6.55
-6.55
-6.55
-6.55
k7
0.4
0.7
0.8
0.8
0.8
0.8
If you are using frequencies that are not in the above tables, you can deduce the starting values
from those of the nearest frequency.
376
Using Propagation Models
Configuring a Free Space Loss Model
The Free Space Loss model can be used to simulate the signal strength loss across a line-of-sight
path in which the transmit and receive antennas operate in an otherwise empty environment.
Note: A Free Space Loss model is supplied and used by default:
 The Free Space Loss model is only available in ASSET Backhaul.
 If you have upgraded from a version earlier than 9.1, then this model will be assigned to
your upgraded links.
 When you create a new link, this model is automatically assigned to it.
To configure a Free Space Loss model:
1. Complete the initial steps as described in Adding and Editing Propagation Models on page
371.
2. On the General tab:
o
Set the mobile receiver height (in m).
o
Select the type of heights that you want to use - clutter, building vector and/or building
raster.
o
Select the diffraction loss calculation method that will be used with the model.
For more information on the methods, see the ASSET Technical Reference Guide.
o
If you also want to calculate reflection loss, select the checkbox and then choose which
method you want to use.
Note: If you do not specify a calculation method, no reflection loss will be calculated in
the Link Budget.
3. If you have chosen to use clutter heights, on the Clutter tab, specify the values for the
different clutter categories by:
o
Double-clicking the current value
o
Typing the required value
4. If you have chosen to use building vector heights, on the Building Vectors tab, select the
building vectors that you want to use.
5. Click OK.
Configuring a SUI Model
Note: The SUI model is designed for use in analysing fixed wireless broadband communication
networks at frequencies below 11GHz. See About the SUI Model on page 370.
To configure a SUI propagation model:
1. Complete the initial steps as described in Adding and Editing Propagation Models on page
371.
2. On the General tab, set up the general parameters, including the frequency and effective
earth radius.
377
ASSET User Reference Guide
Important: The Mobile Rx Height and Std. Deviation of Interference values are not used in
the calculation. However, on the SUI tab (see next step) there is a value you must specify
for CPE Height, which is used in the calculation.
3. On the SUI tab, set the various model parameters. See Default Starting Parameters for the
SUI Model on page 378.
4. On the Diffraction tab, if you have set a non-zero value for
calculation method to be used.
d 0 , choose the diffraction loss
For more information on the available methods, see the ASSET Technical Reference
Guide.
5. On the Clutter tab, you can select a category, then in the Clutter Info pane you can:
o
Edit the Offset Loss value to allow for different loss characteristics in different clutter
environments.
o
Enter a through-loss for each clutter type, as well as a generic value for through-loss
distance. For information on how these values are used, see About Through-Loss for
Clutter on page 362.
o
Add clutter heights to the terrain height to incorporate them into the obstruction loss
calculations.
Important: Using clutter heights and separations will slow down the model. You do not
need to use them if you can tune your model satisfactorily. If you use clutter heights, for
each clutter category, you must specify a separation to reduce the diffraction effect at the
CPE. The clutter separation distance is used to separate the CPE from the surrounding
clutter in order to prevent the CPE from being swamped by high diffraction losses. Clutter
lying within this distance from the CPE is considered as having a clutter height of zero. The
clutter height is added to the terrain height along the profile except for the specified
separation distance at the start and end of the profile.
Note: When you create pathloss predictions, the above three options are activated only if
you select the appropriate checkboxes in the Clutter Options pane. You can select or
deselect these options at any time.
6. Click OK.
7. Apply and Commit your changes as required, then click Close.
Default Starting Parameters for the SUI Model
This table provides details of the default Terrain Type parameters for the SUI model. These values
can be edited on the SUI tab of the Propagation Models dialog box.
Terrain Type
Model constant 'a'
Model constant 'b'
Model constant 'c'
A
4.6
0.0075
12.6
B
4.0
0.0065
17.1
C
3.6
0.005
20
Note: These values only represent typical starting values. They may not be suitable for all types of
map data. For your live projects, you must tune (calibrate) the pathloss values in accordance with
the real environment.
378
Using Propagation Models
In addition, you can set:
 Minimum Distance (
d 0 ). The default is 100m.
X
 Terrain Type (A, B or C). This determines which value for h , and which values for a, b
and c (model constants) will be used in the path loss formula.
 CPE Height (Hm). This is used to calculate the value of
.
 Diffraction Loss Scale factor. The default is 0.00 (zero value means diffraction will not be
used).
For more information on these parameters, see Path Loss Formula for the SUI Model on page 370.
Configuring an SLR Model
The SLR (Standard Long-range) model can be used for DVB-H analysis. For more information, see
About the SLR Model on page 371.
To configure an SLR model:
1. Complete the initial steps as described in Adding and Editing Propagation Models on page
371.
2. On the General tab, set up the general parameters, including the frequency and effective
earth radius.
Note: The Std. Deviation of Interference is not used for DVB-H analysis.
3. On the Clutter tab, you can select a clutter category, and then, using either the edit boxes
or the table columns:
o
Add or edit the Offset values to allow for different loss characteristics in different clutter
environments.
o
Add or edit clutter-specific Heights to incorporate them into the pathloss calculations.
However, using clutter heights will slow down the predictions.
o
Select the appropriate Terrain Type for each type of clutter.
Ensure you select the Use Offsets and/or Use Heights checkboxes if you wish to
activate them in the model.
4. Click OK.
5. Apply and Commit your changes as required, then click Close.
Deleting a Propagation Model
To delete a propagation model:
1. If you are using ASSET Radio, from the Configuration menu, click Propagation Models.
- or If you are using ASSET Backhaul, from the Arrays menu, click Propagation Models.
2. Select the model you want to delete.
3. Click Remove.
If the model is currently assigned to any cells (ASSET Radio) or links (ASSET Backhaul),
you will receive a warning, asking whether you want to proceed. The number of affected
cells/links is displayed in the Message Log.
379
ASSET User Reference Guide
If you proceed, the model assignments for those cells/links will be changed to 'Unknown'.
4. Click Yes to delete the model.
The affected cells/links are displayed in the Message Log.
If you later want to create another propagation model with the same name, you must permanently
delete the propagation model from the Wastebasket.
Note: You cannot delete propagation models if the project has been opened with Partial Load or
Region Load.
About Multiple Height Pathloss Predictions
When performing coverage analysis or running a simulation, the ability to consider a range of
different receiver heights can be useful in various situations. For example, it could be of relevance
to buildings with multiple levels, because the mobile terminals could be at varying heights.
ASSET provides multiple height pathloss prediction capability for the following model types:
Enhanced, Standard Macrocell 3, MYRIAD, Volcano. For more information, see Model Types
Supported by Multiple Height Capability on page 382.
Note: Multiple heights are only applicable to the Coverage Analysis wizards and to the Simulator.
They play no part in any other ASSET Radio functionality such as the Neighbour Planner or Model
Tuning, where only the model's 'main height' is used.
ASSET's pathloss propagation system can produce pathloss predictions for:
 Main Height, as determined by the Mobile Rx Height parameter in the Propagation
Model Parameters dialog box of the individual model. (For Volcano, main height is
determined by the lowest defined height in the model.)
Whether there is only one propagation model involved in the analysis, or multiple models,
only a single array instance is generated, so it does not matter if propagation models are
configured with different main heights.
Here is an example of how an output array appears in the Layer Control Pane when using
this mode:
 All Heights, where additional heights have been configured in the Propagation Model
Parameters dialog box of the individual model. This mode will always include the main
height(s).
The heights you see displayed may be from just one model or from several models (if the
cells in the selected filters involve more than one model in the analysis).
One array instance will be generated for each height in the list. In this respect, main and
additional heights are not differentiated.
When you use this mode, the height values will be appended in the output array names.
Here is an example:
380
Using Propagation Models
 Custom List, where additional heights have been configured in the Propagation Model
Parameters dialog box of the individual model.
You can specify any heights you want, but the arrays generated are only meaningful for the
main height and any additional heights that have been set up in the individual model. For
any requested heights where this is not the case, a blank array will be generated (in this
situation, the message log will alert you accordingly). This flexibility allows you to navigate
in the Map View to areas where different models have been configured for different heights
(for example, urban/rural), without having to keep changing the custom list between runs.
One array instance will be generated for each height in the list.
The custom list is persisted between runs of the coverage analysis wizard.
When you use this mode, the height values will be appended in the output array names.
Here is an example:
Note: When you run the coverage analysis wizard, and choose one of the multiple height modes
(All Heights or Custom List), the output arrays will exclude predictions relating to cells that are
assigned with models that do not support multiple height capability.
If you want to take advantage of the multiple heights capability, you need to specify the additional
heights you require on your propagation model(s).
This picture shows an example of the additional height settings in the Propagation Model
Parameters dialog box:
381
ASSET User Reference Guide
Model Types Supported by Multiple Height Capability
ASSET provides multiple height capability for these model types:
 Enhanced Model
 Standard Macrocell 3 Model
 MYRIAD Model
 Volcano Model
More models may be supported in future releases (please contact Product Support).
The choice of whether to configure multiple heights is on a model by model basis.
Whenever you use a model that is set up for multiple heights to create pathloss predictions, the
predictions at all requested heights are automatically created.
All components of the ASSET prediction system have been upgraded to support multiple heights.
This includes components such as Distributed Tasks Coordinator and Agents, File Management
and Caching system for predictions, the Prediction SDK and Prediction Access Module.
In addition, ARRAYWIZARD analysis and prediction agents support multiple height propagation
models (for coverage only). For more information, see the ARRAYWIZARD User Reference Guide.
Note: In the case of the Enhanced Model and Standard Macrocell 3 Model:
 We do not recommend specifying receiver heights above 10m
 The multi heights capability does not restrict its results to ‘indoor’ pixels
These notes only apply to the above two models. For the other models, please consult the
appropriate user guide.
Specifying Additional Heights on the Propagation Model
These instructions are supplementary to the main instructions for configuring the model (see
Adding and Editing Propagation Models on page 371).
Note: These instructions primarily relate to the Enhanced Model and Standard Macrocell 3 Model.
If you want to specify additional heights for a MYRIAD Model or VOLCANO Model, please consult
the model-specific user guide.
To specify additional heights on the propagation model:
1. In ASSET Radio, from the Configuration menu, click Propagation Models.
2. In the dialog box that appears, select the appropriate model.
3. Click the View/Edit Model Parameters button.
4. On the General tab, enable the 'Calculate additional pathloss values' checkbox.
Note: The specified heights will be in addition to the main height (Mobile Rx Height)
already specified on the model.
382
Using Propagation Models
To specify the additional height values, you can:
o
Add a specific height and then click Add.
o
Add an evenly separated range by setting a number of heights and a separation value.
The separation value will be the first value, unless you select the 'Start from' checkbox
and specify it. When finished, click Add range.
You can also:
o
Remove a height from the list by selecting it and clicking Remove.
o
Remove all heights from the list by clicking Clear list.
Here is an example of this part of the General tab:
Note: The additional heights will not be considered for pathloss predictions unless the
checkbox is selected.
5. When you have specified the heights you require, click OK.
6. In the Propagation Models dialog box, click Apply to save the configuration.
About the Receiver Heights Mode in the Coverage Analysis Wizard
When you run a coverage analysis, you can choose which receiver heights mode you require,
enabling you to activate the multiple height capability only when you want to.
When the coverage analysis wizard is run, the cells included in the filter selection are checked for
their propagation model assignments, and the resulting arrays are generated according to your
chosen method.
Note: When you choose one of the multiple height modes (All Heights or Custom List), the output
arrays will exclude predictions relating to cells that are assigned with models that do not support
multiple height capability.
For full information on using the receiver heights mode in the Coverage Analysis Wizard, see the
appropriate technology-specific section in the ASSET Radio User Reference Guide:
 Creating Signal Coverage Arrays (GSM)
 Creating Signal Coverage Arrays (UMTS)
 Creating Signal Coverage Arrays (LTE)
 Creating Signal Coverage Arrays (5G)
 Creating Signal Coverage Arrays (NB-IoT)
(Each of these has its own sub-section with the heading: 'Choosing the Receiver Heights Mode'.)
383
ASSET User Reference Guide
Generating Multiple Height-specific Arrays in a Simulation
When you run a simulation, you may want the output arrays that take account of floor levels in
buildings. You can achieve this if you have Building Vectors as part of your map data,
ASSET enables you to convert a raster that already exists in memory into a 3D version of it. In
simple terms, this feature spreads the values in the original raster over a number of floors of a
building. This means that you can output multiple height-specific array instances when you run the
Simulator.
Note: This feature is only available in ASSET Radio. It is not available in ARRAYWIZARD, because
traffic data cannot be loaded.
When the simulation is run, the cells included in the filter selection are checked for their
propagation model assignments, and the resulting arrays are generated according to the heightspecific predictions that match the additional heights set up in the corresponding propagation
model.
At the end of the simulation, one array instance will be generated for each height derived from the
3D traffic raster. The height values will be appended in the output array instance names.
Here is an example:
For information on how to produce a 3D traffic raster, see 'Converting 2D Traffic to 3D Traffic' in the
ASSET Radio User Reference Guide.
Recommended Mapping Data for Propagation Models
Reliable mapping data plays an essential part in producing an accurate propagation model. This
section suggests what mapping data characteristics are required to produce a sufficiently accurate
model.
These are guidelines and may not be applicable to all situations.
 It is important that the mapping data supplied is as up-to-date as possible so that it reflects
any recent changes in land use. It should be derived from source material less than two
years old.
 To support a certain degree of accuracy in the propagation model, it is recommended that
these map datasets are used:
o
A countrywide dataset for macrocell modelling in rural and semi-rural locations.
o
More detailed datasets for macrocell /microcell / small cell modelling in the larger towns
and cities.
o
High resolution 3D datasets for microcell / small cell modelling in the dense urban
areas.
 Because ASSET can handle mixed resolution mapping, it is recommended that you use the
datasets in combination, that is, you do not need to define a different project for each
mapping data resolution. It is therefore important that the clutter datasets use common
classifications – even if some are not used in the less detailed sets.
384
Using Propagation Models
For information about map data file formats, see the 'Map Data File Formats' chapter of the ASSET
Technical Reference Guide.
Countrywide Dataset Mapping Data
It is recommended that you use a countrywide dataset. It should comprise:
 50m digital terrain model (DTM) layer (Z accuracy of
10m).
 50m clutter type layer – categorised by 10 types typically, the classification will need to be
distinct in terms of propagation loss and traffic. A compromise of the two would be
preferable. Do not have too many types as tuning the model will become problematic.
This mapping data is not essential to propagation models, but is a useful addition:
 Vector information to include at least highways, roads, railways, coastline, rivers and
boundaries and so on
 Text information for the whole to include at least city and town names
 Map backdrops or satellite images
Note: This dataset shows typical values and may not be suitable for every situation.
Urban Datasets Mapping Data
Urban datasets are recommended and should comprise:
 20m digital terrain model (DTM) layer (Z accuracy of
5m).
 20m clutter type layer – categorised with the same codes as the countrywide dataset but
with additional clutter classifications to permit more accurate urban modelling, for example,
open in urban, parks in urban, isolated high rise and so on.
Note: This dataset shows typical values and may not be suitable for every situation.
Tip: If you have many clutter types (for accurate traffic modelling) you should consider grouping
similar propagation types when analysing model performance, to allow valid statistical analysis. The
model tuning may become problematic if too many types are included.
High Resolution Datasets Mapping Data
High-resolution datasets are recommended and should comprise:
 5m DTM raster
1m (above sea level).
 5m building height (DEM) raster (that is, height above ground level).
 5m clutter type raster.
 Building outline polygon layer with polygons having height attributes. Please note that
closed vectors in the dataset must not intersect each other.
Note: This dataset shows typical values and may not be suitable for every situation.
385
ASSET User Reference Guide
386
Working with Data
13 Working with Data
This chapter describes a number of ways that you can work with your ASSET data to, for example,
make the planning process quicker and easier.
Using Nominal and Candidate Properties
In ASSET, a nominal Property is a new Property placed in an approximate location, that you can
use as a way of indicating that you need a site somewhere near this area. Using the search area of
the nominal Property, you define the radius that you consider as suitable for your new Property. In
this search area, you can place a number of other Properties – called candidates - that are possible
alternative locations for the new site.
This picture shows a nominal Property (157) and two candidates (157_A and 184), based on the
search area shown by the black circle:
Using nominal and candidate Properties
Depending on the options you have chosen on the Candidate Options tab of the Preferences
dialog box, you can have candidates automatically take on the same equipment and parameters as
the nominal Property. Options on this tab apply only to search areas created after the Enable
checkbox was selected.
Adding Nominals and Candidates in the Site Database
To add a candidate Property to a Property in the Site Database:
1. On the Candidate Options tab of the Preferences dialog box, ensure that you have
selected the Enable checkbox in the Candidate Functionality pane and defined your
preferred settings.
2. On the Site Database window in the View menu, ensure the Network Display Mode is set
to Location.
3. Right-click the Property to which you want to add a candidate, and from the menu that
appears, point to Add.
4. From the menu that appears point to Add Candidate Property.
387
ASSET User Reference Guide
5. From the menu that appears, select either the default object template or a template you
have created. For more information about templates see Using Templates for Network
Elements on page 222.
The Specify Property dialog box appears.
6. If you want to specify a new candidate Property, enter its identity (if you want to override
the default) and its co-ordinates, and then click OK.
- or If you want to specify an existing Property as a candidate:
a. Click Browse. The Property Chooser dialog box appears.
b. Select any required search criteria, and then click Find.
c. In the list of Properties that appears, select the one that you want to make a candidate.
d. Click OK.
If the Property you chose in the Site Database was not a nominal already, it now becomes
one and the symbol next to it becomes blue to indicate this. The symbol next to the
Property you chose as a candidate turns green to indicate its candidate status.
Next time you open the Site Database, the candidate Property appears underneath the
nominal alphabetically. Depending on the options that you selected in the Preferences
dialog box:
o
The candidate Property may be renamed with a prefix of the nominal’s name
o
BTS equipment from the nominal may be copied to the candidate
o
The candidate Property may be not be able to change location
This table describes the colour coding used to distinguish between different types of Property:
Property Colour
Property Type
Property with unused candidate/nominal status
Black
Nominal Property
Blue
Candidate Property
Green
About the Candidate Options on the Toolbar
The Map View toolbar provides a wide range of buttons enabling you to design your network. This
table describes the buttons relating to the candidate functionality:
This Button
Enables You To
Make a Candidate.
Break a Candidate.
Show Search Area.
Show Candidates.
Set Search Area.
Cancel Search Area.
388
Working with Data
Tip: When you click one of the above buttons, you remain in that mode until you press the Esc key
or click the
button.
Adding Nominals and Candidates in the Map View Window
To place nominal and candidate Properties in the Map View window:
1. On the Candidate Options tab of the Preferences dialog box, ensure that you have
selected the Enable Candidate Functionality checkbox and chosen your preferred
settings. For full details on doing this, see Setting Candidate Options Preferences on page
43. These options will not affect any existing search areas.
2. In the Map View window, add a Property in the approximate location that you are interested
in (or use an existing one).
3. From the toolbar of the Map View, find and click the Set Search Area button
.
4. Click the Property and drag until the search area is of the required size.
This search area now defines the location you are interested in and the Property becomes
a nominal Property, and its symbol is coloured blue
in the Site Database.
The radius you have defined is stored in the Site Database (on the Search Area tab)
where you can change it if required.
The search area appears in the list of data types and is automatically selected so that is
displayed on the map immediately. For information on editing the way that the search area
is displayed, see Changing the Display of the Search Area for a Property on page 391.
It is also retained and refreshed if you move the Property to a new location.
Tips:
o
If you select the wrong Property or site, press Escape to select a different one
o
To resize the search area, click the Property, then click the Site/Property Search Area
button again and draw the search area again
5. Add the sites and equipment that you need for this nominal and set up all the parameters,
such as which model you require and so on.
Tip: If you have selected to do so, on the Candidate Options tab in the Preferences
dialog box, the nominal's equipment and parameters are copied to each candidate you
add.
6. Place new Properties or move any existing ones (as long as they were created with the
checkbox selected as described in step 1) into this search area. Depending upon the
options you have selected, the candidates:
o
Can take on the characteristics of the nominal including the cells, equipment, cell
layers, parameters and so on. BSCs, MSCs and repeaters are not duplicated.
o
Can have the same name as the nominal but appended with a unique letter.
o
Can be moved in or out of the search area.
389
ASSET User Reference Guide
Warning: Any equipment you add to a nominal Property when it already has candidates
will not be copied to those candidates but will be copied to any new candidates that you
add.
This picture shows a nominal with three candidates:
Adding More Candidates to a Nominal
If you have an existing nominal Property, you can expand the search area to include further
Properties. However, you can also mark a Property as a candidate when it is outside the existing
search area. To do this:
1. From the toolbar of the Map View, click the Make Candidate button
.
2. Click the relevant nominal Property then click the Property you want to be a candidate.
– or –
Click the prospective candidate then click the nominal Property.
3. When asked to confirm, click Yes to add this candidate to the selected nominal.
This picture shows that Property157 has an existing search area containing one candidate.
By using the Make Candidate button, Property184 is also being added as a candidate:
390
Working with Data
Hiding Search Areas
When you first create a search area, it is displayed automatically in the list of data types and on the
map. When you have many search areas, you may want to stop some of them displaying on the
map, and possibly in the list of data types too.
To stop displaying search areas on the map:
Clear the checkbox next to the appropriate search area(s):
To stop displaying a search area on the map and also remove it from the list of data types:
Right-click the particular search area and from the menu that appears, click Remove.
To stop displaying all search areas on the map and hide them in the list of data types:
In the list of data types, right-click the Search Area heading and from the menu that
appears, click Remove All.
Showing Search Areas
To show a search area:
1. From the Map View toolbar, find and click the Show Search Area button
(this is on the drop-down for Candidate Options toolbox
).
2. Click the Property/site or Properties/sites whose search area(s) you want to display.
The search areas appear on the map and are listed alphabetically in the Layer Control
Pane of the Map View.
Note: Search areas are automatically refreshed if you move Properties/sites to new
locations.
Changing the Display of the Search Area for a Property
After you have created a search area for a Property, the search area is automatically displayed in
the Map View window.
To change how the search area is displayed:
1. In the Map View, in the Layer Control Pane, click the Data Types tab.
2. In the list of data types, select and expand Search Area, and then double-click the required
Property.
391
ASSET User Reference Guide
3. In the dialog box that appears, enter the required information as shown here, and then click
OK:
On this tab
You can
Style
Select the radius line style, colour, width and transparency.
GIS Export
Select the content type for the GIS Export, and, in the case of Raster image,
the type of output file. For more information, see Exporting Map Layers
using GIS Export on page 435.
Visibility Settings
Select options for changing the visibility of the search area:

Always

View Zoom Range - set the Min. and Max. distances within which it will
be visible. You can base this on Distance (East-West) or Distance
(North-South)

Scale Range - set the Min. and Max. scale ratios within which it will be
visible
Tip: You can show the scale range for the current Map View in the Map
Information Pane. See Viewing Scale Information Relating to the Current
Map View on page 113.
Removing a Search Area
To remove a search area:
1. From the toolbar of the Map View, find and click the Cancel Search Area button
.
2. Select the Property whose search area you want to remove.
3. Click Yes to confirm.
This sets the search area radius to '0' in the Site Database on the Search Area tab for a
Property, and also removes candidate status from any Properties within the search area.
Displaying Candidates and Nominals in the Map View
You can show candidates on the Map View. To do this:
1. From the toolbar of the Map View, find and click the Show Candidates button
2. Click the nominal Property that you are interested in.
392
.
Working with Data
This picture shows the line that is displayed on the Map View from the nominal to the
candidate Property:
For information on how to edit the way that candidate properties are displayed, see
Changing How Candidates are Displayed in the Map View.
Changing How Candidates are Displayed in the Map View
To change how candidate Properties are displayed:
1. Ensure that you have shown candidates on the Map View.
2. In the Map View, in the Layer Control Pane, click the Data Types tab.
3. In the list of data types, select and expand Candidates, and then double-click the required
Property.
4. In the dialog box that appears, enter the required information as shown here, and then click
OK:
On this tab
You can
Style
Select the radius line style, colour, width and transparency.
GIS Export
Select the content type for the GIS Export, and, in the case of Raster image,
the type of output file. For more information, see Exporting Map Layers using
GIS Export on page 435.
Visibility Settings
Select options for changing the visibility of the candidates:

Always

View Zoom Range - set the Min. and Max. distances within which it will
be visible. You can base this on Distance (East-West) or Distance
(North-South)

Scale Range - set the Min. and Max. scale ratios within which it will be
visible
Tip: You can show the scale range for the current Map View in the Map
Information Pane. See Viewing Scale Information Relating to the Current
Map View on page 113.
393
ASSET User Reference Guide
Removing Candidate Status from a Property
To remove candidate status from a Property:
1. From the toolbar of the Map View, find and click the Break Candidates button
.
2. Click the candidate.
3. When prompted, choose whether you want the candidate status to be removed or not.
Note: If you chose the Renaming option on the Candidate Options tab of the Preferences dialog
box, the name of the modified Property will revert to its former name, both in the Site Database and
in a (refreshed) Map View window.
Tip: You can also remove candidate status from a Property by:
 Resizing a search area to exclude a candidate
 Right-clicking the Property whose candidate status you wish to remove
Resizing the Search Area to Exclude the Candidate
To remove candidate status from a Property by resizing the search area:
1. Ensure the search area for the Property is not locked on the Search Area tab in the Site
Database:
2. Resize the search area of the nominal so that the candidate is no longer included in the
search area.
What Happens When Search Areas Overlap?
If you have nominal Properties whose search areas overlap on the map and you place a candidate
site in the common area, you are asked which nominal Property you want the new Property to
belong to.
394
Working with Data
This picture shows an example of an overlap, including nominal selection:
Nominal Sites with Overlapping Search Areas
Viewing and Editing Logical/Cellular Connections
In the Logical/Cellular Connection Database window, you can view and edit details of
logical/cellular connections (or interfaces) that you have created in the project network.
Every connection active in the selected filter is displayed in a list view showing its end points and
the amount of traffic it carries. If the connection has not been committed, it is marked with an
asterisk in the left-hand column. Also, the type of connection is shown in this column.
This picture shows an example of the Logical/Cellular Connection Database window:
Example Logical/Cellular Connection Database Window
395
ASSET User Reference Guide
Notes:
 The network elements will be designated as A and B based on the order in which they are
clicked when creating the logical/cellular connection.
 If the traffic is moving from the element higher in the hierarchy to the lower one (for
example BSC to BTS, or RNC to Node B), then A->B shows the total downlink traffic, and
B->A shows the uplink traffic (with respect to the lower network element).
 If the traffic is moving from the element lower in the hierarchy to the higher one (for
example BTS to BSC, or Node B to RNC), then A->B shows the total uplink traffic, and B>A shows the downlink traffic (with respect to the lower network element).
To open the Logical/Cellular Connection Database window:
1. Ensure that logical/cellular connections exist.
For information on how to do this, see:
o
Adding Logical and Cellular Connections on the Map on page 92
o
Adding Logical and Cellular Connections in the Site Database on page 240
Note: If you have manually created hierarchies in the Site Database, the cellular
connections are created automatically, and are shown in the Logical/Cellular Connections
Database.
2. From the Database menu, click Logical/Cellular Connections.
3. Click Details>> to expand the window. You can view and edit information on the following
tabs:
Tab
Description
General Displays basic information about the selected connection.
On this tab, you can edit the connection name, as well as add a description/comment
for the connection.
Status
Edit the fields that are associated with the selected connection. If you have
administrator permissions, you can define these fields in Administrator. For more
information on using fields, see Using Filters and Fields on page 273.
Routes
Enables you to view and modify the logical/cellular connection routes.
For more information, see Adding Routes and Hops to a Logical/Cellular Connection on
page 397.
On this tab, you can also view the traffic occupancy (%), traffic load (Mbps) and
availability (%) on each hop, as well as the total availability (%) of the entire route.
Occupancy is calculated as:
Occupancy (%) = 100*Routed Traffic/(Total Capacity-Control Overhead)
Admin
Enables you to:

Set permissions for the selected connection

Check to see if any committed changes have been made by other users working on
the same project

Update the connection to include their changes
This is similar to the Admin tab on the Site Database. For more information, see About
the Admin Tab on page 243.
396
Working with Data
4. To generate a logical/cellular connection report:
o
Click the Report button
o
In the Reporting dialog box, select the required report format and where it will be
saved (if applicable)
o
If you have specified a format other than Microsoft Excel, select how the report will be
opened (or specify it will just be saved to file)
o
Click OK
The report is generated.
Adding Routes and Hops to a Logical/Cellular Connection
If you have ASSET Backhaul installed, you can use the Unified Route Planner to route traffic
across the logical/cellular connections that you have created. For more information, see the ASSET
Backhaul User Reference Guide.
However, you can also add routes and hops manually. For each connection, you can define one
primary route and one secondary route.
To do this:
1. In the Logical/Cellular Connection Database window, on the Routes tab, click Add
Route.
A new route is added:
2. To add a hop to a route, select the route you wish to add a hop to and click Add Hop.
3. From the dialog box that appears, select the link that you wish to use and click OK:
4. If the route is still invalid, repeat steps 2 and 3 until no more hops are required.
397
ASSET User Reference Guide
Tips:
o
If you want to remove a hop at any time, select the hop and click Remove Hop.
o
As you add hops to a route, the traffic occupancy traffic load and availability on each
hop are displayed. This information will only be saved if the route is Applied.
- or If a valid route has been created, go to the next step.
5. Click Apply.
The route is saved in the Logical/Cellular Connection Database and added to the
Routes tab for the appropriate network element in the Site Database. This picture shows
an example:
398
Working with Data
Viewing and Editing the Traffic on a Logical/Cellular Connection
In the Logical/Cellular Connection Database window, on the Traffic tab, you can view and edit
details of the traffic routed through the logical/cellular connection (or interface):
Traffic tab in the Logical/Cellular Connection Database
For each logical/cellular connection, the Traffic tab displays the following circuit-switched (CS) and
packet-switched (PS) traffic values for the network elements routed over the connection:
Item
Description
UL Traffic, DL Traffic (Mbps)
Total Uplink and downlink traffic (Mbps), which are taken from the
Carried Traffic tab in the Site Database for the end A and B nodes.
For more information, see the ASSET Radio User Reference Guide.
UL Percentage, DL Percentage (%)
The proportions of uplink and downlink traffic (in %). If required, you
can edit these values, and also specify a % greater than 100, so that
you can 'over-dimension' the traffic on this node.
Note: For cellular connections, one node represents the 'lower'
element and the other represents the 'higher' element; for example,
in GSM networks, the 'higher' element is Node A and the 'lower'
element is Node B. By default, for the 'lower' node, the uplink and
downlink traffic percentages will be 100%, and for the 'higher' node,
the percentages will be 0%.
Logical UL Traffic, Logical DL Traffic Calculated values for the uplink and downlink traffic that is used
(Mbps)
over the logical connection for each end. These are calculated as
follows (for both CS and PS):
Logical UL Traffic = UL Traffic*UL Percentage/100
Logical DL Traffic = DL Traffic*DL Percentage/100
Logical CS Traffic, Logical PS Traffic The total CS and PS traffic values from End A to End B and End B
(Mbps)
to End A. These are calculated as follows:
Logical CS Traffic = Logical UL CS Traffic + Logical DL CS Traffic
Logical PS Traffic = Logical UL PS Traffic + Logical DL PS Traffic
If required, you can set your own values by selecting the Override
checkbox and typing the required values.
Note: If you do this, then you cannot edit the UL and DL
Percentages.
399
ASSET User Reference Guide
Item
Description
Total Logical Traffic (Mbps)
The combined total of CS and PS traffic in both directions (A->B, B>A).
These values are used in the Unified Route Planner, which is
available if you have ASSET Backhaul installed and have the
appropriate licence. For more information, see the ASSET Backhaul
User Reference Guide.
About Using GPS
ASSET is a portable planning tool. You can connect ASSET to a NMEA compatible GPS system
and use site placement to locate your position on the earth. This means that when you are at a new
site, you can obtain your co-ordinates and then choose automatically to:
 Indicate your location on the map
 Move a specified site to the current location
 Create a new site at the current location
Positioning the GPS Receiver
You must position the GPS receiver so that it has an unobstructed view of the sky as it must "see"
at least four satellites in order to get a fix on its position. Therefore, it is recommended that you
place the GPS receiver on the roof of the survey vehicle using a magnetic mount.
Before using the GPS receiver for the first time, you must ensure that the GPS has had enough
time to obtain a fix on its position. The first fix can sometimes take up to 30 minutes because the
GPS needs to store the constellation information for the satellites of its current location.
On subsequent occasions, if the GPS has moved less than 500 km since it last obtained a position
fix, it will produce a fix within a few minutes. Improvements in accuracy can be achieved if you
increase this period of time to about five minutes, as it is more likely that the GPS will have had
time to produce a 3d fix instead of a 2d fix.
Using GPS
To use GPS:
1. Ensure you have connected the GPS system correctly.
2. From the Tools menu, click GPS Interface.
This dialog box appears:
400
Working with Data
3. Choose the correct Com Port and click Connect.
4. In a Map View window, display a map that includes your position and then:
To
Do This
View your current location
From the Data Types list in the Map View window, select the GPS
Interface option and click on the 2D Map View. The position is
automatically shown as a crosshair on the map.
Move a site to the current
position
Click the Move button and move to any location in the box
surrounding the crosshair.
Add a new site (or
distribution node and so on)
Click the Add Site button and place the new site near the crosshair
at the current position.
Setting Default Identifiers
You can set the default identifiers for network elements, so that their IDs are based on a specified
string.
Site Identifier dialog box
401
ASSET User Reference Guide
To set identifiers:
1. From the Database menu, click Identifiers.
2. In the left pane, select the item you require.
3. For Cells, select the option required from those shown. For all other network items, follow
the remaining steps.
4. Specify the base string you want. All future default IDs are based on this.
5. If you want to specify a minimum length for the numeric part of the identity, select the Use
Padding Min Length checkbox and enter a Min Length value. If needed, the network
element number will be prefixed with zeros to the length you have specified.
6. For cell sites and nodes, you can additionally select the Update Cell IDs checkbox if you
want a cell's ID to automatically update if its parent site ID changes.
7. If you want to ensure that a particular naming convention for this network item is followed,
select the Enforce Naming Convention (On Commit) option, and type your required
naming convention string in the Pattern String pane.
Any network item of this type that is given a name that does not conform to the convention
cannot be committed.
The naming convention string uses regular expressions based on the Perl engine - for
more information, see Examples of Searching by Regular Expression on page 109.
Tip: To check whether a particular pattern string is valid:
o
Click the Test button.
o
In the Naming Convention Test dialog box that appears, in the Pattern String pane,
type the string that you want to test.
o
In the Test Name pane, type the name that you want to test against the pattern string.
o
The Result pane indicates whether your name and rule is valid or not. This picture
shows an example:
o
When you have finished testing the pattern, click OK.
8. Click Apply, and then click Close.
402
Working with Data
Converting Files
To convert files:
1. On the Utilities tab, from the Converters menu, click one of the options, which are
described in this table:
This Option
Converts Files
Text Converter
From Planet text map data files to binary format, so they can be read by
ASSET. A backup (*%s) of the original file is created and the original file
replaced with a file in the new format.
Text 2 Bin
From ASSET text files in text format to binary format, for speed. The file
extension is automatically changed from *.txt to *.bin. You should manually
edit the file index.txt to reference the new binary files instead of the old text
files.
Vec 2 Bin
From ASSET vector files (*.txt) to binary format, for speed. The file
extension is automatically changed from *.txt to *.bin. You should manually
edit the file index.txt to reference the new binary files instead of the old text
files.
2. Browse to select the .txt file you want to convert.
3. Click Convert.
The file is converted to the required format.
Editing the Map Data
You can edit terrain height, clutter type and building height.
Warning: Be certain you want to change these features. You can only reverse any changes you
make by laboriously changing each individual point back to its original value. Any changes you
make are saved to the map data directories and will affect all projects that use the same map data.
Editing Terrain Height
To edit terrain height:
1. Ensure you really want to change terrain height because you can only reverse any changes
you make by changing each individual point back to its original value.
2. On the Utilities tab, from the Tools menu, click Height.
403
ASSET User Reference Guide
3. In the Map View window, click the point whose height you want to change, type the new
height and click Apply.
Your changes are saved to the map data directories and will affect all projects that use the
same map data.
Editing Clutter Types
You can change clutter from one type to another:
 For an area of one type of clutter where the area is either linked by orthogonal connections
between blocks only or includes those pixels linked diagonally as well
 For part of an area of clutter within a defined polygon
 For a single location
Warning: Be certain you want to change these features. You can only reverse any changes you
make by laboriously changing each individual point back to its original value. Any changes you
make are saved to the map data directories and will affect all projects that use the same map data.
Editing Clutter for an Area
To change any area of one clutter type to another clutter type:
1. In the Map View window, ensure you have clutter displayed.
2. On the Utilities tab, from the Tools menu, click Clutter.
3. In the Clutter Editor, click Select Area.
4. The 'Area Can Be Connected Diagonally' checkbox allows you to select whether the area
will also include any pixels that are connected diagonally.
The following is an example of how this affects your selection:
For this area of clutter:
404
Working with Data
you could select to include pixels linked diagonally as shown here:
or select not to include them as shown here:
5. In the Map View window, click the area whose clutter type you want to edit.
6. In the Clutter Editor, in the Clutter Types pane, select a different clutter type and click
Apply.
You can also add new clutter types, using the appropriate button.
Note: All clutter types must have a unique name.
Editing Clutter Using Pre-Defined Polygons
If you have pre-defined polygons stored in your Site Database, then you are able to use these to
edit clutter types on the Map View.
To edit clutter using pre-defined polygons:
1. In the Map View window, ensure you have clutter displayed.
2. On the Utilities tab, from the Tools menu, click Clutter.
3. In the Clutter Editor, ensure Select Area is selected.
Choose whether you want the area to include those pixels that are only connected
diagonally, or whether you want to exclude those pixels.
4. In the Polygons pane, select the 'Use pre-defined polygon(s) for selection' option.
5. Select which polygon(s) you want to use.
6. Click Apply Polygons to display these on the map view.
405
ASSET User Reference Guide
7. Click in the polygon. It flashes on the map, and in the Clutter Editor, the current clutter type
is selected in the list. This picture shows an example:
8. Select the new clutter type from the list that will apply to the area within the polygon and
click Apply.
The clutter type within the polygon is changed.
Note: Where the polygon contains different clutter types, you can only select one type at a
time, that is, only one type flashes. For each type, repeat steps 7 to 8 above. You are
changing from one type to another so the clutter boundaries stay the same.
Editing Clutter at a Single Location
To edit clutter for a single point where a clutter type is already defined:
1. On the Utilities tab, from the Tools menu, click Clutter.
2. In the Map View window, click the point whose clutter type you want to edit.
The co-ordinates in the Clutter Editor reflect the point you have selected.
3. In the Clutter Editor, ensure Select Point is selected.
4. Click a different clutter type and click Apply.
You can also add a new category of clutter.
If do not have write permissions to edit clutter, a message appears in the Message Log, and the
changes are not made in the Clutter Editor.
Editing Building Heights
If you have building raster data, you can edit the building height of:
 A single point
 A contiguous area of a range of heights (to a single value)
 A contiguous area of a range of heights within a polygon (to a single value)
A contiguous area is an area either limited to orthogonal connections between pixels or also
including pixels that are only connected diagonally.
406
Working with Data
Warning: Be certain you want to change these features. You can only reverse any changes you
make by laboriously changing each individual point back to its original value. Any changes you
make are saved to the map data directories and will affect all projects that use the same map data.
Editing Building Height at a Single Point
To edit building height for a single point:
1. On the Utilities tab, from the Tools menu, click Building.
The Building Height Editor appears:
2. Ensure Select Point is selected.
3. In the Map View window, click the point whose height you want to edit.
The co-ordinates are displayed in the Building Height Editor.
4. In the Height box, type the new height, and then click Apply.
Editing Building Height for a Contiguous Area
To edit building height for a whole contiguous area on the map:
1. On the Utilities tab, from the Tools menu, click Building.
2. In the Map View window, click the required location.
3. In the Building Height Editor, click Select Area.
4. Select whether or not the area extends over diagonal connections.
5. Using the slide bar, select an amount of deviation – this is the tolerance within which
heights surrounding the selected pixel will be counted as being within the area to be
changed.
If you set a deviation of 2m, clicking a pixel in the Map View will result in that pixel plus any
connecting pixels that have the same height plus or minus 2m being selected.
407
ASSET User Reference Guide
So, if the deviation is 2m, clicking on a square of height 20m will select that plus any
connected pixels with a height of 18m to 22m.
6. In the Height box, type the required height, and then click Apply.
All the selected squares now have the height you entered.
Editing Building Height for Part of a Contiguous Area
To edit building height for part of a contiguous area:
1. On the Utilities tab, from the Tools menu, click Building.
2. Ensure Select Area is selected.
3. Select whether the area extends over diagonal connections or not.
4. Click Select Polygons.
5. In the dialog box that appears, select the required polygon(s) and click OK.
6. Using the slide bar, select an amount of deviation.
If you set a deviation of 5m, clicking a pixel in the Map View will result in that pixel plus any
connecting pixels that have the same height plus or minus 5m being selected.
So, if the deviation is 5m, clicking on a square of height 20m will select that plus any
connected pixels with a height of 15m to 25m.
7. In the Height box, type the required height.
8. Click Apply to change only the building heights that fall within both the polygon and the
contiguous area of heights.
Using Attachments
You can associate extra information with an installation within the ASSET database by using
attachments.
Only a shortcut to the attachment is stored in the database, so if the attachment file is moved or
deleted, the shortcut will not work.
To associate a file with a site:
1. In the Site Database window, navigate to the site that you want to have an attachment.
2. Click the Attachments tab.
3. Click the Add File button
and locate the attachment or using a tool such as Windows
Explorer, drag the file into the attachment area.
A shortcut to the attachment is stored in the database. If the associated file is moved or
deleted, the shortcut will not work.
To view a file associated with a site:
1. In the Site Database window, select the site.
2. Click the Attachments tab.
3. Right-click the attachment shortcut, and from the menu that appears, click Open.
408
Working with Data
Note: If the associated file is moved or deleted, the shortcut in the Attachments pane will no longer
work.
Using Photographs
You can associate photographs with pieces of equipment and with network elements. Photographs
can be stored as bmp, dib, gif, jpg, jpeg, tif, tiff, pcx and tga files. You can associate photographs
with a variety of objects, including cellular and microwave antennas, BTS and cell equipment, radio
equipment, masts, cabins, feeders, Sites and Properties.
Associating a Photograph with Equipment
To view or associate a photograph with a piece of equipment:
1. From the Equipment menu, click the appropriate menu item (such as Cellular Antennas,
Microwave Antennas, Cell Equipment, Radios, Masts).
2. In the Equipment dialog box that appears, select the individual item.
3. On the General tab, click the Photo button. If a photograph is already associated, it is
shown here.
4. To associate a new photograph with a piece of equipment, click Browse and locate the file.
Here is an example of a photograph associated with a mast:
409
ASSET User Reference Guide
Associating a Photograph with a Network Element
To view or associate a photograph relating to a Property:
1. In the Site Database window, select the required Property.
2. On the General tab, click Panoramic. If a photograph is already associated, it is shown
here.
3. To associate a new photograph with the Property, click Browse and locate the file.
To view or associate a photograph relating to a Site:
1. In the Site Database window, select the required Site.
2. On the General tab, click Site. If a photograph is already associated, it is shown here.
3. To associate a new photograph with the Site, click Browse and locate the file.
When a photograph is associated with a Property, you can also view it from any Sites existing on
that Property. To do this:
1. In the Site Database window, select the required Site.
2. On the General tab, click Panoramic. If a photograph is already associated with the
Property, it is displayed.
410
Importing and Exporting
14 Importing and Exporting
Using importing and exporting functions provided by ASSET, you can transfer a variety of different
information, including:
 Data between normally incompatible software packages
 Equipment in to and out of the database
 User settings from one project to another
 Filters from one project to another
ASSET supports a large number of formats, including XML, 3GPP, MapInfo and PlaNet/EET
(various versions).
The following sections describe procedures for importing and exporting:
 Data
 Equipment (including antennas)
 User settings
The data formats that you can use are also described.
Important: Because each software package models data differently, there will always be some
assumptions made when importing and exporting. For example, the concept of cell layers does not
exist in PlaNet. Therefore if you exported from ASSET to this format then created a new database
and imported your data, only a default cell layer would be created, and you will have lost
information compared to the original.
This means that you cannot recreate your original database from exported information. The only
way to back up your database is to do so at database level. For information on this, see your
Oracle database administration documentation.
Importing Data
You can import data from a number of formats, as described in the following sections.
Importing ASSET Data
To import ASSET data:
1. Ensure you are using a blank project, otherwise importing this file will overwrite all your
data.
2. From the File menu, point to Import and click ASSET.
3. Browse for the ASSET file (*.aii) and click Import.
Importing XML Data
You can import XML data to ASSET using the XML Import.
Note: If you are using region loading, you cannot import Config items or create new elements
during the import.
411
ASSET User Reference Guide
Tips:
 If you want to import an XML file containing only the project settings, see Importing Project
Settings on page 30.
 You can automatically save the created/modified objects from an XML import into the
Selection Filter. This can be a useful way of identifying, checking and reviewing the
changes. See Saving the Contents of an Import into the Selection Filter on page 305.
Using the XML Import
To import XML data:
1. Ensure that:
o
You have permissions to import data. Permissions for importing XML and for exporting
committed ASSET data as XML are set up in Administrator. If you do not have
permissions, see your administrator.
o
You are not using region loading, if you want to import Config items or create new
elements during the import.
o
If you are using a file that was exported from a project earlier than version 9.1, and it
included ADVANTAGE or ASSET ACP files, you should manually remove these before
performing the import, as they are no longer supported. There are six *.xml files to
remove: PLAN-LIST001; CLUTTER-PARAM-LIST001; VECTOR-THRESHOLDPARAM-LIST001; COST-FUNCTION-WEIGHTS-LIST001; ACTIONCONSTRAINTS-TEMPLATE-LIST001; OPTIONS-LIST001.
o
The import file contains the required information. For information on the valid format for
each network element, see the ASSET Technical Reference Guide.
Tip: You can modify the files in an editor (for example, ASSET's XML Data Editor)
before importing them, provided that you do not alter the format of the files. For more
information, see Using the XML Data Editor on page 437.
412
Importing and Exporting
2. From the File menu, point to Import and click XML. The XML Import dialog box appears.
This picture shows an example:
3. Click the Browse button
and locate the *.xml file(s) that you want to import.
4. Select the file(s) (holding down CTRL to select multiple files) and click Open. The file and
path will appear in the File Import pane and a list of items available for import will appear
on the appropriate tabs.
5. On each tab, select the items you want to import.
Tip: If you want to import all items select the Select All checkbox on each tab.
6. For each item that you have selected, click the Options button to select a number of
advanced options, including automatic XML schema validation. For more information, see
About the Advanced Options for Importing XML Files on page 414.
7. In the Import Conflicts pane, select how you want conflicts to be handled during import.
You can be prompted on an individual basis, or for all conflicts, you can replace the data in
the project with the imported data, merge the data or leave the existing data as it is.
8. When prompted, click Import to begin importing. During import:
o
If you do not have permission to create or update an object type that you are trying to
import, you are given the choice of stopping importing or ignoring.
o
If the user specified in your import does not exist in your database, the user will default
to the current user.
o
If an imported element's parent does not exist in your database, a dummy parent is
created prior to its import.
413
ASSET User Reference Guide
o
If there were any problems, messages are shown in the message log.
o
When you Replace, the existing information is overwritten with that in the XML import
file. This applies even if there are blanks in the file, for example, neighbours of a cell
are deleted and replaced with the imported blank list, so the cell would then have no
neighbours.
About the Advanced Options for Importing XML Files
If you are importing XML files into ASSET, you can select a number of additional options to
determine the content of the output.
To select the advanced options for an object type:
In the XML Import Dialog Box, click on the name of the required object type and then click
the Options button:
The Options dialog box appears, comprising a set of tabs displaying the import options for that
specific object type only. This table describes the available options:
414
Importing and Exporting
Object Type
Tab
Most object types Validation
Option
Description
Enable XML Schema
Validation
If you select this option, ASSET will check
the XML file against the structure, syntax
and restrictions defined in the XSD file for
the corresponding object type.
This ensures that only correct and reliable
data is imported by ASSET.
For more information, see How ASSET
Validates XML Files on page 415.
If the validation fails for a particular object,
the import for that object will be cancelled
and a message appears in the Message
Log. However, validation will continue for
other objects of that type.
GSM Cells,
Bands/Channels
Replace on
Merge
On Merge Replace Lists
If you are importing GSM cells (ASSET
Radio) or Bands (ASSET Backhaul), and
select to merge the items on import, you can
select this option to replace the child data
lists.
GSM Cell: This option will replace the child
carrier data lists (allocated, forbidden, fixed)
that exist in your database.
Bands: This option will replace the child
channel lists that exist in your database.
Terminal Types
Selective
Import
Ignore Zero Traffic Under
Vectors
If you are importing terminal types that
contain all or many zero traffic values under
their Vectors tab, you can use this option to
speed up your import, by ignoring such
vectors for each terminal type. This is
especially useful when you have lot of vector
data (polygon, line or point) that has no
traffic assigned.
How ASSET Validates XML Files
If you are importing or exporting XML data in ASSET, and you select 'Enable XML Schema
Validation' in the Options dialog box, ASSET will try to verify the XML file against the structure,
syntax and restrictions defined in the XSD file for the corresponding object type.
Tip: You can view the XSD files using an appropriate viewing tool (for example XML Spy). By
default, they are located in the C:\Program Files\TEOCO\ASSET\XML Schemas folder.
During validation, ASSET will check:
Validation Check
Example
Data type (string, decimal, integer, A field with the 'integer' data type cannot have the value 'ABC'.
Boolean, date and time)
Enumerated values (restricted
strings)
A field with only two possible string values ('Planned' or 'Live') cannot
have the value 'Nominal'.
Enumerated values (restricted
integers)
A field with two possible integer values (for example, 0 or 1) cannot
have the value 2.
Length of a string
1 to 127 characters for an element name (for example, the BSC ID).
Decimal point restriction
Most decimal fields in ASSET have a maximum of 6 decimal places.
415
ASSET User Reference Guide
Validation Check
Example
Positive/negative value check
(integers and decimal numbers)
Some fields (for example, signalling overhead, antenna height, azimuth,
feeder length) do not accept negative values.
Pattern checks
Some fields (for example, latitude/longitude data) have a specific
format, using numbers, the degree symbol, and N/S/E/W characters in
a particular order.
The validation has a number of limitations:
 ASSET will not validate the complete XML tree or root (the '-LIST' node - for example,
'MSC-LIST'). Only the individual object nodes (for example, the MSC nodes) within the root
node will be validated.
This means that any outlying attributes (for example, XML-VERSION) will not be validated.
 ASSET validates string lengths according to the number of characters, not the number of
bytes. If you are using a multi-byte character set (for example, Chinese) then the string may
be validated, even though it exceeds the maximum number of bytes supported by ASSET
for that element or attribute.
Therefore you should separately check that any multi-byte character data that appears in
the XML files that you want to import/export is an appropriate length. For more information
on the maximum string lengths for an object type, see the ASSET Database Reference
Guide.
Using the 3GPP Import/Export
You can use the 3GPP XML import/export to import and export UMTS data in a XML file format
compatible with the 3GPP specification. You can use this to synchronise ASSET with a
configuration planning tool, performing configuration management actions such as updating cell
parameters and neighbours and importing the changes back into ASSET.
The 3GPP XML import cannot be used to create new cells and network elements, and you cannot
import 3GPP data to a new (blank) project. You cannot delete network elements except for
neighbour relations.
You can only import and export elements that already exist in an ASSET database and are limited
to a subset of the data required for management of:
 RNC
 UTRAN Cell (including UTRAN and GSM neighbour relations)
Important: In order to export 3GPP data, you need a network hierarchy, that is, PLMN, Logical
Network, RNC, Node.
Importing 3GPP Data
If you have import privileges set up in the ASSET Administrator, you can import and export
committed ASSET data as 3GPP XML files. To import data from 3GPP XML:
1. From the File menu, point to Import and select 3GPP.
2. Enter the name of file you want to import.
–or–
Click the Browse button
416
, locate the required file, and then click OK to select it.
Importing and Exporting
3. Select the Verbose Reporting option if you require full details of the import in the Message
Log, for example specific information on any objects that fail to import.
4. Click OK.
The 3GPP data is imported.
Importing PlaNet/EET Data
To import PlaNet/EET data:
1. From the File menu, point to Import, Project Data and click PlaNet/EET.
You can import from PlaNet Versions 2.5, 2.6 2.7 and 2.8; the version of the PlaNet files
you are importing is determined automatically by ASSET.
2. In the PlaNet Import dialog box, on each tab, select the checkbox for each item that you
want to import (for example, carriers) and browse for the text file for that item.
3. Where enabled, choose whether you want to delete existing items and replace them with
the imported ones.
4. If carriers are required, on the Carriers tab, select the checkbox and browse for the text
file. For the carrier types (layers), select the checkbox and browse for two files (*.types and
*.names). If carrier groups are to be imported, click the groups checkbox and browse for the
groups file (*.groups):
5. If antennas are required, you can also add the antennas to all the projects saved under this
database.
6. When all the files have been selected for the PlaNet/EET import, click Import.
417
ASSET User Reference Guide
Note:
 There is a power tool for converting Planet Antenna files (*.txt / *.msi) into Antenna XML
files so that multiple antennas and patterns can be converted into ASSET XML format. It is
available from Add-ins under the File menu (see Using the Planet Antenna Utility on page
343), but can also be run independently of ASSET. If you require further details, please
contact your regional Product Support centre.
 There is also a Planet PAFX Antenna Import feature that supports the direct import of
*.pafx antenna files, where the Antenna Device and multiple Antenna Patterns that are
contained in the *.pafx file are imported directly into ASSET. No intermediate steps or
manual intervention are required. See Using the Planet PAFX Antenna Import on page 342.
Importing Antennas and Microwave Antennas
Cellular antennas and microwave antennas can be imported using XML (recommended) and
PlaNet/EET file formats.
For more information about importing antennas using XML see Importing XML Data on page 411.
To import antennas using PlaNet/EET:
1. From the File menu, point to Import, Project Data then click PlaNet/EET.
2. On the Antennas tab, select the Antenna checkbox then click Add to navigate to the
location where your antennas are located.
3. Select the *.txt file you require, and click Open.
4. Select the Add to All Projects checkbox if you want to make the antennas available to all
projects in the database. (This option is permission-controlled.)
5. Click the Import button.
Note:
 If you have a microwave link planning product (for example, ASSET Backhaul) installed,
you can also import microwave antennas using *.mwa files or *.nsm files. For more
information, see the ASSET Backhaul User Reference Guide.
 When importing cellular antennas, if values for Electrical Downtilt, Azimuth Offset,
Horizontal Beamwidth and Vertical Beamwidth do not exist in the import file, the values for
these antenna pattern attributes will be automatically calculated.
About Importing Using PlaNet 2.7
If you are importing using PlaNet 2.7, there are some important operational differences that you
should be aware of:
 When you import sites and sub-cells, PlaNet 2.7 adds the cell layer with the highest priority,
rather than adding the default cell layer
 When you import carriers, they are assigned to the cell layer with the highest priority
418
Importing and Exporting
Resolving Conflicts between Current and Imported Data
When importing, there may be conflicts between imported data and current data in the project.
When a conflict is detected, a dialog box appears, prompting you with the methods to resolve it.
Note: If you have anything shared between projects, for example cell equipment, and you export
and re-import as a new project in the same database, you will get a message telling you that you
are re-importing duplicate information. Ideally, you should not re-import items that are shared
between projects.
About the Carrier Layer Name Match Dialog Box
If the names of an imported and an existing carrier match, a dialog box is displayed in which you
can choose to do one of the following:
Option
Description
Rename
The carrier can be imported under a new name.
Merge
The carriers in the imported layer are merged with the existing ones.
Merge All
This and any other carrier for which there is a name match will be merged.
Stop
The Import will be stopped at this point. Carrier layers already imported will be
unaffected, but no further carriers will be imported.
About the Database Parent Mismatch Dialog Box
If a site in the import file is parented onto a site that does not exist, a dialog box is displayed and
you can choose to:
 Update the current database to match. Thus, the site with the name of the parent site will
be created. You can then choose whether to re-parent the child site onto the newly created
site.
 Update the current database to match and create both the new parent site as well as any
other sites which are parents in the import file, but not present in the project.
 Not to update the current database to match and not to create the new parent site.
 Not to update the current database to match and not to create any new parents.
 Stop the import, and not to import any further sites or cells.
Importing Property Data
When you import Property data from a file you have previously exported, follow these steps:
1. Open the text file and have a look to see whether the Property data was exported with XY
co-ordinates, LON LAT co-ordinates or both.
2. If the file contains both sets of co-ordinates, choose one, and delete the two columns that
make up the other.
For example, cut and paste the file into Microsoft Excel, keep the XY columns and delete
the LON LAT columns.
3. Save the file again.
4. From the File menu, point to Import, Project Data and click Property Data.
5. Locate the appropriate file and click Open.
419
ASSET User Reference Guide
Importing GSM Data
To import GSM data:
1. Create data files for the GSM carriers, neighbours and exceptions, for example, in Microsoft
Excel.
For information about these file formats, see the ASSET Technical Reference Guide.
2. Save the files as *.txt files and import them:
3. From the File menu, point to Import, Project Data and click GSM Import.
4. Select the option(s) you require.
5. For each selected option, browse for the file (*.txt) you require then click Import.
Importing CellOpt Data
If you have produced GSM carrier information using Actix's CellOpt AFP, and want to use this data
in ASSET, you can import it.
Important:
 To be valid for import, the CellOpt data must be stored as a text file, and use the
appropriate format. For more information, see the ASSET Technical Reference Guide.
 Only GSM carrier data can be imported in this way.
 You can only update existing data objects; you cannot create new data objects.
 For any carrier layer, you can only import a number of carriers up to the Maximum
allocatable carriers defined in the Carrier Layer Configuration dialog box. Any carriers
beyond this threshold are not imported.
To do this:
1. From the Import menu, point to Project Data and click Actix CellOpt.
The Actix CellOpt Import dialog box appears:
2. Type the full path and filename of the text file that you want to import.
- or Click the Browse button
, locate the required file and click Open.
3. Click Import.
The GSM carrier information in the selected file is imported into ASSET.
420
Importing and Exporting
Importing Vector File Data
You can import selected vector file data from a range of formats into the database at any time.
Important: For all the formats, if the imported vector is in a different projection system to that of the
current project, it will be automatically converted during import. This is also true for 'Mapinfo (*.tab)'
vector files, but there is an additional option to import 'Unconverted Mapinfo (*.tab)' vector files if
you do not want conversion to take place. (The subsequent section provides more information.)
To import vector file data:
1. In the Vector Manager, right-click a folder or top level node and from the menu that
appears, click Import Vector File:
2. You can choose from any of the following supported formats:
Notes:
o
You can define CPE (Customer Premises Equipment) FWA Terminal height and
azimuth values with the Table Browser. For more information, see Setting Values for
the Attributes on page 265.
o
You can import point vectors using the CSV format. Doing this requires the .csv file and
accompanying .prj and .csvt files to be available for import.
A new vector file feature is created and the vector data file is imported. If the vector file
feature consists of a single TAB file, the import is complete.
3. If the vector file feature is made up of multiple TAB files, you should now right-click the new
vector file feature name and from the menu that appears, click Import Vector File.
The vector file feature is updated with the additional TAB file.
4. Continue to add files, until all of the files have been imported.
421
ASSET User Reference Guide
Note: If the vector file feature has any missing files, it is still loaded and the missing files
marked with a red cross.
MapInfo Vectors - Coordinate System Conversion
Before version 8.1, the Import Vector File process ignored any difference between the coordinate
system of the imported vector and the coordinate system of the project. From 8.1 onwards, you
have the choice of selecting:
 MapInfo with conversion (which converts the imported vector file’s coordinate system to
match the project)
- or  MapInfo without conversion (which leaves the imported vector file's coordinate system
unchanged)
Note: The original TAB file is not changed by either option.
In 8.1 onwards, when using the Import Vector File process, the default type of file is MapInfo (with
conversion):
If you use this option, a <VECTORNAME>_conv.TAB fileset will be created when the vector file is
imported, and the message log confirms the conversion.
This conversion may cause the area and perimeter of the new converted file to differ from the
original TAB file. You can check this by opening the _conv file and the original file in MapInfo and
comparing them. Any differences will probably produce a difference in ASSET’s Array Statistical
Reports for total area between a polygon vector imported in 7.0 and the same polygon vector
imported in 8.1 onwards.
Note: The conversion only occurs within the vector import process; any polygon vectors upgraded
to 8.1 onwards will not show a difference between 7.0 and 8.1 onwards.
In light of the above, in situations where you are importing a vector file in 8.1 onwards, and require
backward compatibility regarding the array area and perimeter, you can choose the non-conversion
option:
Warning: Importing a vector in a different system without conversion may lead to incorrect results.
Therefore we generally recommend that you do not use the Unconverted MapInfo importing option
unless you are sure that the vector and the project already have matching coordinate systems.
422
Importing and Exporting
Exporting Data
You can export data in order to produce something that can be read by earlier versions of the
software or by alternative software. However, certain information is not retained between versions
so exporting data only includes the information needed by the earlier version of the software.
Warning: You cannot recreate your original database from exported information. The only way to
back up your database is to do so at database level. For information on this, see your Oracle
database administration documentation.
You can export data to a number of formats, as described in the following sections.
Exporting ASSET Data
You can export ASSET data, but this is in no way equivalent to creating a database backup using
Oracle export. You should only export ASSET data when you want to import into:
 Another project in the same database
 A new project in a different database created in the same build
This table shows the important differences between ASSET export and database backup:
ASSET Export
Database Backup
Only guaranteed to work in the same build of
ASSET because later builds may change the
database structure.
Guaranteed to work in all later builds of ASSET by
upgrading.
Contains committed data for a single project or Contains all projects, that is, everything that you
region, that is, everything that you have
have entered in the tool.
entered in the tool after starting the project.
Also contains users and groups, permissions, map
Does not contain users and groups,
data and projection settings.
permissions, map data and projection settings.
To perform an ASSET export:
1. From the File menu, point to Export and click ASSET.
2. Browse for, or type, the name of the file to contain the project information. The file status is
indicated as you type or when you select a file, and can be any of the following:
o
good
o
file already exists
o
cannot create file
3. For projects with Region Load defined (for more information see Loading a Subset of
Project Data (Site Region Load) on page 33 you can limit the export to only those elements
that fall within the defined region by selecting the Restrict Site Load to Region option.
Notes:
o
If you select this option, ASSET Backhaul links are not included in the export.
o
This option requires the CREATE TABLE database privilege to have been granted to
the NETWORK_PLANNING schema by your system administrator. For more
information, see the ASSET Installation and Administration Guide. If that privilege has
not been granted, a warning appears in the Message Log.
423
ASSET User Reference Guide
4. The number of sites, nodes (PLMNS, LOGICAL NODES, SGNS, MSCs, BSCs and
LOGNODEs), and cells that will be included in the project or region export are shown in the
Number of Elements pane.
Click Export to proceed.
A progress bar appears until the export is complete.
An *.aii file is created, together with *.aid files that contain all the data from that project or
region.
To back up your database:
Use an appropriate database tool. For more information on backing up and restoring
databases, see the ASSET Installation and Administration Guide.
What If I Did Not Back Up My Database?
If you did not back up your database, and want to reclaim some exported data, you would have to:
 Re-install the exact build of ASSET that you had when you created the export of data
 Create a blank database
 Create any custom projections/ellipsoids
 Create users and groups
 Create a new project then import the exported data into it
 Create a database backup using the appropriate database tool, for your reference
 Install the latest version of ASSET
 Upgrade the database to the latest version by using Upgrade Database in the Administrator
Exporting XML Data
You can export XML data from ASSET using the XML Export.
Exporting XML data will produce:
 An index.xml file that details all the contents of all the files
 Various other xml files depending on what you have selected, for example, BSCs.xml
Note: Before exporting, unless you want to export the whole project, consider whether you may
want to use a filter to limit the exported content.
Tip: If you want to export an XML file containing only the project settings, see Exporting Project
Settings on page 29.
424
Importing and Exporting
Using the XML Export
To export XML data:
1. From the File menu, point to Export and click XML. The XML Export dialog box appears.
This picture shows an example:
2. In the Export Folder pane, click the browse button
and locate the folder to which you
want to export the data. Alternatively, there is an option to make a new folder. When
finished, click OK.
3. In the Limit Export to Modify Date pane, optionally use the From Date and Time and the
To Date and Time checkboxes together with the date and time selection drop-downs
associated with them, to limit the elements exported to those last modified within the
specified date range.
4. On the Project tab of the XML Export dialog box, use the drop-down list in the Export
Filter pane to select the filter from which you want to export data.
5. On the Project, Config, Templates and Filters tabs, select the items you want to export. If
you want to export all the items on a specific tab, select the 'Select All' checkbox (this
option is tab-specific only).
6. For each item that you have selected, click the Options button to select a number of
advanced options, including automatic XML schema validation. For more information, see
About the Advanced Options for Exporting XML Files on page 426.
425
ASSET User Reference Guide
7. When you have selected all the items you want to export, click Export.
An XML file is generated for the items you have chosen.
About the Advanced Options for Exporting XML Files
If you are exporting XML files from ASSET, you can select a number of additional options for each
object type, to determine the content of the output.
To select the advanced options for an object type:
In the XML Export dialog box, click on the name of the required object type and then click
the Options button:
The Options dialog box appears, comprising a set of tabs displaying the export options for
that specific object type only. This table describes the available options:
Object Type
Tab
Option
Description
Property
Location
Location Units
Enables conversion to other
units.
Most object
types
Read-Only
Fields
Include All
If you select this option, the XML
data will include all read-only
fields.
Most object
types
File
Filename and XML Limit
Shows the filename and enables
a limit on the number of
elements.
Export Prediction System
Info
Enables the generated XML to
include comprehensive
Prediction data (read-only) for
each antenna. This includes
location, height, pattern, model
information, and so on.
Cell, Repeater, Prediction
Property
426
Importing and Exporting
Object Type
Tab
Option
Description
Export Prediction File
Path
The above details can include
the file path of the prediction file
for the antenna.
Export Prediction File
Existence Check
The above details can include
confirmation of whether or not
the prediction file exists.
Repeater
Parent Cell
Pred
Export Pathloss from
Parent Cell
Enables the generated XML to
include the pathloss from the
parent cell.
Antenna
Filter
Restrict by 'antenna' filter
Provides two useful filtering
options. For more information on
these options, see About the
Filtering Options for Antennas on
page 427.
Restrict by 'network
element' filter
Terminal Type
Selective
Export
Ignore Zero Traffic Under
Vectors
If you are exporting terminal
types that contain all or many
zero traffic values under their
Vectors tab, you can use this
option to exclude such vectors
for each terminal type from the
generated XML. This is
especially useful when you have
lot of vector data (polygon, line or
point) that has no traffic
assigned.
This helps to speed up the
subsequent import of the file (or
you can achieve the same
benefit by using the
corresponding option in the XML
import process).
About the Filtering Options for Antennas
For antennas, clicking the Options button provides access to a Filter tab that provides a variety of
useful filtering options, as shown in this example:
Example of the filtering options for antenna objects in the XML Export
427
ASSET User Reference Guide
If you want to restrict the export of antennas, you can achieve this by using an Antenna filter or a
Network Element filter (if both are used simultaneously, the results are exclusive and cumulative).
Restricting by Antenna Filter
This relates to the 'Restrict by filter (antenna)' checkbox. If you select this, the following rules will
apply:
 If a device is in the filter:
o
If “Restrict by Usage” is unselected: The export will operate regardless of whether or
not the device is assigned to any physical antennas.
o
If “Restrict by Usage” is selected with the “Used” option: The export will only include a
device that IS assigned to any physical antennas.
o
If “Restrict by Usage” is selected with the “Unused” option, The export will only include
a device that is NOT assigned to any physical antennas.
The resulting export, in accordance with the chosen restriction option, will include that
device plus ALL of its patterns. This is regardless of whether any of its patterns are also in
the filter, and regardless of the 'Include All Patterns For Exported Devices' checkbox.
 If a pattern is in the filter but not its parent device:
o
If “Restrict by Usage” is unselected: The export will operate regardless of whether or
not the pattern is assigned to any logical antennas.
o
If “Restrict by Usage” is selected with the “Used” option: The export will only include a
pattern that IS assigned to any logical antennas.
o
If “Restrict by Usage” is selected with the “Unused” option: The export will only include
a pattern that is NOT assigned to any logical antennas.
The resulting export, in accordance with the chosen restriction option, will behave
differently according to the 'Include All Patterns For Exported Devices' checkbox:
If it IS selected:
The export will include that pattern, plus its parent device, plus ALL that device’s other
patterns (regardless of whether they are in the filter and regardless of whether they are
used).
If NOT selected:
The export will include ONLY that pattern (and its parent device).
Restricting by Network Element Filter
This relates to the 'Restrict by filter (element)' checkbox. If you select this, the following rules will
apply:
 If a Property is in the filter:
o
The export will include all devices used on all physical antennas on that Property, plus
all their patterns, regardless of the 'Include All Patterns For Exported Devices'
checkbox.
 If a cell or repeater is in the filter, the resulting export will behave differently according to
the 'Include All Patterns For Exported Devices' checkbox:
If it IS selected:
428
Importing and Exporting
The export will include all patterns, and their devices, and all those devices' other
patterns, used on all logical antennas used by that cell or repeater.
If NOT selected:
The export will only include all patterns, and their devices, that are used on all logical
antennas used by that cell or repeater.
This example helps to show how the filtering options operate:
Filter X contains two patterns (ant1, ant2) and one cell (Node7A); the cell uses ant3, but ant3 is not
included in the filter.

If you select 'Restrict by filter (antenna)' using Filter X, the export will consist of ant1, ant2

If you select 'Restrict by filter (element)' using Filter X, the export will consist of ant3
Filter Y contains two patterns (ant3, ant4) and two cells (Node7A, Node8A); Node7A uses ant3,
Node8A uses ant5.

If you select 'Restrict by filter (antenna)' using Filter Y, the export will consist of ant3, ant4

If you select 'Restrict by filter (element)' using Filter Y, the export will consist of ant3, ant5
If you select both the restricting options together, using Filter X for Restrict by antenna and Filter Y
for Restrict by network element, the export would consist of ant1, ant2, ant3, ant5 (ant1, ant2 from
Filter X; ant3, ant5 from Filter Y).
About User-Defined Fields when XML Exporting
Exporting XML from ASSET does not include the export of user-defined fields, which are
maintained in Administrator. If a project uses fields which you want to export, then you can use the
Export Fields button in the Field Definer in Administrator.
If you are importing XML data that contains field values for network elements, then you must have
already imported the fields and values in Administrator prior to doing the XML Import.
For more information, see the ASSET Installation and Administration Guide, or speak to your
administrator.
Exporting 3GPP Data
If you have import privileges (permissions are defined in Administrator), you can import and export
committed ASSET data as 3GPP XML files.
To export data as 3GPP XML:
1. From the File menu, point to Export and select 3GPP.
429
ASSET User Reference Guide
The 3GPP XML Export dialog box appears. This picture shows an example:
2. In the 3GPP XML Export dialog box, enter the following details:
Item
Description
Export File
Enter the name of the XML file you want to save the data to, or browse to a
location, type a filename and click OK.
Export Data
Select the data options that you want to export. You can select any of the
following:

RNCs

UTRAN Cells

UTRAN Relations

GSM Relations
Warning: The elements for all of the options above the lowest option selected will
be exported regardless of whether they are selected or not, but the parameters for
those not selected will be ignored.
Comparison
File
Optionally select a comparison XML file.
This is typically the file used to originally import the data. All data specified in this
document may be exported (updated) to the file provided you have the correct
network hierarchy, that is, all cells must be associated with an RNC and all RNCs
with a logical network.
For more information on how this is used, see Using a Comparison File for 3GPP
XML Export on page 431.
Export Prefix
Enter an identifying prefix for the export file. This is for your information only.
Filter
Select any relevant filter containing the information that you want to export.
Note: If you intend to include RNC and UtranCells in the export, ensure these are
included in the filter itself.
3. Click OK.
430
Importing and Exporting
Using a Comparison File for 3GPP XML Export
To ensure you export the correct information, you can use a 3GPP XML file that you previously
imported as a comparison file to compare with the 3GPP file that you want to export. In this way
ASSET will selectively export neighbours according to the situation:
 If the neighbour is present in ASSET, but not in the comparison file, then a neighbour is
created and exported
 If the neighbour is present in the comparison file, but not in ASSET, then the neighbour is
marked for deletion in the export file
 If the neighbour is present in both, then no neighbour will be exported
Important: In order to use a comparison file effectively, you must closely synchronise all of the
cells in RANOS with ASSET.
Exporting Filters
You can export your filters to share them or to keep a backup of them by using the XML Export:
1. From the File menu, point to Export and then click XML.
2. Click the Browse button to select the location to which you want to export the *.xml file(s).
3. On the Filters tab, select the filters that you want to export:
4. Click Export to begin exporting.
431
ASSET User Reference Guide
Exporting Vector File Data
You can use the Vector Manager to export selected vector file data.
Tip: You can export the files as they are (TAB files) or in MID/MIF format.
To export vector file data:
1. In the Vector Manager, right-click the appropriate vector (includes all its files) or an
individual vector file.
2. From the menu that appears, click:
Export to Folder
- or Export to MID/MIF format
3. Choose a folder and click OK.
The appropriate files are output to the chosen folder.
Exporting PlaNet/EET Data
ASSET supports Versions 2.5, 2.6 and 2.8 of PlaNet, corresponding to EET R2B and EET R2C. If
you want to export 2.7, use 2.8.
To export to PlaNet format:
1. From the File menu, point to Export, Project Data and click PlaNet/EET.
2. Select the version of the export file required.
Note: Distribution nodes will not be exported, and if you are using 2.6, nor will repeaters.
3. Choose a filter to export certain network elements or choose All to export all network
elements.
4. Select a delimited format for your export file - either using spaces or tabs.
5. Select the checkbox of each item required and browse to the correct location of the relevant
file, or type in the path and filename.
Note: Although the files for user-defined fields, sites/cells, carriers and neighbours should
include their extension (.txt), the filename for Carrier Types/Names/Group should not
include an extension, as this is used as the stem of three files, to which extensions are
added.
6. Click Export.
Warning: Exporting data produces something that can be read by earlier versions of the
software or alternative software. However, it does not export everything - for example,
microwave antennas cannot be exported - and so you cannot recreate your original
database from an export. For more information on this, see Exporting Data on page 423.
432
Importing and Exporting
Exporting Property Data
To export property data from ASSET, follow these steps:
1. From the File menu, point to Export, Project Data, and then click Property Data.
2. Select the Property data set that you want to export, by choosing one of the filters.
3. Select whether you want to export the Property data with Easting & Northing co-ordinates
or Longitude & Latitude co-ordinates.
4. Type in the required Export Filename, or click the Browse button, locate the required file,
and click Save.
5. Click OK.
The selected Property data is exported.
Exporting CellOpt Data
If you are using ASSET in conjunction with Actix's CellOpt AFP, you can export GSM carrier and/or
interference data from ASSET for use in CellOpt AFP.
The data is exported to a text file, using a specific format. For more information, see the ASSET
Technical Reference Guide.
Note: Only GSM carrier and interference data can be exported in this way.
To export data:
1. From the Export menu, point to Project Data and click Actix CellOpt.
The Actix CellOpt Export dialog box appears:
2. If you want to export carrier data:
o
Select the filter containing the required carriers
o
Select the Export Carriers File option
o
Type the full path and a filename for the file that will be created during export
- or 433
ASSET User Reference Guide
Click the Browse button
, browse to the required file location, type a filename for
the file that will be created during export, and click Open
3. If you want to export interference data:
o
Ensure that you have interference data in your project - either loaded from an existing
file or generated using the Interference Table Wizard
o
Select the Export Interference Data File option
o
Type the full path and filename of the file that you want to import
- or Click the Browse button
, browse to the required file location, type a filename for
the file that will be created during export, and click Open
o
If you want to scale up the interference data table so that a larger set of values is
exported to CellOpt AFP, in the Interference Scale Factor pane, type the required
interference scale factor. For example, to double the values in the interference data
table, type an interference scale factor of 2.
Note: The default value of 1 exports the values exactly as they are in ASSET.
4. Click Export.
The carrier information and/or the interference data in the selected file(s) is exported from
ASSET. The files are now ready for import into CellOpt AFP.
Exporting Web Service Data
You can export data associated with web services from ASSET.
To do this:
1. From the Export menu, point to Project Data and click Web Service Export.
The Web Services Export dialog box appears.
2. In the Data pane, select the required format (CGA or PGA), technology (5G, LTE or
NBIoT), items, and the filter that contains the data that you want to export.
3. In the Parameters pane, edit if necessary the entries in the Value column for each of the
parameters listed as required.
4. In the Overrides pane, select the Indoor Loss Schema option if you want to override the
clutter indoor loss schema on all cells selected for export (if any) and the Indoor Schema
data item. You can then select a different schema from the adjacent drop-down box.
Note: If you select the Cell item as part of the export set then all other selected items that
have a ‘used by’ relationship with the cells are filtered to contain only items that are in use
by the cells selected for export, that is: Carriers, Antennas, Models, and so on. Otherwise
all items present in the project for those types are exported without any filtering.
5. In the Output Folder pane:
o
Type the full path and a filename for the file that will be created during export
- or Click the Browse button
, browse to the required folder, then click Select Folder.
6. Click Export.
The selected project data is exported.
434
Importing and Exporting
Exporting Map Layers using GIS Export
The GIS Export facility can export any or all of the map layers (vectors, heights, clutter, coverage
arrays, network element filters and so on) that are currently displayed in the Map View.
You can export any of your map layers for use with:
 MapInfo
 Google Earth
 ESRI ArcGIS
Tip: For vectors and network element filters, you can also export the related attribute information if
you select the attributes as labels in the item's display properties in the Map View.
Important: The Polygons/Rectangles option also exports any vectors that are currently displayed in
the Map View. If you are exporting a large area and want to quicken the export process, we
recommend that you do not display the vectors in the Map View prior to the export.
Additional Information about the ASC, BIL, GRD and GRC File Formats
For information on these file formats, see the 'Array File Information (ASC, BIL, GRD, GRC)' topic
in the 'Miscellaneous Vendor and Third Party File Formats' chapter of the ASSET Technical
Reference Guide.
Preparation for the GIS Export
To prepare for the GIS Export:
1. See the general information in Exporting Map Layers using GIS Export on page 435.
2. In the Map View window, on the Data Types tab of the Layer Control Pane, double-click
the item that you wish to export and in the Display Properties dialog box that appears,
click the GIS Export tab. You will then see the export settings for that item.
(For Filters, which can export the network elements, these export settings reside on the
icon in the left pane.)
3. In the Content Type pane, select the content type that you want to be used for exporting
your data. This table describes the options available:
Option
Description
Raster
Image.
This is the usual image format where each pixel of an item is given a colour.
(This can
include
numeric
values,
see step 5
below).
You must choose the type of output file that you require (JPG, PNG, GeoTIFF, ESRI,
GRD/GRC and so on).
The colour white is marked as the 'transparent colour', which improves the usability of the
export (especially when exporting multiple layers).
Note: For special information on the *.asc, *.bil, *.grd and *.grc file formats, see the 'Array
File Information (ASC, BIL, GRD, GRC)' topic in the 'Miscellaneous Vendor and Third
Party File Formats' chapter of the ASSET Technical Reference Guide.
Tip: These exports do not include the Legend information relating to arrays. If you need
this, please see the topics under Printing from the Map View on page 125, including
Printing a Map View to File on page 128.
435
ASSET User Reference Guide
Option
Description
RLE
Contains run-length encoded rectangles. This scans the coverage array and encodes
Rectangles. consecutive pixels with the same value into rectangles in the output. So you have multiple
small rectangles representing the coverage area rather than one larger polygon.
Benefits: Fast method, and the destination software handles the results more easily.
Drawbacks: The file size is larger and may prevent analysis in the destination software.
Polygons.
Creates a true polygon for each coverage area but requires more processing time.
Symbol
points.
Exports display filters as scalable font symbols. These are set for each filter and for each
visualiser.
Note: Symbol points are only available on filters and visualisers. Due to font limitations,
the export may not reproduce the exact appearance of the Map View.
4. If you have selected Raster Image, then from the Raster output file type pane, select the
required format, otherwise go to step 6.
5. If you select one of the Geo TIFF or ESRI HDR file types, in the Pixel type pane, select
either Color or Numeric, otherwise you can skip this step. Choosing Numeric enables you
to export value based rasters into formats that are compatible for import into ASSET Web.
6. Click OK.
Tip: The export settings for each item are persisted until you change them again. Each item can
have independent settings.
Performing the GIS Export
To perform the GIS Export:
1. Ensure you have followed the steps in Preparation for the GIS Export.
2. In the Map View window, from the File menu, click GIS Export.
The GIS Export dialog box contains checkboxes for Image, Polygons/Rectangles and
Symbol points. These correspond to the options on the GIS Export tab of the Display
Properties dialog box, as described in the table in the preceding topic.
3. In the GIS Export dialog box, either:
o
Type the name of a folder to which you want to export the output files, and then add a
filename prefix
- or o
Click the Browse button
, locate the folder to which you want to export the output
files, and then enter a filename prefix
4. Select which option(s) you want to enable:
o
Image files: You can choose whether to include a TAB file and/or a KML file. If you
select KML you can also choose to group all layers into a single file rather than
producing a separate file for each layer:
Note: Do not select the 'Include a KML file' option if you intend to export a GRD/GRC
file. This is because the KML/KMZ file implies a coordinate conversion of the layers,
and this is not supported for GRD/GRC files.
436
Importing and Exporting
o
Polygons/Rectangles: You can choose the required file type from the drop-down list:
Note: The Polygons/Rectangles option also exports any vectors that are currently
displayed in the Map View. If you are exporting a large area and want to quicken the
export process, we recommend that you do not display the vectors in the Map View
prior to the export.
o
Symbol points: You can choose the required file type from the drop-down list:
5. If you are exporting a large array, you should split the output array into tiles. To do this,
select the 'Split the export' option, and then select the required number of tiles.
6. You can change the EPSG (European Petroleum Survey Group) code by typing a different
one or by clicking the Configure button. To revert to the EPSG code specified in the
Project Settings dialog box, click the Reset button. For more information, see About the
Coord System Tab on page 24.
The current projection is shown below the EPSG Code field. This picture shows an
example:
Note: You cannot change the EPSG code if your export includes a KML/KMZ file, because
this type of file must be produced in EPSG 4326. This means that other types of file (if
included) will also be produced in EPSG 4326.
7. Click OK.
ASSET exports all selected layers to the selected formats.
Using the XML Data Editor
You can use the XML Data Editor to:
 Open, edit and save ASSET-produced XML files
 Transfer data into ASSET-compatible XML format via other applications, such as Microsoft
Excel or a *.csv (Comma-Separated Value) file, without having to edit the XML files directly
To open the XML Data Editor:
In ASSET, from the File menu, point to Add-ins and click XML Data Editor.
437
ASSET User Reference Guide
- or Click Start, and from the menu that appears, point to Programs, TEOCO, Version, Misc
and click XML Data Editor.
Note: In most cases, the XML Data Editor accepts XML data for the supported element types from
only the current ASSET version. However, for some element types, it may also support XML data
from older versions (for example, site data and Property data). However, XML data saved in the
XML Data Editor will only be compatible with the current ASSET version, or any later version that
does not make significant changes to the format of the data.
About the XML Data Editor User Interface
The main areas of the XML Data Editor are:
 The list of supported network elements, in which any open XML files are organised
 The grid display pane, in which you can edit open XML files
 The message log window
The List of Supported Network Elements
The tree list in the left-hand pane displays the network element types that are supported by the
XML Data Editor. If the file contains complex data, this will be separated into a number of views.
For example, Properties data is divided into separate views for Fields, Physical Antennas and
Logical Antennas:
As you select each view, different detail for the required type is displayed in the grid display pane.
Important: Within multiple views, there is a relationship between parent views and dependent
('child') views. Therefore if an ID is changed in a dependent view, the same parent ID must exist in
the parent view. However, if you change a parent ID, the IDs in the dependent views will change
automatically.
438
Importing and Exporting
The Grid Display Pane
When you open an XML file in the XML Data Editor, the data in the file is displayed in the grid
display pane. This picture shows an example:
Grid display pane
The columns are coded as follows:
This code
Means that the data in this column
Bold text
Represents a unique ID or key.
Blue cell
Is mandatory; a value must be entered.
Magenta cell
Is numeric.
For all other columns, data of any type can be added or the column can be left blank (subject to
ASSET XML import restrictions).
The Message Log Window
The XML Data Editor generates messages as part of its normal course of data editing. Most 'error'type messages are safe to ignore, and are a useful guide to help you edit your documents.
However, the following messages are significant.
If you receive the following message:
6:09:09 PM : Opening C:\XML Data\CELL-LIST001.xml...
6:09:10 PM : This XML was produced by an earlier version of ASSET that is
not compatible with this tool. The file cannot be loaded
This indicates that the XML file you are trying to open was created in an earlier version of ASSET,
which is not supported by the XML Data Editor. Each element type has a minimum supported
version, which will typically be the current version.
Tip: To view the minimum supported version for an element type, view the
XMLMetaTypesData.xml file, which is stored at the location where you have installed ASSET, for
example C:\Program Files\TEOCO\ASSET\XML Editor\XML. This picture shows an example:
439
ASSET User Reference Guide
If you receive the following message:
6:14:43 PM : Failed to enable constraints. One or more rows contain
values violating non-null, unique, or foreign-key constraints.
It can indicate that:
 The XML Data Editor has found an element in the file that it did not expect
- or  The XML Data Editor has found duplicate data
To ensure this message does not occur, in the Preferences dialog box, select Ignore Constraint
Violations.
Setting Preferences for the XML Data Editor
In the XML Data Editor, you can set specific preferences, determining how data is loaded, and
changes are saved.
To do this:
1. From the File menu, click Preferences.
The Preferences dialog box appears.
This picture shows an example:
2. You can define the following options:
440
Importing and Exporting
Item
Description
Ignore Constraint
Violations
When loading an XML file, ASSET will ignore any constraint errors that
occur and continue to attempt loading.
Constraint errors occur when ASSET finds a duplicate row inside the
source data, because ASSET respects unique constraints of certain key
columns (for example, ID).
Important: If you select this option, after the file has loaded you should
delete the duplicate data row. You can then de-select this option.
Validate file
When saving changes, ASSET will check the XML file against the
structure, syntax and restrictions defined in the XSD file for the
corresponding object type.
For more information, see How ASSET Validates XML Files on page
415.
Warning: Using this setting can make saving changes take longer.
Format data
ASSET will make the XML file easier to read in other software, for
example, Notepad.
By default, this option is not selected, to make it more compatible with
ASSET. In some cases, ASSET will not accept files formatted this way,
and may fail to merge the change during an XML import.
Automatically backup
original file
ASSET will create a backup of the original file when saving, which you
can recover if there is accidental damage to the XML when you are
editing it.
The backup file is given the name of the original file with the addition of
a serial number. For example, the backup file of demo.xml will be
demo.1.xml.
Note: If a file with this name already exists, the XML Data Editor will use
the next available number.
Automatically split files
greater than
In order to allow ASSET to load very large XML files, XML files that are
larger than the specified number of Kb will automatically be split into
multiple files with an index file.
The index file is given the same name as the original file with the
addition of the suffix 'index'. For example, the index file for demo.xml will
be demo.index.xml.
The multiple files are given the same name as the original file with the
addition of the suffix 'part-x', where 'x' is the number of the file, starting
at 0 for the first file. For example, if there are 3 multiple files for
demo.xml, they will be named demo.part-0.xml, demo.part-1.xml and
demo.part-2.xml.
Opening and Closing XML Files
To open an existing XML file:
1. From the File menu, click Open.
- or Click the Open button
.
2. In the dialog box that appears, locate the required XML file and click Open.
441
ASSET User Reference Guide
The file is opened and its contents are displayed in the grid pane. The file name is listed in
the tree pane, associated with the appropriate network element type.
3. If the file has multiple views, click the view name to open it.
To close a file or view:
Right-click the item that you want to close, and from the menu that appears, click Close. If
the file has multiple views, click Close All.
Editing and Deleting Data
To edit a single cell:
Double-click it and make the required change.
Tip: To undo an edit, press Escape.
To edit multiple cells:
1. Select the required cells by clicking the first one and dragging the mouse across the other
required cells while still holding down the mouse button.
2. Release the mouse button and start typing the required change. This should appear in the
last cell that you selected.
3. When you have finished typing, press Enter.
Your change should be copied across all selected cells.
Note: When you edit multiple cells in this way, if one of your columns has a unique value,
then it is not modified in order to maintain the referential integrity.
You can also edit data using the Find and Replace option.
To do this:
1. Select the row in which you want to start the Find and Replace, which by default will
proceed downwards.
Tip: To proceed upwards instead, select the Search Up option in the Find dialog box.
2. From the Edit menu, click Find.
- or On your keyboard, press Ctrl+F.
3. Click the Replace tab.
442
Importing and Exporting
4. You can find and replace particular items in different ways:
o
Using a simple find and replace, with additional options to match the case or match
whole words.
o
Use a find and replace with regular expressions. A number of regular expressions are
supported, which enable you to find and replace data in a more flexible, detailed way.
For more information on regular expressions, see http://www.regular-expressions.info.
To delete a row or rows:
1. Select the row(s) that you want to delete.
Tip: To select all the rows, select the top left cell in the view.
2. Right-click, and from the menu that appears, click Delete.
- or Press the Delete key.
Warning: If you delete data that also has dependent views, then the data in those views is
also deleted.
Viewing and Editing Antenna XML Files
When you open an antenna XML file in the XML Data Editor, patterns are displayed graphically, as
a diagram (similar to the diagrams shown on the Mask tab in the Cellular Antennas dialog box in
ASSET Radio or Microwave Antennas dialog box in ASSET Backhaul).
This means that you can perform the following actions:
Item
Description
Copy a pattern and paste it into another 1. Double-click the pattern.
file type (Word document, Excel
2. In the dialog box that appears, right-click the pattern.
spreadsheet and so on) as an image
3. From the menu that appears, click Copy Image to Clipboard.
4. In the Microsoft Excel spreadsheet, Word document or other
file type, click Paste.
Copy a pattern and paste it into another 1. Right-click the pattern.
file type (Word document, Excel
spreadsheet and so on) as a numerical 2. From the menu that appears, click Copy.
value
3. In the Microsoft Excel spreadsheet, Word document or other
file type, click Paste.
Edit the pattern in the XML Data Editor.
1. Double-click the pattern.
2. In the dialog box that appears, edit the angle and loss values.
3. Click OK.
Copy the angle and loss values and
paste them into another file type (Word
document, Excel spreadsheet and so
on) as numerical values
1. Double-click the pattern.
2. In the dialog box that appears, select the table of angle and
loss values.
3. Right-click, and from the menu that appears, click Copy.
4. In the Microsoft Excel spreadsheet, Word document or other
file type, click Paste.
Any changes you make in another file type can be pasted back into the XML Data Editor.
443
ASSET User Reference Guide
This picture shows an example of the Antenna Pattern dialog box:
Pattern dialog box
Changing the Display of Data in the XML Data Editor
You can change what data is displayed in the grid display pane of the XML Data Editor.
Note: Your changes will only affect the current view, and not any related sub-views for the same
network element.
To do this:
1. From the Edit menu, click Show Filters.
A drop-down button is added to each of the column headings, providing a list of the
possible value options for the column.
2. Click the drop-down button for the column that you want to filter on, and from the list that
appears, select the required value.
Only the data rows that contain this value are displayed.
This filter is only applied to the current view; if you select another view, the filtering
disappears.
444
Importing and Exporting
Tip: If this type of filtering has been applied to a column, the drop-down button will be
coloured blue.
To remove the filtering:
From the Edit menu, click Show Filters again.
- or At the bottom of the XML Data Editor, click Show All:
Note: A more detailed level of filtering is available. For more information, see Using Advanced
Filtering and Sorting on page 445.
Using Advanced Filtering and Sorting
As well as using basic column-based filtering and sorting in order to display your data, you can also
perform more detailed filtering and sorting. You can do this using the Advanced Sort/Filter dialog
box. To open this:
1. In the tree list of network element types, select the required item.
2. Click the Filter/Sort button
.
- or From the Edit menu, click Advanced Sort/Filtering.
This picture shows an example for a neighbour file:
445
ASSET User Reference Guide
To sort data:
1. Click the Sort tab.
2. In the left-hand pane, you can view all the column headings for the selected element type.
3. To sort on a column heading in a particular way, select the column heading, and then click
the required button:
o
Click the
button to sort column data in ascending order
o
Click the
button to sort column data in descending order
The selected column heading appears in the right-hand pane.
Tip: If you choose the wrong column, select the column in the right-hand pane and click
the
button.
4. To change the order of the columns, select the column you want to move and click the Up
or Down button as appropriate.
5. Click OK.
The data for the selected element type is displayed according to your sort criteria.
To filter data:
1. Click the Filter tab.
On this tab, you can create specific filter rules which will determine how your XML data is
displayed.
2. From the Columns drop-down list, select the column on which you want to filter.
3. In the next drop-down list, select the rule definition for your filter:
4. In the final box, type the required value, for example:
5. To add the filter, click the required Add button:
446
o
Click the Add (And) button to add the filter with an AND logical operator
o
Click the Add (Or) button to add the filter with an OR logical operator
Importing and Exporting
This table describes how the logical operators will affect your results:
If you choose
A value will be returned
OR
If any of the attributes of your filter are present.
AND
Only if all of the attributes of your filter are present.
You can use this operator if you have two filters or more.
The defined filter is added to the filter list.
Tip: If you want to redefine the filter from the beginning, click the Clear Filter button.
6. Click OK.
The data for the selected element type is displayed according to your filter.
Creating New XML Data Files
In the XML Data Editor, you can create new files, which can then be imported into ASSET as XML.
This might be useful for example, to create 'sparse' XML files that just contain the values that you
will then merge into ASSET to update your network elements.
To create a new file:
1. From the File menu, click New.
- or Click the New File menu button.
2. In the dialog box that appears, select the required file type, and then click OK.
Tip: You can also create a new file by right-clicking the required file type in the left-hand
pane, and clicking New from the menu that appears.
A new blank file appears under the chosen type, called 'New document'.
3. You can now add new data or paste existing data into the file.
For more information on how to do this, see Copying and Pasting Data in the XML Data
Editor on page 448.
4. When you have finished creating your file, click the Save As button.
- or From the File menu, click Save As.
Note: If you have selected the 'Validate file' option in the XML Editor Preferences, the
XML Data Editor will attempt to validate the XML file according to the XSD for the
appropriate type. If the validation fails, an error message appears, and you must modify
your file accordingly. For more information, see How ASSET Validates XML Files on page
415.
447
ASSET User Reference Guide
Editing Fields
For most element types, fields are displayed in their own view:
Fields View
In this example, the Fields view for the above file lists the available fields as the column headings
and the value for each instance of the element type in the rows.
Important: The XML Data Editor can only store 80 fields in total (for all network elements).
For these existing fields, you can copy, paste, add and delete data as you would normally.
For new documents, no fields are listed, so you must add fields manually. To do this:
1. In the left-hand pane, right-click the required Fields view.
2. From the menu that appears, click Add/Remove Field Groups.
3. In the dialog box that appears, in the New Group box, type the name of the new field and
click Add.
A new field (column) is added to your new document, for which you can now add values
(providing entities using that field exist).
Copying and Pasting Data in the XML Data Editor
In the XML Data Editor, you can copy cells amongst each other, or across multiple documents or
other applications, such as Microsoft Excel.
Note: When you copy and paste data, the rules of the target columns still apply. For example, if the
data must be numeric, you should ensure that the copied data is numeric as well.
To copy data:
1. Select the grid cells that you want to copy.
Tip: To select an entire row, click the cell before the cell's first column.
448
Importing and Exporting
2. Right-click, and from the menu that appears, click Copy.
- or Click the Copy button.
- or Press Ctrl + C (If you use this option, it may be slightly slower than the equivalent option in
Microsoft Excel - the Message Log will indicate when the copy has been completed).
To paste data following the copied cell order, into the current document or a new one:
1. Ensure you have copied the required data.
2. In the required document, select the cells into which you want to paste the copied data.
3. Click the Paste button.
- or Right-click, and from the menu that appears, click Paste.
- or Press Ctrl + V.
Important: If any of the data contains special symbols (for example, the degree symbol),
you must use the Paste Special option to ensure that the data is copied across correctly.
To paste data using a different cell order, into a current document or a new one:
1. Ensure you have copied the required data.
2. In the required document, select the cells into which you want to paste the copied data.
3. Right-click, and from the menu that appears, click Paste Special.
- or Click the Paste Special button.
4. In the dialog box that appears, use the drop-down buttons in each column heading to
specify where you want to paste the data contained in the selected column:
o
To paste it into a specific column, select the column name
o
To ignore the column and not paste its data at all, select Ignore
o
To create a new column for this data, select New Data:
449
ASSET User Reference Guide
Tip: If the column headings in the copied data match the column headings in the XML
Data Editor, you can select the First row contains column headings option, which will
map the column headings and paste the data according to this.
5. When you have correctly set all of the columns, click the Paste button.
6. To save the column heading mappings that you have defined, click the Save As button.
Using the XML Data Editor with Microsoft Excel
The XML Data Editor makes editing XML much more easy and convenient, but you can also use it
in conjunction with Microsoft Excel to use macros, for example, or generate data automatically.
For more information on the functions of Microsoft Excel, please see the Microsoft Excel user
assistance.
To copy and paste data from the XML Data Editor to Microsoft Excel:
1. If you want to copy and paste the column headings as well as the column data (to make it
easier to remember where the source data was copied from), from the Edit menu, ensure
that Include Column Headings in clipboard is selected.
Note: This is the default option.
2. In the XML Data Editor, select the grid cells that you want to copy.
Tip: To select an entire row, click the cell before the cell's first column:
3. Right-click, and from the menu that appears, click Copy.
- or Click the Copy button.
4. In Microsoft Excel, open the worksheet into which you want to paste the data.
5. Select the cells into which you want to paste the copied data.
6. Use Paste or Paste Special as required; for more information, see Copying and Pasting
Data in the XML Data Editor on page 448.
The selected cells are pasted into Microsoft Excel.
Note: Data that appears as a checkbox option in XML Data Editor is pasted into Microsoft
Excel as YES/NO text (or TRUE/FALSE depending on the source XML data).
To copy changes you make in Excel and paste them back into the XML Data Editor:
1. In the XML Data Editor, on the Edit menu, ensure that the Include Column Headings in
clipboard option is not selected.
2. In Excel, select the cells that you want to copy.
3. From the Edit menu, click Copy.
- or Click the Copy button.
450
Importing and Exporting
4. In XML Data Editor, open the file into which you want to paste the data.
5. Select the cells into which you want to paste the copied data.
6. Use Paste or Paste Special as required; for more information, see Copying and Pasting
Data in the XML Data Editor on page 448.
Using the XML Data Editor with CSV Files
In the XML Data Editor, you can import comma-separated value (*.csv) files, work with them in the
editor, and then save them as csv files again.
To do this:
1. From the File menu, point to Import and click CSV Delimited File.
2. In the dialog box that appears, locate the required CSV file and click Open.
3. In the dialog box that appears, select which type of network element type the CSV file
contains.
4. In the dialog box that appears, use the drop-down buttons in each column heading to
specify where you want to paste the data contained in the selected column:
o
To paste it into a specific column, select the column name
o
To ignore the column and not paste its data at all, select Ignore
o
To create a new column for this data, select New Data
Tip: If the column headings in the CSV file data match the column headings in the XML
Data Editor, you can select the First row contains column headings option, which will
map the column headings and import the data according to this.
Note: You cannot leave any column marked as ('Unknown'). If you are importing the file
into a blank document, set all of the columns you want to 'New Data' and all the columns
that you do not want to include to 'Ignore'.
Important: Ensure that you maintain the rules for any unique or mandatory column data
that exists for the element type that you are importing, for example, the ID column.
5. Click the Import button.
451
ASSET User Reference Guide
Updating an ASSET Project with the Edited Data
When you have finished using the XML Data Editor, you can update your ASSET project with the
edited data.
Important: It is recommended that you manually check the XML file created in the XML Data Editor
before you import it into ASSET.
Unless you are editing an existing file, it is recommended that you select the Merge option in the
XML Import dialog box, particularly when dealing with sparse XML data:
Merge option in the XML Import dialog box
Warning: If you choose Replace, the target item will be completely overwritten with the content of
the XML file. Ensure that you have a backup of your original data before using the Replace.
452
Importing and Exporting
Importing and Exporting Equipment
You can import and export equipment such as antennas, antenna beam patterns, microwave
antennas, BTS equipment, masts, cabins, feeders and cell equipment, as well as contact and
supplier details using the All Equipment import/export feature.
Note: When importing a file using the All Equipment import, if you do not have write access to
items in the equipment database, (set in Administrator) you will not be able to import the specific
equipment, and an error is displayed in the message log. This applies to Antenna, Supplier, BTS
Equip, Tower, Radio Type, Link Term, Feeder, Cell Equipment, Cabin, Contact Details.
Tip: You can also use this option as a quick way of importing equipment into ASSET, by exporting
the correct file structure out of ASSET, modifying it, and then importing the equipment back.
Exporting Equipment
To export equipment:
1. From the File menu, point to Export, Equipment and click All Equipment.
2. Enter the name of a file, or browse to an existing file that you wish to replace and click
Save.
3. Choose the required equipment by:
o
Selecting it in the Available pane.
o
Clicking Add.
Tip: To export all equipment, click All.
4. Click Export. If you want to modify this file and re-import, see Modifying the All Equipment
File for Re-Import of Data on page 453.
Modifying the All Equipment File for Re-Import of Data
Use the following tips if you wish to modify an All Equipment file to import all your equipment:
 If you have not entered any details for a particular section (for example, "Supplier
Details"), you can delete the section. However, sections that you do want to retain must
appear in the specified order. For example, if you have an "Antennas" section, it must
immediately precede "Antenna Mask Data".
 If there is no value for something, the field can be empty or 0.
 Antenna mask can be -1 if it is not set.
 Everything must have an ID.
 Information in the ID column must be unique, except where the relationship is one to many
(for example the same ID will appear in the "Antennas" section and in the "Antenna Mask
Data" to indicate it is the same antenna.
 There must be a blank line between each section.
 The long number strings named Filter ID and contained in the header sections of the file
are class IDs (CLSIDs). For example:
{0a037051-5281-11d4-80b7-00b0d0388bb2}
453
ASSET User Reference Guide
These number strings, in curly brackets, tell the software exactly what version of the
equipment it is importing (for example, version 4.1). You should not edit these long number
strings,
 You should not edit the headers or unique IDs for sections that exist.
 You should ensure there are no invalid values.
Entering Valid Values into the All Equipment File
This table shows the various values which must be within a certain acceptable range in the All
Equipment import file. Invalid values cannot be produced in the export but if you are modifying the
exported file for re-import you should ensure the following values lie within the range specified here:
Equipment
Value Ranges
BCF Type

Max BTS, MAX TRX and NMS Code must be values between 0-99.
BTS Equipment

Power Step, Site Spacing, Cell Spacing, Min Power and Max Power must be
positive numbers.

Max power must be greater than Min Power.
Tower

Mast height must be a positive number.
MW Antenna

Min and Max Operating Frequencies must be between 500-350000 MHz.

Min Operating Frequencies must be less than the Max.

Diameter must be a positive number.
Radio Equipment 
Min and Max Power must be between -30 and 200 dBm.

Thresholds must be between -150 and 20 dBm.

Frequencies must be between 0.5 and 350 GHz.

Bandwidth must be between 0.1 and 1000 MHz.

All branching losses must be a positive number.
CI Objective

Bandwidths must be between 0.1 and 1000 MHz.
Bands Channels

Bandwidth must be between 0.1 and 1000 MHz.

Channel Frequencies must be between 500 and 350000 MHz.

Channel Frequencies must be unique within the Band.
For equipment types not listed, no checking is performed.
Importing Equipment
To import equipment:
1. From the File menu, point to Import, Equipment and click All Equipment.
2. Browse to the required text file and click Open.
3. Select the Add to all projects checkbox if you want the equipment added to all projects in
the current database. (This option is permission-controlled.)
4. Click Import.
Error checking (for example bounds-checking) is performed on import, and if a value falls
outside a specified range, then an error is displayed in the Message Log window, and that
line inside the entry file is skipped.
If there are any duplicate names, you are asked whether you want to rename them or skip
that entry. If you select the Add to All checkbox, ASSET searches all projects in the
454
Importing and Exporting
database for a duplicate ID. If equipment does not support addition to all projects, only the
current project is searched.
If a piece of equipment has not got an associated ID, then that erroneous equipment will
not be imported and a warning is given in the message log, indicating that the entry was
skipped.
For full details of modifying an exported file and what are valid values to include, see the
ASSET Technical Reference Guide.
5. To rename, type in a new name then click Rename or press Enter. Otherwise, click Skip.
Tip: You can also press the ESC key to skip entries quickly and not import the duplicate.
Importing and Exporting User Settings
You can export all or a selection of your current user settings. You can then:
 Re-use them in another project
 Back them up
If you back up your settings they can then be imported subsequently as required.
Exporting User Settings
To export user settings:
1. From the File menu, point to Export and click User Settings. The User Settings Export
dialog box appears:
2. Click All to select all your user settings for export.
- or Click Specific to limit your selection and choose the specific settings you require.
455
ASSET User Reference Guide
3. In the Export File field, type the path and name of the file to which you want to export, or
browse to an existing file that you want to replace and click Save.
4. Click Export.
A file with the suffix .stt containing your user settings is created in the folder you specified.
Importing User Settings
To import user settings:
1. From the File menu, point to Import and click User Settings.
2. Either type the path and filename of the file containing your user settings that you wish to
import
- or Browse to it and click Open.
Note: Settings files have a suffix of .stt.
3. Click Import.
The file containing your user settings is imported.
Deleting User Settings
If Settings Management is enabled and in use, you can delete your user settings for the current
project.
To delete User Settings:
1. Select the Utilities tab.
2. From the Tools menu, select Delete User Settings.
3. Click Yes to confirm the deletion.
456
About the Grid Data Loader
15 About the Grid Data Loader
The Grid Data Loader provides a method of adding to or updating the information stored in the
Site Database and/or the Link Database.
(This method is complementary to the other data creation and update methods in ASSET, such as
manual or global edits in the Site Database, or the XML import routines).
It incorporates a grid that contains rows and columns in which you can organise the data, and
provides validation messages to help towards a successful import into the ASSET database. This
picture shows an example:
Example of Grid Data Loader
The Grid Data Loader enables you to create and/or edit the following network elements:
 Property
 GSM: MU-Node (BTS), Cell, Subcell
 UMTS: MU-Node (NodeB), Cell
 LTE:
MU-Node (eNodeB), Cell
 5G (NR): MU-Node (gNodeB), Cell
 NB-IoT: MU-Node, Cell
 Link (for ASSET Backhaul)
For a full list of the objects and parameters that are supported by the Grid Data Loader, see Valid
Headers for Each Object Type on page 477.
There are several ways you can enter data into the Grid Data Loader:
 Manually
 Load from a file
 Copy and paste from within the grid, or paste from an external source
457
ASSET User Reference Guide
 Use the Site Database Reports dialog box to generate the data. This method enables
rapid editing of data that is already in your database, and offers an easy selection facility to
choose what you require. Another benefit is automatic column matching which should
minimise the need to perform row and column editing. A typical use case would be where
you want to perform a bulk UPDATE of your existing network data, modifying a cell setting
on all the cells, with the benefit of clear visibility of the data within rows and columns.
You can output the generated results:
o
Directly into the Grid Data Loader (you can still manipulate the data in the Grid Data
Loader)
o
Into Microsoft Excel or a text editor, then load the file into the Grid Data Loader
(enables you to manipulate the data first)
For information on this method, see Integrating the Site Database Reports with the Grid
Data Loader on page 466.
Data created or modified via the Grid Data Loader is saved for the individual user, into the 'Applied'
state.
Before Using the Grid Data Loader
Before using the Grid Data Loader, you should read:
 Basic Difference between Insert and Update on page 459
 Hierarchy and Information Flow on page 459
 Guidelines for the Grid Data Loader on page 460
 Examples of Use Cases on page 501
It is good practice to decide beforehand:
 Which operation you intend to perform:
o
INSERT new objects. This relates to network elements such as Property or Cell.
o
UPDATE the data of existing objects. This relates to the 'data parameters' of the above
network elements, such as cell name, antenna azimuth, and so on.
o
INSERT + UPDATE the data. This is equivalent to a merge operation, where if an
object does not exist it inserts it, and if an object already exists it updates it. Both
actions are possible in the same row.
 How you will enter the data into the grid: Loading from file, Manually, or using Paste. You
can also use a combination of these.
 Which headers you want to be present in the column header row. See Valid Headers for
Each Object Type on page 477.
Important:
 Within each session of the Grid Data Loader, you should focus on a singular objective, in
terms of creating objects, updating objects, and so on. If you keep the objectives simple
and consistent within each session, you are more likely to achieve your expected results.
 The Grid Data Loader aims to compose XML type structures that ASSET will recognise at
the import stage. With respect to this, there is an option to retain the generated XML files
when you successfully validate or import, which can be a useful way of checking the data.
 It is sensible to perform a Commit All on the Site Database before using the Grid Data
Loader. This would enable you to perform a Restore All to return to the previous situation, if
necessary.
458
About the Grid Data Loader
Basic Difference between Insert and Update
There are some key differences between the main two import modes of the Grid Data Loader.
The following points relate to the INSERT mode:
 If you are INSERTING a new MU-Node (and possibly Cells) on an existing Property, the
row must include the Property ID.
 If you are INSERTING a new MU-Node (and possibly Cells) on a new Property, the row
must include the Property ID with location coordinate information (see About the Location
Parameters on page 500).
 If you are INSERTING a new Cell on an existing MU-Node, the row must include the MUNode's Identity, but you do not have to include the Property ID (this is already known by the
MU-Node).
 If you are INSERTING a new GSM Subcell on an existing Cell, the row must include the
Cell's Identity, but you do not have to include the MU-Node's identity, nor the Property ID
(these are already known by the Cell).
For an example, see 1 - Creating New MU-Nodes (INSERT mode) on page 502.
The following point relates to the UPDATE mode:
 If you are UPDATING a data parameter of an MU-Node, the row must include the MUNode's Identity, and the appropriate data parameter, but you do not have to include the
Property ID (this is already known by the MU-Node).
In an UPDATE operation, the validation and import will fail if the specified identity
parameter does not exist.
For an example, see 3 - Modifying a Data Parameter of an MU-Node (UPDATE mode) on page
505.
Important: For any one object, an 'identity parameter' on its own in a grid row will never result in an
Update, but an Update would be attempted by ASSET if that object also has one or more 'data
parameters' present in the same grid row.
Hierarchy and Information Flow
The hierarchical dependencies between network elements play a significant part in the import
process. The processing of a row of data will stop at the level where data is detected as invalid.
For example, if the data in the row is invalid at the Property level, it will not proceed down to the
MU-Node or cell level. But if the data is valid at the Property level, and then invalid at the MU-Node
level, the Property data will still be processed, resulting in 'partial processing' of the data in that row.
It is for this reason that consecutive clicks of the Import button may produce different results.
459
ASSET User Reference Guide
Here is an example of how the hierarchical dependency affects the information flow:
 In the Grid Data Loader, you supply the following data:
Property ID
Physical Antenna parameter (and/or Index)
MU-Node Identity
Logical Antenna parameter (and/or Index)
Cell Identity
LA Select (=True)
 You choose INSERT mode.
This is what ASSET does when you run the import process:
1. Creates Property with the supplied ID.
2. Creates Physical Antenna on the Property (auto-assigns the Index No. if not supplied).
3. Creates MU-Node with the supplied Identity, and parents it to the Property.
4. Creates Logical Antenna on the MU-Node (auto-assigns the Index No. if not supplied).
5. Creates Cell with the supplied Identity, and parents it to the MU-Node.
6. Selects the antenna assignment checkbox on the Cell.
Guidelines for the Grid Data Loader
Here are some guidelines that may serve as a useful guide when using the Grid Data Loader.
General
 In most situations, if a valid header is set and there is no equivalent data in that column in a
row, this will cause a validation error for that row. The only exception is where that specific
parameter allows a blank entry. In such a case, an import will update the parameter to
blank in the Site Database (this may of course be intentional).
 You cannot use the Grid Data Loader for renaming any objects.
Grid Structure
 There is no interdependency between the data in different rows. The sequencing of the
rows in the Grid Data Loader has no impact on the results of the import process.
 The sequencing of the columns is unimportant. The data will be automatically gathered into
its proper hierarchical structure. However, you may be more comfortable if you arrange the
columns in a logical visible order.
 Data that exists in the grid will not be included in the import process if the header of that
column is (i) not a valid header or (ii) if it is set to "Ignore".
 Only one instance of each valid header (and therefore the corresponding parameter data)
can exist in each row.
 You can, if required, mix technologies in the same grid, and even in the same row (for
example, if adding a UMTS cell and LTE cell to the same Property). However, it simplifies
validation if each row contains only one technology.
460
About the Grid Data Loader
Import Process
 Whatever the data contents in the Grid Data Loader, no database objects or parameters
will be created or updated unless there is a valid header for the column containing that
data. Any data without a valid column header will be ignored. (Technically speaking, the
import process to the database is based on 'sparse' data fill.)
 When you run the import process, be aware that, if only some of the data is valid, partial
processing of a row may occur. For that reason, for more complex imports, we recommend
that you dedicate some time for validation, in order to avoid unwanted results in the
database.
 The hierarchical dependencies between network elements play a significant part in the
import process. It can result in 'partial processing' of the data. See Hierarchy and
Information Flow on page 459.
 The Grid Data Loader import process works in much the same way as XML Import process.
The only significant difference is that in some situations, the Grid Data Loader attempts to
resolve missing data from the accompanying data.
 The Grid Data Loader uses the same XML schema validation that is used in the XML
Import. In general, this is highly effective, but it cannot protect against very occasional
database errors.
 Data created or modified via the Grid Data Loader is saved for the individual user, into the
'Applied' state.
Using the Grid Data Loader
To use the Grid Data Loader:
1. Read Before Using the Grid Data Loader on page 458.
2. From the Database menu, click Grid Data Loader.
3. In the Settings pane, it is important that you select the 'Import Mode' that you require.
Select either:
o
Insert
o
Update
o
Insert + Update
4. Ensure the header row is correct (unless this is contained in a file you intend to load). See
Setting the Header Row on page 464.
5. Enter the data into the grid using one or more of these methods:
o
Use the Site Database Reports to generate the input data. (See Integrating the Site
Database Reports with the Grid Data Loader on page 466.)
o
Load from a file. (See Loading Data from a File on page 469.)
o
Manual edit. (See Manually Editing the Data Rows on page 471.)
o
Paste from within the grid or from an external source. (See Editing the Data Rows
Using Copy and Paste on page 473.)
6. If you have loaded a file containing a header row, ensure the header row is correct. See
Setting the Header Row on page 464.
7. Click the Validate button (this is optional but recommended).
461
ASSET User Reference Guide
Important: If you click Import without first clicking Validate, the validation process and
messages still occur, but the import may 'partially process' the data, as described in
Hierarchy and Information Flow on page 459. It is valuable to dedicate time to validation
before importing, particularly with large or complex sets of data. If you wish to be in control
of exactly what will be imported, you should always click Validate first.
8. If the validation is unsuccessful, see About the Validation Messages on page 474 to fix the
problems.
- or If the validation is successful, click the Import button.
The 'All items were imported successfully' message appears. You can now see the
changes in the Site Database.
Tip: You can automatically save the created/modified objects from a Grid Data Loader import into
the Selection Filter. This can be a useful way of identifying, checking and reviewing the changes.
See Saving the Contents of an Import into the Selection Filter on page 305.
Setting Preferences
The Preferences in the Grid Data Loader enable you to:
 Limit which technologies, network elements and parameters you want to be available as
column headers.
 Set a logging level and a log files folder.
Note:
 It is advised that you only change the Preferences while you have no data in grid.
Otherwise, any existing headers in the grid that you de-select in the Preferences will then
be set to 'Ignore.'
 If you load a file that includes a header row, any headers that are not included in the
Preferences will be set to 'Ignore'.
To set the Preferences for the Grid Data Loader:
1. From the Database menu, click Grid Data Loader.
2. In the Grid Data Loader, from the File menu, click Preferences.
462
About the Grid Data Loader
The Preferences dialog box appears:
3. In the Preferences dialog box, select the items that you want to be available as column
headers.
Tip: The Show Selected button may be useful to check precisely which items are
selected. The tree list expands to show all current selections.
Where items are grouped by technology or network hierarchy, you can select or de-select
all child items by selecting or clearing the parent item.
4. Set the logging level to Off, Information (logs errors and related information) or Verbose
(logs full task process details).
If you have chosen Information or Verbose, set a destination folder for the log files.
5. Optionally, select 'Extend Keep XML to validation failures' if you want to save any validation
failure files in addition to the successful files (same location). This can help with diagnosis
of problems.
6. Click Apply.
463
ASSET User Reference Guide
Setting the Header Row
When using the Grid Data Loader, you need to ensure that your headers are all valid. See Valid
Headers for Each Object Type on page 477 (also see Sample Header Row Files on page 477).
When a column heading does not contain a valid header, the term 'Ignore' is shown, indicating that
data in any columns without a valid heading will be ignored by the import process.
Note: You can limit which technologies, network elements and parameters you want to be available
as headers (see Setting Preferences on page 462). So if you do not see the items you expect when
creating or loading headers, always check your Preferences settings.
 You can use the drop-down lists to select headers in the Grid Data Loader. This picture
shows an example of the headers you can choose from:
After selecting one of the headers, it appears at the top of the column as shown here:
 You can load, save, and clear sets of headers that you have created:
464
About the Grid Data Loader
To load a set of Headers into the Grid Data Loader:
In the Grid Data Loader, from the File menu, click Load Headers.
Tip: It may be quicker to click Recent Header Files instead.
To save a set of Headers:
In the Grid Data Loader, from the File menu, click Save Headers.
To clear a set of Headers from the Grid Data Loader:
In the Grid Data Loader, from the File menu, click Clear Headers.
Important: You should ensure that each field in the data rows contains valid data that matches
each specified header. For example, if a valid header is set and there is no equivalent data in that
column in a row, this will cause a validation error for that row (the only exception is if the field allows
a blank entry).
Inserting and Deleting Columns
The Grid Data Loader enables you to add or remove columns:
To insert columns into the grid:
1. Right-click on the header row in the column that where you want to start.
The insertion of columns will take place to the left of the selected column.
2. In the dialog box that appears, use the up/down arrows to specify the number of columns
you want to add:
(The maximum number of columns you can add depends on the current content of the grid.
The absolute maximum is 150.)
3. Click Apply.
To delete columns from the grid:
1. Right-click on the header row in the column that where you want to start.
The deletion of multiple columns will start at the selected column and then continue to the
right. The deletion operation takes no account of whether a column header is valid or
invalid. The minimum number of columns is 1.
465
ASSET User Reference Guide
2. In the dialog box that appears, specify the number of columns you want to remove:
(The maximum number of columns you can delete depends on the current content of the
grid. At least one column must always remain.)
3. Click Apply.
For information on inserting or deleting rows, see Inserting and Deleting Rows on page 472.
Tips:
 To clear the grid and start afresh, you can click New from the File menu. But be aware this
will clear all columns, rows and data, so ensure you save it first if you need it later.
 You can re-order the columns by clicking on a column header and dragging it left or right to
its new position.
Integrating the Site Database Reports with the Grid Data Loader
There are various ways you can enter data into the Grid Data Loader. These are described in
About the Grid Data Loader on page 457.
One method is to use the Site Database Reports dialog box to generate the data. This may prove
very useful and convenient when making multiple changes to your existing network data.
A typical use case is where you want to perform a bulk UPDATE of your existing network data, for
example modifying a cell setting on all the cells, with the benefit of clear visibility of the data within
rows and columns.
This method has the advantage of using an easy selection facility to choose what you require. You
can then use the data as input to the Grid Data Loader.
This method provides some major benefits:
 Rapid editing of data that is already in your database
 Easy selection facility to choose the parameters that you require
 Automatic creation of the column headers that are compatible with the Grid Data Loader
Afterwards, you can use the Grid Data Loader in the normal way, performing the validation and
import procedures to update your database.
466
About the Grid Data Loader
This picture shows the Report Into drop-down box with the 'Grid Data Loader' option selected:
Example of Site Database Reports dialog box
Note: The steps for opening the Site Database Reports dialog and performing the above process
are described in Using Site Database Reports Data as Input to Grid Data Loader on page 468.
The Site Database Reports dialog box can output the generated results directly into the Grid Data
Loader. However, you may prefer to visualise and manipulate the data in an output file first. For this
reason, you have a choice of your default preference:
 Grid Data Loader Direct
 Excel File
 CSV File
If you choose one of the output file options, you would subsequently need to load the file into the
Grid Data Loader (see Loading Data from a File on page 469).
For the complete procedure for this method, see Using Site Database Reports Data as Input to Grid
Data Loader on page 468.
467
ASSET User Reference Guide
Notes:
 The Grid Data Loader supports GSM, UMTS, LTE and 5G. When interacting with the Site
Database Reporter, you can only use one technology at a time.
 The Grid Data Loader supports many, but not all of the items in the database (see Valid
Headers for Each Object Type on page 477).
 Within the above technologies, the items selected in the Site Database Reports dialog box
that are supported by the Grid Data Loader will each map to an automatically created
header column (that is, a valid header for the Grid Data Loader) directly in the Grid Data
Loader or within an output file, according to the chosen preference.
 Within the above technologies, any selected items that are not supported by the Grid Data
Loader will each map to (according to the chosen preference):
o
A column header named 'Ignore', if output is direct to the Grid Data Loader.
o
A column header persisted with the original name in the Site Database Reports dialog
box in an output file. When loaded, this would be renamed 'Ignore', to indicate that the
data in that column will be ignored by the import process.
 The 'Excel file' and 'CSV file' options within the Grid Data Loader Preferences are distinct
from the 'Excel' and 'Text Editor' options in the Report Into drop-down box. The latter pair
are the basic Site Database Reports outputs, and they cannot be loaded into the Grid Data
Loader. For a complete description of using the Site Database Reports (without the
involvement of the Grid Data Loader), see 'Generating Site Database Reports' in the
ASSET Radio User Reference Guide.
Using Site Database Reports Data as Input to Grid Data Loader
You can use the Site Database Reports dialog box to generate data as an input to the Grid Data
Loader.
Important:
 Before proceeding, please read the information, notes and options in Integrating the Site
Database Reports with the Grid Data Loader on page 466.
 If you intend to output the data directly to the Grid Data Loader ('Grid Data Loader Direct'),
ensure that the Grid Data Loader dialog box is closed first.
 The steps below relate specifically to the interaction between the Site Data Reports and the
Grid Data Loader. For a complete description of using the Site Database Reports facility
(without the involvement of the Grid Data Loader), see 'Generating a Site Database Report'
in the ASSET Radio User Reference Guide.
To do this:
1. On the main toolbar, click the Site Database Reports
button.
The Site Database Reports dialog box appears.
2. In the Filter drop-down box: Select a filter for the Properties/MU-Nodes/Cells/Antennas you
want to include in the report.
3. In the Report Into drop-down box: Select 'Grid Data Loader' from the drop-down list.
4. Click the GDL Preferences button.
468
About the Grid Data Loader
5. Choose the option for the output data:
(The chosen option will be the default on future occasions whenever you Report Into Grid
Data Loader and click Generate.)
6. Click OK.
7. On the tabs of the Site Database Reports dialog box (taking into account the above notes),
select the information you want to extract from the database.
8. Click Generate.
If you chose Excel file or CSV file in the Preferences, the report will be generated. You can
then edit it as required, before loading the file into the Grid Data Loader.
- or If you chose 'Grid Data Loader Direct' in the Preferences, the Grid Data Loader will open
automatically, showing the data that was generated. You can then check, edit and validate
it as required, within the Grid Data Loader.
See Using the Grid Data Loader on page 461 for information on the remaining steps in the Grid
Data Loader (checking the header row, validating and importing into the database).
Loading Data from a File
This section describes how to get data into the grid by loading a file. (For the complete process of
using the Grid Data Loader from start to finish, see Using the Grid Data Loader on page 461.)
Prerequisites
Note: The prerequisites may not be necessary if you are loading a file that you already exported
from the Grid Data Loader.
 Prepare the file and ensure the data in the file is delimited in some way (such as tab,
space, comma).
 Ensure that the file name suffix is in lower case (otherwise a corrupted preview will result).
 Optionally, check that your header rows are all valid (or you can attend to this later). See
Setting the Header Row on page 464.
 Ensure the Import Mode (Insert, Update) is set as required (in case you forget to set this
after the file is loaded).
469
ASSET User Reference Guide
To load a file into the Grid Data Loader:
1. In the Grid Data Loader, from the File menu, click Load.
Tip: If you have loaded the file on a previous occasion, it may be quicker to click Recent
Files.
2. In the dialog box that appears, select the file type in the drop-down list that matches your
file format.
3. Browse to your file and click Open.
The File Import dialog box appears as in this example (depending on the size of the file,
this may take a few seconds):
ASSET reads the file and will determine the most probable Delimiter (Tab, Comma and so
on). But you can modify this, if required, and see the effect on the layout of the data.
ASSET also determines the Header Row settings based on whether it identifies one or
more valid headers in the file. However, you can control how the Grid Data Loader treats
the first row of the file. This table describes the options:
Header Row Settings
Description
The Grid Data Loader will consider the first row of the loaded file as a
data entry row (not a header row). It assumes that you will map the
headers in the grid of the Grid Data Loader after loading the file.
The Grid Data Loader will consider the first row of the loaded file as a
header row (but it will set any headers that are invalid to "Ignore").
Where there are headers that already exist in the Grid Data Loader but
do not exist in the load file, this will modify such headers to "Ignore".
Note: This is only for the number of columns from left-to-right in the grid
that correspond to the number of columns in the file. Any other columns
in the grid are left unchanged.
4. Click the Load button.
470
About the Grid Data Loader
The file is loaded and the contents of the file appear in the Grid Data Loader, as in this
example:
Note: The Load operation always populates the grid from the top-left cell.
5. To continue with the remaining steps (checking the header row, validating and importing),
see Using the Grid Data Loader on page 461.
Manually Editing the Data Rows
The Grid Data Loader enables you to enter or amend data in the grid manually (this is also an
option after loading a file).
When you right click in the grid, the menu offers the following options:
You can also use the keyboard (Ctrl, Ctrl+Shift, and so on) to multi-select fields, and then perform
the above options. To select a whole row, click on the left side of the grid at the beginning of the
row.
Note: The sequencing of the rows has no direct impact on the import process. The sequence used
to for the import is random.
For information on inserting or deleting rows, see Inserting and Deleting Rows on page 472.
Grid Symbols
At the left side of the grid, at the beginning of each row, you may see these symbols:
Symbol
Description
This symbol is important because it shows the last selected row. Also, if you perform any of
the right-click options (such as Copy, Clear or Delete Row), this will be the affected row.
This symbol appears when you are editing any field in a row. The symbol only disappears
when you press Enter or when you move to another field.
This symbol indicates the final 'dummy' row that contains no data. It is always present in the
grid.
471
ASSET User Reference Guide
For information on inserting or deleting columns, see Inserting and Deleting Columns on page 465.
Tip: To clear the grid and start afresh, you can click New from the File menu. But be aware this will
clear all columns, rows and data, so ensure you save it first if you need it later.
Inserting and Deleting Rows
The Grid Data Loader enables you to add new rows or remove existing rows:
Important:
 The insertion of rows always occurs above the selected row.
 The deletion operation takes no account of whether a row contains data or not.
Inserting a Single Row
1. Select the appropriate row, so that the
symbol appears at the beginning of the row.
2. Right-click, and then click Insert Row(s).
The new row is inserted.
Inserting Multiple Rows
1. Multi-select the required number of rows.
2. Right-click, and then click Insert Row(s).
The same number of new rows are inserted.
(Example: If you multi-select 12 rows, 12 new rows will be inserted.)
Deleting a Single Row
1. Select the appropriate row, so that the
2. Right-click, and then click Delete Row(s).
The row is deleted.
Deleting Multiple Rows
1. Multi-select the required number of rows.
2. Right-click, and then click Delete Row(s).
The selected rows are deleted.
472
symbol appears at the beginning of the row.
About the Grid Data Loader
Editing the Data Rows Using Copy and Paste
The Grid Data Loader's right-click menu enables you to use standard copy/paste functionality within
Grid Data Loader:
You can:
 Clear, Cut, Copy and Paste data within the grid
 Paste data from an external source (such as Excel)
You may want to select, copy and paste data relating to specific rows or fields, you can use the
keyboard (Ctrl, Ctrl+Shift, and so on) to multi-select the required items.
Tip: To select a whole row, click on the left side of the grid at the start of the row, so that the
symbol appears. You can then use the Ctrl and Shift keys to include other rows in the selection.
In some situations, you may want to multi-select specific fields (rather than whole rows or columns).
The field selections do not have to be contiguous, but the field selections for each row and column
must be uniform.
Here are two examples of uniform selections and what the pasted items would look like:
Example 1
Example 1 (copied items)
Example 1 (after pasting)
Example 2
Example 2 (copied items)
Example 2 (after pasting)
In the above examples, non-selected rows or columns will be ignored in the copy and paste
operation (that is, the paste will act in a contiguous manner).
Most of the above information is also relevant to the exporting of files. See Exporting (Saving) a File
on page 476.
473
ASSET User Reference Guide
Note: When you use Paste, you can populate the grid from any cell, whichever one you click on.
The data fill will spread right and downwards from that cell.
Editing the Data Rows Using Paste Special
Within the Grid Data Loader's right-click menu, there is a Paste Special option:
When you choose this option, a dialog box appears. Here is an example:
Paste Special dialog box
This is of particular relevance to pasting data from an external source (such as Excel). It provides
extra control over how the data will be pasted.
It gives you the chance to: check how the data will be formed into rows and columns, before you
paste the data into the grid.
The Paste Special dialog box works in a similar way to the File Import dialog box. For a description
of the options, see Loading Data from a File on page 469.
Note: When you use Paste Special, you can populate the grid from any cell, whichever one you
click on. The data fill will spread right and downwards from that cell.
474
About the Grid Data Loader
About the Validation Messages
After you have clicked Validate in the Grid Data Loader, the validation process takes place.
Important: If you click Import without first clicking Validate, the validation process and messages
still occur, but the import may 'partially process' the data, as described in Hierarchy and Information
Flow on page 459. It is valuable to dedicate time to validation before importing, particularly with
large or complex sets of data. If you wish to be in control of exactly what will be imported, you
should always click Validate first.
The validation process checks all the rows included in the grid.
To see the result for each row, click on the row so that the
symbol shows.
If all rows pass validation, the 'All items were validated successfully' pop-up message appears.
Otherwise, one or more of the rows will have failed.
When a row fails validation, an error icon appears at the start of the row, as in this example:
And an appropriate failure message appears in the Messages pane of the Grid Data Loader:
You can click on any individual row to read its validation message.
In more complex situations, the Messages pane of the Grid Data Loader may prompt you to check
the general Message Log:
And the more comprehensive information appears in the Message Log, as in this example:
Important: In situations where some of the rows have passed and some have failed, or where the
data in some columns within the same row are valid, but the data in some columns are not valid,
you can still click Import if you are sure you want to proceed. In both cases, the valid data will be
imported into the database, and the appropriate import messages appear in the Messages pane of
the Grid Data Loader.
475
ASSET User Reference Guide
Exporting (Saving) a File
You can export a file from the Grid Data Loader in *.csv format. When you do this, you have the
option to:
 Change the data delimiter (Tab, Comma, and so on) to influence the formation of the
columns of data.
 Include or exclude the Header Row.
 Include or exclude the Data (and the Results if you have validated the data)
 Export the whole grid, or export specifically selected rows, columns or fields.
For information on selecting specific sections, see Editing the Data Rows Using Copy and
Paste on page 473.
Notes:
o
In the case where only one field in the grid is selected (which is the default behaviour of
the grid), the entire grid is exported.
o
In the case where non-uniform selections are made, the entire grid is exported.
To export a file from the Grid Data Loader:
1. From the Database menu, click Grid Data Loader.
2. Ensure that the existing content (headers, data, rows, columns) of the grid is how you want
it to be.
3. If you want to export specific sections (as explained above), make the required selections in
the grid.
4. In the Grid Data Loader, from the File menu, click Export.
In the Export Options dialog box, choose the options you require, as described above.
5. Click Save.
For information on loading an exported file into the Grid Data Loader, see Loading Data from a File
on page 469.
Creating a New File
You can create a new file in the Grid Data Loader. Normally, this is not necessary, because the grid
starts afresh each time you open the Grid Data Loader (there is no persistence from a previous
session). However, it can be a useful way of quickly clearing the grid.
Warning: This will remove any data entries that already exist in the Grid Data Loader.
To create a new file in the Grid Data Loader:
1. From the Database menu, click Grid Data Loader.
2. In the Grid Data Loader, from the File menu, click New.
476
About the Grid Data Loader
Valid Headers for Each Object Type
In the header row of the Grid Data Loader, you can specify which headers you want to be present
in the grid. See Setting the Header Row on page 464.
Tip: Sample XML files of header rows are provided with your ASSET installation. See Sample
Header Row Files on page 477.
Each header is based on an Object Type and an associated parameter (which is an 'identity
parameter' or a 'data parameter').
The most important (high-level) Object Types are:
 Property
 MU-Node
 Cell
 Link
Property is relevant to ASSET Radio and ASSET Backhaul.
MU-Node and Cell is relevant only to ASSET Radio.
Link is relevant only to ASSET Backhaul.
The following sections contain lists of the supported parameters for the above Object Types.
Note: The parameters are in alphabetic order in the Grid Data Loader user interface. In general,
these sections list the parameters in the same way, except that the 'identity parameter' is at the top.
Sample Header Row Files
Sample XML files of header rows are provided with your ASSET installation. Assuming you use the
default installation, you can locate them here:
C:\Program Files\TEOCO\ASSET\Samples\Grid Data Loader - Header files\
This enables you to use the Load Headers option to load any of these ready-made header rows
into the Grid Data Loader. You can then refine the sample header row by adding or removing (or
'Ignore') headers, and use the Save Headers option to save it as a customised header row for
future use.
For information on creating, loading, saving and clearing header rows, see Setting the Header Row
on page 464.
Note: You can limit which technologies, network elements and parameters you want to be available
as headers (see Setting Preferences on page 462). So if you do not see the items you expect when
creating or loading headers, always check your Preferences settings.
Object Type: Property
Parameters supported at the Property level.
(Allowable Values and Comments are only added where applicable.)
477
ASSET User Reference Guide
Valid Header for each Supported Parameter
Allowable Values
Property: ID
Comments
String - no spaces
Property: Address 1
Property: Address 2
Property: County
Property: Fields
According to whether the
field type is Boolean, Date
and Time, Float, Integer or
Picklist.
Property: Post Code
Property: Property Code
Property: State
Property: Town
Valid Header for each Supported Parameter
Allowable Values
Comments
'EN' or 'decLL' or 'LL'
See About the
Location
Parameters on
page 500.
Valid Header for each Supported Parameter
Allowable Values
Comments
Property: Physical Antenna: Antenna Device
'Unknown', 'Default', or any
valid Device ID
Property: Physical Antenna: Azimuth (deg)
0-359
Property: Location: EPSG
Property: Location: Units
Property: Location: X Coordinate
Property: Location: Y Coordinate
Property: Physical Antenna: Height - Inventory (m)
Property: Physical Antenna: Height - Offset (m)
Property: Physical Antenna: Index
Positive number >0
See About
Antenna Indexes
on page 500.
Property: Physical Antenna: Location: Absolute/Relative
'ABS' or 'REL'
See About the
Location
Parameters on
page 500.
Property: Physical Antenna: Location: EPSG
Property: Physical Antenna: Location: Units
Property: Physical Antenna: Location: X Coordinate
Property: Physical Antenna: Location: Y Coordinate
Property: Physical Antenna: Master Patterns: Master
Pattern 1
... and the same for Master Pattern [2 ... 8]
Any valid pattern existing on
the specified or existing
device.
Property: Physical Antenna: Mechanical Down Tilt (deg)
Property: Physical Antenna: RET Groups
Property: Physical Antenna: Twist (deg)
478
Any combination of
A,B,C,D,E,F,G,H,I,J,K,L,M,N
,
O,P,Q,R,S,T
Determines which
groups are
available on child
logical antennas.
About the Grid Data Loader
Valid Header for each Supported Parameter
Allowable Values
Comments
Property: Logical Antenna: Assigned RET Group
A,B,C,D,E,F,G,H,I,J,K,L,M,N,
O,P,Q,R,S,T or -
Dependent on
RET Group values
at parent physical
antenna.
(singular value allowed or '-'
to clear
Property: Logical Antenna: Beam Set ID
Any valid beam set name
Only relevant to
Switched Beam
antennas.
Positive number >0
See About
Antenna Indexes
on page 500.
'0' or '1'
'0' represents
Primary/Secondar
y mode.
Property: Logical Antenna: DL Correction Gain (dB)
Property: Logical Antenna: Electrical Tilt (deg)
Property: Logical Antenna: Frequency
Property: Logical Antenna: Index
Important: See note at end of this table.
Property: Logical Antenna: Inner/Outer Mode
'1' represents
Inner/Outer mode.
See the
references in
Overview of
Pathloss
Predictions.
Property: Logical Antenna: Instance ID
Property: Logical Antenna: Master Pattern Inheritance
0,1,2,3,4,5,6,7 or 8
0 = Do Not Inherit
Property: Logical Antenna: Parent Physical Antenna
Index
Positive number >0
See About
Antenna Indexes
on page 500.
Property: Logical Antenna: Pattern
Any valid pattern existing on
the specified or existing
device.
Property: Logical Antenna: UL Correction Gain (dB)
Note: For the "Property: Logical Antenna: Index" parameter, there is a design restriction
that when you are creating a new logical antenna, the import process will automatically generate
the index number. So we advise not to include this parameter in this situation. However, the
parameter can be included if you are updating a logical antenna.
Valid Header for each Supported Parameter
Allowable Values
Property: Logical Antenna: Primary Prediction: Model
'Unknown', or any valid entry
Property: Logical Antenna: Primary Prediction: Radius (km)
Property: Logical Antenna: Primary Prediction: Resolution (m)
Valid Header for each Supported Parameter
Allowable Values
Property: Logical Antenna: Secondary Prediction: Model
'Unknown', or any valid entry
Property: Logical Antenna: Secondary Prediction: Radius (km)
Property: Logical Antenna: Secondary Prediction: Resolution (m)
479
ASSET User Reference Guide
Object Type: MU-Node
Parameters supported at the MU-Node level.
The MU-Node object can accommodate a single technology or multiple technologies. For more
information, see 'About MU-Nodes' in the ASSET Radio User Reference Guide.
In the Grid Data Loader, it can comprise any mixture of:
 GSM BTS
 UMTS Node B
 LTE eNodeB
 5G (NR) gNodeB
 NB-IoT
For that reason, the table below shows the complete list of the headers, for all technologies.
Tip: When using the Grid Data Loader, it is generally easier to control if you use a single
technology at a time (see Guidelines for the Grid Data Loader on page 460).
The valid headers for the MU-Node (assuming you have all the technology licences) are shown in
the table below:
(Allowable Values and Comments are only added where applicable.)
Valid Header for each Supported Parameter
Allowable Values
MU Node: Identity
Comments
String - no spaces
MU Node: 1st Name
MU Node: 2nd Name
MU Node: Comments
MU Node: DC-Identity
Blank or any valid
identity
MU Node: EN-DC
480
MU Node: Fields
According to whether the
field type is Boolean,
Date and Time, Float,
Integer or Picklist.
MU Node: Fixed Technology Mode
'TRUE' or 'FALSE'
MU Node: GSM Cabin Equipment
'Unknown', or any valid
identity
MU Node: GSM Site Equipment
'Unknown', or any valid
identity
MU Node: GSM Technology Active
'TRUE' or 'FALSE'
MU Node: GSM Tower Equipment
'Unknown', or any valid
identity
MU Node: Inter-Node DC
'YES' or 'NO'
MU Node: Is NFV Element
'YES' or 'NO'
Corresponds to the
'Enable Technology'
checkbox in the Site
Database.
About the Grid Data Loader
Valid Header for each Supported Parameter
Allowable Values
Comments
MU Node: LTE Carriers
Any valid carrier name
Example of specifying
multiple values:
'Carrier1,Carrier4'
MU Node: LTE Technology Active
'TRUE' or 'FALSE'
Corresponds to the
'Enable Technology'
checkbox in the Site
Database.
MU Node: LTE-DC
'YES' or 'NO'
MU Node: NB-IoT Carriers
Any valid carrier name
Example of specifying
multiple values:
'Carrier1,Carrier4'
MU Node: NB-IoT Technology Active
'TRUE' or 'FALSE'
Corresponds to the
'Enable Technology'
checkbox in the Site
Database.
MU Node: NE-DC
'YES' or 'NO'
MU Node: eLTE NB
MU Node: LTE eNB ID
MU Node: NFV Host Server ID
MU Node: Node-Id
'Unknown', or any valid
identity
MU Node: NR Carriers
Any valid carrier name
Example of specifying
multiple values:
'Carrier1,Carrier4'
MU Node: NR Technology Active
'TRUE' or 'FALSE'
Corresponds to the
'Enable Technology'
checkbox in the Site
Database.
MU Node: NR-DC
'YES' or 'NO'
MU Node: Parent PLMN
Any valid PLMN Network If not specified it will use
Identity
the default PLMN.
MU Node: UMTS Carriers
Any valid carrier name
MU Node: UMTS Node B Type
'Unknown', or any valid
identity
MU Node: UMTS Technology Active
'TRUE' or 'FALSE'
Corresponds to the
'Enable Technology'
checkbox in the Site
Database.
Valid Header for each Supported Parameter
Allowable Values
Comments
MU Node: NR gNB ID
Example of specifying
multiple values:
'Carrier1,Carrier4'
MU Node: Latency: Assigned Table
MU Node: Latency: enable Backhaul Support
MU Node: Latency: Fixed Network Delay
MU Node: Latency: total Served Traffic
MU Node: Latency: Transmission Capacity
481
ASSET User Reference Guide
Object Type: Cell
Parameters supported at the Cell level.
The Cell object can accommodate a single technology or multiple technologies. For more
information, see 'About Cells' in the ASSET Radio User Reference Guide.
In the Grid Data Loader, it can comprise any mixture of:
 GSM Cell
 UMTS Cell
 LTE Cell
 5G (NR) Cell
 NB-IoT Cell
When using the Grid Data Loader, it is generally easier to control if you use a single technology at a
time (see Guidelines for the Grid Data Loader on page 460). Therefore, it may be easier to look at
the appropriate technology-specific topic.
For that reason, the table below only shows the list of parameters common to all technologies, and
the subsequent sections will focus on the technology-specific headers.
(Allowable Values and Comments are only added where applicable.)
Valid Header for each Supported Parameter
Allowable Values
Cell: Identity
String - no spaces
Cell: Active Technology
'GSM' or 'UMTS' or 'LTE'
or '5G' or 'NB-IoT (or '-'
for Not Active)
Cell: Fields
According to whether the
field type is Boolean,
Date and Time, Float,
Integer or Picklist.
Cell: Fixed Technology Enabled
'TRUE' or 'FALSE'
Cell: Physical Parent Identity
Cell: Technology (Identifier)
This only has an effect
on Variable cells.
Set Variable cell to Fixed
or vice versa.
String - no spaces
'GSM' or 'UMTS' or 'LTE'
or '5G' or 'NB-IoT' (or '-'
for Variable)
(The Variable option
would be used if you
have a mixture of Fixed
and Variable cells.)
Valid Header for each Supported Parameter
Allowable Values
Cell: Logical Antenna: 5G Technology Enabled
'YES' or 'NO'
Cell: Logical Antenna: Feeder Length (m)
482
Comments
Cell: Logical Antenna: Feeder Type
'Unknown', or any valid
entry
Cell: Logical Antenna: GSM Technology Enabled
'YES' or 'NO'
Cell: Logical Antenna: LTE Technology Enabled
'YES' or 'NO'
Mandatory if you are
using 'Fixed Technology'
cells on your network.
This is because fixed
cells with separate
technologies can share
the same identity.
See About the
Technology (Identifier)
Parameter on page 503.
Comments
About the Grid Data Loader
Valid Header for each Supported Parameter
Allowable Values
Comments
Cell: Logical Antenna: MHA Gain (dB)
Cell: Logical Antenna: MHA Type
'Unknown', or any valid
entry
Cell: Logical Antenna: NB-IoT Technology Enabled
'YES' or 'NO'
Cell: Logical Antenna: Physical Parent Identity
String - no spaces
Cell: Logical Antenna: Select
'YES' or 'NO'
This is useful when you
are inserting an antenna
at the Cell level, and you
want the antenna to be
assigned in the same
action. It is also useful if
you want to select or deselect all antennas on an
existing cell.
Cell: Logical Antenna: Selection(s)
1, 2, and so on
This is the Index No. of
the Logical Antenna.
Example of specifying
multiple values:
'1,2,3'
Also see About Antenna
Indexes on page 500.
Cell: Logical Antenna: UMTS Technology Enabled
'YES' or 'NO'
Parameters supported at the GSM Cell level
(Allowable Values and Comments are only added where applicable.)
Valid Header for each Supported Parameter
Allowable Values Comments
Cell: GSM: Cell Equipment
Unknown', or any
valid entry
Cell: GSM: Cell Name
Cell: GSM: CGI
'Unknown', or any
valid entry
Cell: GSM: Enabled
'TRUE' or 'FALSE'
Cell: GSM: GSM ID
'Unknown', or any
valid entry
Corresponds to the
'Technology
Supported' checkbox
in the Site Database.
Cell: GSM: Indoor Clutter Loss Schema
Cell: GSM: LAC
'Unknown', or any
valid entry
Cell: GSM: MCC
'Unknown', or any
valid entry
Cell: GSM: MNC
'Unknown', or any
valid entry
Cell: GSM: RAC
'Unknown', or any
valid entry
483
ASSET User Reference Guide
Valid Header for each Supported Parameter
Allowable Values Comments
Cell: GSM: BSIC: BCC
'Unknown', or any
valid entry
Cell: GSM: BSIC: NCC
'Unknown', or any
valid entry
Valid Header for each Supported Parameter
Allowable Values Comments
Cell: GSM: Cell Service: Area (km2)
'Unknown', or any
valid entry
Cell: GSM: Cell Service: Range (km)
'Unknown', or any
valid entry
Parameters supported at the GSM Subcell level
(Allowable Values and Comments are only added where applicable.)
Note: When making changes or additions involving subcells, you must specify at least GSM
Subcell Identity and the Cell Identity of its parent.
Valid Header for each Supported Parameter
Allowable Values
Cell: GSM: Subcell: Identity
Comments
This is the identity of the
Cell Layer used on the
subcell (it appears on the
SubCell tab in the Site
Database).
Cell: GSM: Subcell: Antenna PA Output (inc. EIRP)
Cell: (dBm)
Cell: GSM: Subcell: CS Traffic (E)
Cell: GSM Subcell: Signal Offset (dB)
Cell: GSM Subcell: Signal Threshold (dBm)
Cell: GSM Subcell: Subcell ID
Cell: GSM Subcell: Subcell Name
Cell: GSM Subcell: TA Threshold
Valid Header for each Supported Parameter
Allowable Values
Comments
Cell: GSM Subcell: Allocated MA List
Any valid Carrier Layer
name.
For allocating Carrier
Layers designated as MA
Lists.
Cell: GSM Subcell: Associated MA List: Allocation
Any valid Carrier Layer
name.
For associating Carrier
Layers designated as MA
Lists.
Cell: GSM Subcell: Carrier Layer: Allocated Carriers
1, 2, 3, and so on.
Example of specifying
multiple values:'1,4,7,10'
Cell: GSM Subcell: Carrier Layer: Allocation
Any valid Carrier Layer
name.
For normal Carrier Layers
that are not designated as
MA Lists.
1, 2, 3, and so on.
Example of specifying
multiple values:'1,4,7,10'
Cell: GSM Subcell: Carrier Layer: Carriers Required
Cell: GSM Subcell: Carrier Layer: Fixed Carriers
484
About the Grid Data Loader
Valid Header for each Supported Parameter
Allowable Values
Comments
Cell: GSM Subcell: Carrier Layer: Forbidden Carriers
1, 2, 3, and so on.
Example of specifying
multiple values:'1,4,7,10'
Cell: GSM Subcell: Carrier Layer: Hopping
'YES' or 'NO'
Cell: GSM Subcell: Carrier Layer: TRX Required
Cell: GSM Subcell: Carrier Layer: Total TRX
Allocation
Valid Header for each Supported Parameter
Allowable Values
Comments
Cell: GSM Subcell: Hopping: HSN
Cell: GSM Subcell: Hopping: MAIO Offset
Cell: GSM Subcell: Hopping: MAIO Step
Cell: GSM Subcell: Hopping: MALID
Cell: GSM Subcell: Hopping: Status
'HoppingOn' or
'HoppingOff'
Cell: GSM Subcell: Hopping: Type
'BaseBand', 'Synthesiser'
or 'SiteHop'
Parameters supported at the UMTS Cell level
(Allowable Values and Comments are only added where applicable.)
Valid Header for each Supported Parameter
Allowable Values
Comments
Cell: UMTS: Active Set Size
Cell: UMTS: AICH Power (dBm)
Cell: UMTS: Assigned Carrier
Any valid entry assigned
to parent node
Cell: UMTS: Cell Id
'Unknown', or any valid
entry
Cell: UMTS: Cell Name
Cell: UMTS: C-RAN Group ID
Cell: UMTS: Enabled
'TRUE' or 'FALSE'
Corresponds to the
'Technology
Supported' checkbox
in the Site Database.
Cell: UMTS: HSDPA Power (dBm)
Cell: UMTS: HS-SCCH Power (dBm)
Cell: UMTS: Indoor Loss Clutter Schema
Cell: UMTS: LAC
'Unknown', or any valid
entry
Cell: UMTS: Local Cell Id
'Unknown', or any valid
entry
Cell: UMTS: Max TX Power (dBm)
Cell: UMTS: Mean HSDPA DL Traffic Power (dBm)
Cell: UMTS: Mean UL Noise Rise (dB)
Cell: UMTS: Mean UMTS DL Traffic Power (dBm)
485
ASSET User Reference Guide
Valid Header for each Supported Parameter
Allowable Values
Comments
Cell: UMTS: Noise Figure (dB)
Cell: UMTS: Noise Rise Limit (dB)
Cell: UMTS: Orthogonality Factor
Cell: UMTS: P-CCPCH Power (dBm)
Cell: UMTS: PICH Power (dBm)
Cell: UMTS: Pilot Power (dBm)
Cell: UMTS: P-SCH Power (dBm)
Cell: UMTS: RAC
'Unknown', or any valid
entry
Cell: UMTS: SAC
'Unknown', or any valid
entry
Cell: UMTS: S-CCPCH Power (dBm)
Cell: UMTS: Scrambling Code ID
'Unknown', or any valid
entry
Cell: UMTS: Soft Handover Window (dB)
Cell: UMTS: S-SCH Power (dBm)
Cell: UMTS: URA1
... and the same for URA[2 ... 8]
'Unknown', or any valid
entry
Valid Header for each Supported Parameter
Allowable Values
Cell: UMTS: Cell Service: Area (km2)
'Unknown', or any
valid entry
Cell: UMTS: Cell Service: Range (km)
'Unknown', or any
valid entry
Comments
Parameters supported at the LTE Cell level
(Allowable Values and Comments are only added where applicable.)
Valid Header for each Supported Parameter
Allowable Values
Cell: LTE: Assigned Carrier
Any valid entry
assigned to parent
node
Cell: LTE: Avg Num of Connected Users
Cell: LTE: Broadcast Offset
Cell: LTE: Carrier Aggregation Cell ID
Cell: LTE: Cell Name
Cell: LTE: Control Offset
Cell: LTE: C-RAN Group ID
Cell: LTE: DL Cell Centre Load (%)
Cell: LTE: DL Cell Edge Load (%)
Cell: LTE: DSS Identity
Cell: LTE: DSS Max MBSFN Subframes
Cell: LTE: DSS Min MBSFN Subframes
486
Comments
About the Grid Data Loader
Valid Header for each Supported Parameter
Allowable Values
Comments
Cell: LTE: DSS Non-MBSFN Symbols/Subframe
Cell: LTE: DSS Reserved PRACH RBs
Cell: LTE: DSS Reseved Traffic DL
Cell: LTE: DSSReserved Traffic UL
Cell: LTE: DSS Support CRS Rate Matching
'YES' or 'NO'
Cell: LTE: DSS Support DL
'YES' or 'NO'
Cell: LTE: DSS Support UL
'YES' or 'NO'
Cell: LTE: ECI
'Unknown', or any
valid entry
Cell: LTE: eICIC Cell Centre Downlink ABS Pattern
custom mask
Any valid entry
Cell: LTE: eICIC Cell Centre Downlink ABS Pattern
name
Any valid entry
Cell: LTE: eICIC Cell Centre Uplink ABS Pattern
custom mask
Any valid entry
Cell: LTE: eICIC Cell Centre Uplink ABS Pattern name
Any valid entry
Cell: LTE: eICIC Cell Edge Downlink ABS Pattern
custom mask
Any valid entry
Cell: LTE: eICIC Cell Edge Downlink ABS Pattern name Any valid entry
Cell: LTE: eICIC Cell Edge Uplink ABS Pattern custom
mask
Any valid entry
Cell: LTE: eICIC Cell Edge Uplink ABS Pattern name
Any valid entry
Cell: LTE: eICIC Schemes Enabled
'YES' or 'NO'
Cell: LTE: Enable Carrier Aggregation
'YES' or 'NO'
Cell: LTE: Enabled
'TRUE' or 'FALSE'
Cell: LTE: First Assigned RSI
'Unknown', or any
valid entry
Cell: LTE: ICIC Enabled
'YES' or 'NO'
Corresponds to the
'Technology Supported'
checkbox in the Site
Database.
Cell: LTE: Indoor Clutter Loss Schema
Cell: LTE: Max TX Power (dBm)
Cell: LTE: Noise Figure (dB)
Cell: LTE: Number of assigned RSIs
'Unknown', or any
valid entry
Cell: LTE: Number of required RSIs
'Unknown', or any
valid entry
Cell: LTE: PCI ID
'Unknown', or any
valid entry
Cell: LTE: PCI Schema
Any valid entry
Cell: LTE: Power Auto-Calculate Method
'Off' or 'Max TX
Power' or 'Ref Signal
PPRE'
Cell: LTE: Preamble Format
'Unknown', or any
valid entry
Cell: LTE: Reference Signal PPRE
Any valid entry
487
ASSET User Reference Guide
Valid Header for each Supported Parameter
Allowable Values
Cell: LTE: RSI Schema
Any valid entry
Comments
Cell: LTE: RSRP Offset (dB)
Cell: LTE: RSRP Offset Enabled
'YES' or 'NO'
Cell: LTE: SU-MIMO Downlink Enabled
'YES' or 'NO'
Cell: LTE: SU-MIMO Downlink Spatial Mode
'Diversity' or
'Multiplexing' or
'AdaptiveSwitching'
Cell: LTE: SU-MIMO RX Elements
Cell: LTE: SU-MIMO TX Elements
Cell: LTE: SU-MIMO Uplink Enabled
'YES' or 'NO'
Cell: LTE: SU-MIMO Uplink Spatial Mode
'Diversity' or
'Multiplexing' or
'AdaptiveSwitching'
Cell: LTE: Synchronisation Offset
Cell: LTE: TAC
Unknown', or any
valid entry
Cell: LTE: Timing Advance (yes/no)
'YES' or 'NO'
Cell: LTE: Timing Advance Mode
'MaxTA' or
'MaxRange'
Cell: LTE: Traffic Offset
Cell: LTE: UL Cell Centre Load (%)
Cell: LTE: UL Cell Edge Load (%)
Valid Header for each Supported Parameter
Allowable Values
Cell: LTE: Cell Service: Area (km2)
'Unknown', or any
valid entry
Cell: LTE: Cell Service: Range (km)
'Unknown', or any
valid entry
Valid Header for each Supported Parameter
Allowable Values
Cell: LTE: Timing Advance: Max Range (km)
Any valid entry
Cell: LTE: Timing Advance: Max TA (msec)
Any valid entry
Valid Header for each Supported Parameter
Allowable Values
Cell: LTE: Latency: CPRI Length (km)
Cell: LTE: Latency: DL Configured Scheduling (ms)
Cell: LTE: Latency: DL Re-Transmission Time (ms)
Cell: LTE: Latency: DL Scheduler Latency
Cell: LTE: Latency: DL Transmission Time (ms)
Cell: LTE: Latency: Num of DL ARQ Re-Transmissions
Cell: LTE: Latency: Num of DL HARQ ReTransmissions
Cell: LTE: Latency: Num of UL ARQ Re-Transmissions
Cell: LTE: Latency: Num of UL HARQ ReTransmissions
Cell: LTE: Latency: UL Configured Grant (ms)
488
Comments
Comments
Comments
About the Grid Data Loader
Valid Header for each Supported Parameter
Allowable Values
Comments
Cell: LTE: Latency: UL Re-Transmission Time (ms)
Cell: LTE: Latency: UL Scheduler Latency
Cell: LTE: Latency: UL Transmission Time (ms)
Parameters supported at the 5G (NR) Cell level
(Allowable Values and Comments are only added where applicable.)
Valid Header for each Supported Parameter
Allowable Values
Comments
Cell: NR: Adaptive SU-MIMO DL Traffic SINR
Threshold
Cell: NR: Adaptive SU-MIMO Threshold Enabled
Cell: NR: Adaptive SU-MIMO UL Traffic SINR
Threshold
Cell: NR: Assigned Carrier
Any valid entry
assigned to parent
node
Cell: NR: Avg Num of Connected Users
Cell: NR: Carrier Aggregation Cell ID
Cell: NR: Cell Code
Cell: NR: Cell Group
Cell: NR: CSIRS Offset
Cell: NR: Downlink Load Percentage
Cell: NR: DSS Identity
Cell: NR: DSS Reserved PRACH RBs
Cell: NR: DSS Support DL
'YES' or 'NO'
Cell: NR: DSS Support UL
'YES' or 'NO'
Cell: NR: Enable Carrier Aggregation
'YES' or 'NO'
Cell: NR: Enabled
'TRUE' or 'FALSE'
Corresponds to the
'Technology Supported'
checkbox in the Site
Database.
Cell: NR: High SINR Enabled
Cell: NR: Indoor Clutter Loss Schema
Cell: NR: Line of Sight Enabled
'YES' or 'NO'
Cell: NR: Max DL Modulation
Cell: NR: Max Scheduled Users
Cell: NR: Max TX Power (dBm)
Cell: NR: MUG non-Rayleigh Adjustment
Cell: NR: MU-MIMO DL Traffic SINR Threshold
Cell: NR: MU-MIMO Downlink Average Co-scheduled
Terminals
Cell: NR: MU-MIMO Downlink Enabled
'YES' or 'NO'
Cell: NR: MU-MIMO Threshold Enabled
'YES' or 'NO'
Cell: NR: MU-MIMO UL Traffic SINR Threshold
489
ASSET User Reference Guide
Valid Header for each Supported Parameter
Allowable Values
Cell: NR: MU-MIMO Uplink Average Co-scheduled
Terminals
Cell: NR: MU-MIMO Uplink Enabled
'YES' or 'NO'
Cell: NR: NCGI
'Unknown', or any
valid entry
Cell: NR: NCI
'Unknown', or any
valid entry
Cell: NR: Noise Figure (dB)
Cell: NR: NR Cell Name
Cell: NR: PCI Schema
Any valid entry
Cell: NR: PDCCH Offset
Cell: NR: PDSCH Offset
Cell: NR: Physical Cell ID
Cell: NR: Power Auto-Calculate Method
'Off' or
'SSS / PBCH PPRE'
Cell: NR: PRACH Config Index
'Unknown', or any
valid entry
Cell: NR: PRACH Delay Spread
Cell: NR: PRACH FDM
Any valid entry
Cell: NR: PRACH First Assigned RSI
'Unknown', or any
valid entry
Cell: NR: PRACH Frequency Start
'Unknown', or any
valid entry
Cell: NR: PRACH Preamble Format
'Unknown', or any
valid entry
Cell: NR: PRACH Restricted Set Type
'Unrestricted' or
'Restricted Type A' or
'Restricted Type B'
Cell: NR: PRACH Subcarrier Spacing
Any valid entry
Cell: NR: PRACH ZCZC
'Unknown', or any
valid entry
Cell: NR: PSS Offset
Cell: NR: RSI Calculation Method
'RequiredRange' or
'ZCZC_Ncs'
Cell: NR: RSI Schema
Any valid entry
Cell: NR: Signalling Overhead
Cell: NR: SINR Threshold
Cell: NR: SSS PBCH PPRE
Any valid entry
Cell: NR: SS-SNR Threshold
Cell: NR: SS-SNR Threshold Enabled
'YES' or 'NO'
Cell: NR: SS-RSRP Offset (dB)
490
Cell: NR: SS-RSRP Offset Enabled
'YES' or 'NO'
Cell: NR: SU-MIMO Downlink Enabled
'YES' or 'NO'
Cell: NR: SU-MIMO Downlink Spatial Mode
'Diversity' or
'Multiplexing' or
'AdaptiveSwitching'
Comments
About the Grid Data Loader
Valid Header for each Supported Parameter
Allowable Values
Comments
Cell: NR: SU-MIMO RX Elements
Cell: NR: SU-MIMO TX Elements
Cell: NR: SU-MIMO Uplink Enabled
'YES' or 'NO'
Cell: NR: SU-MIMO Uplink Spatial Mode
'Diversity' or
'Multiplexing' or
'AdaptiveSwitching'
Cell: NR: TAC
'Unknown', or any
valid entry
Cell: NR: Timing Advance (yes/no)
'YES' or 'NO'
Cell: NR: Timing Advance Mode
'MaxTA' or
'MaxRange'
Cell: NR: UL/DL Decoupling CSI-RSRP Threshold
(dBm)
Cell: NR: UL/DL Decoupling Identity
Cell: NR: UL/DL Decoupling SS-RSRP Threshold
(dBm)
Cell: NR: UL/DL Decoupling SS-RSRP Threshold
Enabled
Cell: NR: Uplink Load (%)
Cell: NR: Uplink Noise Rise
Valid Header for each Supported Parameter
Allowable Values
Cell: NR: Cell Service: Area (km2)
'Unknown', or any
valid entry
Cell: NR: Cell Service: Range (km)
'Unknown', or any
valid entry
Valid Header for each Supported Parameter
Allowable Values
Cell: NR: Timing Advance: Max Range (km)
Any valid entry
Cell: NR: Timing Advance: Max TA (msec)
Any valid entry
Valid Header for each Supported Parameter
Allowable Values
Comments
Comments
Comments
Cell: NR: Bandwidth Part: ACTIVE-BWP-INDEX
Cell: NR: Bandwidth Part: Avg Num Connected Users
Cell: NR: Bandwidth Part: BWP-ID
Cell: NR: Bandwidth Part: BWP-Type
Cell: NR: Bandwidth Part: CSI-RS EPRE Offset (dB)
Cell: NR: Bandwidth Part: DL Cyclic Prefix
Cell: NR: Bandwidth Part: DL Load (%)
Cell: NR: Bandwidth Part: DL Numerology
Cell: NR: Bandwidth Part: DL PRBs
Cell: NR: Bandwidth Part: Max Scheduled User
Cell: NR: Bandwidth Part: PDCCH EPRE Offset (dB)
Cell: NR: Bandwidth Part: PDCCH Resource Blocks
Cell: NR: Bandwidth Part: PDSCH EPRE Offset (dB)
491
ASSET User Reference Guide
Valid Header for each Supported Parameter
Allowable Values
Comments
Allowable Values
Comments
Cell: NR: Bandwidth Part: PDSCH Overhead (%)
Cell: NR: Bandwidth Part: PSS EPRE Offset (dB)
Cell: NR: Bandwidth Part: PUCCH Resource Blocks
Cell: NR: Bandwidth Part: PUSCH Overhead (%)
Cell: NR: Bandwidth Part: Scheduler
Cell: NR: Bandwidth Part: SSB Numerology
Cell: NR: Bandwidth Part: SSB Periodicity
Cell: NR: Bandwidth Part: SSS PBCH PPRE (dBm)
Cell: NR: Bandwidth Part: ARFCN DL
Cell: NR: Bandwidth Part: ARFCN UL
Cell: NR: Bandwidth Part: TDD Slot DL (%)
Cell: NR: Bandwidth Part: TDD Slot UL (%)
Cell: NR: Bandwidth Part: UL Cyclic Prefix
Cell: NR: Bandwidth Part: UL Load (%)
Cell: NR: Bandwidth Part: UL Noise Rise (dB)
Cell: NR: Bandwidth Part: UL Numerology
Cell: NR: Bandwidth Part: UL PRBs
Valid Header for each Supported Parameter
Cell: NR: Latency: CPRI Length (km)
Cell: NR: Latency: DL Configured Scheduling (ms)
Cell: NR: Latency: DL Re-Transmission Time (ms)
Cell: NR: Latency: DL Scheduler Latency
Cell: NR: Latency: DL Transmission Time (ms)
Cell: NR: Latency: Num of DL ARQ Re-Transmissions
Cell: NR: Latency: Num of DL HARQ Re-Transmissions
Cell: NR: Latency: Num of UL ARQ Re-Transmissions
Cell: NR: Latency: Num of UL HARQ Re-Transmissions
Cell: NR: Latency: UL Configured Grant (ms)
Cell: NR: Latency: UL Re-Transmission Time (ms)
Cell: NR: Latency: UL Scheduler Latency
Cell: NR: Latency: UL Transmission Time (ms)
Parameters supported at the NB-IoT Cell level
(Allowable Values and Comments are only added where applicable.)
Valid Header for each Supported Parameter
Cell: NB-IoT: # LTE RS Ports
Cell: NB-IoT: # of RX Elements
Cell: NB-IoT: # of TX Elements
492
Allowable Values
Comments
About the Grid Data Loader
Valid Header for each Supported Parameter
Allowable Values
Cell: NB-IoT: Assigned Carrier
Any valid entry
assigned to parent
node
Cell: NB-IoT: Auto-Calculate Method
'Off' or
'NRS PPRE'
Cell: NB-IoT: Deployment
'Standalone'
or
'In-Band (LTE)'
or
'Guard-Band'
Cell: NB-IoT: DL Diversity Enabled
'YES' or 'NO'
Comments
Cell: NB-IoT: DL Load (%)
Cell: NB-IoT: DL Repetitions CE Level 0
Cell: NB-IoT: DL Repetitions CE Level 1
Cell: NB-IoT: DL Repetitions CE Level 2
Cell: NB-IoT: Enabled
'TRUE' or 'FALSE'
Corresponds to the
'Technology Supported'
checkbox in the Site
Database.
Cell: NB-IoT: Indoor Clutter Loss Schema
Cell: NB-IoT: Local Cell ID
Cell: NB-IoT: Max TX Power (dBm)
Cell: NB-IoT: NBCH Offset (dB)
Cell: NB-IoT: NB-IoT Cell Name
Cell: NB-IoT: NB-IoT Cell Type
Cell: NB-IoT: NB-IoT Identity
Cell: NB-IoT: NPCI
Cell: NB-IoT: NPDSCH/NPDCCH Offset (dB)
Cell: NB-IoT: NPSS Offset (dB)
Cell: NB-IoT: NRS PPRE (dBm)
Cell: NB-IoT: NRSRP Threshold (dBm) CE Level 0
Cell: NB-IoT: NRSRP Threshold (dBm) CE Level 1
Cell: NB-IoT: NRSRP Threshold (dBm) CE Level 3
Cell: NB-IoT: NSSS Offset (dB)
Cell: NB-IoT: Signalling Overhead
Cell: NB-IoT: UL Diversity Enabled
'YES' or 'NO'
Cell: NB-IoT: UL Noise Rise (dB)
Cell: NB-IoT: UL Repetitions CE Level 0
Cell: NB-IoT: UL Repetitions CE Level 1
Cell: NB-IoT: UL Repetitions CE Level 2
Cell: NB-IoT: UL SCS (kHz)
493
ASSET User Reference Guide
Valid Header for each Supported Parameter
Allowable Values
Cell: NB-IoT: Cell Service: Area (km2)
'Unknown', or any
valid entry
Cell: NB-IoT: Cell Service: Range (km)
'Unknown', or any
valid entry
Comments
Object Type: Property (for ASSET Backhaul)
Parameters supported at the Property level (for ASSET Backhaul).
(Allowable Values and Comments are only added where applicable.)
Valid Header for each Supported Parameter
Allowable Values
Comments
Property: END A: Address 1
Property: END A: Address 2
Property: END A: County
Property: END A: ID
String - no spaces
Property: END A: Location: EPSG
'EN' or 'decLL' or 'LL'
See About the
Location
Parameters on
page 500.
'EN' or 'decLL' or 'LL'
See About the
Location
Parameters on
page 500.
Property: END A: Location: Units
Property: END A: Location: X Coordinate
Property: END A: Location: Y Coordinate
Property: END A: Post Code
Property: END A: Property Code
Property: END A: State
Property: END A: Town
Property: END B: Address1
Property: END B: Address2
Property: END B: County
Property: END B: ID
Property: END B: Location: EPSG
Property: END B: Location: Units
Property: END B: Location: X Coordinate
Property: END B: Location: Y Coordinate
Property: END B: Post Code
Property: END B: Property Code
Property: END B: State
Property: END B: Town
494
About the Grid Data Loader
Object Type: Point to Multi Point Link
Parameters supported at the Point to Multi Point Link level (ASSET Backhaul).
(Allowable Values and Comments are only added where applicable.)
Valid Header for each Supported Parameter
Allowable Values
Comments
PMP: 1st Name
PMP: 2nd Name
PMP: END A: Carrier ID
String - no spaces
PMP: END B: Antenna Height
PMP: END B: Antenna ID
PMP: END B: Antenna Type
PMP: END B: Feeder Length
String - no spaces
PMP: END B: Feeder Type
PMP: END B: Property ID
PMP: END B: Radio
PMP: ID
Object Type: Multi Band Link
Parameters supported at the Multi Radio Link level (ASSET Backhaul).
(Allowable Values and Comments are only added where applicable.)
Valid Header for each Supported Parameter
Allowable Values
Comments
MBL: 1st Name
MBL: 2nd Name
MBL: END A: Antenna Height
MBL: END A: Antenna ID
MBL: END A: Antenna Type
MBL: END A: Property ID
String - no spaces
MBL: END B: Antenna Height
MBL: END B: Antenna ID
MBL: END B: Antenna Type
MBL: END B: Property ID
String - no spaces
MBL: ID
String - no spaces
MBL: Sublink: Band
MBL: Sublink: Channel
MBL: Sublink: END A: Antenna ID
MBL: Sublink: END A: Antenna Type
MBL: Sublink: END A: Feeder Length
MBL: Sublink: END A: Feeder Type
MBL: Sublink: END A: Radio
495
ASSET User Reference Guide
Valid Header for each Supported Parameter
Allowable Values
Comments
MBL: Sublink: END B: Antenna ID
MBL: Sublink: END B: Antenna Type
MBL: Sublink: END B: Feeder Length
MBL: Sublink: END B: Feeder Type
MBL: Sublink: END B: Radio
MBL: Sublink ID
MBL: Sublink: Polarisation
Object Type: Multi Radio Link
Parameters supported at the Multi Radio Link level (ASSET Backhaul).
(Allowable Values and Comments are only added where applicable.)
Valid Header for each Supported Parameter
Allowable Values
Comments
MRL: 1st Name
MRL: 2nd Name
MRL: END A: Antenna Height
MRL: END A: Antenna ID
MRL: END A: Antenna Type
MRL: END A: Property ID
String - no spaces
MRL: END B: Antenna Height
MRL: END B: Antenna ID
MRL: END B: Antenna Type
MRL: END B: Property ID
String - no spaces
MRL: ID
String - no spaces
MRL: Sublink: Band
MRL: Sublink: Channel
MRL: Sublink: END A: Feeder Length
MRL: Sublink: END A: Feeder Type
MRL: Sublink: END A: Radio
MRL: Sublink: END B: Feeder Lenght
MRL: Sublink: END B: Feeder Type
MRL: Sublink: END B: Radio
MRL: Sublink ID
MRL: Sublink: Polarisation
496
About the Grid Data Loader
Object Type: Repeater
Parameters supported at the Repeater level
(Allowable Values and Comments are only added where applicable.)
Valid Header for each Supported Parameter
Allowable Values
Comments
PR_B2B: 1st Name
PR_B2B: 2nd Name
PR_B2B: Band
PR_B2B: Channel
PR_B2B: END A: Antenna Height
PR_B2B: END A: Antenna ID
PR_B2B: END A: Antenna Type
PR_B2B: END A: Feeder Length
PR_B2B: END A: Feeder Type
PR_B2B: END A: Property ID
String - no spaces
PR_B2B: END A: Radio
PR_B2B: END B: Antenna Height
PR_B2B: END B: Antenna ID
PR_B2B: END B: Antenna Type
PR_B2B: END B: Feeder Length
PR_B2B: END B: Feeder Type
PR_B2B: END B: Property ID
String - no spaces
PR_B2B: END B: Radio
PR_B2B: ID
String - no spaces
PR_B2B: Polarisation (End_A_to_PR_Property)
PR_B2B: Polarisation (PR_Property_to_End_B)
PR_B2B: Repeater: Antenna Height1
PR_B2B: Repeater: Antenna Height2
PR_B2B: Repeater: Antenna Type1
PR_B2B: Repeater: Antenna Type2
PR_B2B: Repeater Property ID
PR_B2B: Waveguide: Length
PR_B2B: Waveguide: Loss/m
497
ASSET User Reference Guide
Object Type: Point to Point Link
Parameters supported at the Point to Point Link level (ASSET Backhaul).
(Allowable Values and Comments are only added where applicable.)
Valid Header for each Supported Parameter
Allowable Values
Comments
PTP: 1st Name
PTP: 2nd Name
PTP: Band
PTP: Channel
PTP: END A: Antenna Height
PTP: END A: Antenna ID
PTP: END A: Antenna Type
PTP: END A: Feeder Length
PTP: END A: Feeder Type
PTP: END A: Property ID
String - no spaces
PTP: END A: Radio
PTP: END B: Antenna Height
PTP: END B: Antenna ID
PTP: END B: Antenna Type
PTP: END B: Feeder Length
PTP: END B: Feeder Type
PTP: END B: Property ID
String - no spaces
PTP: END B: Radio
PTP: ID
String - no spaces
PTP: Polarisation
Object Type: Reflector
Parameters supported at the Reflector level
(Allowable Values and Comments are only added where applicable.)
Valid Header for each Supported Parameter
REF_PR: 1st Name
REF_PR: 2nd Name
REF_PR: Band
REF_PR: Channel
REF_PR: END A: Antenna Height
REF_PR: END A: Antenna ID
REF_PR: END A: Antenna Type
REF_PR: END A: Feeder Length
498
Allowable Values
Comments
About the Grid Data Loader
Valid Header for each Supported Parameter
Allowable Values
Comments
REF_PR: END A: Feeder Type
REF_PR: END A: Property ID
String - no spaces
REF_PR: END A: Radio
REF_PR: END B: Antenna Height
REF_PR: END B: Antenna ID
REF_PR: END B: Antenna Type
REF_PR: END B: Feeder Length
REF_PR: END B: Feeder Type
REF_PR: END B: Property ID
String - no spaces
REF_PR: END B: Radio
REF_PR: ID
String - no spaces
REF_PR: Polarization
REF_PR: Reflector: Height
REF_PR: Reflector: Passive Centre Height
REF_PR: Reflector Property ID
REF_PR: Reflector: Width
Object Type: Dual Polar Link
Parameters supported at the Dual Polar Link level (ASSET Backhaul).
(Allowable Values and Comments are only added where applicable.)
Valid Header for each Supported Parameter
Allowable Values
Comments
XP-DPL: 1st Name
XP-DPL: 2nd Name
XP-DPL: END A: Antenna Height
XP-DPL: END A: Antenna ID
XP-DPL: END A Antenna Type
XP-DPL: END A: Property ID
String - no spaces
XP-DPL: END B: Antenna Height
XP-DPL: END B: Antenna ID
XP-DPL: END B: Antenna Type
XP-DPL: END B: Property ID
String - no spaces
XP-DPL: ID
String - no spaces
XP-DPL: Sublink: Band
XP-DPL: Sublink: Channel
XP-DPL: Sublink: END A: Feeder Length
XP-DPL: Sublink:END A: Feeder Type
XP-DPL: Sublink: END A: Radio
XP-DPL: Sublink: END B: Feeder Length
XP-DPL: Sublink: END B: Feeder Type
499
ASSET User Reference Guide
Valid Header for each Supported Parameter
Allowable Values
Comments
XP-DPL: Sublink: END B: Radio
XP-DPL: Sublink: ID (H)
XP-DPL: Sublink: ID (V)
About Antenna Indexes
The following object types contain parameters relating to antenna indexes:
Object Type
Parameter
Property
Physical Antenna Index
Logical Antenna Index
Cell
Logical Antenna Index (Selections)
Important: Antenna index numbering is a requirement within the structure of the Site Database, but
this can be user-controlled or automatic.
 If your organisation is not concerned about the antenna index numbering, it is not
necessary to specify them in the Grid Data Loader. You can exclude the physical antenna
index and logical antenna index columns, and the import process will automatically
generate the index numbers. But be warned that the sequencing of the rows in the grid
during import is random, so the index numbers may not match the sequence of the rows.
 If your organisation is concerned about the antenna index numbering, you should explicitly
specify them, by including the physical antenna index and logical antenna index columns.
Parameters Controlling Logical Antenna Assignments
In general, when assigning antennas to the cells, use the "Logical Antenna: Selection(s)"
parameter if you know the antenna indexes, or the "Logical Antenna: Select" parameter if
you are creating a logical antenna and want to assign it in the same action.
Here is the area of the Site Database these two parameters correspond to:
The "Logical Antenna: Select" parameter is also useful if you want to select or de-select all
antennas on an existing cell.
About the Location Parameters
The 'Property' object type contains a set of parameters related to location:
 Property location
 Physical Antenna locations
 Logical Antenna locations
500
About the Grid Data Loader
These location-related parameters are:
 EPSG
 Units
 X Coordinate
 Y Coordinate
 Absolute/Relative (for antennas only)
In the Grid Data Loader, whenever you supply X and Y Coordinates (for Properties or antennas),
you must also supply the Units and/or the EPSG. In addition (for antennas only), you must supply
the Absolute/Relative value (ABS or REL).
This section summarises the special considerations for these parameters when using the Grid Data
Loader:
If the grid data supplies these values
The result of the import proces will be
Units, X Coordinate, Y Coordinate
EPSG is derived from the project settings. This will be the
Projected EPSG if the supplied Units are 'EN' or the
Geodetic EPSG if the supplied Units are 'LL' or 'decLL'.
EPSG, X Coordinate, Y Coordinate
The units will be considered as 'EN' if the supplied EPSG is
a Projected number, or 'decLL' if the supplied EPSG is a
Geodetic number.
EPSG, Units, X Coordinate, Y Coordinate
If the supplied EPSG is a Projected number, 'EN' is used,
and the Units are ignored.
If the supplied EPSG is a Geodetic number, the units are
checked to determine whether the values are treated as 'LL'
or 'decLL'.
This table shows examples relating to each type of Unit:
Units
Also known as
X Coordinate
Y Coordinate
'EN'
Easting-Northing or Grid
564025
5450475
'decLL'
Decimal Lat-Long or DLL
-2.1210589
49.20372403
'LL'
Lat-Long or LL
002°07'15.81"W
49°12'13.40"N
Examples of Use Cases
Here is a selection of use cases, which may help to illustrate some of the points made in the topics
referenced in Before Using the Grid Data Loader on page 458.
501
ASSET User Reference Guide
1 - Creating New MU-Nodes (INSERT mode)
If you want to create, for example, a new MU-Node, you can do this using the following entries in
the grid:
Notice that when you insert an MU-Node, you must also designate a Property.
 If this Property exists, the MU-Node will be added to that Property.
 If this Property does not exist, then a new Property will be created in the import, and the
MU-Node will be added to that Property.
(If you do not supply location details, the Property will be located at the centre of the
project's map data.)
 If one (but only one) of these objects already exists, the other will still be created.
(For example, if the MU-Node exists, but the Property does not exist, the Property will still
be created.)
 If both objects already exist, nothing will happen.
For a new Property, if you also include any data parameters of the Property, that parameter's data
will be 'created' too. But for an existing Property, that parameter would require to be 'updated',
which is not allowed in INSERT mode, and so the row would be invalid.
Here is a variation of the above example, involving three new MU-Nodes, where two of them are on
the same Property:
502
About the Grid Data Loader
Important: The above scenarios assume situations where you are adding 'Fixed' MU-Nodes. For
'Variable' MU-Nodes, you would omit the following two parameters:
 MU-Node: Fixed Technology Mode
 MU-Node: GSM* Technology Active
* The GSM option is used in the above examples, but it could equally be UMTS, LTE or 5G.
2 - Creating New Properties, Nodes, Cells, Antennas (INSERT mode)
This shows how you can create a new Property with new MU-Nodes and cells, and at the same
time set up the physical and logical antennas.
Notice that, although this example is INSERT mode, the same Property ID needs to appear in
multiple rows to achieve this objective.
Important: Antenna index numbering is a requirement within the structure of the Site Database, but
this can be user-controlled or automatic.
 If your organisation is not concerned about the antenna index numbering, it is not
necessary to specify them in the Grid Data Loader. You can exclude the physical antenna
index and logical antenna index columns, and the import process will automatically
generate the index numbers. But be warned that the sequencing of the rows in the grid
during import is random, so the index numbers may not match the sequence of the rows.
 If your organisation is concerned about the antenna index numbering, you should explicitly
specify them, by including the physical antenna index and logical antenna index columns.
 The above scenario assumes a situation where you are adding 'Fixed' MU-Nodes and cells.
For 'Variable' MU-Nodes and cells, you would omit the following two parameters:
o
MU-Node: Fixed Technology Mode
o
Cell: Technology (Identifier)
503
ASSET User Reference Guide
About the Technology (Identifier) Parameter
The Technology (Identifier) parameter exists for identification purposes.
Whenever you create or update a cell that is in 'Fixed Technology' mode, it is mandatory to use this
parameter, so that the Grid Data Loader can identify the correct cell during an update operation, or
set the required technology when creating a new cell.
This parameter is listed in the parameters supported at the cell level. See Object Type: Cell on
page 482.
The reason behind this identification parameter is that:
 Multiple 'fixed' cells with the same cell identity can exist in a project, as long as they are set
to separate technologies.
 Whenever a 'variable' (not fixed) cell exists, no other cells (fixed or otherwise) can be
created with the same identity.
More general information ('About Cells' and 'About MU-Nodes') can be found in the ASSET Radio
User Reference Guide.
Here is an example of when you might use this parameter in an 'UPDATE' situation:
This picture shows three 'fixed' cells sharing the same identity, but with different technologies:
So, for example, if you want to modify the carrier assignment on the above UMTS cell, you would
do this:
Tip: In general, even if you have no cells in your network with the same identity, we recommend
that you use the Technology (Identifier) parameter when your cells are in 'Fixed Technology'
mode.
504
About the Grid Data Loader
3 - Modifying a Data Parameter of an MU-Node (UPDATE mode)
Here is a simple example of how you can modify a data parameter of an MU-Node.
If you just want to modify the '1st Name' data parameter, you can do this using the following entries
in the grid:
Notice that you do not need to designate a Property in this situation. This is because ASSET insists
on unique names for the identity parameters within a project.
In an UPDATE operation, the validation and import will fail if the specified identity parameter does
not exist.
Important: The above scenario assumes a situation where you are adding a 'Fixed' MU-Node. For
'Variable' MU-Nodes, you would omit the following two parameters:
 MU-Node: Fixed Technology Mode
 MU-Node: UMTS* Technology Active
* The UMTS option is used in the above example, but it could equally be GSM, LTE or 5G.
505
ASSET User Reference Guide
4 - Modifying an Antenna Parameter using Cell Identity (UPDATE
mode)
If you want to modify a data parameter of a physical antenna (for example, its azimuth), you can do
this using only the cell identity, by using the following entries in the grid:
Notice that you do not need to designate a Property or even the parent Node in this situation. The
Cell Identity is sufficient. This is because ASSET can resolve this, due to unique names for the
identity parameters within a project. The only exception to this rule is when the cells have separate
technologies, but this is resolved by the Technology (Identifier) parameter.
The antenna(s) currently assigned on that cell in the Site Database will be changed with the new
azimuth, and that new azimuth will be visible on the Antennas tab for the cell and on the
corresponding Physical/Logical Antennas tabs of the parent Property.
In an UPDATE operation, the validation and import will fail if the specified identity parameter does
not exist.
Important: The above scenario assumes a situation where you are adding a 'Fixed' cell. For
'Variable' cells, you would omit the 'Cell: Technology (Identifier)' parameter. For more information,
see About the Technology (Identifier) Parameter on page 503.
506
About the Grid Data Loader
5 - Changing a Physical Antenna Assignment (UPDATE mode)
Here is another example, this time changing a Logical Antenna's Physical Antenna assignment.
If you want to modify Logical Antenna 2 to use Physical Antenna 3, you can do this using the
following entries in the grid:
This would result in this assignment on the Antennas tab of the cell in the Site Database:
(If the physical antenna for the specified index does not already exist on the parent Property, it will
be created.)
Important: The above scenario assumes a situation where you are adding a 'Fixed' cell. For
'Variable' cells, you would omit the 'Cell: Technology (Identifier)' parameter. For more information,
see About the Technology (Identifier) Parameter on page 503.
507
ASSET User Reference Guide
508
Index
16 Index
3
3GPP
exporting • 433
importing • 420
Map Information Control • 81
why use • 420
A
Actix, CellOpt AFP • 424, 437
Algorithms
Prediction file caching algorithm • 26, 27
Antennas
comparing beam patterns • 332
creating • 314, 319, 347
deleting • 329
dialog box • 314
editing • 97, 330
grouping by device • 338, 339
importing • 422
in the XML Data Editor • 446
managing • 313, 315
microwave • 314
moving beam patterns • 330
organising • 338, 339
searching • 328, 334
site visibility • 97
storing • 314
viewing beam patterns • 331
Applying, changes • 205
Archive
maps • 126
Arrays
large array support • 46, 130
swapping system for large arrays • 46, 130
Attachments, adding • 411
Attributes
adding to vectors • 264
defining for a vector file feature • 264
displaying vector information • 113
editing • 265
viewing as screentips • 202
AutoRes, using • 172
B
Base strings, setting • 405
BCCH Prerequisite Rule • 39
Beam patterns
adding • 325
comparing • 332
viewing path losses • 331
Bing Maps • 86
BTSs
equipment • 75, 353
Building heights, editing • 410
C
Cabins
creating • 355
Caching algorithm for predictions • 26
Candidates
adding • 391, 393
breaking • 398
displaying • 396
removing • 398
Cell Equipment window, about • 74
CellOpt AFP
exporting data to • 437
importing data from • 424
Cells
adding • 234
deleting • 238
displaying • 226
editing • 246
equipment • 354, 359
naming • 405
updating • 210
viewing attributes as screentips • 202
Cellular connections
adding • 92
adding routes and hops • 401
defining traffic for • 402
viewing • 75, 399
Change reports • 217
Clutter
displaying • 171
editing • 171, 407
Committing, changes • 205
Contacts
adding • 233
Converters • 406
Copying
data in the XML Data Editor • 452
filters • 287
D
Data
loading • 28, 32
ordering • 83
project • 20
shared • 21
viewing • 82, 83
viewing attributes as screentips • 202
viewing external pages • 245
XML Data Editor • 441
Databases
about • 221
backing up • 428
editing Site Database using Global Edit • 246, 248
uncommitted changes • 217
Defaults
filters • 44
identifiers • 405
Deleting
items from wastebasket • 76
network elements • 90, 238
restoring deleted items • 76, 239
Delta reports • 217
Displaying
attributes • 113, 202
cross-sections • 114
database contents • 221
filters • 177, 178, 180, 182, 185, 186
network items • 169
site visibility • 94
tabs for network elements • 227
vectors • 191
windows • 54
Distributing
509
ASSET User Reference Guide
simulations • 29
Distribution nodes
moving • 91
DVB-H
SLR model • 375
polygons as • 251
preferences • 44
setting a default • 44
speeding up • 308
using • 275, 296, 307
E
G
Earth radius • 39
Editing
lines and polygons • 269
Site Database using Global Edit • 246, 248
vector file feature attributes • 265
XML data • 445, 446
Equipment
amplifiers • 358
cell • 354
costs • 74
exporting • 456
importing • 456
suppliers • 359
Examples
applying and committing • 207, 212
expressions • 108
fields • 276
filters • 187, 190, 288, 309, 310
Exporting
3GPP • 420, 433
about • 426
CellOpt data • 437
equipment • 456
Google Earth • 438
MapInfo • 438
XML • 428, 433
Expressions, regular • 108
External data pages
viewing • 245
GIS Export, from Map View • 438
Global
changes • 39
Global Editor, using • 246, 248
Google Earth (Root)
exporting to • 438
GPS, using • 404
Graphs, analysis • 147
Grid Data Loader
about • 461
examples of use cases • 504
using • 465
valid headers • 480
Grids
map • 175
F
Favourites
accessing • 100, 101
saving • 100, 101
Features
creating vector file features • 259
using and managing vector file features • 251, 265
Feeders
creating • 356
dialog box • 74, 356
Field strength, units • 39
Fields
editing in the XML Data Editor • 451
examples • 276
Files
attaching to sites • 411
converting • 406
Fill, for vector file features • 194
Filtering
data in the XML Data Editor • 448
Filters
adding • 277, 278, 283
copying • 199, 287
deleting • 286
displaying • 175, 178, 180, 182, 185, 186
editing • 286
examples • 187, 190, 288, 289, 290, 294, 309, 310
exporting • 428
importing • 415
optimising • 308
organising • 286
510
H
Height profile
window • 114
Height, data • 170, 407, 410
Hexagon radius • 180
Hierarchy tab
adding to filter • 299
reparenting • 248
History
History
tabs • 244
version reporter • 219
Holes, for polygons • 270
Hopping
creating • 401
route • 401
Hops • 401
I
iDEN
about • 41
Identifiers, setting defaults • 405
Importing
3GPP • 420
about • 415
antennas • 422
ASSET data • 415
CellOpt data • 424
equipment • 456
GSM data • 423
links • 456
PlaNet • 421
Properties • 423
XML • 416, 420
Interference
arrays • 139
Islands, for polygons • 270
K
KML/KMZ files, exporting to MapInfo, Google Earth,
ESRI ArcGIS • 438
Index
L
Labels
displaying • 186, 196
vector file features • 196
Large Array Support, swapping system • 46, 130
Licence Administrator, using • 77
Line data, changing display • 191
Lines
spreading traffic • 264
vector file features • 195, 251
Loading
files generated by ARRAYWIZARD • 135
options • 32
regions • 33
subsets of project data • 33, 415
Locations, finding on map • 106
Log in
overview • 17
Logical
connections • 92, 399
routes • 401
Logical/cellular connections
about • 75
adding • 92
adding routes and hops • 401
defining traffic for • 402
viewing • 399
M
Macrocell models
about • 364
map data recommended • 388
Map data
projections • 24
specifying • 24
Map Information Control • 71, 81
Map View
archiving • 126
backdrop • 173
deleting items • 90
displaying • 83, 169, 173
displaying attribute data • 202
extents • 28
favourites • 100, 101
grids • 175
Map Information Control • 81
Map Information pane • 111, 112, 113
printing • 124
redrawing • 83, 100
repositioning • 100
saving • 100, 101
saving to file • 126
saving views • 100, 101
selecting items • 84
site visibility • 94
vector file features • 191, 259
MapInfo, exporting to • 438
MapQuest • 86
Mast head amplifiers
creating • 358
Masts
creating • 357
Messages
Already in Use by Another User • 215
Log window • 76
Moving
antennas • 330
items on map • 91
Multiple Height Pathloss Predictions • 383
N
Naming
setting defaults • 405
troubleshooting • 76
Network Display Mode • 48, 226
network elements • 248
Network elements
editing in Site Database • 242
Networked PCs for simulations • 29
Networks
adding elements • 86, 234, 237
connections • 92
displaying items • 169, 227
logical • 92
refreshing display • 227
settings • 39, 41, 48, 87, 226
Nominals
displaying • 396
overlapping search areas • 398
O
Object Count in Site Database • 49
Ordering, map data • 83
P
Partial Load • 22
Pathloss
viewing for beam patterns • 331
Pixel Analyser, about • 148
PMR
about • 41
Points
about • 251
attributes • 264
creating • 259
displaying • 191, 192
spreading traffic • 264
Vector Manager • 259
Polygons
about • 251
as filters • 251
attributes • 264
creating • 251, 259
displaying • 191
examples • 290
holes and islands • 270
reports based on polygons • 139, 162
spreading traffic • 264
Vector Manager • 251, 259
Population Statistics reports • 264
Predictions
file caching system • 26, 27
file management algorithm • 26, 27
Preferences
XML Data Editor • 443
Preferences dialog box, about • 39
Printing
maps • 124
Project Settings dialog box • 22
Projections
specifying • 24
Projects
creating • 17, 20
editing • 22
511
ASSET User Reference Guide
loading subsets • 28, 32, 33, 415
sharing data • 21, 422
viewing settings • 111
Propagation Models
about • 361
adding • 375
DHM • 367, 378
Enhanced Macrocell • 368, 378
recommended parameter values (Macrocell) • 377
SLR model for DVB-H • 375, 382
Standard Macrocell • 364, 376
SUI model • 374, 381
Supported Models • 362
using • 361
Properties
about • 231
addresses • 233
candidates • 398
contact details • 233
definition • 231
deleting • 238
details • 311
importing • 423
naming • 405
search area • 395, 396
updating • 210
viewing attributes as screentips • 202
viewing external data • 245
Q
Quick Finder
searching with • 106
R
Radius
displaying • 94, 395
earth • 39
hiding • 395
removing • 396
Receiver Heights Mode • 383
Redrawing maps • 100
Refreshing
maps • 100
Region loading
about • 28
using • 33, 415
Regions
loading • 28, 33, 415
Regular expressions, examples • 108, 110
Repeaters
deleting • 238
moving • 91
naming • 405
updating • 210
Reports
about • 162
coverage statistics • 162
delta • 217
statistics • 139, 159, 162
uncommitted changes • 217
Repositioning, maps • 100
Resolution
changing • 171, 172
line of sight • 94
troubleshooting • 172
Restoring
deleted items • 239
RNCs, reparenting network elements • 248
512
Routes
displaying • 401
logical • 401
Rules
for filters • 308
S
Saving
map views • 99, 100, 101, 126
Scale, displaying in Map View Information Pane • 112
Scanmaps, configuring • 112
Scanned maps, configuring • 112
Schemas
display schemas • 139, 140, 143, 144
Search areas
displaying • 395
hiding • 395
overlapping • 398
removing • 396
Searching
antennas • 328, 334
attributes • 265
expressions • 108
for windows • 54
maps • 106
vectors • 265
Secondary routes, creating • 401
Selection Expert • 296
Selection Filter • 296, 307
Service areas, displaying • 187
Settings
changing • 39
global • 39
projects • 17
viewing project • 111
Shortcuts
zooming • 99
Show Windows dialog box, about • 54
Simulations
distributing • 29
Site Database network parameters
editing • 242
Site Database Settings • 48, 226
Site Database window, about • 60, 227
Site Database, Object Count • 49
Site tips, displaying • 202
Sites
adding • 215, 234
attaching files • 411
definition • 231
deleting • 238
displaying • 60, 82, 94, 106, 226, 311
equipment • 75, 353
fields • 276
filters • 275, 286, 287, 288, 297, 299, 308
finding on map • 106
moving • 91
naming • 405
plotting line of sight • 114
search area • 395, 396
selecting • 60
templates • 222, 223, 224, 225
troubleshooting • 215
updating • 210
viewing • 82, 94
viewing attributes as screentips • 202
viewing external data • 245
visibility • 94, 97
Sorting
Index
XML data • 448
Statistics
reports • 159, 162
Status fields
examples • 276
Storing data • 221
Subscriber reports • 159
Suppliers, editing • 359
Swapping System, for large arrays • 46, 130
Symbols, changing • 180, 182, 185, 197, 198
T
TAB files, exporting to MapInfo, Google Earth, ESRI
ArcGIS • 438
Table Browser, using • 265
Tabs
customising which tabs to display in Site Database
• 227
Templates
adding elements based on • 237
creating • 222, 223, 224, 225
deleting • 225
from existing elements • 224
Terrain
height • 407
viewing cross-section • 114
TETRA
about • 41
Text
as a vector file feature • 251
creating • 259
displaying on map • 169, 198
on map • 106
Toolbars
Height Profile • 115
Map View • 64
Vector Editor • 259
Traffic
editing • 402
viewing routed • 402
Troubleshooting
co-ordinates • 28
naming items • 76
resolution • 171, 172
selecting items • 84
sites • 215
vectors • 256
Table Browser • 265
troubleshooting • 256
Vector Manager • 251, 259
Visibility
of sites • 94
of vector file features • 196
Visualisers, about • 199, 200, 201
W
Warnings, message log • 76
Wastebasket
about • 76
example • 215
Web content
viewing in the Site Database • 245
Web Maps, viewing • 86
Windows
organising • 54, 55, 56
Workspaces
creating • 56
managing • 59
X
XML
copying and pasting data • 452
creating files • 450
Data Editor user interface • 442
data in CSV files • 454
data in Microsoft Excel • 453
exporting • 428, 433
importing • 416, 420
using the XML Data Editor • 441
Z
Zoom
methods of zooming • 64, 67, 97
saving • 100, 101
shortcuts • 99
U
Uncommitted changes, reporting • 217
Units, setting • 39
UTM, co-ordinate system • 24
V
Vectors
about • 251
attributes • 264
Attributes in Map Information pane • 113
configuring • 253
creating • 251, 259
customising • 191
displaying • 113, 191
editing • 269
exporting • 256
managing • 265
reports based on vectors • 162
spreading traffic • 264
513
ASSET User Reference Guide
514