Aircom Asset

ENTERPRISE Version 8.
0 Commercial Release Notes
Author: AIRCOM International

Date: 09 February 2012
Copyright 2012 AIRCOM International - All rights reserved. No part of this work, which is protected by copyright, may be reproduced in
any form or by any means - graphic, electronic or mechanical, including photocopying, recording, taping or storage in an information
retrieval system – without the written permission of the copyright owner.
Contents
1 Important Information......................................................................................................... 4
2 What’s New in the V8.0 Release?......................................................................................5
2.1 What’s New in ENTERPRISE 8.0?............................................................................5
2.1.1 XML Schema Validation........................................................................................ 5
2.1.2 Selection Expert Enhancements...........................................................................5
2.1.3 Group Level Apply (Sandboxing) in ENTERPRISE...............................................6
2.1.4 Using WMS Client................................................................................................. 7
2.1.5 Map View Enhancements......................................................................................7
2.1.6 KML Export............................................................................................................ 8
2.1.7 Export Geo-Transform Raster Outputs..................................................................8
2.1.8 Multi-Coordinate System Data...............................................................................8
2.1.9 New Filterable State for Objects (New, Modified, Committed)...............................8
2.2 What’s New in ENTERPRISE Administrator 8.0?......................................................9
2.2.1 Group Level Apply (Sandboxing) in Administrator.................................................9
2.2.2 Licensing Reservation Tool....................................................................................9
2.3 What’s New in ADVANTAGE 8.0?.............................................................................9
2.3.1 Antenna Constraints in Site Database...................................................................9
2.4 What’s New in ARRAYWIZARD 8.0?......................................................................10
2.4.1 Interference Table (Matrix) Support.....................................................................10
2.4.2 New Parameter Sets for Location-related Planners............................................10
2.4.3 LTE Support........................................................................................................ 10
2.4.4 Independent ARRAYWIZARD Scheduler with Web Service Interface.................10
2.5 What’s New in ASSET 8.0?.....................................................................................10
2.5.1 Improved Antenna Management.........................................................................10
2.5.2 Information about Simulated Terminals...............................................................12
2.5.3 Map View Enhancements for Displaying Neighbours..........................................12
2.5.4 Model Assignment Calculator Enhancement.......................................................13
2.5.5 Neighbour Planning Wizard based on Handover Events.....................................13
2.5.6 Neighbour Planning Wizard based on Traffic......................................................15
2.5.7 Neighbour Planning Wizards using Background Thread.....................................15
2.5.8 Neighbour-related Conflict Warnings in Neighbour Analysis...............................15
2.5.9 Prediction Radius Calculator Enhancements......................................................15
2.5.10 Restricting Coverage and Simulation Arrays to Vectors..................................16
2.5.11 Site Database – Customisable Object Count..................................................17
2.5.12 CDMA2000 and EV-DO – Enhanced PN Code Planner..................................17
2.5.13 GSM – Optional Network Hierarchy and Support for Logical Connections......18
2.5.14 GSM – Writing Interference Table Traffic to Sub-Cells.....................................18
2.5.15 GSM and UMTS – LAC and RAC Assignment Planner...................................18
2.5.16 GSM and UMTS – Location Based Services Planner.....................................19
2.5.17 GSM and UMTS – Polygon Assignment Planner............................................20
2.5.18 LTE – Line of Sight Array and Improved MIMO Modelling...............................20
2.5.19 LTE – Scheduled Users Limit added to Simulator...........................................21
2.5.20 LTE – Support for MME and SAEGW Network Elements................................21
2.5.21 Planning Wizards – Copying Data to Clipboard...............................................21
2.6 What’s New in CONNECT 8.0?...............................................................................22
2.6.1 Automatic Frequency and Capacity Planning......................................................22
2.6.2 Enhanced Carried Traffic Analysis.......................................................................22
Author: AIRCOM International ENTERPRISE Version 8.0 Commercial Release Notes p.2 of 45
3 System Requirements...................................................................................................... 23
3.1 Hardware Requirements......................................................................................... 23
3.2 Operating System, Service Packs and Oracle Version Support..............................23
3.3 Test Matrices Per Product.......................................................................................24
3.3.1 ENTERPRISE Core, ASSET, ARRAYWIZARD and ADVANTAGE......................24
3.4 Upgrading to V8.0 Licences....................................................................................24
3.5 Large Fonts............................................................................................................. 24
3.6 Character Sets........................................................................................................ 24
3.7 Regional Settings.................................................................................................... 25
4 Installation........................................................................................................................ 25
4.1 General Information................................................................................................. 25
4.2 Installing ENTERPRISE Software...........................................................................25
4.2.1 Installation Prerequisites.....................................................................................25
4.2.2 Installation Procedure..........................................................................................26
4.3 Upgrading ENTERPRISE Software from a Previous Version..................................27
5 Upgrading Oracle Database Server from a Previous Version..........................................28
6 Upgrading Database Instance from a Previous Version...................................................29
6.1 Sizing Rollbacks/Undo Tablespace.........................................................................29
6.2 Tablespaces............................................................................................................ 29
6.3 Database Consistency Check.................................................................................30
6.4 AIRCOM Administrator User...................................................................................30
6.5 APIs and Interfaces................................................................................................. 30
6.6 Database Schema Changes Between 7.0 and 8.0..................................................30
6.7 User Preferences.................................................................................................... 30
6.8 Change made to the Prediction Folder .dat file.......................................................31
6.9 Filter Migration Procedure for WiMAX Users...........................................................33
7 Important Notices............................................................................................................. 36
7.1 Versions No Longer Supported...............................................................................36
7.2 All ENTERPRISE Customers..................................................................................36
7.3 ARRAYWIZARD...................................................................................................... 39
7.4 ASSET.................................................................................................................... 40
7.5 CONNECT.............................................................................................................. 41
7.6 RANOPT................................................................................................................. 42
7.7 Citrix Users.............................................................................................................. 42
8 Known Issues with this Release......................................................................................43
9 Reporting a Bug............................................................................................................... 44
9.1 Europe..................................................................................................................... 44
9.2 Americas................................................................................................................. 44
9.3 Asia Pacific.............................................................................................................. 44
9.4 Middle East............................................................................................................. 44
9.5 Africa....................................................................................................................... 45
9.6 India........................................................................................................................ 45
9.7 All Other Countries.................................................................................................. 45
1 Important Information
This document aims to clarify any issues involved with the installation of
ENTERPRISE V8.0. Please read the 'Installation' section carefully before installing
ENTERPRISE V8.0.
V8.0 of ENTERPRISE is a major release, with many new features.
As such, we strongly recommend that users become familiar with these new
features and how they impact on the planning process before they consider
implementing it into the live environment. It is likely that you will want to change
some of your processes and consider training your users to get the maximum
benefit from V8.0 before going live.
A well-planned implementation of V8.0 will minimise disruption to the live planning
environment.
AIRCOM recommend these minimum steps:
 Read the V8.0 Release Notes thoroughly before installation/upgrade.
 Read the V8.0 ENTERPRISE Installation and Administration Guide.
 Take a full backup of your live ENTERPRISE planning database prior to any
upgrade.
 Create a copy of your live planning database and carry out a trial upgrade so
that you and your planners can become familiar with the new features and
changes before deploying these in your live environment.
As part of the installation package, you will receive full product documentation; this
includes a ‘What’s New?’ document. Please take time to study all of these.
Your regional Product Support team (see Section 9) can provide an ‘Upgrade
Checklist’ document to assist in the above steps, or discuss any queries on this
process.
Important : You should be aware of these issues that affect an Upgrade to 8.0:
 There is a new Co-ordinate System method deployed in ENTERPRISE v8.0.
This is a newer and more efficient system for storing and converting
geographical coordinates. It uses projection systems specified by a single
number, termed EPSG (European Petroleum Survey Group).
This new EPSG system replaces the old system (Geocalc). The old system
still exists within the tools in v8.0, but it is now dormant, except where it
assists with upgrade. It will be completely removed at some future stage.
 When upgrading a database to v8.0, a Database Upgrade wizard now
appears on Upgrade. Because of the new EPSG Code functionality, the
upgrade to v8.0 must be performed with the utmost care. There are some
critical checks and procedures, and it is vital that they are actioned correctly.
 For the ‘AIRCOM’ schema tablespace, the schema will be migrated to
become ‘NETWORK_PLANNING’. Due to this schema rename, we strongly
recommend that before your users connect to the upgraded database, to
ensure the optimal performance of the Oracle database after the upgrade,
you execute the following steps :
o Connect to the database as a user with sysdba permission such as ‘sys’
o Execute the following command (which may take some minutes): ‘exec
dbms_stats.gather_dbms_stats;’
o Logout
For detailed information on the above issues, please refer to the ENTERPRISE
Installation and Administration Guide.
2 What’s New in the V8.0 Release?
The following information describes briefly what is new in ENTERPRISE 8.0
Release. For more detailed information, please refer to the ‘What’s New in the
ENTERPRISE Suite 8.0?’ Quick Reference Guide, available on the AIRCOM
support website (www.aircominternational.com/support).
2.1 What’s New in ENTERPRISE 8.0?

In ENTERPRISE 8.0, the following additional features are now available:
2.1.1 XML Schema Validation

When importing or exporting XML data files, you now have the option to Enable
XML Schema Validation.
If you select this option, ENTERPRISE will check the XML file against the
structure, syntax and restrictions defined in the XSD file for the corresponding
object type.
Typical checks include string lengths, enumerated values and positive/negative
values, and object types that fail these checks will not be imported or exported.
This ensures that only correct and reliable data is transferred into and out of
ENTERPRISE.
This validation is also performed automatically when saving XML data files in the
XML Data Editor if the “Validate file” option is selected in Preferences.
2.1.2 Selection Expert Enhancements

There are now a number of new ways to add items to a Selection filter:
 Using an existing polygon vector
 Using the element hierarchy
Using the Existing Polygon Vector
On the Location tab of the Selection Expert, you can add network elements that lie
within a particular polygon to a Selection filter.
In the Select Polygon Vector(s) dialog box, you can select one or more polygon
vectors which contain elements that you want to add.
If you have classified your vectors, you can filter these according to their vector
class.
You can then add all of these elements to the Selection filter by clicking the Add All
Elements button in the Selection Expert.
Using the Element Hierarchy
If your Selection filter already contains network elements, on the Hierarchy tab of
the Selection Expert, you can add other, related network elements.
You can add:
 The logical/physical parent(s) of one or more selected elements
 The logical/physical child (or children) of one or more selected elements
 The neighbours (inward, outward, mutual) of one or more elected network
