Mentum_Planet_5 6-ReleaseNote (Full).pdf

>> Release Noteversion 5.6

Copyright © 2013

Mentum S.A. All rights reserved.

Notice

This document contains confidential and proprietary information of Mentum S.A. and maynot be copied, transmitted, stored in a retrieval system, or reproduced in any format ormedia, in whole or in part, without the prior written consent of Mentum S.A. Informationcontained in this document supersedes that found in any previous manuals, guides,specifications data sheets, or other information that may have been provided or madeavailable to the user. This document is provided for informational purposes only, andMentum S.A. does not warrant or guarantee the accuracy, adequacy, quality, validity,completeness or suitability for any purpose the information contained in this document.Mentum S.A. may update, improve, and enhance this document and the products to whichit relates at any time without prior notice to the user. MENTUM S.A. MAKES NOWARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THISDOCUMENT OR THE INFORMATION CONTAINED HEREIN.

Trademark Acknowledgement

Mentum, Mentum Planet, Mentum Ellipse, Mentum Fusion, Mentum CellPlanner, andMentum LinkPlanner are registered trademarks owned by Mentum S.A. MapInfoProfessional and the Spectrum Suite are registered trademarks of Pitney Bowes SoftwareInc. Map data copyright OpenStreetMap contributors, CC BY- SA. iBwave Design is atrademark 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 respectiveowner.

Last updated March 25, 2013

2 Mentum Planet Release Note

IntroductionThis document accompanies the release of Mentum Planet 5.6. It describes the new featuresand enhancements contained in the release. It also contains a list of the issues that havebeen 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 issuesthat have been resolved in this release of Mentum Planet, see the Customer Care downloadpage of the mentum 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

http://www.mentum.com/index.php?page=product-downloads&hl=en_US


New Features and EnhancementsThis list details the new features and enhancements contained in Mentum Planet releases.

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-basedInter-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 networkanalyses (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 PDSCHchannels, 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 ofMentum 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 inmountainous 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 buildingpolygon 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 usersto 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 (asopposed to 2 GB of RAM in previous releases of Mentum Planet)

n Increased scalability for all the tools in Mentum Planet that leverage InterferenceMatrices

Data Manager Features

n Ability from within Mentum Planet to Get, Submit, and Synchronize projects with theData Manager.

n Ability to define conflict resolution rules (priority given to Mentum Planet or DataManager) for Get, Submit, and Synchronize operations.


n Option to automatically synchronize the local Mentum Planet project with the DataManager 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

Note: In previous releases of Mentum Planet, the microwave features were available aspart of the software. To use the microwave features with Mentum Planet 5.6, you mustnow install Mentum Ellipse 8.2.1 or 8.2.2 separately. This change enables you to benefitfrom features in the most recent release of Mentum Ellipse (as long as the user interfacein Mentum Planet is not affected).

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 whichneighbors 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 displayedadjacent 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 settingsis now 128. Case 35321


n Total RSRP and Reference C/I layers have been added for LTE FDD and LTE TDDtechnologies. 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 FCCcontour report even if the value is below 30m. In previous versions, the value of 30mwas 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. Youcan 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, channelbonding)

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 antennaalgorithms

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 multipletransmit 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-DSCHComposite 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 - BestPilot 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 shouldbe accounted for when computing inclination angles and/or when computingdiffraction 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 availablelocally

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-switchingpatterns

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 toMentum 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 forMentum Planet users, as files are now transferred using the Data Manager built-indata exchange mechanism

n MapInfo 11.5

