Mentum Planet Release Note

>> Release
Note
version 5.7
Copyright © 2013
InfoVista S.A. All rights reserved.
Notice
This document contains confidential and proprietary information of InfoVista S.A. and may
not be copied, transmitted, stored in a retrieval system, or reproduced in any format or
media, in whole or in part, without the prior written consent of InfoVista S.A. Information
contained in this document supersedes that found in any previous manuals, guides,
specifications data sheets, or other information that may have been provided or made
available to the user. This document is provided for informational purposes only, and
InfoVista S.A. does not warrant or guarantee the accuracy, adequacy, quality, validity,
completeness or suitability for any purpose the information contained in this document.
InfoVista S.A. may update, improve, and enhance this document and the products to which
it relates at any time without prior notice to the user. INFOVISTA S.A. MAKES NO
WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THIS
DOCUMENT OR THE INFORMATION CONTAINED HEREIN.
Trademark Acknowledgement
Mentum, Mentum Planet, Mentum Ellipse, Mentum Fusion, Mentum CellPlanner, and
Mentum LinkPlanner are registered trademarks owned by InfoVista S.A. MapInfo
Professional and the Spectrum Suite are registered trademarks of Pitney Bowes Software
Inc. Map data copyright OpenStreetMap contributors, CC BY- SA. iBwave Design is a
trademark owned by iBwave. This document may contain other trademarks, trade names,
or service marks of other organizations, each of which is the property of its respective
owner.
Last updated Wednesday, December 04, 2013
2 Mentum Planet Release Note

Introduction
This document accompanies the release of Mentum Planet 5.7 including the Data Manager. It
describes the new features and enhancements contained in the release. It also contains a list
of the issues that have been resolved in this release as well as a list of known issues and
limitations.
For a detailed list of known limitations and issues as well as a complete listing of the issues
that have been resolved in this release of Mentum Planet, see the Customer Support
download page of the InfoVista web site.
This document contains the following information:
n New features and enhancements

n Issue resolutions
n Known issues
n Known limitations
n System requirements
n Documentation
Mentum Planet Release Note 3

New Features and Enhancements
This list details the new features and enhancements contained in Mentum Planet releases.
version 5.7
Network Data
n Mentum Planet is now compatible with the InfoVista VistaInsight solution for Mobile
Network Performance, in order to allow Mentum Planet users to:
n Import, visualize, and analyze performance data from within Mentum Planet.
n Leverage per-cell traffic data measured in live networks, in the Traffic Map
Generator.
n Leverage per-cell cell loads measured in live networks:
n when generating network analyses
n with the Automatic Cell Planning tool
n with the Small Cell Planning tool
n
l Implementation of a Geolocalization engine to geolocalized LTE call trace events.
Call trace events geolocalized by third-party companies can also be imported into
Mentum Planet.
n Introduction of a dedicated tool for the selection and optimization of small cells.
n 64-bit Radio Propagation Engine, for all models included with Mentum Planet, with
the exception of Predict 4.
LTE Features
n Implementation of VoLTE specific features including semi-persistent scheduling and
TTI bundling.
n Support for Frequency Selective Scheduling.
n Uplink Fractional Power Control parameters can now be defined on a per cell basis.
This is important in HetNet, as one may want to define different Uplink Fractional
Power Control parameters for macro cells and for small cells.
n Ability to define beamforming and beam-switching patterns for multiple electrical
tilts (and electrical parameters in general), within the same .pafx antenna file.
n Ability to define beamforming and beam-switching patterns for multiple frequency
bands, within the same .pafx antenna file.
n Ability to define different patterns for the different antenna elements leveraged in
smart antenna algorithms.

n Slight modification to the computation of the Reference Signal C/(N+I). It is worth
noting that in some scenarios, this modification will lead to differences between the
Reference Signal C/(N+I) computed in Mentum Planet 5.7 and the Reference Signal C/
(N+I) computed in previous releases of Mentum Planet.
n Slight modification to the computation of the RSSI. It is worth noting that this
modification also impacts the RSRQ.
n Slight modification of the computation of the average power per PDSCH resource
element, and the average power per PDCCH resource element, in the case where
more than 4 transmit antennas are being used.
HSPA 3GPP Release 11 Features

n Downlink carrier aggregation for up to 8 component carriers.
n Downlink MIMO capabilities extended to 4 streams.
n Support for uplink MIMO (2x2).
n Support for 64-QAM modulation on the uplink.
Data Manager
n Support for Data Manager “Partial Get” feature. Mentum Planet users can retrieve a
subset of the sites that are part of the Data Manager if they want, as opposed to all the
sites.
Automatic Cell Planning Tool

n Optimization of antenna heights.
n Ability to finish site selection scenarios upon request.
n Speed improvements.
Traffic Map Generator

n Ability to account for social media traffic.
n Ability to support geolocalized call trace events.
Universal Model Updates

n Integration with Universal Model v420:
n Support for 64-bit predictions.
n Enhancements for multi-floor predictions.
n Ability to calculate indoor predictions only.
n Building calculation option compatible with raster data.
n Minor improvements/corrections.

Miscellaneous improvements
n Support for 3D WCDMA, Cdma2000, GSM, and HetNet analyses.
n Integration with MapInfo 12.0.2.
n For neighbor lists, it is now possible to define neighbor cells even if those cells are
not part of the Mentum Planet project.
n New model tuning reports, with ability to generate on-demand statistics and graphs.
n Ability to create MIMO gains from multiple antenna systems (for the same cell).
n Performance improvements when opening/saving/closing Mentum Planet projects.
n Metro Designer: visualization of grids with "building facade and roof" mode.
n Point-to-Point profile tool enhancement for the calculation of the receiver’s antenna
gain when using the Planet 3D Model and directive receiving antennas.
n The Planet 3D Model can now leverage in-building penetration algorithms defined in
the polygon file, which allows the definition of different penetration losses for
different buildings.
n The Planet 3D Model can now leverage polygon files where polygon heights were
defined Above Mean Sea Level.
n Performance improvements for the Planet 3D Model.
n Project validation tool to verify that antenna optimization constraints and antenna
parameters are in line.
n Carrier names are now displayed in the graphical neighbor plan editor.
n In the graphical neighbor plan editor, you can now select which neighbors are to be
displayed on the map.
n Ability to view settings and selected sectors for neighbor plans.
n Ability to save settings when exporting data using the Import/Export tool.
n You can now “smooth” antennas within the Mentum Antenna Editor.
n In the Site Editor, you can now visualize the neighbor counts.
n In the Site Editor, you can now visualize UTRAN Cell IDs for WCDMA Cells.
n In the Site Editor, you can now visualize E-UTRAN Cell IDs for LTE Cells.
Note: To use the microwave features with Mentum Planet 5.7 and benefit from the
most recent changes to Mentum Ellipse, you must install Mentum Ellipse 8.3 or 8.3.1
separately.

version 5.6
LTE Features
n MBSFN (Multicast-Broadcast Single Frequency Network), also known as eMBMS

(enhanced Multimedia Broadcast Multicast Services).
n LTE-Advanced features:
n Support for Almost Blank Subframes (eICIC)
n Support for cross-carrier scheduling, also known as carrier aggregation-based
Inter-Cell Interference Coordination
n Modeling of Release 11 User Equipment
n Rel.10/11 Carrier Aggregation
n Support for LTE Rel.8/9 Inter-Cell Interference Coordination schemes:
n Fractional Frequency Reuse
n Soft Frequency Reuse
n Partial Frequency Reuse
n Interactive Analysis Tool
n 3D network analyses
n New algorithm for carrier preferences in Monte Carlo simulations and network
analyses (e.g., possibility to prioritize a given frequency band over another one)
n The Downlink C/(N+I), which was previously used for both PDCCH and PDSCH
channels, has been replaced by the following channels:
n PDCCH C/(N+I)
n PDSCH C/(N+I)
It is worth noting that in some scenarios, the PDSCH C/(N+I) and the PDCCH C/N+I)
will be different than the Downlink C/(N+I) computed in the previous releases of
Mentum Planet.
n New network analysis layers:

n Total RSRP
n Reference C/I
n Geometry Factor
WCDMA/HSPA Features
n New network analysis layers:

n MIMO Gain for HSDPA

n HSPDA Spectral Efficiency
n P3M (Planet 3D Model) propagation model, with the following characteristics:
n Designed for urban environments, but can be used everywhere, including in
mountainous areas where the receiver is higher than the transmitter.
n Supports all geodata solutions (i.e., height, clutter, clutter height, polygons)
n Multi-resolution support (e.g., height/clutter at 30m resolution, and building
polygon data), with optional dual-resolution calculation).
n Automated Model tuner for optimal accuracy
n User-adaptable in-building penetration algorithm
n Support for all cellular layers (including macro-cells and small cells)
n Optimized for 3D propagation, in terms of accuracy, performance and scalability
n Supported in Point-to-Point Profile and tools in Mentum Planet that require point-
to-point predictions
n Supports frequencies between 100 MHz and 60 GHz
Metro Designer (previously known as the City Designer):
n Ability to view sites/sectors/repeaters/antennas, including their properties (e.g.,

antenna height, azimuth, tilts, e-parameters, etc.).
n Ability to view building properties
Point-to-Point Profile tool
n Complete re-design of the Graphical User Interface

n Ability to start the Point-to-Point Profile tool from within the map for a particular site
(or selected group of sites)
n Ability to define clutter heights from selected propagation model
n Performance improvements when opening the tool
n Miscellaneous improvements
Automatic Cell Planning tool
n Performance improvements
n Site selection algorithms developed for small cells
Mentum Planet extensions
n Mentum Planet 5.6 is compatible with the Mentum Planet extension that allows users
to create Traffic Maps from Twitter feeds
Wi-Fi Features

n Automatic Frequency Planning tool
WiMAX Features
Performance and Scalability Improvements
n Starting Mentum Planet

n Project opening (for projects with a lot of antennas and/or a lot of groups/flags).
n Project saving
n Antenna format: internal structure modifications, in order to:
n Minimize the memory usage
n Allow faster access to necessary information
n Tabular Editor
n Import/Export tool
n Working with site sets
n Data Manager:
n Get operation
n Submit operation
n Synchronize operation
n Refresh operation
n Point-to-Point Profile tool
n Performance improvements to open the tool
n Ability to start the tool for a selected site on the map window
n Predictions: Ability (for all models) for RPE agents to use up to 4 GB of RAM (as
opposed to 2 GB of RAM in previous releases of Mentum Planet)
n Increased scalability for all the tools in Mentum Planet that leverage Interference
Matrices
Data Manager Features
n Ability from within Mentum Planet to Get, Submit, and Synchronize projects with the
Data Manager.
n Ability to define conflict resolution rules (priority given to Mentum Planet or Data
Manager) for Get, Submit, and Synchronize operations.
n Option to automatically synchronize the local Mentum Planet project with the Data
Manager when closing a project.

Compatibility with Mentum Ellipse
n Compatibility with Mentum Ellipse 8.2.1 and Mentum Ellipse 8.2.2

n Compatibility with future versions of Mentum Ellipse as well
New Version of Universal Model (version 410)
n Management of bridge thickness