elements
2.1.3 Group Level Apply (Sandboxing) in ENTERPRISE
A Sandbox is an optional environment within ENTERPRISE 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.
If you have logged in to ENTERPRISE as a Sandbox user, 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.
To use a Sandbox you must have been made a member of a Sandbox by your
system administrator. If you choose to log in to a sandbox and your administrator
has given you access to more than one, you can select the required Sandbox from
a drop-down list of those available.
Having logged in to a Sandbox, the Apply, Commit, Restore, Commit All, Restore
All and Global Edit buttons in the Site Database, Link Database and
Logical/Cellular Connection Database windows behave differently from normal as
follows:
Click To
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.
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.
To use Commit, you must have been granted the Sandbox Commit/Restore functional
privilege by your administrator.
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
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 : Commit All commits the latest sandbox changes (from any sandbox member) to the
Master Tables of the ENTERPRISE Database.
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 : Restore All deletes diff data and reloads master data – no additions or updates are
performed on the diff table.
Global Edit Open the Global Editor, for when you want to change all network elements identified by a
filter. If there are any conflicting events, the edit is not enacted.
To use Global Edit, you must have been granted the Sandbox Global Edits functional
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.
2.1.4 Using WMS Client

You can now show Web Map Service (WMS) images in the Map View window.
For more information, see ‘Viewing Web Maps’ in the ENTERPRISE User
Reference Guide.
As with WFS Services, connections to WMS Services are configured in
ENTERPRISE Administrator.
2.1.5 Map View Enhancements

A number of enhancements have been made to the usability of the Map View:
 A Distance toolbox has been added to the Map View toolbar. This contains
four buttons as follows:
This Button Enables You To
Measure the distances between points on a line, and the

total length of the line.
Show the coordinates of a point.
Measure the size of an area.
Change the display properties of the above tools.
To preserve the information displayed by these tools, you can do so by saving

it as a vector. The labels of vector file features can retain these metrics.
 A tracking cursor has been added to the Map View toolbar:
This Button Enables You To
Turn cross hairs on and off. The tracking cursor displays the
coordinates at the cursor cross hairs.
You can use the tracking cursor with the Map Grid, the Pixel
Analyser, when adding or moving properties or network
elements and when moving or reorientating an antenna.
 You can now display a scale bar in the Map View window.
2.1.6 KML Export
You can now export a variety of map information, such as Images of arrays,
Polygons/Rectangles and Symbol Points, to the KML/KMZ file format for use with
Google Earth. You do this by making the appropriate selections in the GIS Export
dialog box.
2.1.7 Export Geo-Transform Raster Outputs

If you are exporting:
 An Image and you have chosen to include a TAB file
 Polygons/Rectangles and you have selected TAB/DAT
 Symbol points and you have selected TAB/DAT
You can now change the EPSG (European Petroleum Survey Group) code by
typing a different one or by clicking the Find button. To revert to the EPSG code
specified in the Project Settings dialog box, you can click the Reset button.
The current projection is shown below the EPSG Code field.
For more information, see ‘Exporting Map Information’ with GIS Export in the
ENTERPRISE User Reference Guide.
2.1.8 Multi-Coordinate System Data

The Geospatial Data Abstraction Library (GDAL) now replaces Geocalc for the
purposes of:
 Selecting a coordinate system
 Performing projections between coordinate systems
This is reflected on the Coord System tab of the Modify Project dialog box in
ENTERPRISE.
You will also need to enter the correct EPSG code when populating the Support
schema in ENTERPRISE Administrator after creating a new ENTERPRISE
database.
2.1.9 New Filterable State for Objects (New, Modified, Committed)

You can now filter objects based on their Add State (inserted, updated, committed)
as a filterable attribute to network elements.
For all objects that are filterable (generally the site database objects, but also the
antenna device and pattern), there is now a filterable attribute that represents the
DIFF state of the object. The attribute will be of picklist type, and the three possible
values (as they appear on the interface) will be "New", "Modified", and
"Committed".
"New" will refer to objects inserted by the current user or sandbox user.
"Modified" will refer to objects updated by the current user or sandbox user.
"Committed" will refer to objects neither inserted, nor updated, nor deleted, by the
current user or sandbox user.
The State attribute will be accessible in the following areas:
- Site database Status tabs (read-only)
- Filter definition
- Filter display attributes
- Quick finder
- Site tips
2.2 What’s New in ENTERPRISE Administrator 8.0?
In ENTERPRISE Administrator 8.0, the following additional features are now
available.
2.2.1 Group Level Apply (Sandboxing) in Administrator

A new user type known as a Sandbox user has been introduced.
A Sandbox is an optional environment within ENTERPRISE in which Sandbox
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. If you add a Sandbox in ENTERPRISE Administrator, then users who you
designate as Sandbox users (by adding them to the Sandbox Users group) will
have the option to log in to the Sandbox environment in ENTERPRISE where they
will have Sandbox Apply and Commit options.
A Sandbox apply will make changes visible to the other users of the Sandbox. A
Sandbox commit will make changes visible to all users. You can set up multiple
Sandboxes with different users in each.
To access the Add Sandbox function, in Administrator, select the new Sandboxes
in the left pane.
2.2.2 Licensing Reservation Tool

If you are using network licences you may wish to prevent specified users from
accessing particular licences. You can now do this by adding a user to a
reservation file which is held on the server and which controls group access to
licences. By adding a user to an excluded group, you can prevent access to a
specified licence. To generate the required reservation file you can use a utility
called Wlsgrmgr.
2.3 What’s New in ADVANTAGE 8.0?

In ADVANTAGE 8.0, the following additional features are now available.
2.3.1 Antenna Constraints in Site Database

ADVANTAGE 8.0 provides a new group of antenna constraints that you can set in
the Site Database.
You can now activate and set the following constraints per antenna slot, if you
want to enable such changes during optimisation:
 Total Downtilt - Min; Max
 Electrical Downtilt - Min; Max; Step
 Mechanical Downtilt - Min; Max; Step
So, for example, setting values for 'Electrical Downtilt' means that the Optimiser
will consider changes to the electrical tilt, within the defined range, for that antenna
slot.
These parameters are already available in the (plan-specific) Action-Constraints
dialog box, but the option to set them for your network provides more flexibility, as
well as consistency with other parameters.
The Antenna Constraints tab appears at the cell level for GSM, and at the
site/node level for all other technologies.
Note : The 'Total Downtilt - Max' parameter replaces the 'Constrain Max Main
Lobe Tilt' that existed in older versions.
2.4 What’s New in ARRAYWIZARD 8.0?
In ARRAYWIZARD 8.0, the following additional features are now available.
2.4.1 Interference Table (Matrix) Support

You can now create Interference Table Analysis parameter sets to be run by
ARRAYWIZARD.
2.4.2 New Parameter Sets for Location-related Planners

You can now create the following parameter sets to be run by ARRAYWIZARD:
 LAC and RAC Assignment planning
 Location Based Services planning
 Polygon Assignment planning
2.4.3 LTE Support

You can now create LTE Analysis parameter sets to be run by ARRAYWIZARD.
2.4.4 Independent ARRAYWIZARD Scheduler with Web Service Interface

ARRAYWIZARD has a new service-based scheduler which is not reliant on the
ARRAYWIZARD Administrator running. It also has a web service interface which
provides for the execution, querying and editing of scheduling activities.
The ENTERPRISE Super User can:
 View the scheduler log
 Add and drop user schemas to and from the database to which
ARRAYWIZARD is connected
 Stop and start the scheduler
 Change the password for the Scheduler internal account
 Specify a user account against which to run a post parameter set processing
executable or a batch file
Using the ENTERPRISE ARRAYWIZARD Web Service you can:
 Retrieve all schemas within an ENTERPRISE Database
 Retrieve all tasks that belong to a particular schema
 Start a task
 Stop a task
 Retrieve the current status of a task
 Delete a task
 Edit the region extent of a task
 Edit plan filters and best server filters for a task
2.5 What’s New in ASSET 8.0?
In ASSET 8.0, the following additional features are now available.
2.5.1 Improved Antenna Management

ASSET 8.0 provides some powerful functionality to help you manage your
antennas. The following areas have been improved:
 Cellular Antennas dialog box
 Site Database
 Global Editor
 XML Export
The following topics provide information about each of these areas.
Antenna Management in the Cellular Antennas Dialog Box
ASSET 8.0 provides some powerful new functionality in the Cellular Antennas
dialog box to help you manage your antennas:
 The Tree tab now contains a Filter drop-down box that enables you to view
only the antennas that exist in your chosen filter (appropriate to filters that are
based on antenna objects).
 In addition, the Tree tab has added options. You can now:
o Add a device or pattern to the Selection Filter
o Add a device or pattern to the list in the Advanced Search tab
 The Advanced Search tab has added options. You can now:
o Add a device or pattern to the Selection Filter
o Remove the antenna device (with all its patterns), or an individual pattern,
from the Search results
o Include all patterns for the selected device or all currently listed devices in
the Search results
o Cut and paste a pattern onto a different device
o Delete an individual item from the database
o Find all antenna devices that do not contain any antenna patterns
o Perform a database removal of all the devices currently listed in the
Search Results
o Use the Group Antennas by Device dialog box for a flexible way of
grouping together selected patterns under a particular antenna device
 On both tabs, there is an additional set of display options:
o Show All Devices: All antenna devices, irrespective of their usage in the
Site Database.
o Show only Used Devices: Only antenna devices that have at least one
pattern in use in the Site Database.
o Show only Unused Devices: Only antenna devices that have none of their
patterns in use in the Site Database
For detailed information on the Cellular Antennas dialog box, see the ‘Storing
Antennas and Equipment’ chapter in the ENTERPRISE User Reference Guide.
Antennas in the Site Database and Global Editor
ASSET 8.0 provides new ways of editing electrical tilts in the Site Database and
Global Editor:
 Site Database:
There is a new Electrical Tilt drop-down box on the Antennas tab in the Site
Database.
This enables you to easily select a different electrical tilt (from those available on
the device). The corresponding pattern is then automatically selected.
The antenna configurations for Repeaters also now have this same editing
functionality.
 Global Editor:
When you want to assign different patterns/electrical tilts (of the currently assigned
antenna device) using the Global Editor, there are now two ways of achieving this:
o Basing the global edit on a specific antenna device and pattern, by
selecting the Antenna checkbox, and then selecting the antenna
device/pattern (optionally using the Electrical Tilt drop-down box). The
Global Editor will assign the specified device/pattern to the appropriate
network elements in the Site Database.
o Basing the global edit on a specified electrical tilt value across all currently
assigned antenna devices. To do this, select the Elec. Tilt checkbox. You
can then type a value in the edit box. The Global Editor will check for all
the existing antennas within the filter whose tilt is currently different from
the specified value. It will then check if they have a matching electrical
downtilt in the list of patterns parented to their existing antenna device.
Where it finds them, it will assign the different patterns to the appropriate
network elements in the Site Database.
Exporting Antennas Using XML Export
ASSET 8.0 provides some new XML Export filtering options for antenna objects.
If you want to restrict the export of antenna objects, you can achieve this by using
an antenna filter or a network element filter (or both).
 Using an Antenna filter: Only the antennas included in this filter are exported.