n New version of the Universal Model (version 403) includes the addition of the 'Useweighted tuning coefficients' option, the possibility to manage the priority of rasterdata with same resolution, the possibility to specify specific loss corrections for eachpolygon (included with Model-defined penetration option.

n TEMS Route Reader 8.1 is integrated with Mentum Planet 5.5, in order to allow theimport of native-format TEMS Investigations files


n All changes implemented as part of Mentum Planet patches included in Mentum Planet5.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 Switchingantenna 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 wellas 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 innetwork 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 antennaformat can automatically be migrated to the new antenna format. Mentum Planetusers may download antennas in the .pafx format from the Mentum Antenna Serverdirectly 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 theperformance of the functionalities that leverage predictions (e.g. network analysesand Monte Carlo simulation)

n Mentum Planet 5.4 includes the latest version of MapInfo Professional (version11.0.1). For information on new features of MapInfo Profession version 11, see theMapInfo Professional Release Note, which are available from the PitneyBoweswebsite 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 allowsusers to export network data (e.g. site/sector/antenna information) as well asMapInfo 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 toMentum 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 beserved by a specific sector, as opposed to assuming that the subscriber is alwaysserved 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 persector-antenna basis.

n Advanced filtering is now available in the Report Preview dialog box, the TabularEditor, 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 operatorselected.

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 acalculation resolution, which are independent of the resolution of the Geodata filesbeing leveraged by the propagation model.

n For CRC-Predict 4 models, users can define an output resolution that is independent ofthe 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 andDimensioning 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 theimport of native-format TEMS Investigations files.

n The Installation Guide has been renamed the Getting Started Guide and now includes asection 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 nowrepresents 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 issupported.

n A new Start Page is available where you can view the latest Mentum news as well asopen 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 Geodatafiles defined in raster format.

n The modifications implemented in previous maintenance releases have all beenintegrated in Mentum Planet 5.4.


Issue ResolutionsThe following issues have been resolved in this release:

version 5.6

n Issue whereby the message 'Cannot override network parameters' displayed undercertain 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 notcontain the profile graph. Case 36198

n Issue whereby Mentum CellPlanner project migration failed with the message 'Objectreference not set to an instance of an object'. This problem occurred in cases wherethe project being migrated contained empty custom attribute values. Case 36051

n Issue whereby terrain height values were incorrectly populated with the same valuefor all sites when created using the Create Sites tool. Case 36003

ln 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 willreference the 'Height units' in that sheet. Otherwise, the tool will reference the heightunit specified in the project. Case 35989

n Issue whereby the application terminated unexpectedly while importing grids usingthe Import Grid function in Grid Manager. Case 35899

n Issue whereby the message 'Inconsistencies in the settings have been detectedbetween antennas and their usage' displayed when attempting to activate a site set.Case 35508

n Issue whereby error messages displayed when attempting to generate networkanalysis layers. The problem occurred in cases where the user had changed networkanalysis settings after creating a network analysis. The application now provides moreappropriate messaging in this situation. Case 35447

n Issue whereby the fixed subscriber analysis report did not include some informationwhen 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' displayedwhen attempting to run the DataManagerCmd.exe command. Case 35072

n Issue whereby the message 'Unable to open table' displays when attempting togenerate 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 whenattempting to create a new database schema. Case 34914

n Issue whereby the message 'Failed to add area grid raster to iterator. Cannot findthe area grid at the specified path' displays when attempting to view a Monte Carlosimulation report. Case 34986

n Issue whereby the message 'Site set: Temp is invalid' displayed when opening aproject. This problem occurred after a copy of the Master site set had been madeactive. 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 caseswhere the referenced traffic map has kbps as a unit. Case 34912

n Issue whereby the Interactive Cell Planning tool did not consider the specified colorprofiles 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 aninstance of an object' displayed when attempting to create a Data Manager databaseusing the existing scheme option. Case 34727

n Issue whereby Data Manager Server could not be configured to accept file serverpaths containing spaces. Case 34726

n Issue whereby the Network Overlay tool produced unexpected results when appliedto a group. Case 34643

n Issue whereby the message 'Data on clipboard is not same size and shape as thetarget area' displayed when attempting to copy data into the Tabular Editor. Case34544

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 importprocess has been aborted and no changes made to the project. Data validationmessage: <Sector ID> Power Split (%) for a single antenna must be 100%.'displayed when attempting to modify antenna cable length in Tabular Editor. Case34491

n Issue whereby the generation of an LTE PCID plan failed. Now, If an existingassignment violates a hard constraint and the "Keep existing" option is selected, anappropriate message is shown (with site/sector name) and the PCID calculation iscanceled. Case 34085

n Issue whereby the display of Bing Aerial maps did not work when Windows wasconfirmed to use Russian language/region settings. Case 34175

n Issue whereby grids produced using the Trimmer tool were not correctly aligned. Theproblem occurred in some cases where the minY and/or maxY of the trim polygonwas outside the extents of the geodata. Case 34170


n Issue whereby the message 'Enterprise edition of mPlanet does not support thisfeature” message when there are no ACP licenses available' displayed whenattempting to run optimization when no ACP license was available. Messaging hasbeen 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 displayproperly. The issue occurs when the site ID's of sites for which the graph was based oncontained numeric values. Case 33992

n Issue whereby the cascade option in the Data Manager Console did not work properlywhen applied to custom data fields (e.g. the chosen custom fields availability was notcascaded to all projects). Case 33959

n Issue whereby only the active site set was migrated. Now, all site sets are migratedwhen migrating from version 5.4 or 5.5 (note that only the active site set is migratedwhen migrated from version 5.3.1). Case 33476

n Issue whereby the message 'Could not find AntennaAlgorithm' displayed whenattempting to import data using the Import/Export command line utility (IECON). Theproblem occurred in cases where the antenna algorithm was empty instead ofcontaining a value of 'N/A'. Case 33464

n Issue whereby sections of an analysis layer exported to Google Earth format weremissing. 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 problemwas caused by the fact that the project being migrated contained multiple transceiversreferencing the same carrier (not supported in Mentum Planet) and the service namesexceeded the length allowable in Mentum Planet. Now, if multiple transceiversreference the same carrier only the first one is migrated. Also, Mentum Planet hasbeen 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 closedfollowing project migration. This problem only occurred on systems using the WindowsXP operating system. Case 33367, 29856

n Issue whereby a cloned sector did not automatically display in the map window (theproject had to be re-opened before the new sector would display). Case 33282

n Issue whereby the grid contouring tool produced incorrect results under certainconditions (e.g. with certain range values). Case 32808

n Issue whereby the status information in the model tuning window was incorrect. Insome 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 amessage telling you the process had been aborted. Case 33109

n Issue whereby an out of memory error displayed when attempting to generateprediction using the Planet General Model. Performance has been improved tosupport longer prediction distances (distances will vary depending on data resolutionand computer specifications). Case 1491

n Issue whereby the message '<site name/sectorname> failed : Predict 4.0 radialcalculations: Diffraction algorithm failed to converge' displayed when attempting togenerate 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 wereexported 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 samesite could not be viewed at the same time. Case 29211

n Issue whereby data import using IECON failed when a referenced antenna patternwas not in the Data Manager database. Now, an informative error message isprovided in this situation. Case 28590

n Issue whereby labels generated in the Tabular Editor based on the azimuth fieldoverlapped 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 isoften an indication that other memory is corrupt' displayed when attempting to usethe 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 stoppedinteracting with Windows and was closed’ displayed when carrying out variousoperations. Case 32871

n Issue whereby coverage displayed through network analysis was not as expectedunder certain conditions. Specifically, this problem occurred in cases where anadditional carrier was enabled on a sector after a network analysis configuration wascreated but before it was run. Case 35860

n Issue whereby an out of memory exception displayed when attempting to runnetwork analysis. Case 35813

n Issue whereby a project that could be opened in previous versions could not beopened in Mentum Planet 5.5.0. When project opening was attempted, a messageindicating there were no licenses available displayed even though licenses wereavailable. 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 sitechanges to Data Manager. The issue was caused by a problem with the way DataManager handled conflicts (e.g. when two or more objects had changes to the sameattribute.) Case 35655

n Issue whereby the output layers generated through network analysis did not takeantenna twist into consideration. Case 35621

n Issue whereby the message ‘An error occurred during export: The INSERT statementconflicted with the FOREIGN KEY SAME TABLE constraint' displayed when DataManager migration was running. The problem occurred in cases where the DataManager database being migrated contained nested project folders. Cases 35261,35971

n Issue whereby prediction results based on the Predict Air propagation model wereincorrect 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 runnetwork 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 curvefiles. 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 errorcode 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 DataManager. Case 34916

n Issue whereby the message ‘MapInfo Professional application file has stoppedworking’ displayed when attempting to run WCDMA Monte Carlo simulation. Case34637

n Issue whereby calculated iDEN service probability values were incorrect in the casewhere signal strength was below all the HCL thresholds but greater than the globalsignal strength threshold. Case 34935

n Issue whereby fast fading margins were not accounted for in the calculation of HSDPAdata rate coverage probabilities in WCDMA network analysis and Monte Carlosimulation. Case 34820

n Issue whereby WCDMA Monte Carlo simulation results wrongly showed subscribersbeing blocked for the reason ‘Throughput Limit’. To address this issue, the maximumthroughput limit value has been increased from 1000 Mbits/s to 1000000 Mbits/s. Case34677


n Issue whereby the messages “Layer ‘E-DCH – Max Achievable Data Rate’ on carrier 1will 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 sitefile. Case 33685

n Issue whereby the message “Error: An exception occurred during the ACP engineoptimization” displayed when attempting an ACP run. The problem occurred in caseswhere the optimization profile being used contained only WCDMA uplink goals. Case33977

n Issue whereby Monte Carlo simulation showed subscribers being incorrectly blockedfor the reason ‘No reference coverage’. Case 34564

l Issue whereby values shown on the LTE downlink C/(N+I) analysis layer wereincorrect. The problem occurred in cases where the sectors for which the analysiswas 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 toassign 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 planwas incorrect. Case 34570

l Issue whereby the message “The required technology is not enabled. Enable thetechnology in the network settings” incorrectly displayed when attempting to runTDMA network analysis. Cases 33694, 33881, 33887, 34024

l Issue whereby the application was slow to start. The issue occurred in cases whereincomplete information was provided during registration. Case 33345

l Issue whereby the message “Process aborted. Model tuning failed with the followingerror: Clutter in grid file <PathToClutterFile> is not defined in model <ModelName>”displayed when attempting to tune a Predict 4 model that references a clutter filewith 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 accuratelyreflect the sector for which the analysis was run. The problem occurs in cases wheresector carrier assignments were changed between analysis runs. Cases 35860,36443

n Intermittent issue whereby the application crashed when using the Point Inspectiontool. Cases 34215, 36125, 36121

n Issue whereby the message ‘<SiteID>/<SectorID> failed: Access violation whengenerating 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 betweenversions. 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 occurredwhen 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 whenattempting 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 whenattempting to generate signal strength predictions. The problem occurred in caseswhere, at least some of the sites for which prediction generation was being run, werelocated outside the primary project heights file. Case 30593

n Issue whereby Data Manager security settings associated with user accountsunexpectedly changed from 'passworded' to 'integrated security'. The problemoccurred in cases where users with 'integrated security' were being imported overusers with no set password. Case 29313

n Issue whereby the message 'Error: Value cannot be null' displays when attempting togenerate a traffic map based on fixed subscribers. The problem occurred in caseswhere the project heights map did not cover the region where subscribers wereplaced. The software now provides a suitable message in such cases. Case 28948

n Issue whereby the message 'Thread was being aborted' displayed when attempting todisplay a network analysis layer. The problem occurred after changing the projectgeodata where the newly specified file(s) were in a different coordinate system ascompared 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. Case30640

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 computebuilding 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 numbersgreater than Int32. Case 31417

n Issue whereby the message 'Error initializing tree structure of fixed subscriberstable. Plugin FixedSubscribersPlugin not loaded' displayed when opening a project.Case 32319

n Issue whereby the message 'MapInfo Professional application file has stoppedworking' displayed and the Planet application terminated while scrolling in ProjectExplorer. Case 30769

n Issue whereby the message 'LTE FDD Transceiver <TransceiverID> hasLTETransceiver.FfrUsageRatio=1 value out of range' displayed when attempting toapply cell loads from a Monte Carlo analysis. Case 29329

n Issue whereby the message 'Object reference not set to an instance of an object'displayed when attempting to perform a network overlay. The problem occurred incases where the default.pafx and missing_default.pafx antenna files were missingfrom the project. Case 28598

n Issue whereby the message 'Propagation Model Analysis: None of the surveyantenna properties correspond to their assigned sector antenna properties. Analysisis 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 Profiletool was shifted. This problem occurred in cases where the Point-to-Point Profile toolwas launched when a Bing Maps layer was displayed. Case 30771, 26720, 29700

n Issue whereby the application terminated unexpectedly when the Site Editor windowwas closed. This issue occurred in cases where the Site Editor window was closedwhen the Antenna Editor window was open. The problem was observed on WindowsXP operating system. Case 31844

l Issue whereby the message 'Additional non-parsable characters are at the end of thestring' displayed when allocating test mobile file records to sectors. The problemoccurred in cases where the BSIC field of a record in the test mobile data filecontained no value. Case 29327

n Issue whereby the TDMA_FDMA network analysis wizard dialog box did not displayproperly (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 greaterthan 100%' displayed when attempting to import data. The issue occurred in caseswhere the site and/or sector IDs in the sector_antennas sheet of the file beingimported were different than the site and/or sector IDs in the project to which thedata was being imported. Case 30113

n Issue whereby the message 'System.OutofMemoryException' displayed when CDMAnetwork analysis was being run on a large number of sites/sectors. The problemoccurred 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' whenattempting to connect to Data Manager. Changes have been made in version 5.5 whichreduce the likelihood of this issue occurring. Cases 30526, 30591

n Issue whereby sites selected in a Browser window were not selected in the Mapwindow. Case 23231

n Issue whereby values contained in the LTE common and per-carrier analysis layerswere not the same. The common analysis layers displayed a value of 'No' when therewas 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 havethe same name as another carrier in the same technology' when attempting to migratea 3rd party project. Case 33132

n Issue whereby the message 'Object reference not set to an instance of an object'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 ofchannels at the end of an automated frequency planning (AFP) run when the 'Keepexisting channel assignments' option was enabled. Case 32553

l Issue whereby the 'View results in map' option in the Query window did not functioncorrectly - it selected the sites in the map window instead of displaying them as aseparate map layer. Cases 30253, 30976

l Issue whereby the message 'Cannot display building height profile: Failed to computebuilding height profile with error: Expression does not evaluate to a column or tablename' displayed when attempting to add a building height profile. The problemoccurred when the building height polygon file name contained more than 31characters. 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' Propertieswas incorrect. Case 32572

Issue whereby the message 'The key was not present in the dictionary' displayedwhen attempting to generate a traffic map when the indoor/outdoor feature wasenabled and the when either the indoor or outdoor percentage was sent to '0'. Case29599

Issue whereby filtering a survey based on distance in meters removed all surveypoints. Case 28276

Issue whereby the message 'Error: Could not read network data file. Syntax error inFROM 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 networkdata contained an underscore character. Case 28750

Issue whereby the user documentation indicated that you could rename a Generictechnology in Network Settings when it was actually not possible. The userdocumentation has been updated so that it no longer indicates the renaming option ispossible. Case 29713

Issue whereby you could not change the "Uplink Center Frequency" value for aGeneric technology. Cases 22411, 29714

Issue whereby the default tilt value for a multi-band, multi-tilt antenna displayed (inSite Editor) as '0' even though there were no electrical tilts of '0' defined in theantenna pattern. Case 30783

Issue whereby the Planet General Model AMT tuner incorrectly used the projectdefault clutter file in all cases. Case 25414

Issue whereby the Planet General Model incorrectly applied the Okumura andSuburban correction factors (e.g. It interpreted the +/- signs incorrectly). Case29304

Issue whereby the application locked up and crashed when using Page Up and PageDown keys to scroll through the site list in Project Explorer. Case 32226

Issue whereby network analysis layers were not respecting the analysis area boundsdefined 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 onthe Layer Control tool button. Cases 23405, 26588, 29550

Issue whereby the viewpoint pick tool used in association with the Viewshed Analysistool did not appear when Viewshed Analysis was launched from Grid Manager. Case26570

Issue whereby contour threshold values could not be adjusted. This issue occurredwhen 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 than32,767 records. Case 29610

Issue whereby the message "Column 'Optimal/Forced Best Server' does not allownulls" displayed when attempting to add a fixed subscriber table. The problemoccurred in cases when the required column 'Optimal/Forced Best Server' was notpresent in the file being imported. Case 31886

Issue whereby LTE 'Useful Bits per Symbol' modulation values displayed as floatswhen 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 antennaalgorithm 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 antennalocation coordinates. This issue was due to rounding. Case 29233

Issue whereby, when importing project data, the log window erroneously indicatedthat rows in the Optimization Constraints table had been modified. Case 29234

Intermittent issue whereby the model tuning report was missing clutter statistics forsome 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 toMentum Planet 5.x. The problem occurred in cases where there were missing feedercable values for LTE antenna branches. Case 31749

Issue whereby grid files located in a folder that included '.tab' in its name could not beopened from the Grid Manager window. Case 26565

Issue whereby the site search feature did not work when sites were grouped bytechnology, antenna, or propagation model. Case 26374

version 5.4

n Issue whereby the message 'Cannot find table 0' displayed when attempting to importnetwork data in Microsoft Excel format. The problem occurred in cases where thename of the worksheet being imported began with a number. Case 15830

n Issue whereby the message 'Antenna coordinate system is not the same as DEMcoordinate system' displayed when attempting to run network analysis. This issueoccurred in cases where the project geodata was changed and the new geodata had adifferent coordinate system than the original geodata. Case 17034

n Issue whereby local attachments were deleted after disconnecting from DataManager. Case 17898

n Issue whereby the snap option did not function properly when creating a new siteusing the Place Copy function. Case 18110

n Issue whereby the message 'Error: Index was out of range. Must be non-negative andless than the size of the collection' displayed when attempting to generate a WiMAXfrequency and preamble plan. This problem occurred in cases where the number ofrequired 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 togenerate contours using the Smooth Contouring Tool. Case 19751


n Issue whereby the right-click (shortcut) menu is disabled when accessed from theheights or clutter node in Project Explorer (Project Data>Geodata). This problemoccurred 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 undercertain conditions. The problem occurred in cases where one or more grids beingused as input were not properly aligned. Now, a warning is shown when loading aproject or when attempting to change your project geodata to alert you to the factthat your data is not properly aligned. If your data is not properly aligned you shouldcontact your geodata vendor to have it corrected. Case 21358

n Issue whereby an exception occurred when attempting to create a site template fromProject 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 inMicrosoft Excel format. The problem occurred in cases where users were using anon-English version of Microsoft Office. Cases 21897, 21685

n Issue whereby the sites layer was wrongly removed from the map window aftercarrying out a site edit operation. Cases 22161, 26966

n Issue whereby the application window lost focus (e.g. The application window wentto the back) after closing a dialog box. Case 22502

n Issue whereby flag and group nodes were not properly sorted in Data Manager. Case22668

n Issue whereby sector symbols changed to a star-shaped pattern after adding a newsite using the Place Copy command. This problem occurred in cases where theSiteFile layer within the SiteFilePerformanceLayer was moved above the SiteFilelayer outside the SiteFilePerformanceLayer folder. Case 23113

n Issue whereby site/sector records were not sorted alphabetically when viewed in abrowser window. Case 23236

n Issue whereby the sectors displayed in the Tabular Editor varied depending on howthat 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 ProjectExplorer 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 thePlace Copy command. This problem occurred in cases where the name of the newsite exceeded the 30-character limit. Cases 23897, 24015, 23420, 29097

n Issue whereby a Group layer appeared 'shifted' in relation to the site layer whendisplayed in a map window. Case 23943


n Issue whereby area values displayed in the Layer Statistics Analysis tool did notrespect the units defined in the Preferences dialog. Case 24404

n Issue whereby height values in Universal Model did not respect the units defined in thePreferences dialog. Case 24361

n Issue whereby sector names displayed in the Site Editor were not sortedalphabetically. Case 24691

n Issue whereby the message 'Predict 4 error Failed to open the temporary filescontaining radial data' displayed when attempting to perform propagation modeltuning. Case 24627

n Issue whereby the map window node in Project Explorer did not update after thecorresponding map window was renamed. Case 24875

n Issue whereby the message 'NWSpatialWrapper; vmSpliceGrids: Could not splicegrids' displayed when attempting to view prediction layers. The problem occurred incases where a sector name contained an unsupported character (e.g. An accentedcharacter). Case 24383

n Issue whereby it was difficult to read node labels in Project Explorer when a node wasselected (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 clickedon. Case 25098

n Issue whereby the cursor focus in the Sites tree in Project Explorer jumped to anunexpected location when clicking on sites within the tree. Case 25097

n Issue whereby information for some WCDMA terminal categories was missing in theuser documentation. Case 24904

n Issue whereby the message 'Error: An error occurred while reading the grids: Indexwas outside the bounds of the array' displayed when running optimization with typeSite Selection. The problem occurs in cases where the propagation models associatedwith 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 theavailable propagation model list. Case 25289

n Issue whereby the message 'Unable to open table' displayed when attempting todisplay a prediction layer. The issue occurred in cases where the site name containedUnicode characters. Unicode characters are now supported for the followingpropagation models: PGM, PGM-A, Q9 and Longley-Rice. They are not supported forPredict 4 and Universal Model. Cases 25185, 29231

n Issue whereby the migration of a Mentum CellPlanner 10 WCDMA project failed when adescription 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 awarning 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 whiletrying to compute the analysis. The error is: Vector File too large => nbrecord(109975) > 100000 items' displayed when attempting to generate a new propagationmodel 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 displayedin 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' wasthrown" displayed when attempting to run LTE Monte Carlo simulation. Memorymanagement improvements have been implemented in 5.4.0 that greatly reduce thepossibility of such an exception occurring. Case 25782

n Issue whereby data exported based on a sector Group contained sectors that werenot in that Group. Case 25783

n Issue whereby Fixed Subscriber Analysis results were missing from the MicrosoftExcel results file. This problem occurred in cases where the 'select prediction at CPEantenna height level' option was selected. Case 25918

n Issue whereby the unit uses for MIMO B in the Microsoft Excel Fixed SubscriberAnalysis report incorrectly showed as dB instead of as a percentage. Case 25919

n Issue whereby the Project Explorer behaved erratically. This included problems withscrolling operations, problems opening/closing groups and issues with cursormovement. Changes implemented in version 5.4 make these issues much less likelyto 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 occurredin cases where the user entered some characters in the Sites filter in ProjectExplorer and then immediately changed the focus to another application. When theyreturned the focus to Mentum Planet they found the application had 'frozen'. Case26684

n Issue whereby changes made to a site's properties were incorrectly being reflectedin a copy of that site. Case 26162

n Issue whereby the message 'GSM_Sectors Table: Sector <SectorID> has invalidvalue' displayed when project data was being imported. The problem occurred incases where the GPRS Maximum Supported Coding Scheme and EGPRS Codingscheme 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'" displayedwhen 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 whenthe FH type was set to BBH. Case 26294

n Issue whereby the GSM Worst Offender C/A network analysis layer failed to accountfor the adjacent channel interference rejection factor and therefore did not show thecorrect values. Case 26316

n Issue whereby the message 'sites locked by n/a' displayed Unexpectedly in DataManager. Case 26356

n Issue whereby the message 'Error in the application' displayed while attempting toconnect to Data Manager Server. This problem occurred in cases where the specifiedport number was incorrect. The application now displays a more meaningful errormessage 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 togenerate predictions. This problem occurred in cases where user was trying togenerate predictions for sectors for which prediction generation had previously beenterminated before completion of the process. Cases 26512, 26681, 26897, 26931

n Issue whereby the Scan Receiver Export to Survey function produced incorrect resultsunder certain conditions. Case 26127

n Issue whereby there was an unexpected discrepancy between the LTE FDD uplink MCSand 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. Theproblem occurred when there were missing primary keys in the import file. Case27101

n Issue whereby the message 'failed write to BIN file' displayed when attempting togenerate predictions. The problem occurred in cases where the resolution ofreferenced heights and/or clutter data was not an integer value (a requirement inMentum Planet). Now, a warning message is displayed in such cases alerting the userto 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>: cannotuse 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 orincrease 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. Case26054

n Issue whereby the clutter properties setting in the propagation model editor changesto 'Use default/single properties' when the receiver height is changed. This problemoccurred 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 importprocess has been aborted and no changes made to the project. Data validationmessage: 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 whenexported to Microsoft Excel format. Case 27666

n Issue whereby the survey operations such as generate header from sector, surveyaveraging and survey filtering caused the antenna coordinate values to Unexpectedlychange. Case 27560

n Issue whereby the message 'Failed to load project. Project <ProjectName> musthave at least 1 range optimization constraint. Please make sure you are not deletingone' displayed when opening a project. Case 27835

n Issue whereby clutter properties defined in the Propagation Model Editor are lostwhen switching between clutter grids of different resolutions. Case 27442

n Issue whereby scroll bars in the Tabular Editor Unexpectedly disappear afterapplying filters. Case 27963

n Issue whereby the message 'Index was outside the bounds of the array' displayedwhen generating LTE FDD Monte Carlo simulation. The problem occurs when thetraffic map associated with the subscriber covers a larger area than the projectgeodata. The application now displays a warning message when this condition existswith instructions to trim the traffic map so that it falls within the bounds of thegeodata. Case 28004

n Issue whereby the message 'Sites cannot be placed for the selected region' displayswhen using the Automatic Site Placement Tool. Case 27319

n Issue whereby TDMA network analysis failed when one or more sites considered forthe 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 someantennas from the results. Case 28155


n Issue whereby the ACP site selection algorithm did not activate the correct number ofsites under given conditions. Case 28156

n Issue whereby the message 'Index was outside the bounds of the array' displayedwhen attempting to generate CDMA network analysis layers. The problem occurred onprojects that were migrated from a previous version. Cases 28064, 28981

n Issue whereby the number of subscribers indicated in the Subscribers>Global reportfor WCDMA Monte Carlo simulations was incorrect. Case 28284

n Issue whereby the file generated when viewing a survey transmitting location did notget stored in the project folder. Case 28255

n Issue whereby the message 'UM: Memory allocation failure' displayed whenattempting to generate predictions using Universal Model. This problem occurred incases where the antenna correction option in the model was enabled. Cases 27947,28916

n Issue whereby the application crashed when attempting to run batch projectmigration. Case 28638

n Issue whereby the message 'Warning: Unable to delete directory<ProjectFolder\...\ColorCodePlanning>' displays when attempting to run batch projectmigration. Case 28635

n Issue whereby grid creation using interpolation was not possible (e.g. The processfailed with multiple error messages). Case 28595

n Issue whereby the formula used to compute the number of control channel resourceelements for LTE FDD was incorrect. Case 28760

n Issue whereby the message 'Object reference not set to an instance of an object'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 aproject that did not have a clutter file in the Geodata folder. Case 29200


Known IssuesThe following list details important issues that are known to exist at the time of thisrelease. These issues are being actively tracked and managed, and we expect to resolvethem in the near future. These issues will be addressed as we progress through thesoftware 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. Theissue only affects contours generated using the Narrowband PCS option. Case 34630

Issue whereby the Smooth Contouring tool incorrectly allows you to set the originalbin size, interim bin size, and smoothing window size to the same resolution value.This combination of settings is not valid and may produce incorrect results. Case34132

Issue whereby a project cannot be closed if that project was created by anotheruser. The problem occurs on the Windows 2012 operating system.

Issue whereby the message 'Failed to create site table' displayed when attempting toopen a project. The problem occurs on the Windows 2012 operating system.

Issue whereby the message 'No license available for this action' displayed whenattempting to save a project. The problem occurs in cases where Mentum Ellipse8.2.1 is installed on the same computer where Mentum Planet is installed.

Issue whereby the Help files displayed for microwave functionality inside MentumPlanet is 'offline' even when the user preference in Mentum Ellipse is set to 'online'.

n Issue whereby the capture data option in the Grid Info tool does not functionproperly. To work around this issue, click the Grid Info button after enabling thecapture data option. Case 25583

n Issue whereby the message 'Predict 4 error failed to open the temporary filescontaining radial data' displays when attempting to generate predictions using theCRC-Predict propagation model. To work around this issue, reduce the number ofradials you are using. Case 24627

n Intermittent issue whereby an exception (System.Data.OleDb.OleDbException)occurs when attempting to import project data. If you encounter this issue, reducethe amount of data you are importing and re-try the data import operation. Case23629

n Intermittent issue whereby the application freezes when a user is attempting tochange colors on a classified grid. To work around the issue, close and re-open theapplication. Case 23723

n Issue whereby the application crashes after changing the Windows system font sizeto Extra Large.

n Sector symbol azimuths do not consider eAzimuth. Case 19207


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 namemust start with “long” or “x”, or “lat” or “y”.

n The coordinate system of the Heights file, in which case, the first column nameshould not start with “long”, “x”, “lat” or “y”, but instead the first column mustcontain X coordinates, and the second column must contain Y coordinates.

n When generating propagation model analyses, an “out of memory” exception mayoccur when saving large analyses. If such an error occurs, reduce the number of“distances” in the analyses settings. Network analyses generated in Mentum Planetversion 4.x are not accessible from the Project Explorer in version 5.2. These analysisfiles can be found in the /ProjectName/Obsolete folder (in appropriate technology-dependent sub folder).


Known LimitationsThe following list details limitations that are known to exist at the time of this release.

n F1 Help is not available for items in the Microwave category of Mentum Planet whenyou have Mentum Ellipse 8.2.1 installed. To resolve the issue, upgrade to MentumEllipse 8.2.2.

n The Scan Receiver import function can support files of up to ~15MB. If the file youare importing is larger than this we recommend you use the Scanner Survey Importfunction. Case 30857

l In Mentum Planet, traffic values are stored with 2-byte precision. This means thattraffic maps can utilize a maximum of 65 536 discrete values. If the actual range oftraffic density values exceeds this number, the density values will be scaled to fitwithin the 2-byte range. For any given area, this means that it may not be possible toassign the bins within that area uniform traffic density values. Instead, in order topreserve the total amount of traffic within that area, it may be necessary to assigndifferent traffic values to the bins within the area. In all cases, assigned trafficvalues will be a multiple of the 2-byte interval calculated through the scalingprocess. A 'speckled' pattern may be evident if colors assigned to density values inadjacent bins are different.Case 19072

n Issue whereby the message 'No license available for Universal Model. Please checkthe license file <PlanetDir>\Universal Model\Universal_Model.lic' displayed whenattempting to tune a Universal Model. This issue occurs when attempting to use astandalone 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 issueapplies to HSPA carriers only. To avoid the problem, increase your screen resolution.Case 22236

n There may be minor differences in predictions when compared with Mentum Planet4.5. These differences can be attributed to fixes that were made to the Longley-Ricemodel that existed in Mentum Planet 4.5:

n We found differences between mP5.2.1 and mP4.5 of 0.1 to 0.35dB in some areasdepending on the DEM. In rest of the areas (>90%), the predictions from 4.5 and5.2.1 were almost identical.

n The AFPP tool button applies only to GSM/TDMA technologies. If you wish to run AFPPon a technology other than GSM or TDMA you must launch the tool from the Toolsmenu. Case 21072

n The workflow of connecting a single local project to multiple Data Manager projectsis not supported. If such a workflow is attempted a warning message will bedisplayed. 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 anexisting 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 inthe analysis even though they are not part of the Group or part of the Flag selection. Ifyou 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 morethan 65534 region objects. If your region files contains more than this number ofregions you must break it into parts and perform traffic map generation separately foreach region file. Cases 17030, 21542

n MapInfo Workspace references are not migrated (General tab in Project Settings)when migrating from Mentum Planet 4.5.1 to Mentum Planet 5.3.0. Furthermore, theWorkspace format has changed between versions. You must recreate your Workspaceupon migrating to 5.3.0 and re-set the reference to it in Project Settings. Case 21839

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 yourheights file (in Project Settings) to a file other than the original file then revert to theoriginal file. This action will update the terrain height values. Cases 23595, 23834

n If you change your project clutter file to a new file that does not have the same classstructure as the previous file, you must open your propagation models in thePropagation Model Editor, select the Clutter Properties tab, click anywhere in theProperties section, and then click OK. Case 18603

n Displaying Bing Aerial or Bing Hybrid map layers may cause a shift of layers due toprojection differences. To avoid this shift set Reprojection to Optimized (Map>MapOptions>Image Processing).

n The message 'Marconi error #401' displays when attempting to export a large grid fileto MapInfo Tab format. This error occurs in cases where the resultant Tab file wouldexceed the 2GB maximum size. Case 15521

n The Prediction Generator dialog does not indicate whether a prediction for a givensector is 'merged' as it did in Mentum Planet 4.x. The reason for this is because, inMentum Planet 5.x, individual rows in the Prediction Generator represent sites ratherthan sectors. The sectors on a given site may include a mix of modeled and mergedpredictions 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 (eitheras type modeled or merged). Case 14789

n Sector location offset values may vary slightly after migration from mP 4.x to mP 5.xdue to differences in how the values are computed between versions. These


differences should have no significant impact on the accuracy of predictions. Case14464

n On migration from Mentum Planet 4.x to Mentum Planet 5.x, combined antennas arenot automatically converted to split antennas. The current migration rules are inplace to ensure predictions generated in Mentum Planet 5.x are the same as thosegenerated in mP 4.x. This would not be the case if combined antennas wereautomatically converted to split antennas. Case 14678


System requirementsThe system requirements outlined in this section are general recommendations only and arebased on typical usage of Mentum Planet software. This section details the systemrequirements 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 thissoftware installed on your computer, you will be prompted to connect to the Microsoft website to download and install it. To do so requires an Internet connection.

Warning: Requirements vary depending on the layout of the network, the number ofsites, and the work practices you adopt.

Minimum configuration

This configuration is suggested for networks up to 3 000 sectors. You can work with largernetworks using this configuration but performance may be impacted.

Processor Workstation: Single Core Intel CPU (e.g., the Celeron 440, 2GHzclock) or equivalent

RAM 2 GB

Hard disk At least 20 GB free space


Minimum configuration

Display SVGA (16-bit), 1280x1024

Operating System Windows XP 32-bit

It is recommended that you set the system locale to “English(United States)”.

Some Automatic Updates can cause your computer to reboot,which may interrupt operations in Mentum Planet. It isrecommended that you modify the Automatic Updates settings sothat they are not done automatically.

Required Software In order to use the Mentum Planet Import/Export tool, you musthave Microsoft Excel installed. In addition, you must have AdobeReader installed to view the Mentum Planet user documentation.

Recommended configuration

This configuration is suggested for networks up to 15 000 sectors. You can work withlarger networks using this configuration but performance may be impacted.

Processor Workstation: Intel Core-2 Duo 2GHz or Dual-Core-2 Extreme orequivalent

RAM 4 GB

Hard disk A quick SATA model - 50 GB free space


Recommended configuration


Operating System Windows 7 64-bit

It is recommended that you set the system locale to “English(United States)”.

Some Automatic Updates can cause your computer to reboot,which may interrupt operations in Mentum Planet. It isrecommended that you modify the Automatic Updates settingsso that they are not done automatically.

Required Software In order to use the Mentum Planet Import/Export tool, you musthave Microsoft Excel installed. In addition, you must have AdobeReader installed to view the Mentum Planet user documentation.

Note: An Internet connection is required to validate licenses. If there is no Internetconnection, you can complete the offline registration form and email it to Customer Care.

Note: To run Mentum Planet, you must be a member of the “Power Users” group at aminimum. Regular “Users” must be granted write access privileges to the <MentumPlanet 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 theData 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 isalso contacted periodically throughout the Mentum Planet session. As a result, it is importantto choose a computer that is always available to serve the licenses. Ideally, the LicenseServer should be installed on a file or DNS server because these computers are alwaysonline. Static, fixed IP addresses provide the best performance. However, you can installthe 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 thelicenses are minimal (5 MB free disk space).

The system requirements listed in the following tables are intended for deploymentscenarios 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 donot have this software installed on your computer, you will be prompted to connect tothe Microsoft web site to download and install it. To do so requires an Internetconnection.


Recommended Configuration for a Small Deployment

A small deployment is one in which up to 5 simultaneous users are accessing MentumPlanet installed on a single application server and using either Windows TerminalServices or Citrix for remote access from client.

Processor Xeon-class or equivalent processor with at least 6 cores +hyper-threading

RAM 12 GB of RAM

Hard disk 1 TB of storage


Recommended Configuration for a Small Deployment


Operating System Windows 2008 Server R2, 64-bit

Windows 2012 Server

It is recommended that you set the system locale to“English (United States)”.

Some Automatic Updates can cause your computer toreboot, which may interrupt operations in Mentum Planet.It is recommended that you modify the Automatic Updatessettings 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 MentumPlanet installed on a single application server and using either Windows Terminal Servicesor Citrix for remote access from client.

Processor Dual Xeon-based processor with at least 4 cores perprocessor + hyper threading

RAM 24 GB

Hard disk 2 TB of storage


Operating System Windows 2008 Server R2, 64-bit

It is recommended that you set the system locale to“English (United States)”.

Some Automatic Updates can cause your computer toreboot, which may interrupt operations in Mentum Planet. Itis recommended that you modify the Automatic Updatessettings 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 accessingMentum Planet.

Consult Mentum Customer Care.


System platform compatibilityThe 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.6

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.6

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


DocumentationBefore using this documentation, you should be familiar with the Windows environment. It isassumed that you are using the standard Windows desktop, and that you know how to accessToolTips and shortcut menus, move and copy objects, select multiple objects using the Shiftor Ctrl key, resize dialog boxes, expand and collapse folder trees. It is also assumed thatyou are familiar with the basic functions of MapInfo Professional. For information aboutMapInfo Professional, see the MapInfo online Help and MapInfo Professional User Guide. Youcan access additional MapInfo user documentation from the Pitney Bowes Business Insightwebsite at

http://www.pbinsight.com/support/product-documentation.

Improvements to the Help in Mentum Planet 5.6

Along with additional content to address the new features in this version of the software, theHelp includes the following enhancements:

n High-level workflows are accessible when you select a top-level node such as LTE, Wi-Fi, WiMAX, or Data Manager, etc.

n The Data Manager Application Note is now accessible from the Contents tab.

n An overview of available LTE and WiMAX analysis layers has been incorporated intothe Help.

n See Also related topic links have been added at the end of topics.

n The relative path to the topic is now displayed. You can copy the link displayed in theHelp Topic box (e.g., F1/LayerStats/Analysis_Settings.htm) and send it to colleagues.They can then paste it into the Help Topic box to display the Help page.

Help

Online Help

To benefit from the most up-to-date user documentation, you can connect to the Mentumserver and search for topics of interest. Online Help includes help for MapInfo Professionaldialog 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 displaythe Help page of interest.

Warning: In order to ensure you are viewing the latest Help, verify that your InternetOptions specify that newer versions of stored pages be displayed. In Internet Explorer,


http://www.pbinsight.com/support/product-documentation

http://www.pbinsight.com/support/product-documentation

open the Internet Options dialog box and, in the Browsing History section on the Generaltab, click Settings.

Offline Help

If you are not connected to the Internet, you can still use the local copy of the Help thatwas installed with the software. This version, naturally, will not be as current as theversion accessed from the server. Nonetheless, it contains information about all the basictasks you can perform using Mentum Planet. Local help includes help for MapInfoProfessional dialog boxes and windows.

Context-sensitive Help

You can access Help from every dialog box in Mentum Planet by pressing F1. If you want toview the online Help for a specific panel or tab, click in a field or list box to activate thepanel or tab before you press the F1 key.

Note: Context-sensitive Help for MapInfo Professional opens a separate Help systemthat encompasses only MapInfo Professional topics.

Knowledge Base

You can access the Knowledge Base by choosing the Knowledge Base command from theHelp menu. The Knowledge Base includes up-to-date articles created by the MentumCustomer Care team that provide information and solutions to questions often asked. Youcan access additional resources from the Help menu including product information and thecompany web site. From the Mentum web page, you can download Application Notes andother product documentation as well as access the Self-Service Portal (including theKnowledge Base).

Training

Mentum has a comprehensive training portfolio including on-site training, web training, andmentoring. You can access information about Mentum training by choosing Help > Trainingfrom within Mentum Planet or visit our website.

Getting Started

Read the "Basic Usage" chapter of the Getting Started Guide to begin learning how to useMentum Planet. It provides a quick start tutorial of common tasks.

If you are new to Mentum Planet, tutorials are available that offer a step-by-step look atsome of the main features of the software and are a good way to familiarize yourself withthe tool. Tutorials include a print-ready PDF and a pre-configured project. They areavailable from the Customer Care Download page of the Mentum website.


http://www.mentum.com/

http://www.mentum.com/index.php?page=education&hl=en_US




Read the "Basic Usage" chapter of the Getting Started Guide to begin learning how to useMentum Planet. It provides a quick start tutorial of common tasks.


Contacting MentumMentum is committed to providing fast, responsive technical support. This section providesan extensive list of contacts to help you through any issues you may have.

We also welcome any comments about our documentation. Customer feedback is anessential element of product development and supports our efforts to provide the bestproducts, services, and support we can. See "Send us your comments" on the facing page.

Getting technical support

You can get technical support by phone or email, or by visiting the Self-Service Portal onthe Mentum website at http://www.mentum.com/customer-care.

When you call for technical support, ensure that you have your product ID number andknow which version of the software you are running. You can obtain this information usingthe About command from the Help menu.

When you request technical support outside of regular business hours, a Product SupportSpecialist will respond the next working day by telephone or email, depending upon thenature of the request.

The technical support options available depend on the edition of the software you are usingas shown in Figure 1. For more details about the levels of support, see the Mentumwebsite.

Figure 1: Abbreviated list of support options

North America

Phone: +1 866 921-9219 (toll free), +1 819 483-7094

Fax: +1 819 483-7050

Email: [email protected]

Hours: 9am – 7pm EST/EDT (Monday-Friday, excluding local holidays)


http://www.mentum.com/customer-care

http://www.mentum.com/customer-care

Europe, Middle East, and Africa

Phone: +33 139 26 46 42 (Paris)

Fax: +33 1 39264601


Hours: 9am – 6pm CET/CEST (Monday-Friday, excluding local holidays)

Asia Pacific (excluding Japan)

Phone: +852 2593 1287

Fax: +852 2593 1234


Hours: 9am – 6pm HKT (Monday-Friday, excluding local holidays)

Japan

Phone: +81 3 6861 7555

Fax: +81 3 5847 7901


Hours: 9am – 6pm JST (Monday-Friday, excluding local holidays)

Send us your comments

Feedback is important to us. Please take the time to send comments and suggestions on theproduct you received and on the user documentation shipped with it. Send your commentsto:

[email protected]


mailto:[email protected]?subject=Mentum user documentation

Mentum_Planet_5 6-ReleaseNote (Full).pdf

Documents

Transcript of Mentum_Planet_5 6-ReleaseNote (Full).pdf