RN70

ENTERPRISE Version 7.
0 Commercial Release Notes

Author: Date: AIRCOM International 1 October 2010
Copyright 2009 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 Whats New in V7.0 Release?.................................................................................................5 2.1 Whats New in ADVANTAGE?.........................................................................................5 2.1.1 LTE Support..............................................................................................................5 2.1.2 New Dominance Metric..............................................................................................5 2.1.3 Rollout/Ranking Enhancements.................................................................................5 2.1.4 Reporting Enhancements...........................................................................................6 2.1.5 Extra Flexibility on the Element Status Tab................................................................6 2.1.6 New and Improved User Interface..............................................................................7 2.1.7 Financial Analysis: Support for CDMA2000, EV-DO and LTE.....................................8 2.1.8 Financial Analysis: New Expenditure Metric...............................................................8 2.2 Whats New in ASSET 7.0?.............................................................................................8 2.2.1 LTE Support..............................................................................................................8 2.2.2 Carried Traffic Analysis..............................................................................................9 2.2.3 Interference Table Functionality.................................................................................9 2.2.4 Antenna Instance IDs...............................................................................................11 2.2.5 Extended Character Set Support..............................................................................11 2.3 Whats New in CONNECT 7.0?.....................................................................................11 2.3.1 Backhaul Carried Traffic Analysis.............................................................................11 2.3.2 Enhanced Adaptive Modulation Coding Functionality...............................................12 2.3.3 Ethernet/IP Radio Support.......................................................................................12 2.3.4 TDD Radio Support..................................................................................................12 2.3.5 Support for the Latest ITU Recommendations..........................................................13 2.4 Whats New in ENTERPRISE 7.0?................................................................................13 2.4.1 Extended Character Set Support..............................................................................13 2.4.2 Google Earth Support..............................................................................................14 2.4.3 Licensing Configurations and Permissions...............................................................14 2.5 Whats New in RANOPT 7.0?........................................................................................14 2.5.1 Intelligent Filters.......................................................................................................14 2.5.2 Super Filters............................................................................................................15 2.5.3 Two-Step Deletion of Measurement Files.................................................................15 2.6 Whats New in WEBWIZARD 7.0?.................................................................................15 3 System Requirements...........................................................................................................16 3.1 Hardware Requirements................................................................................................16 3.2 Operating System, Service Packs and Oracle Version Support.....................................16 3.3 Test Matrices Per Product.............................................................................................18 3.3.1 ENTERPRISE Core, ASSET, ARRAYWIZARD, ADVANTAGE, CONNECT and RANOPT..........................................................................................................................18 3.3.2 WEBWIZARD..........................................................................................................19 3.4 Upgrading to V7.0 Licences...........................................................................................19 3.5 Large Fonts...................................................................................................................20 3.6 Character Sets..............................................................................................................20 3.7 Regional Settings..........................................................................................................20 4 Installation............................................................................................................................20 4.1 General Information.......................................................................................................20 4.2 Installing ENTERPRISE Software..................................................................................20 4.2.1 Installation Prerequisites..........................................................................................20 4.2.2 Installation Procedure..............................................................................................21 4.3 RANOPT Interface Pack................................................................................................22 5 Upgrading Oracle Database Server from a Previous Version................................................23 6 Upgrading Database Instance from a Previous Version........................................................24 6.1 Sizing Rollbacks/Undo Tablespace................................................................................24
Author: AIRCOM International Date: 1 October 2010
ENTERPRISE Version 7.0 Commercial Release Notes
p.2 of 44
6.2 Tablespaces..................................................................................................................24 6.3 Database Consistency Check........................................................................................25 6.4 AIRCOM Administrator User..........................................................................................25 6.5 APIs and Interfaces.......................................................................................................25 7 Upgrading ENTERPRISE Software from a Previous Version.................................................26 7.1 Database Schema Changes Between 6.2 and 7.0.........................................................27 7.2 User Preferences..........................................................................................................27 7.3 Change made to the Prediction Folder .dat file..............................................................27 7.4 Filter Migration Procedure for WiMAX Users..................................................................29 7.4.1 Attributes Automatically Upgraded or Changed by an XML Import...........................33 7.4.2 Attributes Specifically Controlled by the XML Import Options...................................34 8 Important Notices..................................................................................................................36 8.1 Versions No Longer Supported......................................................................................36 8.2 Deprecated Features from ENTERPRISE 7.0 Onwards.................................................36 8.3 All ENTERPRISE Customers.........................................................................................36 8.4 ADVANTAGE................................................................................................................37 8.5 ARRAYWIZARD............................................................................................................39 8.6 ASSET..........................................................................................................................40 8.7 Citrix Users....................................................................................................................40 8.8 CONNECT....................................................................................................................40 8.9 RANOPT.......................................................................................................................41 8.10 WEBWIZARD..............................................................................................................41 9 Known Issues with this Release............................................................................................42 10 Reporting a Bug..................................................................................................................42 10.1 Europe........................................................................................................................42 10.2 Americas.....................................................................................................................42 10.3 Asia Pacific..................................................................................................................43 10.4 Middle East.................................................................................................................43 10.5 Africa...........................................................................................................................43 10.6 India............................................................................................................................43 10.7 All Other Countries......................................................................................................44
p.3 of 44
Important Information
This document aims to clarify any issues involved with the installation of ENTERPRISE V7.0. Please read the 'Installation' section carefully before installing ENTERPRISE V7.0. V7.0 of ENTERPRISE is a major new release, with many new features and changes to existing functionality. We believe it represents a major step forward for the tool. 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 V7.0 before going live. A well-planned implementation of V7.0 will minimise disruption to the live planning environment. AIRCOM recommend these minimum steps: Read the V7.0 Release Notes thoroughly before installation/upgrade. Read the V7.0 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, including a Whats New? document - please take time to study these. Your regional Product Support team (see Section 10) can provide an Upgrade Checklist document to assist in the above steps, or discuss any queries on this process.
p.4 of 44
Whats New in V7.0 Release?

The following information describes briefly what is new in ENTERPRISE 7.0 Release. For more detailed information, please refer to the Whats New in ENTERPRISE 7.0? Quick Reference Guide, available on the AIRCOM support website (www.aircominternational.com/support).
2.1 Whats New in ADVANTAGE?