Optionally, you can further restrict by whether the objects are currently being
used on nodes/cells in the Site Database.
 Using a Network Element filter: Only the antennas currently assigned to the
network elements (nodes/cells/repeaters) in this filter are exported. It is not
necessary for the antenna objects to be included in this filter.
For more information on using the XML Export, see the 'Importing and Exporting'
chapter in the ENTERPRISE User Reference Guide.
2.5.2 Information about Simulated Terminals

In ASSET 8.0, when you run the Simulator using snapshots, you can choose to
include arrays that show information about the simulated terminals.
This generates extra arrays, which show the location of the terminals generated by
the snapshots, and also whether they succeeded or failed in making a connection.
The arrays are as follows:
Terminal Info: Failure Rate
In each pixel, the failure rate is the proportion of attempted terminals that failed to
make a connection, calculated as a percentage.
Terminal Info: Failure Reason
This array shows connection successes and failures in a single plot.
Terminal Info: Speed (km/h)
Dependencies: Terminal, Snapshots
This array shows the speed of the terminal in the corresponding Failure Reason
array (some failure reasons are affected by the speed of the mobile).
For more information on these arrays, see the ASSET Technical Reference Guide.
2.5.3 Map View Enhancements for Displaying Neighbours

ASSET 8.0 provides the following enhancements when you are displaying
neighbour relationships in the Map View:
 You can now display neighbours using Static Mode or Hot Track Mode
 You can now interact between the Map View and the Neighbour Analysis
(including proposed neighbours)
You can use:
 Static Mode if you want to show a static display of all the neighbour
relationships that match your criteria
 Hot Track Mode if you want to hover the mouse over each cell's azimuth to
display its specific neighbours that match your criteria
You can also select additional limiting filters. For information about these, see the
'Creating Neighbour Relationships' chapter in the ASSET User Reference Guide.
Interacting between the Neighbour Analysis and Map View
When viewing the contents of the Neighbour Analysis dialog box, you can display
the neighbours on the Map View, even if you have not yet applied the proposed
neighbours to the database. This can be very useful when assessing any
proposed new relationships. (You can set distinct colours for existing and
proposed neighbours.)
When in Static mode, the Map View shows the appropriate neighbours each time
you select a cell in the left pane of the Neighbour Analysis.
When in Hot Track mode, you can move the mouse over each cell's azimuth in the
Map View to dynamically display its neighbours, and at the same time the
respective cell is automatically highlighted in the Neighbour Analysis.
2.5.4 Model Assignment Calculator Enhancement

The quality of the network analysis within ASSET is inherently related to the quality
of the pathloss predictions, which depends mainly on the propagation models
used. In most cases, a specific model will be tuned for a specific environment
(urban, suburban, rural and so on). Where this is the case, it is important that the
model used for a cell matches the environmental characteristics surrounding the
cell antenna.
In older versions of ASSET, the Model Assignment Calculator allowed you to
define your environment types, run the calculation and then produce a report,
giving information on which types would be suitable for each cell in the network.
You could then use that data to help you manually assign the most suitable
propagation model to each cell.
Now, in 8.0, the enhanced Model Assignment Calculator enables you to associate
a specific model to each environment type, so that you can choose to assign the
appropriate propagation models to each cell automatically, based on the results.
In summary, the Model Assignment Calculator now enables you to:
 Define different environment types (based mainly on the composition of clutter
surrounding each cell antenna), and which propagation model should relate to
each type
 Calculate which environment type (and therefore propagation model) is most
appropriate to each cell antenna
 Generate a report and, optionally, choose to Apply the model assignments to
the Site Database
2.5.5 Neighbour Planning Wizard based on Handover Events
ASSET 8.0 now offers a new Event-based Neighbour Wizard, which uses
information from Operations Support Systems (OSS) Performance Management
handover statistics files. It is available for the following neighbour plans:
 UMTS Intra-Frequency
 UMTS Inter-Frequency
 UMTS-GSM
The wizard partly bases its neighbour calculations on the minimum number of
events, read from an input handover statistics file.
For information on the required file format, see the 'Creating Neighbour
Relationships' chapter in the ASSET User Reference Guide.
Complex Sort
You can use the Complex Sort simply as a visual aid in the Neighbour Analysis, or
as a means of setting the priorities automatically by using the Set Priorities button
after sorting.
The information in the right pane of the Neighbour Analysis appears according to
your custom sort.
2.5.6 Neighbour Planning Wizard based on Traffic

ASSET 8.0 now enables you to run the Prediction-based Neighbour wizard with
various calculation methods:
 Area based
 Traffic based
 Area and traffic based
(Previously, only the Area method was available.)
If you want to use Traffic as an input, you simply need a relevant traffic raster
already saved to file.
After running the wizard, you can view the calculated overlapping percentages
(Area, Traffic, Total) in the Neighbour Analysis.
2.5.7 Neighbour Planning Wizards using Background Thread

In ASSET 8.0, the following neighbour planning wizards run on a background
thread:
 The Prediction-based Neighbour wizard
 The Event-based Neighbour wizard
This enables you to continue using ASSET for other purposes while the neighbour
planning process is running.
2.5.8 Neighbour-related Conflict Warnings in Neighbour Analysis
In ASSET 8.0, after using the Neighbour Analysis to update neighbour
relationships, you can now choose to display neighbour-related conflict warnings
for the proposed relationships. The warnings will appear in the Message Log after
the update has been performed.
These warnings relate to BSIC-BCCH conflicts or scrambling code conflicts
between neighbouring cells in the following relationships:
 GSM-GSM
 GSM-GSM-GSM
 GSM-UMTS-GSM
 UMTS-UMTS
 UMTS-UMTS-UMTS
 UMTS-GSM-UMTS
This new option has been added to the existing Update Database dialog box.
2.5.9 Prediction Radius Calculator Enhancements

ASSET 8.0 has made significant enhancements to the Prediction Radius
Calculator.
The main improvement is that you can now choose from two different calculation
methods:
 Pathloss or Signal Strength
But there are also new parameters regarding ‘Minimum Covered Pixel Density’.
There is a great benefit in setting sensible prediction radius values for the purpose
of creating predictions, as it can achieve significant reductions in time taken and
disk space used.
You can use the Prediction Radius Calculator to automatically configure sensible
prediction radii for the cell antennas in the Site Database.
When you run the Prediction Radius Calculator, you can now choose from two
different calculation methods:
Method Description
Pathloss You can set a maximum pathloss value in dB. The calculated prediction radius is the
point furthest from the cell that is equal to or less than the set value, confined by the
general parameters (these are described in the next table).
Signal Strength You can set a minimum signal strength value in dBm. The calculated prediction radius is
the point furthest from the cell that is equal to or greater than the set value, confined by
the general parameters (these are described in the next table).
Note : The Signal Strength values are technology-specific.
There are some general parameters that influence the calculations, described in
this table:
Parameter Description
Max Prediction Radius (km) This sets an outer limit for the radius calculation.
Radius Precision (km) This sets a precision value that forces the final calculated radius
for each cell antenna to be a multiple of this value.
Min Covered Pixel Density (%) This enables you to set a minimum density of pixels that are
'covered' according to the Pathloss or Signal Strength value you
have specified. It works in association with 'rings' that are sized by
the radius precision value.
For a complete description of all these parameters, see the ASSET User
Reference Guide.
2.5.10 Restricting Coverage and Simulation Arrays to Vectors

ASSET 8.0 now enables you to restrict the output arrays from the Coverage or
Simulation wizards to specific vectors (rather than the rectangular region in the
Map View).
You can choose from any of your polygons, lines or points.
The impact of cells and terminals outside the vectors is still considered. In other
words, the coverage or simulation takes place in the normal way, but the arrays
are ‘masked’ according to the chosen vectors.
If you subsequently use the Statistics dialog box to generate statistical reports
from these arrays, the report's analysis area will be automatically restricted to the
same vector(s).
2.5.11 Site Database – Customisable Object Count

When you are viewing the Site Database, you can see the object count at the
bottom of the left pane.
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)
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)
2.5.12 CDMA2000 and EV-DO – Enhanced PN Code Planner

In ASSET 8.0, the PN Code Planner for CDMA2000 or EV-DO has been improved
so that it uses the algorithm and reporting mechanism of the other code planners
(such as UMTS Scrambling Code planner and GSM BSIC Planner).
When you run the PN Code Planner, you can choose from two Code Re-use
methods:
 Fixed - constant re-use distance
 Automatic - variable re-use distance
The PN Code Report dialog box now has greater usability.
It displays the successful assignments, and also displays any details of clashing
sectors (where the constraints have been broken). For example, for each cell, it
presents the following:
 Plan Result Icon: Success, Reuse Violation, Clashing Code
 Sector/Cell Name
 Plan Status
 Intra-Site Spacing
 PN Code
 Number of Clashing Neighbours and Sectors, Distance, Clash Factor
There is also a powerful way of interacting between the Report dialog box and the
Map View, in order to visualise specific cells and any clashing (or interfering) cells.
The chosen cell is highlighted in the Map View, together with its clashing cells.
Tip : For all the code planning wizards in ASSET, you can now right-click on any
row in the Report dialog box, and copy it to the Windows® clipboard. This enables
you to paste the contents of the row into another application such as Notepad,
Word, or a text editor.
2.5.13 GSM – Optional Network Hierarchy and Support for Logical

Connections
In ASSET 8.0, you can now have a non-hierarchical structure in the Site Database
for the GSM technology (and likewise for PMR/TETRA/iDEN).
This means that GSM networks can now be modelled in the same way as other
technologies such as UMTS, LTE and CDMA2000. In other words, the use of
network hierarchies in ENTERPRISE is optional. GSM networks are now attached
to PLMNs in the Site Database. So sites can be parented (non-hierarchically)
directly to this PLMN network, or they can be parented (hierarchically) to a 'higher'
network element.
Here are some further ways that greater consistency between the technologies
has been achieved:
 GSM networks are now included (as with the other technologies) in the
'Network View' mode in the Site Database
Note : For all technologies, any hierarchical structures are disregarded when
in Network View display mode.
 You can now make logical and cellular connections in GSM, in line with the
other technologies, as shown in this example of the Logical/Cellular
Connection Database
2.5.14 GSM – Writing Interference Table Traffic to Sub-Cells