n Improvement of the morphologies generator (redefinition of default themes)
n Minor improvements/corrections
ITCnet Technology
n Availability of a new technology (ITCnet)
Miscellaneous Improvements
n When visualizing neighbors on the map from the Graphical Neighbor Plan Editor,
intra-carrier and inter-carrier neighbors are now visually differentiated. Case 34821
n From the Report Preview dialog box, you can now generate statistics for non-
numerical columns. Case 28660
n When viewing neighbors from the Site Editor, you now have the ability to select
which neighbors are to be displayed on the map.
n Custom reports now support e-parameters.
n Cell IDs are now displayed in neighbor plans. Case 34803
n Ability to export data to Microsoft Excel from the Tabular Editor. Case 31113
n Sector labeling has been improved so that antenna tilt values are now displayed
adjacent to each sector instead of as a single string. Case 16439
n The Report Template tool now allows you to include information about electrical tilts.
Case 35814
n The maximum number of intra/inter-carrier neighbors defined in the network
settings is now 128. Case 35321
n Total RSRP and Reference C/I layers have been added for LTE FDD and LTE TDD
technologies. Cases 34672, 34673
n A new Geometry Factor layer has been added for LTE and WCDMA network analyses.
Cases 34674, 34675
n You now have the ability to select rows of neighbors and view them in a Map window.
Case 33786
n The actual Height Above Average Terrain (HAAT) value is now displayed in the FCC
contour report even if the value is below 30m. In previous versions, the value of 30m
was displayed when the actual HAAT value was below 30m. Case 32961

n The antenna height range in the Automatic Site Placement tool has been increased.
You can now enter values from 3 to 100m. Case 33618
n The site radius range in the Automatic Site Placement tool has been increased. You can
now enter values from 0.03 to 5.12km. Case 33617
n You can now display tilt values as labels in the Map window. Cases 31552, 32174,
32175
l You now have more flexibility to define separate color profiles for technology-specific
network analysis layers. Case 29640
version 5.5
n Mentum City Designer
n Ability to visualize data in 3D (e.g., buildings, predictions, network analyses,
traffic maps)
n 3D and 2D views
n Ability to query grids
n Ability to interpolate grids
n Ability to generate predictions at multiple heights (i.e., “3D predictions”)
n Support of Wi-Fi
n 802.11g/11n/11ac standards
n Advanced Antenna Algorithms (e.g., MIMO, Beamforming)
n Advanced modeling of Wi-Fi (e.g., automatic channel assignments, channel
bonding)
n Support of Wi-Fi in the Automatic Cell Planning tool
n Detailed Wi-Fi network analyses
n Mentum Planet Automatic Cell Planning
n Support for Wi-Fi
n Support for Mobile WiMAX.
n Interactive Cell Planning tool
n Speed improvements
n Support for WiMAX optimization profiles in Single Site Optimization tool
n Heterogeneous Networks
n Support for cellular layers (e.g., Macro, Micro)
n Ability to define Local Area Networks and Hotspots

n Multi-technology analyses (e.g., multi-technology coverage maps)
n Support for traffic offload using Wi-Fi and Local Area Networks
n Ability to define Cell Selection Offsets
n Support for LTE <-> WCDMA neighbor planning
n Traffic Map Generator to account for Wi-Fi coverage and Local Area Networks
n Ability to compare Monte Carlo simulations
n LTE features
n Automatic PRACH Root Sequence Planning
n Ability to define cell selection offsets
n Deterministic algorithms to model beam-switching and beamforming antenna
algorithms
n Support for LTE Rel.10 User Equipment specific resource elements
n Addition of RSSI network analysis layer
n Modification of the calculation of other-system interference
n In network analyses, ability to select loads computed in Monte Carlo simulations
n Modification of the calculation of the RSRQ layer, in scenarios with multiple
transmit antennas
n New “Power recycling” option available when 4 transmit antennas are being
used
n WCDMA/HSPA features
n Ability to define cell selection offsets
n New composite layers (e.g., Best CPICH Composite Ec/Io, Best HS-DSCH
Composite Ec/Nt)
n Support for Uplink Combiner IDs
n cdma2000/EV-DO features
n New composite layers (e.g., 1xRTT - Best Pilot Composite Ec/Io, EV-DO - Best
Pilot Composite Ec/Io)
n Propagation features
n Automatic Model Selection through the use of Propagation Model Signatures
n Planet General Model to leverage numeric clutter height grids
n Predict 4 propagation model to leverage numeric clutter height grids
n For Planet General Models, ability to define whether or not clutter heights should
be accounted for when computing inclination angles and/or when computing
diffraction losses