In ADVANTAGE 7.0, the following additional features are now available. 2.1.1 LTE Support
ADVANTAGE 7.0 provides complete support for LTE. You can perform network optimisations and analysis of LTE networks, and generate the relevant reports. The LTE network parameters are fully integrated with ASSET, in terms of LTE carriers, services, bearers and terminal types. Note : LTE is also fully supported in the Financial Analysis module and ASSET ACP (both are licensed add-on products). For comprehensive information, please refer to the: ADVANTAGE User Reference Guide Financial Analysis User Reference Guide ASSET ACP User Reference Guide New Dominance Metric
2.1.2
The ADVANTAGE optimisation and analysis framework offers a choice of two cost mechanisms each with its own set of metrics: Array-based: This refers to pixel-based values calculated during array generation. Service-based: This refers to the averaged values for successful connections based on a series of simulation snapshots, and relies on traffic rasters.
In ADVANTAGE 7.0, the Array-based mechanism now offers (in addition to signal strength and signal quality) a new metric based on dominance. This enables you to optimise or analyse based on acceptable thresholds for this metric. Here is a general definition of this metric: 'The maximum number of polluters/interferers that are acceptable per pixel'. The precise terminology used in the RF Array Thresholds pages varies according to the technology, as shown in this table: Technology GSM UMTS CDMA/EV-DO LTE 2.1.3 Term used in RF Array Thresholds Polluters Pilot Polluters Pilot Polluters Dominance Interferers
Rollout/Ranking Enhancements
In ADVANTAGE 7.0, the Ranking dialog box (accessed from the Analysis functionality) has been renamed to the Rollout Planning dialog box, and there are additional options to display the columns for Absolute Values and/or Additional
p.5 of 44
Improvement (this has no impact on the report, which always includes both types of information). Note : This functionality is also available in the Financial Analysis module and in ASSET ACP. 2.1.4 Reporting Enhancements
ADVANTAGE 7.0 enables an organisation to configure its own presentation styles for the following reports: Analysis report Optimiser report Rollout Planning report Financial Analysis report Financial Analysis (Difference Method) report
This flexibility can be achieved with user-customised stylesheets based on XSLT (Extensible Stylesheet Language Transformations), allowing the reports to be run directly from cached XML data. ENTERPRISE Administrator enables you to import, export and edit any number of XSLT report formats. The module provides a dialog box in which you can set up and manage the report formats for each of these reports. If required, you can do this on a per project and per user group basis. Notes : If you decide to set up customised report formats, this means that there will be multiple available formats for some or all of the reports (because the defaults cannot be removed). In the ADVANTAGE tool, the individual user can determine the 'mapping' of the required report format to each report type. This functionality is also available in the Financial Analysis module and in ASSET ACP. Extra Flexibility on the Element Status Tab
2.1.5
In ADVANTAGE 7.0, on the Element Status tab, you can now specify that you want your existing network elements to be initially considered as OFF when creating a new plan. (Previously, you could only do this for new network elements.) This functionality can provide several benefits: Improved Selection Planning: The Optimiser can start from a realistic snapshot of the existing network, because new elements will not be initially switched 'ON'. Improved Cost Modelling: The Optimiser can discriminate between new and existing elements when it considers action costs (for actions such as azimuth changes) - only existing elements can incur such costs. Improved Cost Comparisons: You can compare the cost/benefits of turning 'ON' new cells, and/or switching 'OFF' existing cells. If you have a licence for the Financial Analysis module, there are additional benefits: o If you want to evaluate additional captured revenue, rather than total captured revenue, you can differentiate between existing and new network elements (only the new elements contribute to the additional revenue). o CAPEX/OPEX element costs will be considered differently between new and existing elements when calculating Net Income or Return On Investment.
A plan can include both new and existing network elements; the purpose of these options is to enable you to specify one or both categories as OFF.
p.6 of 44
If you do not select either option, the created plan will initially consider all elements as ON (in effect, it makes no distinction between new and existing elements). Here are some examples of when you might find these options useful: If You Want to Achieve an Optimised Network Plan Where the plan's starting point is a true representation of the real-life starting point (existing elements ON, new elements OFF). Where the plan's starting point is independent of the real-life network (existing elements OFF, new elements ON). You Can Perform These Steps 1. Select the 'New network elements...OFF' checkbox. 2. Create your plan. 3. Run an optimisation. 1. Select the 'Existing network elements...OFF' checkbox. 2. Create your plan. 3. Run an optimisation.
Where the plan's starting point has none 1. Select both of these checkboxes. of the elements set to ON. 2. Create your plan. 3. Run an optimisation. 2.1.6 New and Improved User Interface
In ADVANTAGE 7.0, there are some minor user interface improvements, concerning the Optimiser Workflow dialog box. New Toolbar Icon The toolbar button to access the Optimiser Workflow has been modified as follows: Previous New
New Workflow Icon The icon representing each separate page in the workflow has been modified as follows: Previous New
Changes to Terminology In ADVANTAGE 7.0, there are some areas of the interface where the terminology has been modified. The following all relate to the Optimiser Workflow: RF Thresholds - this is now named RF Array Thresholds Performance Metrics/Targets - this is now named RF Metric Targets Under the RF Metric Targets, the two cost mechanisms have been renamed: o Signal Strength - this is now named Array -based o Simulator - this is now named Service based
p.7 of 44
Improved Targets for Array-based Metrics The targets for array-based metrics are now easier to configure. Previously, they appeared in a tree-structure, but now they appear in columns, separately for each technology, and are much easier to view and configure. You can also employ spreadsheet-like functionality, such as copying and pasting single or multiple values. 2.1.7 Financial Analysis: Support for CDMA2000, EV-DO and LTE
The Financial Analysis module now provides complete support for: LTE CDMA2000 and EV-DO
For any of these technologies, you can perform network optimisations and analysis, and generate the relevant reports. The network parameters are fully integrated with ASSET, in terms of carriers, services, bearers and terminal types. 2.1.8 Financial Analysis: New Expenditure Metric
In the Financial Analysis module, there is now a new Expenditure metric, which represents the sum of all Element Costs (CAPEX and OPEX). So the module now offers four different financial metrics: Financial Metric Expenditure Revenue Net Income Return On Investment (ROI) Definition The sum of all Element Costs (CAPEX and OPEX). Captured Revenue. Captured Revenue less Expenditure. Net income divided by Expenditure (expressed as a percentage).
Each of these metrics can be considered at any network level: cell, site or Property.
2.2 Whats New in ASSET 7.0?