An interference table (sometimes known as an interference matrix) contains
values that represent the severity of interference for any cell-pair combination for
which there are overlapping predictions, if that pair of cells were to be allocated
the same or adjacent carriers.
As part of its calculations, the Interference Table wizard can capture the traffic data
for each sub-cell.
For GSM, ASSET 8.0 now enables you to write this data automatically to the sub-
cells in the Site Database.
If you do this, the values are loaded onto the General tab of the Site Database.
This is only applicable to terminal types set to 'GSM Circuit Switched (CS)'.
2.5.15 GSM and UMTS – LAC and RAC Assignment Planner
ASSET 8.0 provides a LAC and RAC Assignment Planner. This enables you to
plan LAC (Location Area Codes) and RAC (Routing Area Codes) for the cells in
your network.
The LAC and RAC parameters are stored within the Site Database at the cell
level.
The calculation of these codes uses an algorithm based on the neighbour
relationships between the cells (either calculated dynamically or retrieved from the
database), but constrained by network element hierarchy rules.
In addition, the calculations for LAC consider any user-defined constraints based
on status field values assigned to network elements in the Site Database (this can
be at the cell, site/node or Property level).
This is the basic process performed by the LAC and RAC Assignment Planner
wizard:
 Calculates neighbour relationships dynamically or loads existing relationships
from database, as specified in the wizard. (The dynamic process uses the
ASSET Neighbour Planner.)
 Runs the LAC and RAC assignment algorithm, constrained or influenced by:
o The neighbour relationships
o The network element hierarchy rules
o Any status field value LAC constraints specified during the configuration of
the wizard
 Determines LAC and RAC values for the cells, where such values are valid.
 Stores the valid LAC and RAC values for the successfully planned cells in the
Site Database on the General tab.
For full information about this feature, see the 'Location-related Planning for GSM
or UMTS' chapter in the ASSET User Reference Guide.
2.5.16 GSM and UMTS – Location Based Services Planner

ASSET 8.0 provides a Location Based Services Planner. This enables you to
obtain specific geographic data for each cell in the network; this data can be useful
to external management information systems for applications such as marketing.
This data is the 'Centre of Gravity' of the service area of each cell in a network,
expressed as geographic co-ordinates.
The following definition of 'Centre of Gravity' reflects the functionality of this
planner:
"The focal point of a cell's service area at which the overall area or traffic may be
regarded as being concentrated".
The Location Based Services Planner calculates this information by generating
service area plots, and using an algorithm based on one of the following
calculation methods:
Calculation Method Basis of Centre of Gravity Calculation
Area The cell's service area.
Traffic The traffic within the cell's service area.
Area and Traffic Weighted combination of area and traffic within the cell's
service area.
You can choose which calculation method to use in the planner.
Optionally, you can also choose to calculate the associated 'Radius'.
The radius is the radius of the circle, centred at the Centre of Gravity co-ordinates,
that contains a user-defined percentage of that cell's served area or traffic.
The results of the calculations will automatically appear in user-defined 'status
fields' in the Site Database for each planned cell.
For full information about this feature, see the 'Location-related Planning for GSM
or UMTS' chapter in the ASSET User Reference Guide.
2.5.17 GSM and UMTS – Polygon Assignment Planner

ASSET 8.0 provides a Polygon Assignment Planner. This enables you to make an
'association' between individual cells and individual polygons.
There are various applications for this information. For example, it can assist the
emergency services in knowing the probable geographic location of an emergency
call, if the cell handling the call is already 'associated' with a polygon representing
a specific emergency zone.
The Polygon Assignment Planner creates cell-polygon associations based on a
service area plot, overlaid on the areas of a user-defined selection of polygons.
The service area of each polygon can be then calculated in terms of 'area' or
'population density', and the polygon giving the highest result can be ascertained.
After the cell-polygon associations have been calculated, the results can be stored
in the Site Database. To achieve this, the planner stores an identifying
characteristic of the associated polygon for each cell as a user-specified 'status
field' value.
There are two basic ways of determining the polygon assignment calculations for
this planner:
Calculation Method Basis of Polygon Assignment Calculation

Area The amount of a cell's service area that overlaps each polygon area.
Population density The amount of traffic within a cell's service area that overlaps each polygon
area.
If you want to calculate by population density, you can either use one or more
vectors, or a traffic raster. In either case, there must be an attribute representing
population, so that each pixel contains a population value.
2.5.18 LTE – Line of Sight Array and Improved MIMO Modelling

For LTE networks, ASSET 8.0 now provides:
 A new Line Of Sight (LOS) array
 Improved MIMO modelling when you run the Simulator
This is relevant if you have the Enhanced Macrocell propagation model or the
MYRIAD model assigned to the cells in your network. These models can use
different calculation parameters for LOS and NLOS, which can be distinguished at
each predicted location.
Now, these models are able to produce LOS/NLOS information for each predicted
location, and this information is used to generate a 'Line Of Sight' array when you
run the LTE Simulator.
In addition, the same information allows you to model MIMO in a better way when
performing an LTE simulation, by choosing to deactivate MIMO in areas that have
LOS to the serving cell. This is because 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. So, when you
run the LTE Simulator Wizard, there is now a new step that enables you to
selectively activate or deactivate the MIMO modes in areas that have LOS to the
serving cell. This relates to cells using either of the above two models.
For more information, see these chapters in the ASSET User Reference Guide:
 Using Propagation Models ('About the Enhanced Macrocell Model' section)
 Using ASSET with LTE ('Using AAS Support for LTE' section)
2.5.19 LTE – Scheduled Users Limit added to Simulator

In ASSET 8.0, for LTE cells, there is a new 'Number of Scheduled Users'
parameter in the Site Database.
This represents the maximum number of simultaneous users considered for
resource allocation by the cell. This number is used in simulations of network
performance (when running snapshots). The cell will not serve more users than
this specified limit, regardless of their service type or transmission mode. When a
connection would cause the limit to be exceeded, ‘User Limit’ shows as a
contributing reason for failure in the LTE Composite Report and LTE Failure
Report.
2.5.20 LTE – Support for MME and SAEGW Network Elements

ASSET 8.0 now supports the LTE higher order network elements:
 MME: Mobile Management Entity
 SAEGW: System Architecture Evolution Gateway
This means that in LTE you can now add these elements to your LTE network in
the Site Database or Map View:
 SAEGW
 MME
 LTE eNodeB
 LTE Repeater
These two new elements are also supported in the filtering, reporting, XML
import/export, and so on.
In the Site Database, if required, an eNodeB can be parented to both an SAEGW
and MME.
You can also parent an eNodeB to multiple SAEGWs and/or MMEs.
In addition to the above cellular connections to/from these new elements, you can
also now create logical connections.
2.5.21 Planning Wizards – Copying Data to Clipboard

In any of the Planner Report dialog boxes, you can select any row in the left or
right pane, and then copy it to the Windows® clipboard.
This is applicable to:
 GSM BSIC Planner
 UMTS Scrambling Code Planner
 CDMA2000/EV-DO PN Code Planner
 LTE Physical Cell ID Planner
 LTE Frequency Planner
 Mobile WiMAX PN Code Index Planner
 Mobile WiMAX Frequency Planner
To do this:
1 Select a row in either the left pane or the right pane of the report dialog box.
2 Right-click on the row.
3 Select 'Copy selected rows to clipboard'.
The contents of the row are copied to clipboard as a text string, which you can
then paste into another application such as Notepad, Word, a text editor, and so
on.
2.6 What’s New in CONNECT 8.0?

In CONNECT 8.0, the following additional features are now available.
2.6.1 Automatic Frequency and Capacity Planning

In CONNECT, you can use the Automatic Planner to optimise the performance for
your network. You can run the planner in two different modes, depending on what
you want to optimise:
 If you run the Frequency Planner (AFP), you can optimise based on:
o Increased availability
o Reduced interference degradation
 If you run the Frequency and Capacity Planner (AFCP), you can additionally
optimise based on:
o Maximised capacity
The Automatic Planner then uses a metaheuristic search algorithm in order to find
a solution to meet the requirements that you set, using the following parameter
values:
 The available frequency channels
 Frequency designation
 Polarisation
 Power
 Modulation (for the AFCP only)
When you run the Automatic Planner, you can view the progress and the results of
the search algorithm in the Automatic Planner dialog box.
Important data is displayed on the left-hand side, indicating the iteration number
that is currently running, the date and time at which the planner was started and
the best solution energy that has been found so far.
The graph on the right-hand side shows a visual representation of the planner
results, plotting the total energy, total interference (in dB) or total capacity (Mbps)
per iteration. You can select which of these data categories is shown using the
radio buttons on the right-hand side.
When the Automatic Planner has finished running, you can present and
manipulate the results in a number of different ways. You can:
 Generate a Microsoft Excel report detailing the best solution from the results
 Save the graph as a graphics image (*.bmp or *.jpg)
 Print the graph displaying the results
 Apply the best solution to the Link Database
2.6.2 Enhanced Carried Traffic Analysis
Further improvements have been made to enhance the backhaul carried traffic
analysis functionality that was introduced in v7.0.
To enable you to model 4th generation networks in a more realistic manner,
logical/cellular connections (or 'interfaces') are now represented more accurately
in CONNECT:
 Logical/cellular connections are now grouped under the label 'interfaces',
according to technology type (for example, UMTS interfaces).
 You can now specify the interface names in the Logical/Cellular Connection
Database.
 In the Logical/Cellular Connection Database, a new Traffic tab has been
added. On this tab, you can view and edit details of the CS and PS traffic
routed through the interface. In particular, you can now specify the percentage
of generated traffic (or the total logical traffic in Mbps) that is routed over each
of the logical connections.
 Also in the Logical/Cellular Connection Database, the Routes tab has been
improved to display more useful information for each hop, such as Load
(Mbps), Occupancy (%) and Availability (%), as well as the Total Availability for
the route (%). You can also view Occupancy on the Type subtab of the
General tab for a link in the Link Database.
 You can now generate a Microsoft Excel report of data from the
Logical/Cellular Connection Database.
 You can now add new interfaces in the Link Database, using the new
Connections tab. From this tab, you can use the Connection Creation dialog
box, which enables you to create interfaces based on defined criteria - for
example, the required technology and maximum length between network
elements.
The Unified Route Planner has also been improved, to enable you to specify the
following routing criteria:
 A maximum occupancy limit (%) for route hops
 A minimum end-to-end availability for routes (%)
You can also now indicate whether you want to automatically create primary or
secondary routes.
3 System Requirements
3.1 Hardware Requirements
AIRCOM software is continually evolving and is designed to exploit the advances
in PC design and specification. Please contact your regional Product Support team
(see Section 9) for the latest recommended hardware specifications for review
prior to installation.
3.2 Operating System, Service Packs and Oracle Version Support