n Support for the Mentum Cell Planner Urban Model.
n Ability to generate propagation as a service or as an application
n Easy Site Creation tool
n New WebHelp
n Online Help continually updated on the Mentum server or Offline Help available
locally
n Ability to search across all Help including PDFs and Import/Export worksheets
n Inclusion of user guide content (i.e., user guide PDFs have been removed)
n Expanded background information with the inclusion of relevant Mentum blogs
n Smooth Contouring tool re-design, including the ability to contour classified (.grc)
grids, and the ability to “remove islands”
n Updated antenna format in order to support beam-switching antennas
n Antenna Editor improvements, including the ability to create beam-switching patterns
n Migration of Mentum CellPlanner 10.1.1 projects to Mentum Planet
n Integration of Mentum Ellipse 8.1.2
n Support for Database-to-Database migration from Mentum Planet 5.3 and 5.4 to
Mentum Planet 5.5.
n Co-existence of Data Manager Server 5.5 with other versions of Data Manager
n Access to the Data Manager file share no longer requires read/write access for
Mentum Planet users, as files are now transferred using the Data Manager built-in data
exchange mechanism
n MapInfo 11.5
n New version of the Universal Model (version 403) includes the addition of the 'Use
weighted tuning coefficients' option, the possibility to manage the priority of raster
data with same resolution, the possibility to specify specific loss corrections for each
polygon (included with Model-defined penetration option.
n TEMS Route Reader 8.1 is integrated with Mentum Planet 5.5, in order to allow the
import of native-format TEMS Investigations files
n All changes implemented as part of Mentum Planet patches included in Mentum Planet
5.5
version 5.4
n Automatic Cell Planning tool enhancements include:
n the support for WCMDA/HSPA, GSM, and TDMA-FDMA technologies.

n graph and report enhancements.
n support for XOR logical operator.
n ability to force site activation.
n support for antenna synchronization.
n support for inter-antenna system optimization constraints.
n ability to input user-defined convergence level.
n LTE enhancements include:
n the introduction of an automatic threshold for the Automatic MIMO Switching
antenna algorithm.
n support for LTE hard handover gain.
n ability to define frequency sub-bands.
n support for PRACH Root Sequence Planning.
n ability to define different antenna algorithms for different channel models, as
well as different diversity and multiplexing gains on the Downlink and the
Uplink.
n modeling of LTE TDD de-synchronization.
n support for carrier aggregation.
n ability to account for Uplink coverage when selecting server.
n addition of a PBCH C/(N+I) layer
n ability to find optimal number of Resource Blocks per user for the Uplink in
network analyses.
n support for multi-band network analyses and Monte Carlo simulations.
n ability to account for fading when selecting multiplexing gains.
n Option to assign PCIDs in the same order as sector-antenna azimuths.
n Introduction of a new antenna format (.pafx) files. Previously supported antenna
format can automatically be migrated to the new antenna format. Mentum Planet
users may download antennas in the .pafx format from the Mentum Antenna Server
directly within Mentum Planet. The new antenna format allows the support for:
n multi-band antennas.
n multi-beam antennas, used in single sector or multi-sector configurations.
n electrical tilt, azimuth, beamwidth.
n remote control units.
n explicit definition of antenna ports
n polarizations, including cross-pole and quad-pole.

n a 3D antenna viewer was implemented.
n A new caching of predictions has been implemented, in order to enhance the
performance of the functionalities that leverage predictions (e.g. network analyses
and Monte Carlo simulation)
n Mentum Planet 5.4 includes the latest version of MapInfo Professional (version
11.0.1). For information on new features of MapInfo Profession version 11, see the
MapInfo Professional Release Note, which are available from the PitneyBowes website
at: http://www.pbinsight.com/support/product-documentation/details/mapinfo-
professional
n Ability to display “Open Street Map Roads” and “Bing Roads” MapInfo layers.
n Introduction of Mentum Planet’s export to Google Earth functionalities, which allows
users to export network data (e.g. site/sector/antenna information) as well as
MapInfo grids (e.g. coverage layers).
n You can now have two base stations with the same technology at a site.
n The iDEN feature set previously available in Mentum Planet 4.X has been ported to
Mentum Planet 5.4.
n HSPA Release 9 and Release 10 standards are now supported.
n WCMDA and cdma2000 network analyses now have Uplink/Reverse Eb/No layers.
n Support for multi-band network analyses and Monte Carlo simulations for WiMAX, LTE
TDD and LTE FDD.
n For fixed subscriber analyses, it is now possible to force a given subscriber to be
served by a specific sector, as opposed to assuming that the subscriber is always
served by the optimal sector.
n Mentum Cell Planner GSM projects can be migrated to Mentum Planet 5.4.
n Support for the migration of Mentum Cell Planner version 10.1.
n The Single Site Optimization tool has been adapted to leverage WCDMA/HSPA, GSM,
and TDMA-FDMA optimization profiles.
n Users can create “custom reports” for all technologies, on a per sector or on a per
sector-antenna basis.
n Advanced filtering is now available in the Report Preview dialog box, the Tabular
Editor, and the Select Antenna File dialog box. Using the Custom AutoFilter, you can
define the conditions with which to filter information based on the values and operator
selected.
n The Point-to-Point profile tool can display building polygons and/or “clutter height”
grids.
n A new advanced antenna masking algorithm (“Berg”) has been implemented.

n For Planet General Models, users can define a specific output resolution and a
calculation resolution, which are independent of the resolution of the Geodata files
being leveraged by the propagation model.
n For CRC-Predict 4 models, users can define an output resolution that is independent
of the resolution of the Geodata files being leveraged by the propagation model.
n It is possible to define larger carrier bandwidths for the TDMA-FDMA technology.
n Users can choose between Erlang B and Erlang C tables in the Traffic Analysis and
Dimensioning tool.
n It is possible to import .aod measurement files for WCDMA/HSPA.
n Sector Display Schemes now support repeaters.
n Mentum Planet 5.4 is integrated with Mentum Ellipse 8.1.
n Survey measurements defined in .xlsx format can now be imported.
n TEMS Route Reader 7.0 is integrated with Mentum Planet 5.4, in order to allow the
import of native-format TEMS Investigations files.
n The Installation Guide has been renamed the Getting Started Guide and now includes
a section on basic usage.
n You can now access Technical Notes, as well as User Guides, from the Help menu.
n The average power per physical resource element has been slightly modified. It now
represents the average power over all the physical resource elements of the frame.
n Support for polarization in antenna definition files.
n The co-installation of Mentum Planet 5.4 and either Mentum Planet 5.3.X or 5.2.X is
supported.
n A new Start Page is available where you can view the latest Mentum news as well as
open a project or create a new project.
n You can now access the training schedule and news from the Help menu.
n Integration of the L-Band Restrictions tool.
n New About dialogs for Mentum Planet and the Mentum Planet Migrator.
n Introduction of a new version of the Universal Model (version 400), which includes:
n multi-processed Universal Model predictions.
n enhanced modeling with Forest Polygons.
n support for units defined in imperial system.
n the enhanced horizontal propagation modeling option is now available for Geodata
files defined in raster format.
n The modifications implemented in previous maintenance releases have all been
integrated in Mentum Planet 5.4.

Issue Resolutions
The following issues have been resolved in this release:
version 5.7
n Issue whereby the Smooth Contouring tool incorrectly allowed you to set the original
bin size, interim bin size and smoothing window size to the same resolution value. This
combination of settings was not valid and could produce incorrect results. Case 34132
n Issue whereby LTE network analysis failed with the message "Exception of type
'System.OutOfMemoryException' was thrown". The issue occurred in cases where the
project contained a large number of antenna files. #Case 32902
n Issue whereby memory estimation made by the Automatic Cell Planning (ACP) tool
was incorrect for very large scenarios. Case 39556
n Issue whereby the Automatic Cell Planning (ACP) tool Force Site Activation feature
was not properly accounted for. Case 39507
n Issue whereby the probability of collision curve did not impact the LTE PDSCH CINR
network analysis layer. Case 39384
n Issue whereby the reported statistics in the Automatic Cell Planning tool were
incorrect in specific circumstances. Case 39450
n Issue whereby network analysis output layers did not display properly. 39344
n Issue whereby user-defined penetration loss was not properly accounted for by the
Universal Model. #39343
n Issue whereby the facets option was not properly accounted for by the Universal
Model. Case 38723
n Issue whereby cdma2000 network analysis results were incorrect under certain
conditions. The problem was evident in areas where there were repeaters. Case
38976
n Issue whereby LTE PDSCH CNI values generated through network analysis were
incorrect under certain conditions. The problem was evident at bins where
interference was received from a repeater. Case 38977
n Issue whereby the message ‘Error: Index was outside the bound of the array’
displayed when attempting to run network analysis. Cases 39095, 38440
n Issue whereby network analysis layers exported to Google Earth format displayed
with vertical and horizontal ‘lines’. Cases 37731, 38866
n Issue whereby default network analysis layers and settings (defined in one version)
were lost upon migration to version 5.6.0. Case 38932
n Issue whereby the Maximum Number of Neighbors constraint in the Neighbor Plan
Generator did not work properly (e.g. the limit was not respected). Case 38043

n Issue whereby Monte Carlo simulations were limited to a number of subscribers that
was too low (e.g. it was limited to 500 subscribers per sector). The limited has now
been increased to 100,000 subscribers per sector. # Case 38151
n Issue whereby antenna port assignments are lost when antenna pattern assignment
is changed. This issue occurs in cases where the new antenna being assigned is not
configured with the same ports as the previous antenna that it is replacing. The
software now displays a message indicating which sheets (in tabular editor) are
affected by the change in antenna pattern. Case 38227
n Issue whereby the vertical beamwidth displayed for an antenna (in Antenna Editor)
was incorrect. Case 38396
n Issue whereby the message ‘Error: An exception occurred during the ACP engine
optimization: Internal error (exception)’ displayed when attempting to run ACP
antenna pattern optimization. Cases 38346, 38399, 38127
n Issue whereby an out of memory error displayed when attempting to run 2G network
analysis. Case 37427
n Issue whereby the statistics generated based on a Monte Carlo simulation report
differed depending on the columns that were selected prior to generating the
statistics. Cases 38456, 36585
n Issue whereby the message ‘Error: An exception occurred during the ACP engine
optimization: Internal error (exception)’ displayed when attempting to run ACP
optimization using the Load Balancing Option. Case 38608
n Issue whereby ACP optimization was not optimal in some instances. Case 38651
n Issue whereby the MIMO algorithm is wrongly picked instead of the diversity
algorithm in cases where the AMS antenna algorithm is being used. Case 38430
n Issue whereby the message “Error: bad input arg theta” displayed when attempting
to run network analysis when configured to use multiple analysis prediction heights.
Case 38579
n Issue whereby the message “Error: Value cannot be null. Parameter name: key”
displays when attempting to generate a neighbor plan using the service probabilities
method. Case 38032
n Issue whereby results produced by the Automatic Cell Planning (ACP) and Interactive
Cell Planning (ICP) tools were incorrect. Case 37995
n Issue relating to the site selection process in the Automatic Cell Planning (ACP) tool.
The problem impacted optimizations being done based on sectors whose predictions
were generated based on the masked Universal Model. Case 37922
n Issue whereby prediction generation failed with the message “<Site/Sector ID>
failed: UM: Please check you can write in temporary directory” when attempted on a
large group of sectors. The problem occurred in cases where predictions were being
generated based on the Universal Model. Case 37856

n Issue whereby Smooth Contouring results were incorrect in some situations. The
problem was caused by the incorrect handling of NULL values in grids being contoured.
Cases 35013, 36576
n Issue whereby prediction values incorrectly showed as NULL in some areas. The
problem was observed when predictions were generated based on the Q9 propagation
model. The problem occurred in cases where the sector for which predictions were
being generated was located in an area where NULL values existed in the elevation
grid. Case 37500
n Issue whereby survey regression and filter analysis performance was very slow. Case
37708
n Issue whereby Interactive Cell Planning (ICP) tool performance was very slow.
whereby Interactive Cell Planning (ICP) tool performance was very slow. Case 37979
n Issue whereby subscribers were not being distributed amongst the available WCDMA
carriers during Monte Carlo simulation. Case 35629
n Issue whereby the message ‘Error: The given key was not present in the dictionary’
displayed when running Automatic Propagation Model Assignment’. The error occurred
in cases where propagation models created based on one geodata set were being
assigned in a project that used a different geodata set. Case 37276
n Issue whereby there was a discrepancy between area predictions and predictions
generated using the Point-to-Point Profile tool. The problem affected predictions
generated based on the P3M propagation model only. Case 37391
n Issue whereby the message ‘Access violation when generating path loss’ displayed
when attempting to generate prediction using the Universal Model. Case 37099
n Issue whereby the message “Error: Object must be a root directory (“c:\”) or a drive
letter (“C”)” displayed when attempting to run LTE FDD network analysis. The problem
occurred in cases where the project data being read from a mapped network drive.
Case 37084
n Issue whereby migrated TDMA analysis layers appeared under the GSM node in
Project Explorer and could not be viewed. Case 37264, 39191
n Issue whereby the message ‘Heights and clutter must have same coordinate system’
displays after selecting a clutter file during project creation. The problem occurs in
cases where the coordinate strings in either the height or clutter files contain an extra
character. Case 37144
n Issue whereby the Point-to-Point Profile tool did not account for a change in the unit
preference from meters to feet. Case 37074
n Issue whereby LTE downlink CINR was incorrectly calculated in cases where antenna
beamforming is used. Case 36926
n Issue whereby an project migration from version 5.6 failed with an error under certain
circumstances. Case 37678

n Issue whereby the message "The specified path, file name, or both are too long. The
fully qualified file name must be less than 260 characters, and the directory name
must be less than 248 characters" displays when attempting to export to Google
Earth. The application now displays a warning message in this instance. Case 39400
n Issue whereby LTE TDD maximum data rate difference between the 8x2 and 4x2
configurations (where same MCS was used) was not realistic. Case 39377
n Issue whereby the Automatic Model Tuner (AMT) for the Planet General Model failed
with an error. Case 39573
n Issue whereby the Best Serving Sector Recolor Tool failed with the message "Item
has already been added. Key in dictionary '<SiteID> key being added: <SiteID>".
The problem occurred when the tool was run more than once during the same
session. Case 39701
n Issue whereby values in some group selection lists were not properly sorted. Cases
39840, 37282
n Issue whereby the application crashed with the message "MapInfo Professional
application file has stopped working" when attempting to export scanner data to
survey. The problem occurred in cases where the resultant survey file name was too
long. The application now displays a warning message in such cases. Case 39623
n Issue whereby optimization constraint values shown in the Site and Tabular Editors
were inconsistent. Case 39655
n Issue whereby the message "Interference Matrix Generation Internal Error.
Unsupported carrier bandwidth: <CarrierBandwidthValue> for LTE TDD carrier"
displayed when attempting to run LTE TDD Desync analysis. Case 38122
n Issue whereby the message "the following error has occurred while submitting data:
ORA-00942: table or view does not exist" displayed when attempting to submit LTE
channel changes to Data Manager. Case 38637
n Issue whereby an unhandled exception occurred while attempting installation. The
problem occurred in cases where the Microsoft XML Core package did not exist on the
PC where the software was being installed. Case 38950
n Issue whereby the message "The submit operation has been cancelled to prevent
data inconsistency. Project Settings <ProjectName> has undefined
ProjectSettings.ElevationGrid" displayed when attempting to submit changes to Data
Manager. The problem occurred in cases where the Heights file had been renamed.
Case 38914
n Issue whereby the unit shown in the FCC points table or text file export was incorrect
in cases where the override function was used. Case 39146
n Issue whereby the message "Antenna <AntennaID> has undefined
AntennaSystem.MechanicalAzimuthConstraint" displays when attempting to submit
changes to Data Manager. Case 39163

n Issue whereby sites (after the first site) created based on a Site Template were not
correctly named. Cases 39283, 39562
n Issue whereby scrambling code group numbers were shown incorrectly in the
Scrambling Code Planning tool reports. Case 37563
n Issue whereby an unhandled exception occurred when attempting to open the Color
Profile editor (Edit>Color Profile). The application now displays a message if for some
reason there is a problem and the Color Profile Editor cannot be opened. Case 37332
n Issue whereby the message "Sector_Antennas Table: Link configurations for
CDMA2000 or WCDMA sectors must be updated using the related Carrier_Antennas
sheet. Value(s) not applied. An item with the same key has already been added."
displayed when attempting to import project data using IECON. Case 37327
n Issue whereby batch TDMA/FDMA network analysis either failed or generated
incomplete results. The problem occurred when not enough memory was available to
run some or all of the analyses. In version 5.7, memory management and error
handling have been improved. Case 37501
n Issue whereby data exported to Excel from the Tabular Editor was incomplete. Case
37680
n Issue whereby the Compare Site Sets function incorrectly indicated differences in
cases where values in the Site Sets being compared were identical. Case 37840
n Issue whereby default bearers for WCDMA terminal categories 25-27 were missing.
Case 37985
n Issue whereby prediction generation failed with the message "Object reference not set
to an instance of an object". This issue occurred when the P3M prediction model was
being used and when the prediction area was completely outside the extents of the
geodata. Case 37794
n Intermittent issue whereby prediction generation failed with the message "Failed to
connect with RPE. Please verify the RPE service is running". Case 39893
n Issue whereby the message ‘An error occurred during export: The INSERT statement
conflicted with the FOREIGN KEY SAME TABLE constraint' displayed when Data
Manager migration was running. The problem occurred in cases where the Data
Manager database being migrated contained nested project folders. Cases 35261,
35971. 36038
n Issue whereby the application froze after locking and unlocking screen (via remote
desktop connection). Case 38371
n Issue whereby the Sectors selected list in the Automatic Cell Planning (ACP)
Optimization Sector Selection window did not display all sectors. Case 36578
n Issue whereby incorrect Groups were displayed in the Settings of a Automatic Cell
Planning optimization. Case 39880

n Issue whereby the message "Selected region is out of the Heights file. Do you want
to continue?" displayed when attempting to place sites using the Automatic Site
Placement Tool. The problem occurred when Windows language settings were set to
'Spanish'. Case 39678
n Issue whereby the message "Value was either too large or too small for an Int32"
displayed when using the Metro Designer. The problem occurred in cases where the
ID of a building polygon was greater than 2^32. Case 39560
n Issue whereby the Fixed Subscriber table was not updated after running Fixed
Subscriber Analysis. The problem occurred in cases where an equipment type
referenced by a subscriber was renamed after the Fixed Subscriber analysis was
created. Case 38693
n Issue whereby the message "Unable to transfer data to the host <HostName):
Connection is not active" repeatedly displays in the Data Manager Server Console.
Case 37502
n Issue whereby the message "<AntennaName>: Arithmetic operation resulted in an
overflow" displayed when opening an antenna (.pafx) file. Case 37583
n Issue whereby an unhandled exception occurred when attempting to create a traffic
map. Case 37682
n Issue whereby commuted licenses were mistakenly shown as type 'Demo' instead of
'Commuter'. Case 38329
n Issue whereby Sector Display Schemes based on an 'identifier' could not be created
when the technology was set to 'WiMAX TDD'. Case 37346
n Issue whereby a network analysis could not be renamed with a name containing
more than 30 characters. Case 37357
n Issue whereby propagation model file nodes (in Project Explorer) were not sorted
after performing a refresh. Case 36580
n Issue whereby the message "Object reference not set to the instance of an object"
displayed when attempting to perform model tuning using the Automatic Model
Tuner. The problem occurred when tuning a P3M model. Case 36893
n Issue whereby performing a Tabular Edit operation caused group nodes in Project
Explorer to expand. Case 37069
n Issue whereby temporary files were not deleted after performing an import
operation using IECON. Case 37124
n Issue whereby the message "Error: Internal error - Requested position is not valid"
displayed when attempting to run Monte Carlo simulation. Case 36795
n Issue whereby the message "An error occurred during export: Exception from
HRESULT: 0x800A03EC: displayed when attempting to export from layer statistics
analysis tool. The problem occurred in cases where the number of rows being

exported exceeded the maximum (65536) for .xls format. This situation is now
handled more gracefully. Additionally, you may work around the issue by setting your
preferred export format (in User Preferences) to .xlsx format (assuming you are using
a version of Excel that supports that format) or by exporting to .csv format. Case
36081
n Issue whereby the message "Error: Input string was not in a correct format" displayed
when attempting to re-generate a WCDMA network analysis. The error occurred in
cases where region/language settings were set to 'Spanish'. Case 35562
n Issue whereby project migration failed with the message "The migrated dataset is
missing 'sectorInfo Table' table". The problem occurred in cases where the project
scanner data folder contained unexpected files. No Case w, if such files are
encountered a warning is displayed and the migration continues. Case 344002
n Issue whereby the results of Monte Carlo simulation were unexpectedly different when
using the 'Use the loading from Monte Carlo simulation' option. Case 29405, 33184
n Issue whereby group names displayed in Project Explorer are 'cut off'. The problem
occurs in cases where the number of groups in the list is large. Case 29890
n Issue whereby TDMA-FDMA simulcast analyses cannot be re-generated following
project migration (because the 'Model height' Analysis prediction heights option is not
checked by default). Case 38318
n Issue whereby the message "Unable to create Site form the template. Please update
your site templates or use the 'Default' one" displays when attempting to place a site.
The problem occurred when the site template was created based on a repeater (only).
Case 39907
version 5.6
n Issue whereby Custom Data values (defined in the Site Editor) were set to default
values after performing a Data Manager update. Custom Data is stored locally and is
not affected by Data Manager actions. Case 47152
n Issue whereby the message 'Cannot override network parameters' displayed under
certain conditions when using the Interactive Cell Planning tool. Case 36181
n Issue whereby the print layout produced by the Point-to-Point profile tool did not
contain the profile graph. Case 36198
n Issue whereby Mentum CellPlanner project migration failed with the message 'Object
reference not set to an instance of an object'. This problem occurred in cases where
the project being migrated contained empty custom attribute values. Case 36051
n Issue whereby terrain height values were incorrectly populated with the same value
for all sites when created using the Create Sites tool. Case 36003
n
l Issue whereby the Create Sites function did not respect project unit preferences. Now,

if the import data file contains a Summary sheet, the Create Sites function will
reference the 'Height units' in that sheet. Otherwise, the tool will reference the
height unit specified in the project. Case 35989
n Issue whereby the application terminated unexpectedly while importing grids using
the Import Grid function in Grid Manager. Case 35899
n Issue whereby the message 'Inconsistencies in the settings have been detected
between antennas and their usage' displayed when attempting to activate a site set.
Case 35508
n Issue whereby error messages displayed when attempting to generate network
analysis layers. The problem occurred in cases where the user had changed network
analysis settings after creating a network analysis. The application now provides
more appropriate messaging in this situation. Case 35447
n Issue whereby the fixed subscriber analysis report did not include some information
when run using the CPE antenna height option. Case 33009
n Issue whereby Data Manager did not save files to the designated File Server Folder.
Case 35152
n Issue whereby the message 'Cannot load type
'clr:Marconi.Wnp.DataManager.Common.Remoting.Server.ISecuritySe' displayed
when attempting to run the DataManagerCmd.exe command. Case 35072
n Issue whereby the message 'Unable to open table' displays when attempting to
generate contours using the Smooth Contour tool. Case 35029
n Issue whereby the message 'Specified argument was out of the range of valid
values' displayed when attempting to export data to Google Earth. Case 34985
n Issue whereby the message 'ORA-00942: Table or view does not exist' displays when
attempting to create a new database schema. Case 34914
n Issue whereby the message 'Failed to add area grid raster to iterator. Cannot find
the area grid at the specified path' displays when attempting to view a Monte Carlo
simulation report. Case 34986
n Issue whereby the message 'Site set: Temp is invalid' displayed when opening a
project. This problem occurred after a copy of the Master site set had been made
active. Case 35011
n Issue whereby the message 'Object reference not set to an instance of an object'
displayed when attempting to run network analysis. The problem occurred in cases
where the referenced traffic map has kbps as a unit. Case 34912
n Issue whereby the Interactive Cell Planning tool did not consider the specified color
profiles when displaying the CPICH EC and CPICH EC/Io layers. Case 34578

n Issue whereby the message 'Error creating database. Object reference not set to an
instance of an object' displayed when attempting to create a Data Manager database
using the existing scheme option. Case 34727
n Issue whereby Data Manager Server could not be configured to accept file server
paths containing spaces. Case 34726
n Issue whereby the Network Overlay tool produced unexpected results when applied to
a group. Case 34643
n Issue whereby the message 'Data on clipboard is not same size and shape as the
target area' displayed when attempting to copy data into the Tabular Editor. Case
34544
n Issue whereby the migration of projects in Asset format failed with errors.
n Issue whereby the message 'Data in the selected import tables is invalid. The import
process has been aborted and no changes made to the project. Data validation
message: <Sector ID> Power Split (%) for a single antenna must be 100%.' displayed
when attempting to modify antenna cable length in Tabular Editor. Case 34491
n Issue whereby the generation of an LTE PCID plan failed. Now, If an existing
assignment violates a hard constraint and the "Keep existing" option is selected, an
appropriate message is shown (with site/sector name) and the PCID calculation is
canceled. Case 34085
n Issue whereby the display of Bing Aerial maps did not work when Windows was
confirmed to use Russian language/region settings. Case 34175
n Issue whereby grids produced using the Trimmer tool were not correctly aligned. The
problem occurred in some cases where the minY and/or maxY of the trim polygon was
outside the extents of the geodata. Case 34170
n Issue whereby the message 'Enterprise edition of mPlanet does not support this
feature” message when there are no ACP licenses available' displayed when
attempting to run optimization when no ACP license was available. Messaging has
been improved in this version to clearly indicate the cause of the problem. Case 34063
n Issue whereby refreshing Project explorer created duplicate network analysis nodes.
The issue affected 2G (TDMA-FDMA) technology only. Case 34081
n Intermittent issue whereby the opening of the Point-to-Point Profile was very slow.
Case 34112
n Issue whereby graphs generated based on Monte Carlo simulation do not display
properly. The issue occurs when the site ID's of sites for which the graph was based on
contained numeric values. Case 33992
n Issue whereby the cascade option in the Data Manager Console did not work properly
when applied to custom data fields (e.g. the chosen custom fields availability was not
cascaded to all projects). Case 33959

n Issue whereby only the active site set was migrated. Now, all site sets are migrated
when migrating from version 5.4 or 5.5 (note that only the active site set is migrated
when migrated from version 5.3.1). Case 33476
n Issue whereby the message 'Could not find AntennaAlgorithm' displayed when
attempting to import data using the Import/Export command line utility (IECON). The
problem occurred in cases where the antenna algorithm was empty instead of
containing a value of 'N/A'. Case 33464
n Issue whereby sections of an analysis layer exported to Google Earth format were
missing. This problem occurred when exporting large coverage areas. Cases 33384,
34913
n Issue whereby the migrating of a Mentum CellPlanner 10.1 project failed. The
problem was caused by the fact that the project being migrated contained multiple
transceivers referencing the same carrier (not supported in Mentum Planet) and the
service names exceeded the length allowable in Mentum Planet. Now, if multiple
transceivers reference the same carrier only the first one is migrated. Also, Mentum
Planet has been modified to allow service names up to 255 characters. Case 33442
n Issue whereby the Mentum Planet Start Page appeared black and could not be closed
following project migration. This problem only occurred on systems using the
Windows XP operating system. Case 33367, 29856
n Issue whereby a cloned sector did not automatically display in the map window (the
project had to be re-opened before the new sector would display). Case 33282
n Issue whereby the grid contouring tool produced incorrect results under certain
conditions (e.g. with certain range values). Case 32808
n Issue whereby the status information in the model tuning window was incorrect. In
some cases, the status would show as 100% before the process was actually
complete. If you tried to dismiss the information dialog box you would receive a
message telling you the process had been aborted. Case 33109
n Issue whereby an out of memory error displayed when attempting to generate
prediction using the Planet General Model. Performance has been improved to
support longer prediction distances (distances will vary depending on data resolution
and computer specifications). Case 1491
n Issue whereby the message '<site name/sectorname> failed : Predict 4.0 radial
calculations: Diffraction algorithm failed to converge' displayed when attempting to
generate predictions using the Predict 4 propagation model. Case 32323
n Issue whereby user-defined site templates could not be activated. Cases 31943,
33819
n Issue whereby solid band color profiles were not retained when analysis layers were
exported to Google Earth using the Google Earth Export tool. Cases 30745, 32634,
36134

n Issue whereby combined signal strength predictions for different bands of the same
site could not be viewed at the same time. Case 29211
n Issue whereby data import using IECON failed when a referenced antenna pattern was
not in the Data Manager database. Now, an informative error message is provided in
this situation. Case 28590
n Issue whereby labels generated in the Tabular Editor based on the azimuth field
overlapped in the map window. The labels are now offset for improved visibility. Case
26043
n Issue whereby the message 'Attempted to read or write protected memory. This is
often an indication that other memory is corrupt' displayed when attempting to use the
Point-to-Point Profile tool. Cases 22567, 20710, 24303, 24267, 24706, 25417, 27818,
29515, 29870
n Issue whereby the message ‘The program MAPINFOW.exe version 11.0.0.15 stopped
interacting with Windows and was closed’ displayed when carrying out various
operations. Case 32871
n Issue whereby coverage displayed through network analysis was not as expected
under certain conditions. Specifically, this problem occurred in cases where an
additional carrier was enabled on a sector after a network analysis configuration was
created but before it was run. Case 35860
n Issue whereby an out of memory exception displayed when attempting to run network
analysis. Case 35813
n Issue whereby a project that could be opened in previous versions could not be opened
in Mentum Planet 5.5.0. When project opening was attempted, a message indicating
there were no licenses available displayed even though licenses were available. Case
35742
n Issue whereby the message ‘Item has already been added. Key in dictionary:
<KeyID> Key being added: <KeyID>’ displayed when attempting to submit site
changes to Data Manager. The issue was caused by a problem with the way Data
Manager handled conflicts (e.g. when two or more objects had changes to the same
attribute.) Case 35655
n Issue whereby the output layers generated through network analysis did not take
antenna twist into consideration. Case 35621
n Issue whereby the message ‘An error occurred during export: The INSERT statement
conflicted with the FOREIGN KEY SAME TABLE constraint' displayed when Data
Manager migration was running. The problem occurred in cases where the Data
Manager database being migrated contained nested project folders. Cases 35261,
35971
n Issue whereby prediction results based on the Predict Air propagation model were
incorrect due to incorrect antenna gain calculations. Case 35216

n Issue whereby the message “Error: Exception of type
‘System.OutOfMemoryException’ was thrown” displayed when attempting to run
network analysis. The problem occurred on a PC that was running Windows XP 32-
bit. The problem did not occur on a PC running Windows 7. Case 33248
n Issue whereby the Data Inspector utility did not extract antenna algorithm and curve
files. Case 35006
n Issue whereby the message ‘Get files from server failed. Could not connect to
net.tcp: <IP Address>. The connection attempt lasted for a time span of 00:00:00.
TCP error code 10048’ displayed when attempting to download a project from Data
Manager. Case 34917
n Issue whereby the message ‘Check in files to server failed. Error saving local file
<PathToAntennaFile>’ displayed when attempting to check a project into Data
Manager. Case 34916
n Issue whereby the message ‘MapInfo Professional application file has stopped
working’ displayed when attempting to run WCDMA Monte Carlo simulation. Case
34637
n Issue whereby calculated iDEN service probability values were incorrect in the case
where signal strength was below all the HCL thresholds but greater than the global
signal strength threshold. Case 34935
n Issue whereby fast fading margins were not accounted for in the calculation of
HSDPA data rate coverage probabilities in WCDMA network analysis and Monte Carlo
simulation. Case 34820
n Issue whereby WCDMA Monte Carlo simulation results wrongly showed subscribers
being blocked for the reason ‘Throughput Limit’. To address this issue, the maximum
throughput limit value has been increased from 1000 Mbits/s to 1000000 Mbits/s.
Case 34677
n Issue whereby the messages “Layer ‘E-DCH – Max Achievable Data Rate’ on carrier 1
will not be generated. No valid HSUPA bears found” and “Error in Validation file”
displayed when attempting to generate WCDMA analysis layers. Case 33683
n Issue whereby a previously generated Neighbor Plan could not be applied to the site
file. Case 33685
n Issue whereby the message “Error: An exception occurred during the ACP engine
optimization” displayed when attempting an ACP run. The problem occurred in cases
where the optimization profile being used contained only WCDMA uplink goals. Case
33977
n Issue whereby Monte Carlo simulation showed subscribers being incorrectly blocked
for the reason ‘No reference coverage’. Case 34564

l Issue whereby values shown on the LTE downlink C/(N+I) analysis layer were
incorrect. The problem occurred in cases where the sectors for which the analysis was
being run referenced a 1.4 MHz band. Case 34238
l Issue whereby the message “Could not update Antenna Algorithm to
<AlgorithmName> for <SectorID> on <SiteID>: Antenna Algorithm
<AlgorithmName> is not valid for technology WiFi” displayed when attempting to
assign an antenna algorithm to sites with WiFi technology using the Tabular Editor.
Case 34200
l Issue whereby the reuse distance shown in reference to a PRACH root sequence plan
l Issue whereby the message “The required technology is not enabled. Enable the
technology in the network settings” incorrectly displayed when attempting to run
TDMA network analysis. Cases 33694, 33881, 33887, 34024
l Issue whereby the application was slow to start. The issue occurred in cases where
incomplete information was provided during registration. Case 33345
l Issue whereby the message “Process aborted. Model tuning failed with the following
error: Clutter in grid file <PathToClutterFile> is not defined in model <ModelName>”
displayed when attempting to tune a Predict 4 model that references a clutter file with
a different class structure that the project clutter file. Case 33446
n Issue whereby the Neighbor Plan Apply>Replace function was very slow. Case 34259
n Issue whereby coverage generated through network analysis does not accurately
reflect the sector for which the analysis was run. The problem occurs in cases where
sector carrier assignments were changed between analysis runs. Cases 35860, 36443
n Intermittent issue whereby the application crashed when using the Point Inspection
tool. Cases 34215, 36125, 36121
n Issue whereby the message ‘<SiteID>/<SectorID> failed: Access violation when
generating path loss’ displayed when attempting to generate predictions. To correct
this issue a new version (v403.2621b) of the Planet Universal Model is included in 5.6.
Cases 33690, 33997
version 5.5
n Issue whereby Pilot Power EIRP values for EV-DO repeaters were different between
versions. This problem affected repeaters with fiber donors. Case 29300
n Issue whereby the message 'Failed to load project <ProjectPath/ProjectName>
displayed when project was opening following migration phase. The problem occurred
when an antenna in the project being migrated was missing a height constraint value.
Case 30440
n Issue whereby the message 'Index was outside the bounds of the array' displays when
attempting to generate Automatic Frequency Plans (AFP). Case 27551

n Issue whereby the message "Task <TaskID>: Failed with exception: 'Extent is
invalid: top left Y coordinate must be greater than bottom right Y coordinate'
displayed when attempting to generate signal strength predictions. The problem
occurred in cases where, at least some of the sites for which prediction generation
was being run, were located outside the primary project heights file. Case 30593
n Issue whereby Data Manager security settings associated with user accounts
unexpectedly changed from 'passworded' to 'integrated security'. The problem
occurred in cases where users with 'integrated security' were being imported over
users with no set password. Case 29313
n Issue whereby the message 'Error: Value cannot be null' displays when attempting to
generate a traffic map based on fixed subscribers. The problem occurred in cases
where the project heights map did not cover the region where subscribers were
placed. The software now provides a suitable message in such cases. Case 28948
n Issue whereby the message 'Thread was being aborted' displayed when attempting
to display a network analysis layer. The problem occurred after changing the project
geodata where the newly specified file(s) were in a different coordinate system as
compared to the original files. Case 30869
n Issue whereby the message 'Failed to load project <ProjectPath/ProjectName>.
<SectorCarrierID> is not valid for Wcdma Transceiver with carrier standard
<StandardID>' displayed when project was opening following migration phase. Case
30640
n Issue whereby the message 'No dpm mapping found for model <ModelName>'
displayed when attempting to generate an interference matrix. Case 30883
n Issue whereby the message 'Cannot display building height profile: Failed to
compute building height profile with error: Value was either too large or too small for
an Int32' displayed when attempting to use the Point to Point profile tool with
polygons. The issue occurred in cases where the polygon table included polygons
with ID numbers greater than Int32. Case 31417
n Issue whereby the message 'Error initializing tree structure of fixed subscribers
table. Plugin FixedSubscribersPlugin not loaded' displayed when opening a project.
Case 32319
n Issue whereby the message 'MapInfo Professional application file has stopped
working' displayed and the Planet application terminated while scrolling in Project
Explorer. Case 30769
n Issue whereby the message 'LTE FDD Transceiver <TransceiverID> has
LTETransceiver.FfrUsageRatio=1 value out of range' displayed when attempting to
apply cell loads from a Monte Carlo analysis. Case 29329
displayed when attempting to perform a network overlay. The problem occurred in

cases where the default.pafx and missing_default.pafx antenna files were missing
from the project. Case 28598
n Issue whereby the message 'Propagation Model Analysis: None of the survey antenna
properties correspond to their assigned sector antenna properties. Analysis is aborted'
displayed when running propagation model analysis. Case 31234
n Issue whereby the start point of a profile line displayed in the Point-to-Point Profile
tool was shifted. This problem occurred in cases where the Point-to-Point Profile tool
was launched when a Bing Maps layer was displayed. Case 30771, 26720, 29700
n Issue whereby the application terminated unexpectedly when the Site Editor window
was closed. This issue occurred in cases where the Site Editor window was closed
when the Antenna Editor window was open. The problem was observed on Windows XP
operating system. Case 31844
l Issue whereby the message 'Additional non-parsable characters are at the end of the
string' displayed when allocating test mobile file records to sectors. The problem
occurred in cases where the BSIC field of a record in the test mobile data file
contained no value. Case 29327
n Issue whereby the TDMA_FDMA network analysis wizard dialog box did not display
properly (e.g. some parts were cut off) under some screen resolutions. Case 30294
n Issue whereby the message '<SectorID> Sum of Power Split (%) can not be greater
than 100%' displayed when attempting to import data. The issue occurred in cases
where the site and/or sector IDs in the sector_antennas sheet of the file being
imported were different than the site and/or sector IDs in the project to which the data
was being imported. Case 30113
n Issue whereby the message 'System.OutofMemoryException' displayed when CDMA
network analysis was being run on a large number of sites/sectors. The problem
occurred on PCs running the Windows XP operating system. Case 32038
n Issue whereby the message 'An item with the same key has already been added' when
attempting to connect to Data Manager. Changes have been made in version 5.5 which
reduce the likelihood of this issue occurring. Cases 30526, 30591
n Issue whereby sites selected in a Browser window were not selected in the Map
window. Case 23231
n Issue whereby values contained in the LTE common and per-carrier analysis layers
were not the same. The common analysis layers displayed a value of 'No' when there
was no coverage whereas the per-carrier analysis layers displayed a value of 'Null'.
Case 29445
n Issue whereby the messages 'The following carriers were not migrated:
<CarrierIDs>' and 'No valid Wcdma carriers found in the project' and 'Cannot have
the same name as another carrier in the same technology' when attempting to migrate
a 3rd party project. Case 33132

displayed when attempting to update local project from Data Manager. Case 31142
n Issue whereby the required number of channels did not equal the total number of
channels at the end of an automated frequency planning (AFP) run when the 'Keep
existing channel assignments' option was enabled. Case 32553
l Issue whereby the 'View results in map' option in the Query window did not function
correctly - it selected the sites in the map window instead of displaying them as a
separate map layer. Cases 30253, 30976
l Issue whereby the message 'Cannot display building height profile: Failed to
compute building height profile with error: Expression does not evaluate to a column
or table name' displayed when attempting to add a building height profile. The
problem occurred when the building height polygon file name contained more than 31
characters. Case 30766
Issue whereby the FCC contour generator report displayed the antenna name as
'default.pafx' even when that antenna was not the one in use. #40782 Case 32572
Issue whereby the value shown for 'Traffic data column' in a traffic maps' Properties
Issue whereby the message 'The key was not present in the dictionary' displayed
when attempting to generate a traffic map when the indoor/outdoor feature was
enabled and the when either the indoor or outdoor percentage was sent to '0'. Case
29599
Issue whereby filtering a survey based on distance in meters removed all survey
points. Case 28276
Issue whereby the message 'Error: Could not read network data file. Syntax error in
FROM clause' displayed when attempting to generate a traffic map based on network
data. This problem was known to occur when the name of a sheet within the network
data contained an underscore character. Case 28750
Issue whereby the user documentation indicated that you could rename a Generic
technology in Network Settings when it was actually not possible. The user
documentation has been updated so that it no longer indicates the renaming option is
possible. Case 29713
Issue whereby you could not change the "Uplink Center Frequency" value for a
Generic technology. Cases 22411, 29714
Issue whereby the default tilt value for a multi-band, multi-tilt antenna displayed (in
Site Editor) as '0' even though there were no electrical tilts of '0' defined in the
antenna pattern. Case 30783
Issue whereby the Planet General Model AMT tuner incorrectly used the project
default clutter file in all cases. Case 25414

Issue whereby the Planet General Model incorrectly applied the Okumura and
Suburban correction factors (e.g. It interpreted the +/- signs incorrectly). Case 29304
Issue whereby the application locked up and crashed when using Page Up and Page
Down keys to scroll through the site list in Project Explorer. Case 32226
Issue whereby network analysis layers were not respecting the analysis area bounds
defined on the Analysis Area pane in the Network Analysis Wizard. Case 31173
Issue whereby the Layer Control window could not be docked if opened by clicking on
the Layer Control tool button. Cases 23405, 26588, 29550
Issue whereby the viewpoint pick tool used in association with the Viewshed Analysis
tool did not appear when Viewshed Analysis was launched from Grid Manager. Case
26570
Issue whereby contour threshold values could not be adjusted. This issue occurred
when attempting to define threshold values for 'polyline' type contours. Case 26788
Issue whereby the message 'Error: Value is either to large or too small for Int16'
displayed when attempting to import a fixed subscriber table containing more than
32,767 records. Case 29610
Issue whereby the message "Column 'Optimal/Forced Best Server' does not allow
nulls" displayed when attempting to add a fixed subscriber table. The problem
occurred in cases when the required column 'Optimal/Forced Best Server' was not
present in the file being imported. Case 31886
Issue whereby LTE 'Useful Bits per Symbol' modulation values displayed as floats
when exported. Case 31957
Issue whereby the message "Sectors Table: Sector <SectorID> has invalid value =
'WiMAX\WiMAX Automatic MIMO Switching.ALGR' for column Antenna Algorithm"
displayed when attempting to import project data. In this case, sector antenna
algorithm information did not get imported. Case 29981
Issue whereby, after exporting and then immediately re-importing project data
(without making changes), the Compare Data function indicated differences in antenna
location coordinates. This issue was due to rounding. Case 29233
Issue whereby, when importing project data, the log window erroneously indicated
that rows in the Optimization Constraints table had been modified. Case 29234
Intermittent issue whereby the model tuning report was missing clutter statistics for
some surveys. Case 23882
Issue whereby the message 'Object reference not set to an instance of an object'
displayed when attempting to migrate a project from Mentum CellPlanner 10.1 to
Mentum Planet 5.x. The problem occurred in cases where there were missing feeder
cable values for LTE antenna branches. Case 31749

Issue whereby grid files located in a folder that included '.tab' in its name could not
be opened from the Grid Manager window. Case 26565
Issue whereby the site search feature did not work when sites were grouped by
technology, antenna, or propagation model. Case 26374
version 5.4
n Issue whereby the message 'Cannot find table 0' displayed when attempting to
import network data in Microsoft Excel format. The problem occurred in cases where
the name of the worksheet being imported began with a number. Case 15830
n Issue whereby the message 'Antenna coordinate system is not the same as DEM
coordinate system' displayed when attempting to run network analysis. This issue
occurred in cases where the project geodata was changed and the new geodata had a
different coordinate system than the original geodata. Case 17034
n Issue whereby local attachments were deleted after disconnecting from Data
Manager. Case 17898
n Issue whereby the snap option did not function properly when creating a new site
using the Place Copy function. Case 18110
n Issue whereby the message 'Error: Index was out of range. Must be non-negative
and less than the size of the collection' displayed when attempting to generate a
WiMAX frequency and preamble plan. This problem occurred in cases where the
number of required channels on a sector was less than the number of allocated ones.
Case 19243
n Issue whereby the message 'Error opening filtered grid' displayed when attempting
to generate contours using the Smooth Contouring Tool. Case 19751
n Issue whereby the right-click (shortcut) menu is disabled when accessed from the
heights or clutter node in Project Explorer (Project Data>Geodata). This problem
occurred when the Layer Control window was open and un-docked. Cases 21356,
21416, 22229, 28932
n Issue whereby the Layer Statistics Analysis tool produced incorrect results under
certain conditions. The problem occurred in cases where one or more grids being
used as input were not properly aligned. Now, a warning is shown when loading a
project or when attempting to change your project geodata to alert you to the fact
that your data is not properly aligned. If your data is not properly aligned you should
contact your geodata vendor to have it corrected. Case 21358
n Issue whereby an exception occurred when attempting to create a site template from
Project Explorer. The problem occurred in cases where users were using a non-
English version of Microsoft Office. Cases 21879, 25208

n Issue whereby an exception occurred when attempting to import network data in
Microsoft Excel format. The problem occurred in cases where users were using a non-
English version of Microsoft Office. Cases 21897, 21685
n Issue whereby the sites layer was wrongly removed from the map window after
carrying out a site edit operation. Cases 22161, 26966
n Issue whereby the application window lost focus (e.g. The application window went to
the back) after closing a dialog box. Case 22502
n Issue whereby flag and group nodes were not properly sorted in Data Manager. Case
22668
n Issue whereby sector symbols changed to a star-shaped pattern after adding a new
site using the Place Copy command. This problem occurred in cases where the SiteFile
layer within the SiteFilePerformanceLayer was moved above the SiteFile layer outside
the SiteFilePerformanceLayer folder. Case 23113
n Issue whereby site/sector records were not sorted alphabetically when viewed in a
browser window. Case 23236
n Issue whereby the sectors displayed in the Tabular Editor varied depending on how
that tool was launched (e.g. From a group node versus from a selection of sites). Case
23389
n Issue whereby the message 'The process cannot access the file <FileName.grc>
because it is being used by another process' displayed when refreshing Project
Explorer after a network analysis is run based on an area grid. Case 23433
n Issue whereby the application crashed when attempting to place a new site using the
Place Copy command. This problem occurred in cases where the name of the new site
exceeded the 30-character limit. Cases 23897, 24015, 23420, 29097
n Issue whereby a Group layer appeared 'shifted' in relation to the site layer when
displayed in a map window. Case 23943
n Issue whereby area values displayed in the Layer Statistics Analysis tool did not
respect the units defined in the Preferences dialog. Case 24404
n Issue whereby height values in Universal Model did not respect the units defined in the
Preferences dialog. Case 24361
n Issue whereby sector names displayed in the Site Editor were not sorted
alphabetically. Case 24691
n Issue whereby the message 'Predict 4 error Failed to open the temporary files
containing radial data' displayed when attempting to perform propagation model
tuning. Case 24627
n Issue whereby the map window node in Project Explorer did not update after the
corresponding map window was renamed. Case 24875

n Issue whereby the message 'NWSpatialWrapper; vmSpliceGrids: Could not splice
grids' displayed when attempting to view prediction layers. The problem occurred in
cases where a sector name contained an unsupported character (e.g. An accented
character). Case 24383
n Issue whereby it was difficult to read node labels in Project Explorer when a node
was selected (e.g. Since the selection highlight color was dark in color). Cases
25094, 25725, 26515
n Issue whereby site nodes in Project Explorer did not immediately expand when
clicked on. Case 25098
n Issue whereby the cursor focus in the Sites tree in Project Explorer jumped to an
unexpected location when clicking on sites within the tree. Case 25097
n Issue whereby information for some WCDMA terminal categories was missing in the
user documentation. Case 24904
n Issue whereby the message 'Error: An error occurred while reading the grids: Index
was outside the bounds of the array' displayed when running optimization with type
Site Selection. The problem occurs in cases where the propagation models
associated with the sectors being optimized reference heights grids with different
resolutions. Case 25095
n Issue whereby the Tabular Editor displayed files with text file (.txt) extensions in the
available propagation model list. Case 25289
n Issue whereby the message 'Unable to open table' displayed when attempting to
display a prediction layer. The issue occurred in cases where the site name contained
Unicode characters. Unicode characters are now supported for the following
propagation models: PGM, PGM-A, Q9 and Longley-Rice. They are not supported for
Predict 4 and Universal Model. Cases 25185, 29231
n Issue whereby the migration of a Mentum CellPlanner 10 WCDMA project failed when
a description field contained more than 255 characters. In version 5.4.0, descriptions
longer than 255 characters will be truncated to 255 characters during migration and a
warning message will display.
n Issue whereby an exception occurred during LTE FDD network analysis when the
'Interference Coordination' analysis layer was selected. Case 25380
n Issue whereby the message 'Propagation Model Analysis: An error occurred while
trying to compute the analysis. The error is: Vector File too large => nbrecord
(109975) > 100000 items' displayed when attempting to generate a new propagation
model analysis. Case 25312
n Issue whereby the message 'Agilent error while dumping AOD file: <FileName>'
displayed while attempting to import an LTE AOD file. Cases 24660, 24457
n Issue whereby the pilot power value associated to EV-DO sector-carrier as displayed
in the Tabular Editor was incorrect and not equal to the PA power value. Case 25521

n Issue whereby the message 'Exception of type 'System.OutOfMemoryException' was
thrown" displayed when attempting to run LTE Monte Carlo simulation. Memory
management improvements have been implemented in 5.4.0 that greatly reduce the
possibility of such an exception occurring. Case 25782
n Issue whereby data exported based on a sector Group contained sectors that were not
in that Group. Case 25783
n Issue whereby Fixed Subscriber Analysis results were missing from the Microsoft
Excel results file. This problem occurred in cases where the 'select prediction at CPE
antenna height level' option was selected. Case 25918
n Issue whereby the unit uses for MIMO B in the Microsoft Excel Fixed Subscriber
Analysis report incorrectly showed as dB instead of as a percentage. Case 25919
n Issue whereby the Project Explorer behaved erratically. This included problems with
scrolling operations, problems opening/closing groups and issues with cursor
movement. Changes implemented in version 5.4 make these issues much less likely to
occur. Cases 25967, 26516, 26517,26584,26587, 26967,25698, 26963, 26637,
25294,27347,27618, 29251
n Issue whereby the application hung when left idle for a while. This problem occurred in
cases where the user entered some characters in the Sites filter in Project Explorer
and then immediately changed the focus to another application. When they returned
the focus to Mentum Planet they found the application had 'frozen'. Case 26684
n Issue whereby changes made to a site's properties were incorrectly being reflected in
a copy of that site. Case 26162
n Issue whereby the message 'GSM_Sectors Table: Sector <SectorID> has invalid
value' displayed when project data was being imported. The problem occurred in
cases where the GPRS Maximum Supported Coding Scheme and EGPRS Coding scheme
was blank for some sectors on the import sheet. Case 26174
n Issue whereby the message "<ModelName>. Internal error. There are not enough
'float' parameters in the model for parameter 'OutputResolutionMeters'" displayed
when propagation models were being migrated. Cases 26226, 27087
n Issue whereby the Tabular Editor did not allow you to allocate MAIO's and HSN's when
the FH type was set to BBH. Case 26294
n Issue whereby the GSM Worst Offender C/A network analysis layer failed to account
for the adjacent channel interference rejection factor and therefore did not show the
correct values. Case 26316
n Issue whereby the message 'sites locked by n/a' displayed Unexpectedly in Data
Manager. Case 26356
n Issue whereby the message 'Error in the application' displayed while attempting to
connect to Data Manager Server. This problem occurred in cases where the specified
port number was incorrect. The application now displays a more meaningful error

message that alerts the user to the problem and suggests they check the port
number. Case 26488
n Issue whereby the message 'failed to create BIN file' displayed when attempting to
generate predictions. This problem occurred in cases where user was trying to
generate predictions for sectors for which prediction generation had previously been
terminated before completion of the process. Cases 26512, 26681, 26897, 26931
n Issue whereby the Scan Receiver Export to Survey function produced incorrect
results under certain conditions. Case 26127
n Issue whereby there was an unexpected discrepancy between the LTE FDD uplink
MCS and uplink data rate analysis layers. Case 26656
n Issue whereby the message 'Exception has been thrown by the target of an
invocation' displayed when using the CPICH Pollution Inspector tool. Case 26370
n Issue whereby an exception occurred when attempting to import network data. The
problem occurred when there were missing primary keys in the import file. Case
27101
n Issue whereby the message 'failed write to BIN file' displayed when attempting to
generate predictions. The problem occurred in cases where the resolution of
referenced heights and/or clutter data was not an integer value (a requirement in
Mentum Planet). Now, a warning message is displayed in such cases alerting the
user to the problem and suggesting to use the Resizer tool in Grid Manager to correct
it. Cases 27372, 27589, 29004
n Issue whereby the message 'Cannot define speed for Usage <UsageName>: cannot
use a speed that is not set for any LTE Modulation of the equipment type defined'
incorrectly displayed when attempting to import project data. Case 27335
n Issue whereby the message 'Analysis Area too large. Reduce analysis bounds or
increase Analysis resolution from XX m to a value greater then YY m in the Analysis
Area Pane.' incorrectly displayed when attempting to run network analysis. Case
26054
n Issue whereby the clutter properties setting in the propagation model editor changes
to 'Use default/single properties' when the receiver height is changed. This problem
occurred when the model type was Predict 4 or PGM. Case 27568
n Issue whereby the message 'Data in the selected import tables in invalid. The import
process has been aborted and no changes made to the project. Data validation
message: Downlink bearer <BearerName> has undefined LTEModulation.Speed'
Unexpectedly displayed when importing project data. Case 27586
n Issue whereby the message 'An item with the same key has already been added'
displayed when migrating a project. Case 27383
n Issue whereby the Antenna_Bands export sheet did not display any data when
exported to Microsoft Excel format. Case 27666

n Issue whereby the survey operations such as generate header from sector, survey
averaging and survey filtering caused the antenna coordinate values to Unexpectedly
change. Case 27560
n Issue whereby the message 'Failed to load project. Project <ProjectName> must have
at least 1 range optimization constraint. Please make sure you are not deleting one'
displayed when opening a project. Case 27835
n Issue whereby clutter properties defined in the Propagation Model Editor are lost when
switching between clutter grids of different resolutions. Case 27442
n Issue whereby scroll bars in the Tabular Editor Unexpectedly disappear after applying
filters. Case 27963
n Issue whereby the message 'Index was outside the bounds of the array' displayed
when generating LTE FDD Monte Carlo simulation. The problem occurs when the traffic
map associated with the subscriber covers a larger area than the project geodata. The
application now displays a warning message when this condition exists with
instructions to trim the traffic map so that it falls within the bounds of the geodata.
Case 28004
n Issue whereby the message 'Sites cannot be placed for the selected region' displays
when using the Automatic Site Placement Tool. Case 27319
n Issue whereby TDMA network analysis failed when one or more sites considered for
the analysis contained a period character in their name. Case 28138
n Issue whereby applying site selection changes (site activation or site deactivation) did
not always function properly. Case 28154
n Issue whereby an antenna query based on central frequency wrongly excluded some
antennas from the results. Case 28155
n Issue whereby the ACP site selection algorithm did not activate the correct number of
sites under given conditions. Case 28156
n Issue whereby the message 'Index was outside the bounds of the array' displayed
when attempting to generate CDMA network analysis layers. The problem occurred on
projects that were migrated from a previous version. Cases 28064, 28981
n Issue whereby the number of subscribers indicated in the Subscribers>Global report
for WCDMA Monte Carlo simulations was incorrect. Case 28284
n Issue whereby the file generated when viewing a survey transmitting location did not
get stored in the project folder. Case 28255
n Issue whereby the message 'UM: Memory allocation failure' displayed when
attempting to generate predictions using Universal Model. This problem occurred in
cases where the antenna correction option in the model was enabled. Cases 27947,
28916

n Issue whereby the application crashed when attempting to run batch project
migration. Case 28638
n Issue whereby the message 'Warning: Unable to delete directory
<ProjectFolder\...\ColorCodePlanning>' displays when attempting to run batch
project migration. Case 28635
n Issue whereby grid creation using interpolation was not possible (e.g. The process
failed with multiple error messages). Case 28595
n Issue whereby the formula used to compute the number of control channel resource
elements for LTE FDD was incorrect. Case 28760
displayed when attempting to generate TDMA-FDMA network analysis. Case 28687
n Issue whereby the Automatic Site Placement Tool (Basic Mode) failed when run on a
project that did not have a clutter file in the Geodata folder. Case 29200

Known Issues
The following list details important issues that are known to exist at the time of this release.
These issues are being actively tracked and managed, and we expect to resolve them in the
near future. These issues will be addressed as we progress through the software
development and testing process.
The following list details limitations that are known to exist at the time of this release.
n Issue whereby contours produced by the FCC Contour Generator are incorrect. The
issue only affects contours generated using the Narrowband PCS option. Case 34630
n Sector symbol azimuths do not consider eAzimuth. Case 19207

Known Limitations
The following list details limitations that are known to exist at the time of this release.
n A 64-bit configuration improves prediction performance but will slightly alter results
when compared to predictions generated with a 32-bit model. The prediction
accuracy remains the same. A 64-bit configuration also allows for the generation of
larger predictions. Affected propagation models include PGM, P3M, Longley-Rice,
PGM-A, Q9, and the Urban model. For more information, contact Customer Support.
n Issue whereby the message 'Predict 4 error failed to open the temporary files
containing radial data' displays when attempting to generate predictions using the
CRC-Predict propagation model. To work around this issue, reduce the number of
radials you are using. Case 24627
n When generating propagation model analyses, surveys must be in either:
n Lat/Long (WGS 84, or NAD 83, or GRS80), in which case the first column name
must start with “long” or “x”, or “lat” or “y”.
n The coordinate system of the Heights file, in which case, the first column name
should not start with “long”, “x”, “lat” or “y”, but instead the first column must
contain X coordinates, and the second column must contain Y coordinates.
l When generating propagation model analyses, an “out of memory” exception may

occur when saving large analyses. If such an error occurs, reduce the number of
“distances” in the analyses settings. Network analyses generated in Mentum Planet
version 4.x are not accessible from the Project Explorer in version 5.2. These
analysis files can be found in the /ProjectName/Obsolete folder (in appropriate
technology-dependent sub folder).
n The Scan Receiver import function can support files of up to ~15MB. If the file you
are importing is larger than this we recommend you use the Scanner Survey Import
function. Case 30857
l In Mentum Planet, traffic values are stored with 2-byte precision. This means that
traffic maps can utilize a maximum of 65 536 discrete values. If the actual range of
traffic density values exceeds this number, the density values will be scaled to fit
within the 2-byte range. For any given area, this means that it may not be possible to
assign the bins within that area uniform traffic density values. Instead, in order to
preserve the total amount of traffic within that area, it may be necessary to assign
different traffic values to the bins within the area. In all cases, assigned traffic
values will be a multiple of the 2-byte interval calculated through the scaling
process. A 'speckled' pattern may be evident if colors assigned to density values in
adjacent bins are different.Case 19072
n Issue whereby the message 'No license available for Universal Model. Please check
the license file <PlanetDir>\Universal Model\Universal_Model.lic' displayed when
attempting to tune a Universal Model. This issue occurs when attempting to use a

standalone license on a server machine. To avoid the problem, use a server license.
Case 27358
n Site templates do not store MIMO antenna settings. Case 25197
n Some settings on the General panel in the Site Editor may be hidden. This issue
applies to HSPA carriers only. To avoid the problem, increase your screen resolution.
Case 22236
n The AFPP tool button applies only to GSM/TDMA technologies. If you wish to run AFPP
on a technology other than GSM or TDMA you must launch the tool from the Tools
menu. Case 21072
n The workflow of connecting a single local project to multiple Data Manager projects is
not supported. If such a workflow is attempted a warning message will be displayed.
Cases 8601, 8700, 8701
n The 'Keep existing physical cell ID assignments' option in the LTE FDD (and TDD)
Automatic Frequency and Physical Cell ID Planning dialog box is disabled when an
existing plan is being updated. Case 21084
n When running network analysis based on a Group or based on the active Flags,
repeater sites associated with sectors in the Group or Flags selection are included in
the analysis even though they are not part of the Group or part of the Flag selection. If
you wish to exclude repeater sites from the analysis you must make the repeater
'inactive'. Case 19750
n When creating a traffic map based on regions, your input data file cannot have more
than 65534 region objects. If your region files contains more than this number of
regions you must break it into parts and perform traffic map generation separately for
each region file. Cases 17030, 21542
n In some cases, the project migrator is not able to migrate terrain height values
(shown on the General tab in the Site Editor). To correct this problem, re-specify your
heights file (in Project Settings) to a file other than the original file then revert to the
original file. This action will update the terrain height values. Cases 23595, 23834
n Displaying Bing Aerial or Bing Hybrid map layers may cause a shift of layers due to
projection differences. To avoid this shift set Reprojection to Optimized (Map>Map
Options>Image Processing).
n The message 'Marconi error #401' displays when attempting to export a large grid file
to MapInfo Tab format. This error occurs in cases where the resultant Tab file would
exceed the 2GB maximum size. Case 15521
n The Prediction Generator dialog does not indicate whether a prediction for a given
sector is 'merged' as it did in Mentum Planet 4.x. The reason for this is because, in
Mentum Planet 5.x, individual rows in the Prediction Generator represent sites rather
than sectors. The sectors on a given site may include a mix of modeled and merged
predictions which would require different status indicators. If the status displays as

'OK' that means that all predictions for sectors on the site have been generated
(either as type modeled or merged). Case 14789

System requirements
The system requirements outlined in this section are general recommendations only and are
based on typical usage of Mentum Planet software. This section details the system
requirements for:
n workstations
n the License Manager Server
System requirements for workstations

The tables below detail the workstation configurations for Mentum Planet.
Mentum Planet runs on the Microsoft .NET framework (version 4.0). If you do not have this
software installed on your computer, you will be prompted to connect to the Microsoft web
site to download and install it. To do so requires an Internet connection.
Warning: Requirements vary depending on the layout of the network, the number of
sites, and the work practices you adopt.

Minimum configuration
This configuration is suggested for networks up to 3 000 sectors. You can work with
larger networks using this configuration but performance may be impacted.
Workstation: Single Core Intel CPU (e.g., the Celeron 440, 2GHz
Processor clock) or equivalent
2 GB
RAM
At least 20 GB free space

Hard disk
SVGA (16-bit), 1280x1024

Display
Windows XP 32-bit
It is recommended that you set the system locale to “English

(United States)”.
Operating System Some Automatic Updates can cause your computer to reboot,
which may interrupt operations in Mentum Planet. It is
recommended that you modify the Automatic Updates settings
so that they are not done automatically.
In order to use the Mentum Planet Import/Export tool, you must

Required Software have Microsoft Excel installed. In addition, you must have Adobe
Reader installed to view the Mentum Planet user documentation.

Recommended configuration
This configuration is suggested for networks up to 15 000 sectors. You can work with larger
networks using this configuration but performance may be impacted.
Workstation: Intel Core-2 Duo 2GHz or Dual-Core-2 Extreme or

Processor
equivalent
RAM 4 GB
Hard disk A quick SATA model - 50 GB free space
Display SVGA (16-bit), 1280x1024
Windows 7 64-bit
It is recommended that you set the system locale to “English

(United States)”.
Operating System
Some Automatic Updates can cause your computer to reboot,
which may interrupt operations in Mentum Planet. It is
recommended that you modify the Automatic Updates settings so
that they are not done automatically.
In order to use the Mentum Planet Import/Export tool, you must

Required Software have Microsoft Excel installed. In addition, you must have Adobe
Reader installed to view the Mentum Planet user documentation.
Note: An Internet connection is required to validate licenses. If there is no Internet

connection, you can complete the offline registration form and email it to Customer
Support.
Note: To run Mentum Planet, you must be a member of the “Power Users” group at a
minimum. Regular “Users” must be granted write access privileges to the <Mentum
Planet installation> folder to run Mentum Planet.
Note: Windows XP , Windows Vista, and Windows 8 (32-bits or 64-bits) are supported.
Note: For information about system requirements for the Data Manager Server, see the
Data Manager Server Administrator Guide

System requirements for the License Manager Server
The License Server is contacted each time a user starts an instance of Mentum Planet. It is
also contacted periodically throughout the Mentum Planet session. As a result, it is
important to choose a computer that is always available to serve the licenses. Ideally, the
License Server should be installed on a file or DNS server because these computers are
always online. Static, fixed IP addresses provide the best performance. However, you can
install the License Server on any computer with Windows Server 2003, Windows Server
2008, Windows 7, Windows XP, or Windows Vista because the resources required to serve
the licenses are minimal (5 MB free disk space).
The system requirements listed in the following tables are intended for deployment
scenarios where Citrix or Windows Terminal Services are being used.
System requirements for server configurations

The tables below detail the configurations for Mentum Planet for server configurations.
Note: Mentum Planet runs on the Microsoft .NET framework (version 4.0). If you do
not have this software installed on your computer, you will be prompted to connect to
the Microsoft web site to download and install it. To do so requires an Internet
connection.

Recommended Configuration for a Small Deployment
A small deployment is one in which up to 5 simultaneous users are accessing Mentum

Planet installed on a single application server and using either Windows Terminal Services
or Citrix for remote access from client.
Xeon-class or equivalent processor with at least 6 cores +

Processor
hyper-threading
RAM 12 GB of RAM
Hard disk 1 TB of storage
Windows 2008 Server R2, 64-bit
Windows 2012 Server
It is recommended that you set the system locale to

Operating System “English (United States)”.
Some Automatic Updates can cause your computer to

reboot, which may interrupt operations in Mentum Planet. It
is recommended that you modify the Automatic Updates
settings so that they are not done automatically.

Recommended Configuration for a Medium Deployment
A medium deployment is one in which up to 10 simultaneous users are accessing Mentum

Planet installed on a single application server and using either Windows Terminal
Services or Citrix for remote access from client.
Dual Xeon-based processor with at least 4 cores per

Processor
processor + hyper threading
RAM 24 GB
Hard disk 2 TB of storage
Windows 2008 Server R2, 64-bit
It is recommended that you set the system locale to

“English (United States)”.
Operating System
Some Automatic Updates can cause your computer to
reboot, which may interrupt operations in Mentum Planet.
It is recommended that you modify the Automatic Updates
settings so that they are not done automatically.
Recommended Configuration for a Large Deployment
A large deployment is one in which more than 10 simultaneous users are accessing
Mentum Planet.
Contact Customer Support.

System platform compatibility
The tables below detail the compatibility of Mentum Planet with various system platforms.
Table 1 Windows workstation compatibility (a black check mark indicates fully tested)
Platform Mentum Planet 5.7
Windows XP Professional 32-bits
Windows XP Professional 64-bits
Windows Vista Professional 32-bits*
Windows Vista Professional 64-bits*
Windows 7 Professional 32-bits*
Windows 7 Professional 64-bits
*partially tested
Table 2 Windows server compatibility (a black check mark indicates fully tested)

Platform Mentum Planet 5.7
Windows Server 2003 32-bits
Windows Server 2003 + 2003 R2 64-bits*
Windows Server 2008 + 2003 R2 32-bits*
Windows Server 2008 64-bits
Windows Server 2008 R2
Windows Server 2012
*partially tested

Documentation
Before using this documentation, you should be familiar with the Windows environment. It is
assumed that you are using the standard Windows desktop, and that you know how to access
ToolTips and shortcut menus, move and copy objects, select multiple objects using the Shift
or Ctrl key, resize dialog boxes, expand and collapse folder trees. It is also assumed that
you are familiar with the basic functions of MapInfo Professional. For information about
MapInfo Professional, see the MapInfo online Help and MapInfo Professional User Guide. You
can access additional MapInfo user documentation from the Pitney Bowes Business Insight
website at
http://www.pbinsight.com/support/product-documentation.
Improvements to the Help in Mentum Planet

Along with additional content to address the new features in this version of the software, the
Help includes the following enhancements:
n User Documentation section added to the Start Page that encompasses videos on how
to use the documentation delivered with Mentum Planet, quick access to the
walkthrough tutorials as well as feedback and survey links.
Help
Online Help
To benefit from the most up-to-date user documentation, you can connect to the InfoVista
server and search for topics of interest. Online Help includes help for MapInfo Professional
dialog boxes and windows.
Tip: Copy the link displayed in the Help Topic box (e.g., F1/LayerStats/Analysis_
Settings.htm) and send it to colleagues who can paste it into the Help Topic box to display
the Help page of interest.
Warning: In order to ensure you are viewing the latest Help, verify that your Internet
Options specify that newer versions of stored pages be displayed. In Internet Explorer,
open the Internet Options dialog box and, in the Browsing History section on the General
tab, click Settings.
Offline Help
If you are not connected to the Internet, you can still use the local copy of the Help that was
installed with the software. This version, naturally, will not be as current as the version
accessed from the server. Nonetheless, it contains information about all the basic tasks you

can perform using Mentum Planet. Local help includes help for MapInfo Professional dialog
boxes and windows.
Context-sensitive Help
You can access Help from every dialog box in Mentum Planet by pressing F1. If you want to
view the online Help for a specific panel or tab, click in a field or list box to activate the
panel or tab before you press the F1 key.
Note: Context-sensitive Help for MapInfo Professional opens a separate Help system
that encompasses only MapInfo Professional topics.
Tip: When you search for Help on a specific dialog box or interface element, open
Mentum Planet and from the dialog box press F1. Alternatively, use the F1 search filter.
Knowledge Base
You can access the Knowledge Base by choosing the Knowledge Base command from the
Help menu. The Knowledge Base includes up-to-date articles created by the Customer
Support team that provide information and solutions to questions often asked. You can
access additional resources from the Help menu including product information and the
company web site. From the InfoVista web page, you can download Application Notes and
other product documentation as well as access the Self-Service Portal (including the
Knowledge Base).
Training
InfoVista has a comprehensive training portfolio including on-site training, web training,
and mentoring. You can access information about training by choosing Help > Training
from within Mentum Planet or visit our website.
Getting Started
Read the "Basic Usage" chapter of the Getting Started Guide to begin learning how to use
Mentum Planet. It provides a quick start tutorial of common tasks.
If you are new to Mentum Planet, Walkthrough Tutorials are available from the Start Page
that offer a step-by-step look at some of the main features of the software and are a good
way to familiarize yourself with the tool. Walkthrough tutorials are based on a pre-
configured project that is available from the Customer Support Download page of the
InfoVista website.

Contacting Customer Support
InfoVista is committed to providing fast, responsive technical support. This section provides
an extensive list of contacts to help you through any issues you may have.
You can get technical support by phone or email, or by visiting the Self-Service Portal on the
InfoVista website at http://www.infovista.com/services/customer-support.
Note: When you call for technical support, ensure that you have your product ID number
and know which version of the software you are running. You can obtain this information
using the About command from the Help menu.
When you request technical support outside of regular business hours, a Product Support
Specialist will respond the next working day by telephone or email, depending upon the
nature of the request.
The technical support options available depend on the edition of the software you are using
as shown in Figure 1. For more details about the levels of support, see the InfoVista website.
Figure 1: Support options
Americas
Phone: +1 866 921 9219 (toll free)
Phone: +1 819 483 7094 (Ottawa)
E-mail: [email protected]
Hours: 9am – 7pm Eastern (Monday to Friday)
Asia-Pacific
Phone: +852 3965 1800

Hours: 9am – 6pm HKT (Monday to Friday)
Europe, Middle East and Africa

Phone: +33 164 86 85 08 (Paris)
Hours: 9am – 6pm Central (Monday to Friday)

Mentum Planet Release Note

Uploaded by

Copyright:

Available Formats

Mentum Planet Release Note

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mentum Planet Release Note

Uploaded by

Copyright:

Available Formats

>> Release

InfoVista S.A. All rights reserved.

Last updated Wednesday, December 04, 2013

2 Mentum Planet Release Note

This document contains the following information:

n New features and enhancements

Mentum Planet Release Note 3

4 Mentum Planet Release Note

HSPA 3GPP Release 11 Features

Automatic Cell Planning Tool

Traffic Map Generator

Universal Model Updates

Mentum Planet Release Note 5

6 Mentum Planet Release Note

n MBSFN (Multicast-Broadcast Single Frequency Network), also known as eMBMS

n New network analysis layers:

n New network analysis layers:

Mentum Planet Release Note 7

Metro Designer (previously known as the City Designer):

n Ability to view sites/sectors/repeaters/antennas, including their properties (e.g.,

Point-to-Point Profile tool

n Complete re-design of the Graphical User Interface

Automatic Cell Planning tool

Mentum Planet extensions

8 Mentum Planet Release Note

Performance and Scalability Improvements

n Starting Mentum Planet

Data Manager Features

Mentum Planet Release Note 9

n Compatibility with Mentum Ellipse 8.2.1 and Mentum Ellipse 8.2.2

New Version of Universal Model (version 410)

n Management of bridge thickness

n Availability of a new technology (ITCnet)

10 Mentum Planet Release Note

Mentum Planet Release Note 11

12 Mentum Planet Release Note

Mentum Planet Release Note 13

14 Mentum Planet Release Note

Mentum Planet Release Note 15

16 Mentum Planet Release Note

Mentum Planet Release Note 17

18 Mentum Planet Release Note

Mentum Planet Release Note 19

20 Mentum Planet Release Note

Mentum Planet Release Note 21

22 Mentum Planet Release Note

Mentum Planet Release Note 23

24 Mentum Planet Release Note

Mentum Planet Release Note 25

26 Mentum Planet Release Note

Mentum Planet Release Note 27

28 Mentum Planet Release Note

Mentum Planet Release Note 29

30 Mentum Planet Release Note

Mentum Planet Release Note 31

32 Mentum Planet Release Note

Mentum Planet Release Note 33

34 Mentum Planet Release Note

Mentum Planet Release Note 35