In ASSET 7.0, the following additional features are now available. 2.2.1 LTE Support
ASSET 7.0 provides complete planning/dimensioning capabilities for LTE, and these capabilities are highly flexible to meet the varying requirements and demands of different network operators and vendors. ASSET provides a flexible approach to planning and analysing different service types by using a combination of service types, terminal types and terminal density arrays. The static simulation provides a wide range of output arrays and report. The LTE functionality includes: Frame structures Frequency bands Carrier definitions (including signalling/control overheads and intercell interference coordination schemes) Advanced antenna system support Site Database network element parameters for LTE Using the Coverage Wizard Traffic modeling: bearers, services, terminal types, clutter parameters
p.8 of 44
Planning physical cell identities Simulator Wizard Interference Table Wizard Frequency planning ASSET ACP (ASSET's automatic cell planning and optimisation tool) The Financial Analysis module (ASSET's network revenue analysis tool) Carried Traffic Analysis
Note : LTE is also fully supported in:
2.2.2
The Carried Traffic Analysis in ASSET 7.0 enables the quick identification of potential transmission network bottlenecks. When you have run a simulation, you can write the calculated traffic values to the cells in the Site Database (you can also manually add or edit it these values). This information will enable you to: Analyse the network throughput, both on the cells and the parent network elements. Identify network bottlenecks. Integrate this traffic information with the CONNECT tool for the purposes of route planning and link capacity. For more information, see What's New in CONNECT 7.0.
Traffic written by the Simulator to the Site Database can be viewed on the Carried Traffic tab, which exists for the majority of the hierarchical network elements. The Simulator generates traffic at the cell level. At higher levels in the network hierarchy, the aggregated traffic of the subordinate elements can be viewed. If you do not want the traffic from subordinate network elements to be aggregated automatically you can choose to turn the Auto Aggregate facility off and you can enter traffic figures manually using the Carried Traffic Editor. 2.2.3 Interference Table Functionality
In ASSET 7.0, the Interference Table functionality has been extended to support more technologies. It now supports: GSM (or AMPS) LTE Mobile WiMAX
Note : The tabs and parameters vary according to the technology you select. The technologies are only visible if you have the appropriate licence. This new functionality means that, for LTE and Mobile WiMAX, the information in the interference table can be used as a vital input to their Frequency Planning Wizards. (For GSM, as before, you can use the table as an input to the Interactive Frequency Analysis, or to ILSA, the automatic frequency planning tool.) Viewing the Table within ASSET In addition, you can now view your interference table in a detailed and customisable analysis window. In the left pane of the report window, the table lists the victim cells with their associated cell layer, and shows the total coverage area and, if applicable, total traffic, corresponding to the victim cell. In the right pane of the report window, the table lists the interfering cells corresponding to the victim cell that is currently selected/highlighted in the left pane.
p.9 of 44
When you select any of the victim cells in the left pane, the list of interfering cells automatically updates in the right pane. For each of the interfering cells in the right pane, the table shows its respective calculated (or loaded) overlapping values. These values are given for both cochannel and adjacent channel interference. The percentages indicate the proportion of the interfering cell's area/traffic values with respect to the total area/traffic values on the victim cell. The interference data relating to each interfering cell is presented in the right pane, as follows: Interference in terms of Area Co-Area (km2) You can: Limit the cells in the report window, by using the Filter drop-down list. Search for a specific victim cell in the left pane, by using the Find button. View the interferers for any of the victim cells by selecting the appropriate victim cell. Re-sequence any of the columns in the left pane or the right pane, by clicking the appropriate column header. For example, you can sort the list of interfering cells to find which cells might be causing the greatest potential problems to the victim cell. Specify the decimal place precision that you require (this influences the right pane only). Customise the column details in the right pane, as described in the following sections. Generate a report by clicking the Report button. This report will reflect your customised columns and decimal precision. Interact with the Map View, helping you to visualise specific cells. This is described below. Interact with the Site Database, helping you to check a specific cell's network parameters. Co-Area (%) Adj-Area (km2) Adj-Area (%) Interference in terms of Traffic Co-Traffic (T or mE) Co-Traffic (%) Adj-Traffic (T or mE) Adj-Traffic (%)
When viewing an interference table analysis, you can interact with the Map View, in order to visualise specific victim cells and/or interfering cells. To do this: 1 2 3 In the lower-left corner of the Interference Table Analysis window, select the 'Render on 2D View' checkbox. Select a victim cell in the left pane. The cell is highlighted in the Map View, together with all its interfering cells.
Tip : If you want to only highlight a specific interfering cell, you can select one of the cells in the right pane of the analysis window. You can also selectively highlight multiple interfering cells, by using the Ctrl or Ctrl-Shift keys in the right pane of the analysis window. You can customise the display settings of the symbols used for the victim cells and interfering cells. To do this: 1 2 3 In the Map View, click the Show Data Types button and, from the list, doubleclick the Interference Table heading. In the dialog box that appears, select your preferred settings. Click OK.
p.10 of 44
In the Show Data Types dialog box, click Redraw. Antenna Instance IDs
2.2.4
ASSET 7.0 now enables you to specify an Instance ID. This is optional, and you can use it to uniquely identify each antenna instance in the network. This parameter may be very useful if your network uses a distributed antenna system (DAS), where there are many antennas assigned to a single cell (or any similar scenario). It enables you to give a unique identity to each antenna instance on such cells, which helps to identify individual antennas when using the Map View, creating Filters, using the Site or Cell Quick Edit, or generating Site/Node Reports. This can help to select the correct antenna when using the Map View for antenna re-orientation. 2.2.5 Extended Character Set Support
ENTERPRISE 7.0 supports the use of extended character sets for the following products: ASSET ADVANTAGE ASSET ACP
As an example of an extended character set, you can now use Chinese characters in the majority of the user interface. For information on configuring ENTERPRISE to support Chinese characters, see the Installation and Administration Guide. For information on the user interface locations where you can type Chinese characters, and the associated database tables and fields, see the ENTERPRISE Technical Reference Guide.
2.3 Whats New in CONNECT 7.0?

In CONNECT 7.0, the following additional features are now available. 2.3.1 Backhaul Carried Traffic Analysis
In CONNECT 7.0, you can perform carried traffic analysis across all technologies. Through this process, you can now: Generate traffic in ASSET, either automatically by using the Simulator or by adding it manually on the network elements. For more information, see What's New in ASSET 7.0?. Use the Unified Route Planner to route the traffic to the required destination across the logical/cellular connections.The Unified Route Planner is a consolidation of the old Route/Timeslot/Capacity Planner and Logical Connection Route Planner, and enables you to route the traffic for all technologies at once from a single location. View the Applied routing results to accurately pinpoint any necessary capacity upgrades: o You can view the routes and traffic demands generated by routing on a particular network element. o Alternatively, you can view the same information on a particular link. o You can also view the impact of this routed traffic on the link capacity on the Type subtab of the General tab for a link.
p.11 of 44
2.3.2
Enhanced Adaptive Modulation Coding Functionality
In CONNECT 7.0, the functionality for Adaptive Modulation Coding (AMC) has been extended. When configuring AMC on the radio equipment, on the Info tab you can click the AMC Thresholds button to specify the thresholds for all of the available modulation types. These values are used in the link budget and fade margin calculations. On the Modulation/Capacity subtab of the Linkend Settings tab, you are now able to refine your throughput definition to include sensitive data such as voice, by specifying a portion of the throughput as high priority, with a higher availability requirement. Because using AMC means that multiple modulation types are available to a radio, on the Adaptive Modulation subtab of the Performance tab, you can analyse the availability of the link while it uses a particular modulation type, and the percentage of time that it uses that modulation type. For the required throughput and availability, CONNECT displays the minimum modulation order required to satisfy that throughput. However, if the demands for throughput and availability cannot be met by the minimum modulation order, then CONNECT will also display the additional fade margin that is required. This functionality is available for point to point and point to multi-point links. 2.3.3 Ethernet/IP Radio Support
When defining radios, you can now specify the type of traffic that a radio can support. Based on this, the radio capacity can be defined and/or calculated - for Native TDM radios, you can define a channel-based capacity (for example, 4 x E1 or 8 xSTM16), but for Native IP radios, the capacity is automatically calculated. If you have chosen the Hybrid IP and TDM type, then the capacity is a combination of these. When configuring a link that is using a Native IP radio, you can also define the packet type and size, which has a significant impact on the link capacity and performance. To calculate the network performance objectives for packet switched networks, CONNECT now utilises the ITU-T Y.1541 calculation methods, which is automatically set if you have used a Native IP or Hybrid IP and TDM radio on the link. Then, based on the performance calculations, you can ascertain whether or not links using the radio can meet the defined objectives. In addition, you can model the mapping of one technology over another - TDM over IP or vice versa, and calculate the available capacity. 2.3.4 TDD Radio Support
CONNECT radios now support TDD (Time Division Duplexing). This is particularly useful for deploying next generation wireless networks. When defining frequency bands, you can now configure them as single/unpaired frequency bands for TDD On the Configuration tab for a radio, you can set a radio to use TDD and also dimension its TDD capabilities - frame size, transition gap and latency - which will contribute to the maximum traffic that the radio can support.
p.12 of 44
You can then set a link to use TDD radios on that link. If the link is using a radio type other than Native-TDM, then you can also specify the symmetry, which defines the number of frames (out of every 100) used for the forward direction. These values are used in the calculations for Total Capacity, Control Overhead and Available Capacity. On the Frequency subtab of the Linkend Settings tab, you can specify the single TDD frequency, and if required, synchronise the radio stations. You can then view the impact of the TDD link on the maximum achievable throughput and interference on the Linkend Settings - Radio subtabs and the Performance - Fade Margin subtab respectively. 2.3.5 Support for the Latest ITU Recommendations
To bring CONNECT up to date with the latest ITU recommendations, a number of enhancements have been made: Atmospheric absorption is now calculated using the ITU-R P.676-7 equations, rather than the 676-3 equations. Full details of these equations can be found in the CONNECT User Reference Guide. Based on the ITU-R P.841-4 recommendation, a number of additional regions have been added to the list available when defining the regional rain rate. These include rain rates for a number of regions in Kyrgyzstan and China, as well as rain rates for 'Tropical, subtropical and temperate climate regions with frequent rain', and 'Dry temperate, polar and desert regions'. This is configured on the Outage Period subtab of the Calculation tab. In order to calculate objective performance targets for Native TDM or Hybrid IP and TDM radios, a number of additional values have been included in the radio information, on the Info tab. These values are automatically calculated for the radio, but you can import more accurate values from radio datasheets, or enter your own values as required. Based on these values, CONNECT calculates the required objectives according to ITU-R. F. 1668-1, and then compares this with the actual link performance.
2.4 Whats New in ENTERPRISE 7.0?