The ENTERPRISE release has been tested on a number of operating systems
against Oracle 10g and 11g. It has also been verified on Citrix Xenapp 6 and Citrix
Xenapp 5.
Warning : ENTERPRISE no longer supports Oracle 9i.
See the next section for a fuller compatibility matrix. For any further queries on
this, or if there is a particular configuration that you are not sure about or would
like advice on, please contact your regional Product Support team (see Section 9).
ENTERPRISE 8.0 has been tested using Microsoft Office 2010 and 2007. Earlier
versions of Office may work although some features won’t be available because it
utilises a feature in the later version of Excel.
Important : Versions earlier than Office 2003 (such as Office XP, 2000, 98/95) are
not recommended.
This represents the explicitly tested Oracle versions, OS and Citrix versions for the
products provided in the installation kit.
3.3 Test Matrices Per Product

Testing has been completed for the following products on the listed environments,
and there are no known issues specific to these environments other than those
listed in the Known Issues section.
3.3.1 ENTERPRISE Core, ASSET, ARRAYWIZARD and ADVANTAGE

 Enterprise Server
o Windows Enterprise Server 2008 R2 x64
o Oracle Client 11.2.0.2.0 (32-bit)
o Oracle Client 11.2.0.1.0 (32-bit)
o Citrix XenApp 6
 Database Server
o Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 (64-bit) on
RHEL 5.5
o Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 (64-bit) on
Windows Server 2008 R2 x64
Important : Oracle Standard edition has been tested and verified, however:
o ASSET users should note that only Oracle Enterprise edition provides the
Oracle Application Enabled roles functionality, which prevents third-party
products such as TOAD or Microsoft Access writing to your backend
database.
o For RANOPT, binning techniques will be disabled (because these require
Oracle Spatial) and there is also a file/filter limitation (because Oracle
Partitioning is not available). Please refer to the RANOPT User Reference
Guide for more information.
Important : When using Windows 7 or Windows 2008 Server, "User Account
Control" must be switched off in order for ENTERPRISE and Oracle to function
properly.
3.4 Upgrading to V8.0 Licences

Since 6.1, licensing has moved from a dongle-based system to a software-based
system, and needs to be configured by your administrator.
If you are the administrator, you should read Appendix C of the ENTERPRISE
Installation and Administration Guide for full instructions on migrating existing
licences, generating new licences and renewing licences.
Note : When you have completed the licensing process, you will no longer need
your dongle. Please return it to your regional Product Support team (see Section
9).
3.5 Large Fonts
ENTERPRISE does not fully support large fonts at this time. You must ensure that
your display settings are at 96dpi and that you use normal font sizes using the
Display Settings Control Panel applet.
3.6 Character Sets

ENTERPRISE supports the following character sets within the software:
 Single-byte character sets (West European language editions)
 Multi-byte character sets (for example, Chinese) in ASSET, ADVANTAGE and
ASSET ACP
For more information on configuring your database to handle Chinese characters,
see the ENTERPRISE Installation and Administration Guide.
Important :
 The MYRIAD and Volcano propagation models do not support non-Western
characters.
 The creation of Chinese user names is only supported in Oracle 11g (11.2.0.1)
onwards.
3.7 Regional Settings

ENTERPRISE does not support European regional settings, specifically for the
decimal separator character.
Therefore, you should only use ENTERPRISE with a point character as the
decimal separator, not a comma.
4 Installation
4.1 General Information
Remember that you must have administrative privileges to install ENTERPRISE. If
you do not have Administrative privileges, then the installation will abort with an
error message.
To obtain administrative privileges, contact your system administrator.
4.2 Installing ENTERPRISE Software
4.2.1 Installation Prerequisites

 Full administration rights
 As a guideline, if you are performing a basic installation of ASSET and the
Core components required for ENTERPRISE to run, around 697MB of space
is required. However, if you are installing Oracle as well, the hard disk space
requirements are:
o ~550MB for Oracle client
o ~6-7GB for Oracle full db server, depending on the size of your database
 A supported operating system version (see Section 3.3 for more information).
 An Installation code (if you are installing WEBWIZARD).
Important : While you can install ENTERPRISE in a 64-bit Windows environment,
it currently uses the 32-bit Oracle client and the following differences apply to the
installation:
 The default installation folder is C:\Program Files AIRCOM\AIRCOM
International\ENTERPRISE 7.0 (Not C:\Program Files (x86)\... as for other 32
bit applications on a 64 bit system).
 A shortcut to the ODBC administrator is also provided in the Start menu.
 You need to ensure Oracle is installed before installing ENTERPRISE. This is
due to some DLL dependencies ENTERPRISE has on Oracle. If you install
ENTERPRISE first, it will fail to run and you will need to reinstall
ENTERPRISE again.
4.2.2 Installation Procedure

The following instructions explain briefly how to install and run ENTERPRISE on a
single or client PC. For full step-by-step instructions, see the ENTERPRISE
Installation and Administration Guide.
1 If you have a previous version of ENTERPRISE, uninstall it using Add or
Remove Programs in Control Panel. Follow the on screen instructions
including restarting your machine if necessary.
2 Download the ENTERPRISE executable from the ENTERPRISE Suite
Downloads page of the AIRCOM ASSIST web site at www.aircomassist.com,
and double-click it.
o If a page stating that ENTERPRISE requires other items to be installed
appears, click the Install button and follow the subsequent on-screen
instructions
o If a dotnetfx module security warning is displayed, click the Run button
3 On the Welcome to the InstallShield Wizard for ENTERPRISE page, click
Next.
4 On the License Agreement page, read to the bottom of the terms of the license
agreement (scroll down as necessary), select I accept the terms in the license
agreement, and click Next.
5 In the User Information dialog box, enter your name and the name of your
organisation, then click Next.
6 On the Setup Type page, select Custom, and then click Next.
7 The Custom Setup page appears. Ensure that the components to be installed
have a hard drive icon next to them and those to be omitted have a cross next
to them, and then click Next.
8 On the Ready to Install the Program page, click Install.
9 Follow the on-screen instructions to complete the dialog boxes that appear.
10 On the final page, click Finish.
11 Install the latest patches by opening the Patch (number) folder on your CD and
double-clicking the .exe file within it. Alternatively, if you have access to the
AIRCOM Support web page, which can be found at www.aircomassist.com,
you can download the latest patch and patch documentation.
12 Check with your administrator that the software has been correctly licensed for
your use. ENTERPRISE is now licensed via a software-based licensing
system, rather than a dongle-based system. If you are the administrator, you
should read Appendix C of the ENTERPRISE Installation and Administration
Guide for full instructions.
Your software should now be available for use. You can:
 Set up a demonstration project: If you ordered ENTERPRISE for trial purposes
you can set up a demonstration project with access to ready-made project
information.
 Set up a blank database: If you do not have a database administrator to do
this for you, you can do it yourself using templates or with a simple Oracle
database creation utility.
 Upgrade an existing database: If you have an existing database, you may
need to upgrade it to work with your new version of ENTERPRISE.
4.3 Upgrading ENTERPRISE Software from a Previous Version

Existing customers with previous ENTERPRISE Versions (see table below) must
upgrade before they can use ENTERPRISE 8.0.
Important : With the release of V8.0, AIRCOM will no longer provide patches for
V6.2 or earlier. Customers on versions 6.2 or earlier are advised to upgrade as
soon as possible.
If you are upgrading from one version to another, make sure that you have
upgraded your system to the last build of your current version as shown in the
table below.
ENTERPRISE Version DB Version
Version 5.0.3 Build 17R63 5059
Version 5.1.1 Build 38R66 5127
Version 5.2.2 Build 9R78.0.1 5211
Version 6.0 Build 43R95.0.1 6026
Version 6.1 Build 118R98.0.1 6135
Version 6.2 Build 239R24.0.2 6237
Version 7.0 Build 273R0 7066
Warning : It is strongly recommended that old databases are backed up before

being upgraded. Any damage to databases cannot be undone.
During the upgrade ALL uncommitted data will be lost. ALL ENTERPRISE users
must commit or restore applied changes AND empty their wastebaskets prior to
upgrading.
There are currently two methods for upgrading ENTERPRISE software from a
previous version:
 If you are upgrading from a version earlier than 5.0, please contact your
regional Product Support team (see Section 9).
 If you are upgrading from V5.0 or later then the steps below give a basic
outline of the procedure.
The upgrade is a process entirely driven by the Administrator tool. For more
information, see the ENTERPRISE Installation and Administration Guide.
5 Upgrading Oracle Database Server from a Previous
Version
Please consult the Oracle database server documentation for a fuller upgrade
description.
Upgrade To Description
Oracle Oracle 10.2.0.4 Please contact your regional Product

9.2.0.7 (ODBC 10.2.0.4), Support team (see Section 9) for
(ODBC Oracle 11.1.0.7 information on how to achieve this.
9.2.0.6.5) (ODBC 11.1.0.7)
Or Important: The recommended method is
Oracle 11.2.0.1 to create a new Oracle database with the
(ODBC 11.2.0.1) ENTERPRISE 8.0 database schema,
followed by an XML export and import of
the original data from the previous release
of the ENTERPRISE database. However,
for large, complex projects, some
information (such as users, fields and
favourites) cannot be migrated in this
way, and so it may be necessary to import
a full Oracle database dump into an
empty Oracle database. This is not a
straightforward process, and
customers should definitely contact
Product Support for assistance with
this.
Important Notes for RANOPT users:

 If you are migrating from a 9i database to a 10g database, you must manually
register certain files to ensure that the library of RANOPT Excel reports works
correctly. For more information on how to do this, see
http://download.oracle.com/docs/cd/B19306_01/win.102/b14309/intro.htm#BG
BDDACA
and
http://download.oracle.com/docs/html/B10952_01/o4o00105.htm
To do this, you need to have the appropriate OO40 redistributable files
installed. If these are not installed already, do this following the instructions at
http://www.oracle.com/technology/software/tech/windows/odpnet/index.html.
 For RANOPT client installations that will connect to a 10g database, ensure
that the Oracle Client version is 10.2.0.4, as Excel reports do not run on
Oracle Client 10.2.0.1 or 10.2.0.2.
6 Upgrading Database Instance from a Previous Version
Always back up databases before attempting any of the tasks below. Any
damage to databases cannot be undone and you must rely on the backups to
restore your data.
Although the Administrator tool runs the upgrade process, it is essential that the
user who logs into the Administrator tool has the same privileges as the default
Oracle SYSTEM user in order to perform all the activities it requires. Check with
your DBA to ensure the right user performs the upgrade.
During an upgrade, a log file is produced recording the entire process. This file is
stored as C:\Program Files\AIRCOM International\ENTERPRISE
8.0\UPGRADE**.LOG. (where ** is the version number for each upgrade step).
They hold vital information which will help us to diagnose any problems.
If you have experienced any problems during the upgrade please send these
file(s) to your regional Product Support team (see Section 9).
Important: The recommended method is to create a new Oracle database with
the ENTERPRISE 8.0 database schema, followed by an XML export and import of
the original data from the previous release of the ENTERPRISE database.
However, for large, complex projects, some information (such as users, fields and
favourites) cannot be migrated in this way, and so it may be necessary to import a
full Oracle database dump into an empty Oracle database. This is not a
straightforward process, and customers should definitely contact Product
Support for assistance with this.
The following sections contain information for DBAs to consider before upgrading.
For full step-by-step instructions on upgrading, see the ENTERPRISE Installation
and Administration Guide.
6.1 Sizing Rollbacks/Undo Tablespace

Depending on the configuration of your Oracle database, the database will contain
either rollback segments or an undo tablespace.
An ENTERPRISE upgrade is a large transaction which requires considerable
rollback space\undo tablespace.
Ensure that your DBA checks that your database has sufficiently large rollback
segments or undo tablespace to accommodate this transaction.
Sizing depends on the amount of data currently in the database. Running out of
rollback space\undo tablespace during an upgrade will result in an incomplete
upgrade.
6.2 Tablespaces
In addition to rollback\undo tablespace sizing it is important that the sizing of other
Oracle tablespaces and their relevant datafiles is correct. This applies to the
provision of extra datafiles to tablespaces and ensuring that redo log sizing is
sufficient to cater for the transactions undertaken during the upgrade. If you are
unsure of sizing you should speak to your Oracle DBA or contact your regional
Product Support team (see Section 9) with details of current tablespace\datafile
sizes.
During the upgrade to V8.0, the indexes in the AIRCOM schema are moved from
the ENTERPRISE Permanent tablespace to the ENTERPRISE Index tablespace.
This obviously causes the ENTERPRISE Index tablespace to grow in size.
Therefore a preliminary recommendation is to add datafiles (500MB each) as
required to the ENTERPRISE Index tablespace until it has the same storage
capacity as the ENTERPRISE Permanent tablespace. As a minimum we
recommend adding two datafiles to the ENTERPRISE Index tablespace to
increase storage capacity by 1GB (2 x 500MB).
If you are planning on using the Centralised Persistence of User Settings feature
and you have a large number of users we advise that you create a dedicated
tablespace prior to the upgrade. The new tablespace should be dimensioned to a
similar size as the Permanent tablespace and configured to automatically increase
its extents. Please consult the ENTERPRISE Installation and Administration Guide
for an approximate guide to dimensioning your database for usage of persistent
user settings. If you have a very large number of users (for example, 150 or more)
it may be necessary to partition the storage of the user settings tables to improve
their performance. (This must be done prior to upgrade otherwise your user
settings may not be migrated) If this is your requirement, or you have any queries
regarding the use of the feature, please contact your regional Product Support
team (see Section 9).
The upgrade makes use of Oracle cursors during the upgrade. The default setting
for the number of open cursors is 50. Please set this value to at least 255. To do
this set the parameter OPEN_CURSORS=255 for your database instance, and
stop and start the database for the change to take effect.
6.3 Database Consistency Check

Prior to upgrading your database, ENTERPRISE will run a database consistency
check on all of the foreign keys and other constraints inside the database schemas
to ensure that there is no invalid data. This is necessary to prevent various
upgrade errors caused by the offending keys. Any inconsistencies are reported by
the tool and stored in a log file (PreUpgrade.log) for your DBA to use when
resolving any problems.
6.4 AIRCOM Administrator User

The database upgrade from pre V5.0 databases creates a new ‘Administrator’
user for use with Enterprise Admin. If either a user or a role exists with a name of
‘Administrator’, then these should be considered prior to running the upgrade. If
necessary these should be dropped and recreated with a different name.”
6.5 APIs and Interfaces

Any pre-V7.0 APIs and interfaces will also need to be upgraded. Please contact
your regional Product Support team (see Section 9) for assistance with this;
depending on the terms of your contract, you may be charged for this service.
6.6 Database Schema Changes Between 7.0 and 8.0

For a full list of database schema changes that have occurred during the
development of V8.0, please see the ENTERPRISE Database Reference Guide.
6.7 User Preferences

User Preference Settings are preserved when upgrading to V8.0 from V5.0
onwards. Unless configured otherwise, the default preferences are now stored at
the following location in the registry:
HKEY_CURRENT_USER\Software\AIRCOM International\ENTERPRISE\Settings
Settings are further stored by a Server, Instance, Project and User basis.
When ENTERPRISE is launched it will use the settings found at this location. If no
settings exist ENTERPRISE populates the registry with defaults.
Remember all ENTERPRISE users need sufficient rights to edit values related to
the tool in the registry. Without these rights, users will not be able to define certain
criteria in the tool. Contact your IT administrator to ensure standard users have
these rights.
Tip : IT administrators can use REGEDT32.EXE to define rights to individual
programs in the registry and leave all other access as it is if required.
To keep a backup of your registry settings between builds you can take an export
of the registry settings and import them after the installation. To export them:
 Start the REGEDIT program.
 Browse to HKEY_CURRENT_USER\Software\AIRCOM
International\ENTERPRISE\Settings.
 Highlight this and then Registry > Export registry file.
6.8 Change made to the Prediction Folder .dat file

ENTERPRISE supports third party propagation models, and some of these use a
dynamic licensing system, where a prediction calculation can fail if no licence is
available at that time.
To improve this situation, the prediction system has been updated to allow such
calculations to be re-tried at specified intervals for a specified maximum length of
time. To allow adjustment of these timeout values on a client (ENTERPRISE)
instance, ENTERPRISE has been updated to read them from two new fields in the
Config.dat file (stored in the Predictions folder specified for each project).
If the Config.dat file was created by a version of ENTERPRISE prior to V6.2 Fixed
Patch Level: R20.0.2, the two new fields will not be present, and when a project is
opened, a warning error message will be displayed in the Message Log, as
follows:
The same warning appears in a Warning Message Box if you click on the Info
button in the Start Project dialog box.
These messages prompt you to amend your Config.dat file so that it has the two
new fields.
Note: Even if you do not use third party propagation models, we recommend that
you address this issue, so that these messages will no longer appear.
You can either follow the steps described in the message itself, or if you prefer,
you can perform the following steps:
1 Close the project.
2 Locate your existing Config.dat file. You will find this in your Predictions folder.
Here is an example:
3 Save a backup copy of the file.

4 Open your existing Config.dat file.
This is how the top section of your existing Config.dat file should look (assuming
you are using default values):
Note: The values for each line are the default values.
5 After the line containing '[Job Limit] 2147483647', insert the following two new
lines, and their default values:
[Dynamic Model License Re-Try Interval (Secs)] 30
[Dynamic Model License Total Re-Try Time (Secs)] 3600
This is how the top section of your new Config.dat file should look, after adding
the two new lines:
6 Save and close the Config.dat file.
The new fields will then be available to ENTERPRISE, and the warning will no
longer be displayed for any project using that Prediction folder.
Note: You should make this amendment to the Config.dat file in every Prediction
folder accessed by ENTERPRISE. For example, if you only have one project, or if
all your projects point to the same Prediction folder, then you only need to do this
once.
Please contact AIRCOM support or your ENTERPRISE system administrator if
you have any queries or require any assistance.
6.9 Filter Migration Procedure for WiMAX Users

If you are upgrading to version 8.0 from version 5.2, 6.0, or 6.1, and you use one
of the WiMAX technologies, you must pay special attention to an essential
procedure to update your filters. If you do not do this, there is a risk that your
WiMAX filters and fields will not be successfully migrated into version 8.0, which
may mean they would need to be recreated manually.
Important:
This procedure is only necessary if:
 You use one or both of the following technologies: Fixed WiMAX and/or Mobile
WiMAX.
- AND -
 You are an existing customer upgrading to 8.0 from 5.2, 6.0, or 6.1.
This procedure is not necessary if any of the following is true:
 You are a new customer to 8.0.
 You were a new customer to 6.2 or 7.0 (and are now upgrading to 8.0).
 You have already upgraded to 6.2 from a previous version (and are now
upgrading to 8.0). In this case, you should already have performed this
procedure, and you do not need to perform it again.
Why is the Update Procedure Necessary?
Improvements were made to ENTERPRISE 6.2, enabling multiple technologies to
be used in the same project. As a consequence of this, any WiMAX filters and
fields that were created in previous versions (5.2, 6.0, 6.1) need to be updated to
be compatible with later versions. This is because existing Filters will all be
referencing the old UMTS equivalent types and will need updating in order to work
as they did before.
This is achieved by using a special updating procedure (using XML Export/Import)
which needs to be performed after the upgrade process.
Which Types of Filters will be affected?
The following types of rules may require an update to work correctly depending on
their rule definitions:
 Static filters
 Dynamic filters based on Attributes (such as antenna types, propagation
model used)
 Dynamic filters based on Network Elements (such as nodes or cells)
 Dynamic filters based on Fields (user-specified flags, such as rollout phase or
region)
Automatic Changes Performed by the Upgrade to 8.0
The general upgrade to 8.0 will perform some automatic changes (from UMTS) for
these types of filter:
 Static filters - any object will be corrected to the appropriate type, Fixed
WiMAX or Mobile WiMAX, in the filter
 Dynamic filters based on Attributes - any attribute that is unique to either Fixed
or Mobile WiMAX will be corrected to the appropriate type in the filter
This same logic is also applied for any XML Imports into 8.0 that involve UMTS
filters.
Note: No other automatic filter changes are performed by the Upgrade.
How the Update Procedure Should be Performed

The recommendation is as follows:
1 Perform the upgrade to ENTERPRISE 8.0.
Note: The general upgrade to 8.0 performs some automatic changes, as
detailed in the above section. The special XML Import (Options) procedure,
described below, enables you to have control of selecting which of the WiMAX
technologies is considered when the filters are modified.
2 After the upgrade has been successful, perform an XML Export for the filters
that you wish to update. This will be necessary for those filters that you want to
become exclusively Fixed WiMAX filters or Mobile WiMAX filters, depending
on the technology you use. (If you use both technologies, you will need to do
this separately for each.)
3 Perform the initial steps of an XML Import, preparing to import the same file
you have just exported.
4 In the XML Import dialog box, on the Filters tab, click the Options button. The
migration options are as follows:
Option selected Operation Outcome