In ENTERPRISE 7.0, the following additional features are now available. 2.4.1 Extended Character Set Support
ENTERPRISE 7.0 supports the use of extended character sets for the following products: ASSET ADVANTAGE ASSET ACP
As an example of an extended character set, you can now use Chinese characters in the majority of the user interface. For information on configuring ENTERPRISE to support Chinese characters, see the Installation and Administration Guide. For information on the user interface locations where you can type Chinese characters, and the associated database tables and fields, see the ENTERPRISE Technical Reference Guide.
p.13 of 44
2.4.2
Google Earth Support
ASSET 7.0 now includes KML as one of the standard GIS export formats. This means it is now possible to export map information from ASSET which can then be displayed in Google Earth. In addition to KML, ENTERPRISE can also produce GeoTIFF exports. To import GeoTIFF images into Google Earth, you should use Google Earth Pro. You can also link your ENTERPRISE Map View with Google Earth, so that when you pan or zoom on the map, Google Earth opens, shows the same view, and reflects any panning and zooming performed. 2.4.3 Licensing Configurations and Permissions
ENTERPRISE 7.0 provides an improved licensing system. Configuring License Distribution in ENTERPRISE Administrator System administrators can control the distribution of licences to users via the Licence Administration tabs in the Group Properties and User Properties dialog boxes in ENTERPRISE Administrator. For more information about how licensing configurations and permissions can be controlled by the system administrator, and further licensing information, see the ENTERPRISE Installation and Administration Guide. User Controlling their Licence Usage in ENTERPRISE Users can control their licence use via the Licence Administrator in ENTERPRISE. The Licence Administrator enables you to view and edit the licences that are available to you after logging in to the database. As an ENTERPRISE user, you can use the Licence Administrator to: Get licences Drop licences Check out (commute) licences for usage remote from the network server, based on a specified number of days Edit the Startup option to determine your default licence configuration
For more information about using the Licence Administrator, see the ENTERPRISE User Reference Guide.
2.5 Whats New in RANOPT 7.0?

In RANOPT 7.0, the following additional features are now available. 2.5.1 Intelligent Filters
In previous versions of RANOPT, the filter application process was slow. A large portion of the time was spent copying data from the RSLT tables in the database to the filtered FLAG tables. In RANOPT 7.0 this delay has been reduced by only copying data from the RSLT table to FLAG tables the second time a file is used in a Filter. This also reduces the overall storage required in the RANOPT database, as there will be one less copy of the data. Although this new feature has not resulted in any changes to the User Interface, the following features are affected by the changes: Snapshots Binning Exclusion rules Polygon filtering
p.14 of 44
Route Correction Super Filters
2.5.2
In previous versions of RANOPT, if you wanted to run reports or do map plots on a larger set of data combined from, for example, 15 existing filters, you would need to create a new filter, which can be time-consuming. In RANOPT 7.0, a new type filter can be created, called a Super Filter. A Super Filter is a container of chosen Filters which allows you to quickly group results from different filters. Super Filters are displayed in the Filter Manager, and can be added to Public Filters in the same way as ordinary filters. A Super Filter is represented by this icon Notes : A Super Filter is a grouping of existing filters. You cannot create new filters during the creation of a Super Filter, you need to create the required filters before creating a Super Filter. The Super Filter does not affect the filters it contains in any way. For example, if you delete a Super Filter, the filters contained in the deleted Super Filter will not be deleted. Two-Step Deletion of Measurement Files in the filter list.
2.5.3
In RANOPT 7.0, there is now a two-step process for deleting Measurement files in the Database Explorer. You can either delete a file permanently, called purging, or you can remove the file from the Loaded Files list to a new Deleted Files folder. Once the file is in the Deleted Files folder, it can be either purged or restored.
2.6 Whats New in WEBWIZARD 7.0?

In WEBWIZARD 7.0, the following additional features are now available: WEBWIZARD Monitor Service - Monitoring and restoration of ArcIMS, ArcSDE and IIS. User Auditing For recording user login and logout activity. Point Selection Ability to select individual features, for example cells. Polygon Selection A new Polygon Select tool enables you to specify a customised area on the Map View on which to report. Cell Cluster Aggregation Ability to view aggregation calculations on selected cells, for example average, standard deviation and so on. Native 64bit Support WEBWIZARD will now run as a 64-bit process on a 64bit machine, that is, it will natively support 64-bit. This allows: o Greater than 4GB RAM usage o Easier configuration on a 64 bit machine (a single version of Oracle client is required) Comprehensive Logging Support Full logging support at a variety of levels, for example, error, warn, info, debug. Supports writing log to database. Information on the state of WEBWIZARD can now be logged to a number of different formats using the Log4net logging framework. Ability to use Database Snapshot for ArcSDE No need for Shape file generation. Geographical updates can potentially be controlled at the database level. Ability to Filter Geographical Data based on Date Allows for geographical aspects such as cell azimuth or cell location to be visualised through differing time snapshots.
p.15 of 44
InfoView Drill Down and Roll Up Can use summary tables to show KPIs for differing network element levels in the hierarchy or time intervals by drilling down or rolling up on selected network elements. You can now view summary information on in-line reports.Click the Summary Data button to see summary details Support for Optima %AGGR Placeholder Ability to aggregate KPIs on-thefly for differing network element hierarchies or time intervals. Support for a 7-figure Number of Published Documents Able to perform with large volumes of published files in the WEBWIZARD Explorer. Image Cache Support Use of image cache where layer settings are constant for better GIS performance. Use of Zoom Level when Specifying Variable Symbol Sizes Bing maps zoom levels can be used rather than scale factors. Better Image Layer Support All main image format types supported in a simpler user interface. Better Layer Searching You can now search for text in a layer using a number of search parameters, including wildcard characters and regular expressions in search strings. Use of Zoom Level when Specifying Scale Extents Bing maps zoom levels can be used rather than scale factors. Associated Layer Selection Able to show associated layer features when selecting features, for example, display neighbours associated to a cell. Better Vector Drawing Support Can draw vectors from the centre of sectored cells so that vectors drawn from co-located cells do not overlap Active Directory Login Support Configurable option to allow users to log in using Active Directory credentials.
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 10) 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 Presentation Server 4.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 10). ENTERPRISE 7.0 has been tested using Microsoft Office 2003 and 2007. Earlier versions of Office may work although some features wont be available because it utilises a feature in the later version of Excel. Important : Excel 2010 is currently being tested, and an announcement will be made about its compatibility by the end of December 2010. Versions earlier than Office 2000 (such as Office XP and 98/95) are not recommended. This represents the explicitly tested Oracle versions, OS and Citrix versions for the products provided in the installation kit.
p.16 of 44
p.17 of 44
3.3 Test Matrices Per Product

Where a cell is marked Y, this indicates that from the testing that has been completed, there are no known issues specific to this OS. 3.3.1 ENTERPRISE Core, ASSET, ARRAYWIZARD, ADVANTAGE, CONNECT and RANOPT Windows XP (32bit) Windows XP (64bit) Windows Vista (64bit) Windows 2003 (32bit) Windows 7 (64bit)*** Win Server 2003 (64-bit) Y Win Server 2008 (64bit)*** Y
Oracle 10g Enterprise Edition (10.2.0.4) Oracle 10g Standard Edition* Oracle 11g Enterprise Edition (11.1.0.7) Oracle 11g Enterprise Edition (11.2.0.1) Oracle 11g Standard Edition* Citrix 4.5 PS
Y**
Y**
Y**
N/A
N/A
N/A
(with Rollup Patch 4) Citrix Xenapp 5.0 Citrix Xenapp 6.0 Testing Ongoing Supported Platforms to be announced by the end of January 2011 Testing Ongoing Supported Platforms to be announced by the end of December 2010
p.18 of 44
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. ** RANOPT Scheduler is not supported on Windows Vista *** 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.3.2 WEBWIZARD Full WEBWIZARD FIREFOX 3.0 NO WEBWIZARD Lite YES
SAFARI v3.0 INTERNET EXPLORER 6 INTERNET EXPLORER 7 INTERNET EXPLORER 8 OPERA v9.0 CHROME Windows Server 2003 64 Bit Enterprise Edition SP2 Windows Server 2008 Windows Server 2008 R2
NO YES YES YES NO NO YES YES YES
YES YES YES YES YES YES YES YES YES
3.4 Upgrading to V7.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 10).
p.19 of 44
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.
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:
p.20 of 44
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). Universal Document Converter is not available. 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. Installation Procedure
4.2.2
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. 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 o 3 4 If a page stating that ENTERPRISE requires other items to be installed appears, click the Install button and follow the subsequent on-screen instructions If a dotnetfx module security warning is displayed, click the Run button
On the Welcome to the InstallShield Wizard for ENTERPRISE page, click Next. 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. In the User Information dialog box, enter your name and the name of your organisation, then click Next. On the Setup Type page, select Custom, and then click Next. 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. On the Ready to Install the Program page, click Install. Follow the on-screen instructions to complete the dialog boxes that appear.
5 6 7
8 9
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:
p.21 of 44
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 RANOPT Interface Pack

The various loaders for vendors have been split from RANOPT and have now been moved to an Interface Pack. Installation of the Interface pack is simple. The setup file can be downloaded from the Aircom support site located at http://www.aircomassist.com/patches.aspx After the Interface Pack has been installed, registration for the Interfaces used is required (registration is free). The application Ranopt Interface Code Generator (which is found in the Aircom folder in the Ranopt Interface Pack subfolder) will generate a unique Key. This key must be copied into the Vendor Interface Request Template which can be found at C:\Program Files\AIRCOM International\RANOPT Interface Pack\Documents. The Vendor Interface Request Template must be completed and emailed to interfaces@aircominternational.com. All information requested in this form is mandatory for the licence generator. The user will then be provided with a licence key that will allow use of the required interface(s) in accordance with the Support Expiry Agreement.
For RANOPT 7.0 to work, you must install Interface Pack 1.7 SP1.
p.22 of 44
5 Upgrading Oracle Database Server from a Previous Version

Please consult the Oracle database server documentation for a fuller upgrade description. Upgrade To Oracle 9.2.0.7 (ODBC 9.2.0.6.5) Oracle 10.2.0.4 (ODBC 10.2.0.4), Oracle 11.1.0.7 (ODBC 11.1.0.7) Or Oracle 11.2.0.1 (ODBC 11.2.0.1) Description Please contact your regional Product Support team (see Section 10) for information on how to achieve this. Important: The recommended method is to create a new Oracle database with the ENTERPRISE 7.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#BGB DDACA 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.
p.23 of 44
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 7.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 10). Important: The recommended method is to create a new Oracle database with the ENTERPRISE 7.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 are information for DBAs to consider before upgrading.
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 10) with details of current tablespace\datafile sizes. During the upgrade to V7.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
p.24 of 44
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 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 10). 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 10) for assistance with this; depending on the terms of your contract, you may be charged for this service.
p.25 of 44
Upgrading ENTERPRISE Software from a Previous Version