Override checkbox n/a. No static, network element or fields
unselected rules will be changed.
Override checkbox Any rules in the XML indicating UMTS Cell, The import will attempt to make the
selected and Mobile UMTS Node or UMTS Repeater will be changes (this affects the dynamic
WiMAX chosen treated as meaning Mobile WiMAX Cell, rules and static lists). This may
Mobile WiMAX Node or Mobile WiMAX result in some records/objects not
Repeater. being imported if the XML is not
correct. For attribute rules only,
Override checkbox Any rules in the XML indicating UMTS Cell, those which are present on both
selected and Fixed UMTS Node or UMTS Repeater will be UMTS and Fixed WiMAX would be
WiMAX chosen treated as meaning Fixed WiMAX Cell, changed, but all others will import
Fixed WiMAX Node or Fixed WiMAX as UMTS, unchanged from before.
Repeater.
Note: Whichever of the above is selected, please bear in mind that the
automatic changes (static filter objects and dynamic filters attributes) will still
have take place during the upgrade.
The following picture shows an example of the dialog box:
Example of Filters Options for Special Updating Procedure
7 Important Notices
7.1 Versions No Longer Supported
With the release of V8.0, AIRCOM will no longer provide patches for V6.2 or
earlier. Customers on versions 6.2 or earlier are advised to upgrade as soon as
possible.
7.2 All ENTERPRISE Customers

Important : You should be aware of these issues that affect an Upgrade to 8.0:
 There is a new Co-ordinate System method deployed in ENTERPRISE
v8.0. This is a newer and more efficient system for storing and
converting geographical coordinates. It uses projection systems
specified by a single number, termed EPSG (European Petroleum
Survey Group).
This new EPSG system replaces the old system (Geocalc). The old
system still exists within the tools in v8.0, but it is now dormant, except
where it assists with upgrade. It will be completely removed at some
future stage.
 When upgrading a database to v8.0, a Database Upgrade wizard now
appears on Upgrade. Because of the new EPSG Code functionality, the
upgrade to v8.0 must be performed with the utmost care. There are
some critical checks and procedures, and it is vital that they are
actioned correctly.
 For the ‘AIRCOM’ schema tablespace, the schema will be migrated to
become ‘NETWORK_PLANNING’. Due to this schema rename, we
strongly recommend that before your users connect to the upgraded
database, to ensure the optimal performance of the Oracle database
after the upgrade, you execute the following steps :
o Connect to the database as a user with sysdba permission such as
‘sys’
o Execute the following command (which may take some minutes):
‘exec dbms_stats.gather_dbms_stats;’
o Logout
For detailed information on the above issues, please refer to the
ENTERPRISE Installation and Administration Guide.
 There was an important change made to the Prediction Folder .dat file in V6.2
Patch Fix Level R20.0.2. If you had not already upgraded your V6.2
installation to this patch level, you should read Section 6.8.
 Differences between predictions can potentially be observed between V6.1
(and greater) and V6.0 (and earlier). These differences are minor and are due
to the changes that Microsoft introduced in their code optimisation module of
the compiler (which occurred between ENTERPRISE V6.0 and V6.1) used by
AIRCOM for developing ENTERPRISE, and also in part due to improvements
in accuracy in the new prediction file system. It should be noted that the
differences in prediction results between V6.1 (and greater) compared to V6.0
(and earlier) of ENTERPRISE can be particularly apparent if the height / clutter
data index file coordinates do not adhere to the map data format requirements,
as warned in the message log when you open the project.
 There is a known issue with Oracle 10g whereby it can no longer handle
values with a very high precision (above 15 decimal places). ‘Original Error
Text: [Oracle][ODBC][Ora]ORA-01406: fetched column value was truncated’. If
you encounter this error, please contact Product Support for a cleanup script
to run on the database to sanitise the data.
 There is a known issue with Oracle 10g Standard Edition whereby you will
receive the following error message when starting ENTERPRISE: ‘Original
Error Text: [Oracle][ODBC][Ora]ORA-00439: feature not enabled: Application
Role’. The Application Role feature is used in ENTERPRISE to prevent other
Oracle users from having the privileges to modify the AIRCOM schemas, so if
this required, you should use Oracle Enterprise edition instead. Otherwise, this
error will not affect the ENTERPRISE functionality.
 ENTERPRISE does not support background printing and users should not
alter the 2D view whilst printing is in progress. ENTERPRISE now outputs a
warning message in the message log to warn users of this.
 When using OS Authentication with large Domains of more than 1000 users or
groups, it can be very slow populating the list box. This is not an issue that
AIRCOM is able to address as the response time on populating / aborting
searching is beyond our control and dependent on the user’s Network
size/speed and Domain sizes.
 If you have trouble enabling OS Authentication, please ensure that the
following line exists and does not have a preceding ‘#’ symbol in your
sqlnet.ora file (located in the Network\Admin folder under your Oracle Home
location):
SQLNET.AUTHENTICATION_SERVICES = (NTS)
 There exists an Oracle Initialisation and Database parameter called
CURSOR_SHARING which is designed to improve database cache efficiency
when set to the value SIMILAR. This setting is not currently supported by
ENTERPRISE and will cause errors such as “ORA-01008: not all variables
bound ” when performing functions such as upgrades, creation\deletion of
projects\users, or any other operations which use stored procedures. We
strongly recommend that this CURSOR_SHARING parameter is set to EXACT
at all times.
 Enterprise.exe (and all its variants), ARRAYWIZARD executables and Db
Commander are now configured to support memory addresses of up to 4GB
on x64 machines. Therefore there is an increase in memory consumption.
 If the menu.txt file containing your clutter codes includes codes with negative
values, these must be changed. From V6.2 onwards, the clutter codes must
be integers between and including 0 to 32767.
 The different ENTERPRISE tools are compiled as follows:
ASSET Visual Studio 2008, Unmanaged C++ and C#
ADVANTAGE Visual Studio 2008
AIRCOM OPTIMA Borland Development Studio 2006
RANOPT Borland C++ Builder 5, Visual Studio 2008 and C#
 In ENTERPRISE 8.0, if you intend to perform an XML import (with XSD

validation activated) that includes any of the following propagation models:
 SUI model (IEEE 802.16 SUI Model V1)
 SLR model (Standard Long Range Model v1)
BEFORE performing the XML import, you must either:
Simple Edit using the ENTERPRISE Interface (8.0 to 8.0 only)
1 Edit the model(s) in ENTERPRISE 8.0. This can be as simple as
modifying the name or adding a comment:
2 Apply the changes.

3 Perform the XML Export.
4 Perform the XML Import to ENTERPRISE 8.0.
- or -
Simple Edit of the Exported XML Files
1 Perform the XML Export in ENTERPRISE 8.0 (or an earlier version if
required).
2 In the exported file, edit the line containing the SUI and/or SLR model
tags, so that the content after the space is removed.
So, for example:
Should be edited to:
3 Perform the XML Import to ENTERPRISE 8.0.

If you do not do either of the above, an error appears in the message log and
any SUI or SLR models do not get imported.
 ENTERPRISE 8.0 has remodelled all AMPS/TDMA related data as a subset of
the GSM data set. This means that AMPS/TDMA is still implicitly supported,
even though it has been removed as an explicit technology from the
File>Preferences dialog box. This has improved the performance and memory
footprint of ASSET.
 The Enhanced Macrocell propagation model now includes Line Of Sight (LOS)
information in the generated predictions. For this reason, when you run
pathloss predictions for cells using this model in Enterprise 8.0, matching
predictions created under previous versions of Enterprise will be considered
out of date, and will be re-generated. This was done to ensure consistency
across all Enhanced Macrocell model predictions, that is, to ensure that they
all have LOS information available.
 When using the KML/KMZ File Export for use with Google Earth, we strongly
recommend that you use Google Earth version 6.1 or later.
 The Database field ANTENNAPATTERNANGLE will be reset to zero during an
Upgrade to v8.0. Previously, it played no role, but it now will play a role in
storing the horizontal offset for antennas, which will be displayed in the user
interface.
 You should be aware of two major changes affecting an Upgrade to v8.0:
o For the AIRCOM schema tablespace, the schema will be migrated to
become NETWORK_PLANNING.
o A Database Upgrade wizard now appears on Upgrade. In one of the
steps, you will need to select an EPSG Code, which identifies the region in
which your network resides. It is important to make sure selection of this is
correct.
For full information on the above, see the ENTERPRISE Installation and
Administration Guide.
7.3 ARRAYWIZARD
 If you are upgrading from V5.1 or earlier, ARRAYWIZARD users must ensure
that previous ARRAYWIZARD installations are completely de-installed from all
agents before installing V6.2 or later.
 We don’t recommend using mapped network drives in the path to map data or
coverage array folders when using ARRAYWIZARD. Instead the user should
use a UNC name.
 We recommend using the same user for the ARRAYWIZARD Administrator
and the agents. All servers should use the same database user, and all
servers should use the same Windows user.
 Only one instance of the Administrator should be run for each database.
Running a single instance is not enforced, but will result in some non-fatal
database errors.
 We recommend that users run their servers in ‘Automatic’ mode. In this way
any new projects and added and items deleted from the database will be
noticed when the agents restart.
 ARRAYWIZARD requires that the ODBC Data Source is configured as a
System DSN rather than a User DSN.
7.4 ASSET
 ENTERPRISE V8.0 uses the following versions of the propagation models:

Model Version
Siradel Volcano 3.1.0.1
Wavecall Wavesight 8.0.0.0
AWE Communications WinProp 12.0.0.0
MYRIAD 400
 If you are upgrading from V5.2.2 (or earlier) before installing V8.0, ensure that
the prediction folder is empty. This is important for the disk space tracking
feature – it will only track disk space that was consumed by the new prediction
system.
 When running distributed predictions, it is possible that you may receive the
following error message: “Unable to obtain a prediction file lock (The process
cannot access the file because it is being used by another process)”. This can
occur sporadically (if two or more agents happen to attempt to write the same
prediction at the same time). The system attempts to recover from this by
backing off for a random time interval before re-trying the write operation. If the
error is seen to occur too frequently, the value in the “[File Write Retry Count]”
section of the ‘Config.dat’ file in the prediction folder can be increased in steps,
until the problem subsides.
 If you are trying to create distributed predictions and the coordinator machine
has more than one network card, then you may see some problems. If you
experience unexplained communication problems between the coordinator
and one of the other components (especially the agents), then you could be
experiencing this problem. Please contact your regional Product Support team
(see Section 9) for more information.
 The Extended Character Support feature is subject to a number of limitations.
For more information, see Section 3.6.
 In ENTERPRISE 8.0, the Simulator now handles repeaters in a better way. In
7.0 and earlier versions, loading a cell into the Simulator would cause all of its
child repeaters to be loaded too, whether or not they were in the chosen filter.
But in 8.0, when loading cells into the Simulator, a repeater will only be loaded
if it was in the filter used to load its parent cell. So you can now easily omit
repeaters from the simulations and coverage arrays by excluding them from
the filter used in these wizards. The GSM Non-Sim coverage arrays are
unaffected because they already only included repeaters if they were in the
filter.
Note: For the Simulator to load a repeater, the repeater and its parent cell
must be included in the filter.
 ENTERPRISE 8.0 now provides the option for a non-hierarchical structure in