Existing customers with previous ENTERPRISE Versions (see table below) must upgrade before they can use ENTERPRISE 7.0. Important : With the release of V7.0, AIRCOM will no longer provide patches for V6.1 or earlier. Customers on versions earlier than 6.2 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 Version 5.0.3 Build 17R63 Version 5.1.1 Build 38R66 Version 5.2.2 Build 9R78.0.1 Version 6.0 Build 43R95.0.1 Version 6.1 Build 118R98.0.1 Version 6.2 Build 239R24.0.2 DB Version 5059 5127 5211 6026 6135 6237
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 10). 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 Installation and Administration Guide. The basic upgrade steps (using V6.2 as an example) are as follows: 1 2 3 4 5 6 7 8 Ensure that your database has been migrated to Oracle 10g or Oracle 11g. For more information, see Section 5. Commit everything you wish to keep in V6.2 and backup the database. Install the latest build of V6.2, as listed above. In V6.2, open the Administrator tool and log in to the database. In the left-hand pane, select Utilities and in the right-hand pane, double-click on Upgrade Database. Uninstall V6.2. Install V7.0. In V7.0, open the Administrator tool and log in to the database.
p.26 of 44
In the left-hand pane, select Utilities and in the right-hand pane, double-click on Upgrade Database.
10 When upgrading, ENTERPRISE Administrator will automatically attempt to detect the tablespaces similar to database creation. If it cannot be certain of them, it will prompt you for them. Warning : You must ensure that you select the correct ones (which are the same as those used in the previous version of ENTERPRISE), so if you are uncertain, please ask your database administrator. 11 You can now log in to your upgraded database with ENTERPRISE V7.0. However, depending on your configuration, you may have to refer to the following sections: o o If you are upgrading an installation of V6.2 on a patch level earlier than R20.0.2 then read section 7.3 If you use either of the WiMAX technologies, then read section 7.4
Important : Schema passwords for AIRCOM, ADVANTAGE and DIRECT schemas have changed to a new internal password. Database Administrators can change these passwords after the upgrade if required. Please note that if they are going to be changed, the passwords must be the same for all 3 schemas.
7.1 Database Schema Changes Between 6.2 and 7.0

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

User Preference Settings are preserved when upgrading to V7.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.
7.3 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.
p.27 of 44
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 2 Close the project. Locate your existing Config.dat file. You will find this in your Predictions folder. Here is an example:
3 4
Save a backup copy of the file. 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):
p.28 of 44
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:
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.
7.4 Filter Migration Procedure for WiMAX Users

If you are upgrading to V7.0 from V5.2, 6.0, or 6.1, and you use one of the WiMAX technologies, you must pay special attention to an essential procedure. If you do not do this, there is a risk that your WiMAX filters and fields will not be successfully migrated into V7.0, which may mean they would need to be recreated manually. Important: This procedure is only necessary if:
p.29 of 44
You use one or both of the following technologies: Fixed WiMAX and/or Mobile WiMAX. - AND You are an existing customer upgrading to V7.0 from 5.2, 6.0, or 6.1. You are a new customer to V7.0. You were a new customer to V6.2 (and are now upgrading to V7.0). You have already upgraded to V6.2 from a previous version (and are now upgrading to V7.0). In this case, you should already have performed this procedure, and you do not need to perform it again.
This procedure is not necessary if any of the following is true:
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 V7.0 The general upgrade to V7.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 V7.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 7.0. Note: The general upgrade to V7.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
p.30 of 44
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 4 Perform the initial steps of an XML Import, preparing to import the same file you have just exported. In the XML Import dialog box, on the Filters tab, click the Options button. The migration options are as follows:
Option selected Override checkbox unselected Override checkbox selected and Mobile WiMAX chosen Override checkbox selected and Fixed WiMAX chosen Operation n/a. Outcome No static, network element or fields rules will be changed. The import will attempt to make the changes (this affects the dynamic rules and static lists). This may result in some records/objects not being imported if the XML is not correct. For attribute rules only, those which are present on both UMTS and Fixed WiMAX would be changed, but all others will import as UMTS, unchanged from before.
Any rules in the XML indicating UMTS Cell, UMTS Node or UMTS Repeater will be treated as meaning Mobile WiMAX Cell, Mobile WiMAX Node or Mobile WiMAX Repeater. Any rules in the XML indicating UMTS Cell, UMTS Node or UMTS Repeater will be treated as meaning Fixed WiMAX Cell, Fixed WiMAX Node or Fixed WiMAX 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.
p.31 of 44
The following picture shows an example of the dialog box:
Example of Filters Options for Special Updating Procedure
p.32 of 44
7.4.1
Attributes Automatically Upgraded or Changed by an XML Import
The following table lists some of the attributes affected by the migrating of filters for WiMAX users. The attributes in this table are automatically changed by the V7.0 upgrade, but they are also changed by an XML Import from a previous version.
Moved from UMTS to Mobile WiMAX: PN Code Index Schema DL Traffic Load (%) PN Code Index ID Cell Segment Preamble Boosting (dB) Pilot Boosting (dB) RX Sensitivity PUSC Group 0 Support PUSC Group 1 Support PUSC Group 2 Support PUSC Group 3 Support PUSC Group 4 Support PUSC Group 5 Support QPSK Modulation Supported 16QAM Modulation Supported 64QAM Modulation Supported AAS Elements UL Collaborative Multiplexing Enabled MIMO TX Elements MIMO RX Elements AAS Support Enabled UL Diversity Support Enabled Moved from UMTS to Fixed WiMAX: RX Sensitivity Control Power Control Activity WiMAX TX Power Subchannel 1/16 Subchannel 1/8 Subchannel 1/4 Subchannel 1/2 WiMAX DL Traffic Power
p.33 of 44
7.4.2
Attributes Specifically Controlled by the XML Import Options
The following tables list the attributes affected by the migrating of filters for WiMAX users, but only those that are specifically controlled by the XML Import Options. Switchable to Either of the WiMAX Technologies and Still Valid for UMTS The items in this table are valid for all three technologies: UMTS, Fixed WiMAX and Mobile WiMAX.
Generic ID Owner Group Owner Writable Group Writable All Writable Cell Cell Name Cell ID Azimuth Mechanical Down Tilt Antenna Height Relative Antenna Location (East) Node 1st Name 2nd Name Comments Node ID Hexagon Radius Fixed Site DB Sector Configuration Repeater ID 1st Name 2nd Name RX Antenna Type RX Feeder Type RX Propagation Model
Last Modified User Relative Antenna Location (North) Antenna Type Primary Prediction Model Primary Prediction Radius Primary Prediction Resolution Secondary Prediction Model Secondary Prediction Radius Secondary Prediction Resolution Relative Antenna Distance Antenna EiRP value Antenna Correction Factor Feeder Type Feeder Length Forbidden Azimuth Range Enabled Clockwise Bearing Angle Anti-Clockwise Bearing Angle Antenna Device Fixed Antenna Pattern Fixed Mechanical Downtilt Fixed Azimuth Fixed Height Fixed Constrain Max Main Lobe Tilt
RX Prediction Radius (km) RX Feeder Length (m) RX Antenna Height (m) RX Azimuth RX Mechanical Down Tilt RX Antenna RX Diversity RX Antenna TX Diversity TX Antenna Type
TX Feeder Type TX Propagation Model TX Prediction Radius (km) TX Feeder Length (m) TX Antenna Height (m) TX Azimuth TX Mechanical Down Tilt
p.34 of 44
Generic
Cell Max Main Lobe Tilt Noise Figure Mean UL Noise Rise (UMTS & Mobile WiMAX) Uplink Noise Rise (Fixed WiMAX)
Node
Repeater TX Antenna RX Diversity TX Antenna TX Diversity TX Primary Prediction Model
TX Primary Prediction Radius (m) TX Primary Prediction Resolution (m) TX Secondary Prediction Model TX Secondary Prediction Radius (m) TX Secondary Prediction Resolution (m) Uplink Gain (dB) Uplink Noise Rise (dB) Downlink Gain (dB) Owner Group Owner Writable Group Writable All Writable Last Modified User
Valid for UMTS and Only One of the WiMAX Technologies The items in this table are valid for either UMTS and Mobile WiMAX, or UMTS and Fixed WiMAX.
Switchable from UMTS to Mobile WiMAX Max TX Power 1st Order NBR 2nd Order NBR Is Shared Antenna Shared Antenna ID DL MIMO Support Enabled Antenna RX Diversity Antenna TX Diversity Switchable from UMTS to Fixed WiMAX
p.35 of 44
Important Notices
8.1 Versions No Longer Supported
With the release of V7.0, AIRCOM will no longer provide patches for pre-6.2 versions. Customers on V6.1 or earlier are advised to upgrade as soon as possible.
8.2 Deprecated Features from ENTERPRISE 7.0 Onwards

Please note that AIRCOM International 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.
8.3 All ENTERPRISE Customers

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 7.3. Existing customers who use either of the WiMAX technologies, and who are upgrading to V7.0 from V5.2, 6.0, or 6.1, should read Section 7.4. This describes how the upgrade will affect your filters, and how you can use a special procedure to control some of the changes. 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. There is a known issue with installing the Volcano propagation model on Windows 2008 server, whereby the installation may hang when installed with a Remote Desktop user.As a workaround, when installing Volcano during the ENTERPRISE setup, click Cancel during the Volcano install. This will trigger the VolcanoSetup.exe to be copied to the Common folder, but skip the actual installation. You should then run the Volcano installer standalone after Enterprise has finished installing, by double-clicking the VolcanoSetup.exe at C:\Program Files AIRCOM\AIRCOM International\ENTERPRISE 7.0\Common\VolcanoSetup.exe. There is a known issue which may occur when installing a new version of the Volcano propagation model on a machine that previously had Volcano on it. If
p.36 of 44
you receive any warnings about mitab.dll when installing Volcano, skip the warning, and the installation should complete as normal. 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 users 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. As part of the enhanced measurement data support in V6.2, crossed feeder analysis is available. 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 ADVANTAGE AIRCOM OPTIMA RANOPT Visual Studio 2008, Unmanaged C++ and C# Visual Studio 2008 Borland Development Studio 2006 Borland C++ Builder 5, Visual Studio 2008 and C#
8.4 ADVANTAGE
If you are upgrading to V7.0 from V5.2, 6.0, or 6.1, you should read the following section. If you are upgrading from V6.2, then you will not be affected. Due to improved functionality in ADVANTAGE 6.2 and subsequent versions, certain objects and settings created in versions earlier than 6.2 are NOT supported by the database upgrade scripts. This means that after a database upgrade these objects and settings will be lost; if these are subsequently needed in V6.2 or later they must therefore be recreated. This is not limited to objects and settings in the Apply state (DIFF tables) as applies to all other areas of the ENTERPRISE Database Upgrade. The Database Administrator should pay particular attention to:
p.37 of 44
Upgrade from Version All versions
Objects and Settings Strategy (aka Cost Function in V5.2 and before) Settings (Options)
V5.2 and earlier
Clutter Parameters Vector Parameters Configuration Profiles Optimisation Profiles Optimisation Matrices (OMXs) Performance Design Targets (Signal Strength and Simulator) Costs and Limits Terminal Types
V6.0
Clutter Parameters Vector Parameters Plans Details Performance Design Targets (Signal Strength and Simulator) Costs and Limits Terminal Types
V6.1
Plans
Objects and settings listed above that existed in previous versions, and are required in the resultant V6.2 or later upgraded database, should have a record made of them outside the tool before the upgrade commences. Once upgraded, the recorded information can be used to recreate the corresponding objects in the new version using the appropriate V6.2 or later features. The Workflow sub-item Details (under Plan Manager) available in V6.0 only has been de-supported from V6.1 onwards, and the functionality moved to other, more intuitive, areas of the tool as follows: o Restrict analysis and optimisation has moved to within Plan definition o Terminal type selection is now done using a new Workflow item Traffic created with the Terminal Types tab o The Detailed Array Settings have all moved: - Resolution: moved to Strategy -> Metrics Selection/Weights - Maximum Number of Servers (GSM): moved to Strategy -> Metrics Selection/Weights - Number of Covering Cells (UMTS): moved to Strategy -> Metrics Selection/Weights - Reference Terminal Type (UMTS): moved to Strategy -> Metrics Selection/Weights - Minimum Signal Strength (GSM and UMTS): moved to Arrays -> Network Data -> Data Array Wizard - All other settings: moved to Settings -> Array Settings The Cached Traffic tab moved from the Workflow item Settings (in V6.0) to the Workflow item Traffic (in V6.1 onwards).
p.38 of 44
Restricting analysis/optimisation to drive-test routes in V6.1 onwards is achieved by selecting the appropriate Measurement Vector(s) in the same way as restricting analysis/optimisation to any other standard ENTERPRISE vector. [Previously this was achieved by selecting the Pathloss Corrections -> Use Location information in Pathloss corrections checkbox in the Plan -> Detail (V6.0) or the Configuration Profile (V5.2 and previous).] The Risk concept within the tool has been de-supported in V6.1 onwards and is no longer available. [Risk factors could previously be defined for Action and Unit Costs, and maximum permissible Risk was defined on the Max Cost/Risk tab in V6.0 (aka Global Design Targets in V5.2 and before). Risk was then calculated alongside the Performance metrics and displayed in the Cost Details during optimisations.] The TEMS Utility function (available in ADVANTAGE V6.0 and earlier) has been superseded by the new Measurements Toolbox in V6.1 onwards (available in ASSET and ADVANTAGE). TEMS FMT files converted using the ADVANTAGE-specific export template can now be directly loaded into the Measurements Toolbox without converting to Signia format beforehand. The three Overlap Signal Strength performance metrics (Service Overlap, Handover Overlap and Interference Overlap) and the Traffic/Area Variation metric have all been de-supported in V6.2 onwards and removed from the tool. This affects the selectable options within the Strategy Workflow item (Metrics Selection/Weights table, Max Degradation tab, Metrics Synthesis tab) and the corresponding (static) Performance Design Targets, Weights and Multipliers. Associated options in the Settings Workflow item have also been removed. Indoor Fading STD, Outdoor Fading STD, Indoor (%) and Indoor Loss parameters, previously defined in ADVANTAGE against clutter types and/or vector types, have been de-supported in V6.2 onwards and removed from the tool. This action has been taken to standardise the concepts of fading and indoor losses across the planning tools (ASSET and ADVANTAGE), and to streamline the cost calculations. Indoor Loss and Fading parameters are still taken into account in ADVANTAGE, when running snapshots from the Monte Carlo engine, by taking the Indoor (%) value defined against the included Terminal Types, and the associated Indoor Loss and Fading parameters from the generic Clutter Parameters dialogs available to both ASSET and ADVANTAGE (previously these were only available when in the ASSET tab).
8.5 ARRAYWIZARD
If you are upgrading from V5.1 or earlier, ARRAYWIZARD users must ensure that previous ARRAYWIZARD installations are completely de-installed from all servers before installing V6.2 or later. We dont 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 servers. 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 servers restart. ARRAYWIZARD requires that the ODBC Data Source is configured as a System DSN rather than a User DSN.
p.39 of 44
The Generate Vector Files option on the Prediction Parameter Set Wizard is only implemented for 2g cells & sites no output will be produced for UMTS or CDMA2000.
8.6 ASSET
If you are upgrading from V5.2.2 (or earlier) before installing V6.2 onwards, 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. ENTERPRISE V7.0 uses the following versions of the propagation models: Model Siradel Volcano Wavecall Wavesight AWE Communications WinProp MYRIAD Version 3.0.2.1 8.0.0.0 10.36.0.0 381
Important : The WinProp model does not currently distribute. This will be fixed in a subsequent patch. 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 10) for more information. The Extended Character Support feature is subject to a number of limitations. For more information, see Section 3.6.
8.7 Citrix Users