the Site Database for GSM. This means that GSM networks can now be
modelled in the same way as other technologies such as UMTS and LTE,
including the potential for logical/cellular connections. Because of this
enhanced capability, users who have databases with a large number of GSM
data elements may experience slightly longer project-load times in 8.0
compared to 7.0.
 LTE in ENTERPRISE 8.0 uses different definitions of EPRE, RSRP, RSRQ,
and RS SNR compared to 7.0. Therefore in 8.0 the signal strength will be
greater by fractions of a dB (depending on the cyclic prefix). Please refer to
the "LTE Static Simulations v8.0" document for the latest formulae.
 In cases where you are generating a Site/Node Report into Excel for large
amounts of network data (for example, 30,000 cells) with most of the reporting
items selected, you may encounter a message from Microsoft Excel ® that
prompts you to select less data or close other applications. If so, when you
click OK, the report is displayed with the amount of data generated up to that
point, and the following message is shown in the Message Log:
“The amount of data selected is too big to be reported in Excel, hence report generation is
stopped. Some data may be missing."
7.5 CONNECT
 As a result of the Carried Traffic Analysis enhancements in v8.0, a number of
new traffic values have been introduced, including the Uplink and Downlink
Percentages for CS and PS traffic.
If you are upgrading to v8.0 from a previous version of CONNECT, these
percentage values are managed as follows:
Item Description
Cellular Connections Percentages are calculated automatically.
Non-LTE Logical Connections All set to 0, which means that the logical connection traffic will be 0
as well.
However, you can edit these values.
LTE Logical Connections – X2 Uplink percentages will be set to 0.
interfaces (between 2 eNodeBs) Downlink percentages will be set to match the Handover
Percentage (%) on the Carried Traffic tab of the respective
eNodeB.
Note : This value is not available in v8.0, as it has been replaced
by the downlink percentages.
LTE Logical Connections – S1 At the SGW, all percentages will be set to 0.
interfaces (between a SGW and At the eNodeB, all percentages will be set to 100.
an eNodeB)
 As a result of the improved capacity support for AMC in v8.0, when defining
capacity information for radio equipment, you can now specify a different
capacity for each modulation type, rather than just once for the radio.
Therefore, during upgrade:
o For radios that do not use AMC, if the Maximum IP Capacity is 0, then it
will take the value set for the static modulation type. If the Maximum IP
Capacity is any other value, then this value will be retained
 As a result of the introduction of multiple ATPC ranges and XPIF values for
AMC in v8.0,
 As a result of improved signature support for AMC in v8.0, when defining
signature information for radio equipment, you can now specify different
signature settings for each modulation type, rather than just once for the radio.
Therefore, during upgrade:
o The ‘Use the same parameters for all modulations’ options will be set by
default
o All modulation types will be given the same values, based on the default
modulation type for the radio
7.6 RANOPT
 AIRCOM will not introduce and/or support any new releases of the ASCOM
TEMS proprietary binary format (.LOG) as measurement files that can be
loaded into RANOPT from the end of October 2010.
7.7 Citrix Users

 V8.0 has currently been verified for use on Citrix Xenapp 6 and Citrix Xenapp
5 – see Section 3.2 for more information. It is very important that the Citrix
Server is configured and dimensioned to AIRCOM guidelines. Please contact
your regional Product Support team (see Section 9) for assistance.
 When using ENTERPRISE in a Citrix environment with Windows 7, we
strongly recommend that you do not close any windows from the taskbar, as
this can cause problems with some operations such as KML export.
8 Known Issues with this Release
The following issues have been identified during our testing. We will endeavour to
correct them as soon as possible in the post-release patches or future releases
(where applicable).
ID Description
AS-29303 When using Volcano, the Distributed Prediction Agent does not run predictions as
the user specified in the Coordinator Options dialog box.
AS-29312 EiRP and ERP are not refreshed when the PA output is changed to the maximum
value of what is set in the BTS Equipment.
AS-29313 When using Volcano v3.1, the predictions cannot be aborted when the new 'run-
as-multi-process' option is active.
AS-29314 ENTERPRISE freezes after opening the MYRIAD Help file, if the MYRIAD model
parameters are edited.
AS-29319 SLR and SUI models will not run on a standalone distribution agent.
AS-29341 Users may experience crashes when running Distributed Predictions for Winprop.
AS-29355 The Browse function does not work properly when selecting Cellular Antennas.
AS-29357 In the Site Template, Rx Diversity does not persist after the user logs out.
AS-29366 Interference Matrix write option disabled.
AW-1026 MID MIF tiles not abutting correctly. This causes a gap between the TAB files.
AW-1089 When Array Wizard agents are logged in to a database as RSU, the user is only
allowed Read Only access in ASSET.
CT-8929 URP doesn’t route the logical/cellular connections properly.
This issue only affects CONNECT Professional customers and will be resolved in
the end of February patch.
CT-8867 While AFCP is running, if you export the xml and change the channel number
then import it back, ENTERPRISE crashes.
EC-17737 Sandbox users may experience ENTERPRISE crashes when using the CDMA
technology.
EC-17738 The Site Node Report function may not generate an Excel file successfully when
using a large database.
EC-17767 Sandbox users may find that certain elements do not merge successfully.
RT-6089 Snapshots not retreiving WCDMA and GSM information.
RT-6090 Cannot include polygons (system and user vectors) in a filter. Cannot open
clipboard.
9 Reporting a Bug
If you experience a fault with the software or the upgrade, please send a full report
with Version Number, Build Number and Type of Database to your regional
support centre, for example, V7.0.xxRx and Oracle 10.2.0.
9.1 Europe
Main Switchboard: +44 1932 442000
Product Support: +44 1932 442345
Email: support@aircom.co.uk
Web: www.aircominternational.com/support
Operating Hours:
0830 to 1800 UK time, Monday to Friday, excluding UK Public Holidays
9.2 Americas
AIRCOM International Inc
Main Switchboard: +1 214 576 2700

Product Support: +1 214 576 2701
Email: support@aircominc.com
Operating Hours:
0830 to 1800 Dallas time, Monday to Friday, excluding US Public holidays
9.3 Asia Pacific

AIRCOM International Pte Ltd
Main Switchboard: +65 6372 0548

Product Support: +65 6372 0548
Email: supportsg@aircominternational.com.
Operating Hours:
0830 to 1800 Singapore time, Monday to Friday, excluding Singapore Public
Holidays
9.4 Middle East
AIRCOM Middle East & Africa

Product Support: +971 4 391 2642
Fax: +971 4 391 8141
Email: supportme@aircominternational.com
Operating Hours:
0830 to 1800 Dubai time, Sunday to Thursday, excluding UAE Public Holidays
9.5 Africa
AIRCOM International South Africa (pty) Ltd

Product Support: +27 11 745 1381 (Radio Planning)
+27 11 745 1496 (OSS)
Email: support@aircom.co.za
Operating Hours:
0830 to 1800 SA time, Monday to Friday, excluding SA Public Holidays
9.6 India
AIRCOM (India) Private Ltd
Main Switchboard: (+91) 124 4102445-49

Product Support: (+91) 124 410 24500
Email: supportindia@aircominternational.com
Operating Hours:
0830 to 1800 India time, Monday to Friday, excluding India Public holidays.
9.7 All Other Countries

Please use Europe contact details above.

Aircom Asset

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Aircom Asset

Încărcat de

Drepturi de autor:

Formate disponibile

ENTERPRISE Version 8.

0 Commercial Release Notes

Author: AIRCOM International

2.1 What’s New in ENTERPRISE 8.0?

2.1.1 XML Schema Validation

2.1.2 Selection Expert Enhancements

2.1.4 Using WMS Client

2.1.5 Map View Enhancements

Measure the distances between points on a line, and the

Show the coordinates of a point.

Measure the size of an area.

Change the display properties of the above tools.

To preserve the information displayed by these tools, you can do so by saving

2.1.7 Export Geo-Transform Raster Outputs

2.1.8 Multi-Coordinate System Data

2.1.9 New Filterable State for Objects (New, Modified, Committed)

2.2.1 Group Level Apply (Sandboxing) in Administrator

2.2.2 Licensing Reservation Tool

2.3 What’s New in ADVANTAGE 8.0?

2.3.1 Antenna Constraints in Site Database

2.4.1 Interference Table (Matrix) Support

2.4.2 New Parameter Sets for Location-related Planners

2.4.3 LTE Support

2.4.4 Independent ARRAYWIZARD Scheduler with Web Service Interface

2.5.1 Improved Antenna Management

2.5.2 Information about Simulated Terminals

2.5.3 Map View Enhancements for Displaying Neighbours

2.5.4 Model Assignment Calculator Enhancement

2.5.6 Neighbour Planning Wizard based on Traffic

2.5.7 Neighbour Planning Wizards using Background Thread

2.5.9 Prediction Radius Calculator Enhancements

2.5.10 Restricting Coverage and Simulation Arrays to Vectors

2.5.11 Site Database – Customisable Object Count

2.5.12 CDMA2000 and EV-DO – Enhanced PN Code Planner

2.5.13 GSM – Optional Network Hierarchy and Support for Logical

2.5.14 GSM – Writing Interference Table Traffic to Sub-Cells

2.5.16 GSM and UMTS – Location Based Services Planner

Calculation Method Basis of Centre of Gravity Calculation

Area The cell's service area.

Traffic The traffic within the cell's service area.

2.5.17 GSM and UMTS – Polygon Assignment Planner

Calculation Method Basis of Polygon Assignment Calculation

2.5.18 LTE – Line of Sight Array and Improved MIMO Modelling

2.5.19 LTE – Scheduled Users Limit added to Simulator

2.5.20 LTE – Support for MME and SAEGW Network Elements

2.5.21 Planning Wizards – Copying Data to Clipboard

2.6 What’s New in CONNECT 8.0?

2.6.1 Automatic Frequency and Capacity Planning

3.2 Operating System, Service Packs and Oracle Version Support

3.3 Test Matrices Per Product

3.3.1 ENTERPRISE Core, ASSET, ARRAYWIZARD and ADVANTAGE

3.4 Upgrading to V8.0 Licences

3.6 Character Sets

3.7 Regional Settings

4.2 Installing ENTERPRISE Software

4.2.1 Installation Prerequisites

4.2.2 Installation Procedure

4.3 Upgrading ENTERPRISE Software from a Previous Version

ENTERPRISE Version DB Version

Version 5.0.3 Build 17R63 5059

Version 5.1.1 Build 38R66 5127

Version 5.2.2 Build 9R78.0.1 5211

Version 6.0 Build 43R95.0.1 6026

Version 6.1 Build 118R98.0.1 6135