V7.0 has currently been verified for use on Citrix Presentation Server 4.5 see Section 3.23.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 10) for assistance. Testing is ongoing for Citrix Xenapp 5 and 6, and the supported platforms will be announced by the end of December 2010.
8.8 CONNECT
If you are upgrading (from any previous version) and a radio is AMC-enabled, then the AMC Thresholds dialog box will be populated using the default values for the modulation scheme(s) available for the radio. This will also happen for AMC-enabled linkends If you are upgrading from versions earlier than 6.2:
p.40 of 44
o o
If you have created your own modulation types, they will be migrated, and will be available for use along with the new default types. When you first open CONNECT, you must manually update all of the performance parameters introduced in V6.2. To do this, from the Options menu, click Performance Calculation, and then click Yes to confirm. If you do not do this, your performance data will be missing, and will not appear in the Link Database.
8.9 RANOPT
If you are using RANOPT, and 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#BGB DDACA 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. The various loaders for vendors have been split from RANOPT and have now been moved to an Interface Pack. For more information, see 4.3. The TEMS interface is only supported on the Windows XP (SP2) and Windows 2000 (SP4) operating systems. If the RANOPT database is installed on a machine that uses a different OS and you want to use the TEMS interface, you should install the RANOPT Loaders on a separate machine that uses Windows XP, with a recommended minimum of 2GB of memory. There is a known issue with the Mindjet MindManager program, which causes reports to fail see http://forum.gb.mindjet.com/viewtopic.php?f=1&t=843 for more information. This program should be removed in order for reports to work correctly. For RANOPT Client installations, Excel reports will not run on Oracle Client 10.2.0.1 and 10.2.0.2. You should install patch 10.2.0.3 to solve this problem. Some report names have changed or have been removed completely. We recommend that you delete all the reports from the Report Registry before upgrading them. If this is not done then some duplicate reports will exist in the database and running the old reports may not work correctly. When using the file loading task, the Scheduler Task Manager service must have full access in the folder security profile (not just the shared folder permissions). When installing or upgrading to RANOPT 7.0, the RANOPT Interfaces Pack version 1.7 SP1 must be installed, otherwise RANOPT 7.0 will not work. When creating a new RANOPT database the procedure is as follows: o First install RANOPT 7.0. o Create the RANOPT database. o Install the latest RANOPT Interface Pack (minimum 1.7 SP1 or later). o Manually start and stop the RANOPT server, using the RANOPT Interface Configurator. For more information, see the RANOPT Interface Pack 1.7 SP1 Release Notes.
8.10 WEBWIZARD
WEBWIZARD is installed using a separate installation package to that of the ENTERPRISE suite. You are prompted to decide whether to launch the WEBWIZARD Installation and Administration Guide at the beginning of the installation process. After the installation has completed, this Guide can also be accessed using the Start menu.
p.41 of 44
If it is necessary to install ArcSDE on a remote database server, i.e. a database server other than the WEBWIZARD application server, then the instructions provided in the following link should be followed before the ArcSDE Post Installation step is started: http://support.esri.com/index.cfm? fa=knowledgebase.techArticles.articleShow&d=23753
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 EC-16892 Description When importing an ENTERPRISE project file (*.aii), antenna devices/patterns are not currently imported, and will not appear in the database or user interface. XML Imports are not affected by this.
10 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.
10.1 Europe
Main Switchboard: Product Support: Email: Web: Operating Hours: 0830 to 1800 UK time, Monday to Friday, excluding UK Public Holidays +44 1932 442000 +44 1932 442345 support@aircom.co.uk www.aircominternational.com/support
10.2 Americas
AIRCOM International Inc Main Switchboard: Product Support: Email: Operating Hours: 0830 to 1800 Dallas time, Monday to Friday, excluding US Public holidays +1 214 576 2700 +1 214 576 2701 support@aircominc.com
p.42 of 44
10.3 Asia Pacific

AIRCOM International Pte Ltd Main Switchboard: Product Support: Email: Operating Hours: 0830 to 1800 Singapore time, Monday to Friday, excluding Singapore Public Holidays +65 6372 0548 +65 6372 0548 supportsg@aircominternational.com.
10.4 Middle East

AIRCOM Middle East & Africa Main Switchboard: Product Support: Fax: Email: Operating Hours: 0830 to 1800 Dubai time, Sunday to Thursday, excluding UAE Public Holidays +971 4 391 2640 +971 4 391 2642 +971 4 391 8141 supportme@aircominternational.com
10.5 Africa
AIRCOM International South Africa (pty) Ltd Main Switchboard: Product Support: Email: Operating Hours: 0830 to 1800 SA time, Monday to Friday, excluding SA Public Holidays +27 11 745 1475 +27 11 745 1381 (Radio Planning) +27 11 745 1496 (OSS) support@aircom.co.za
10.6 India
AIRCOM (India) Private Ltd Main Switchboard: Product Support: Email: (+91) 124 4102445-49 (+91) 124 410 24500 supportindia@aircominternational.com
p.43 of 44
Operating Hours: 0830 to 1800 India time, Monday to Friday, excluding India Public holidays.
10.7 All Other Countries

Please use Europe contact details above.
p.44 of 44

RN70

Încărcat de

Informații document

Descriere originală:

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

RN70

Încărcat de

Drepturi de autor:

Formate disponibile

ENTERPRISE Version 7.

0 Commercial Release Notes

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

Whats New in V7.0 Release?

2.1 Whats New in ADVANTAGE?

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

2.2 Whats New in ASSET 7.0?

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

Note : LTE is also fully supported in:

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

2.3 Whats New in CONNECT 7.0?

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

Enhanced Adaptive Modulation Coding Functionality

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

2.4 Whats New in ENTERPRISE 7.0?

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

Google Earth Support

2.5 Whats New in RANOPT 7.0?

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

Route Correction Super Filters

2.6 Whats New in WEBWIZARD 7.0?

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

3.2 Operating System, Service Packs and Oracle Version Support

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

3.3 Test Matrices Per Product

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

NO YES YES YES NO NO YES YES YES

YES YES YES YES YES YES YES YES YES

3.4 Upgrading to V7.0 Licences

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

3.5 Large Fonts

3.6 Character Sets

3.7 Regional Settings

4.2 Installing ENTERPRISE Software

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

Author: AIRCOM International Date: 1 October 2010

ENTERPRISE Version 7.0 Commercial Release Notes

4.3 RANOPT Interface Pack