Atoll

Atoll
Wireless Network Engineering Software
Administrator Manual
Version 3.4.0
AT340_AM_E3
Atoll 3.4.0 Administrator Manual
Release: AT340_AM_E3 (April 2019)
© Copyright 1997-2019 Forsk. All Rights Reserved.
Published by:
Forsk
7 rue des Briquetiers
31700 Blagnac, France
Tel: +33 562 747 210
Fax: +33 562 747 211
The software described in this document is provided under a licence agreement. The software may only be used or copied under the terms and
conditions of the licence agreement. No part of the contents of this document may be reproduced or transmitted in any form or by any means
without written permission from the publisher.
The product or brand names mentioned in this document are trademarks or registered trademarks of their respective registering parties.
Third party services that are not part of Atoll are governed by the terms and conditions of their respective providers, which are subject to change
without notice.
The publisher has taken care in the preparation of this document, but makes no expressed or implied warranty of any kind and assumes no
responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the
use of the information contained herein.
AT340_AM_E3 Table of Contents
Table of Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.1 Supported Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.2 Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.3 Supported Database Management Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.4 Recommended Hardware and Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.4.1 Single-user Standalone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
1.4.2 Multi-user Thick Client Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
1.4.3 Multi-user Thin Client Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
1.4.4 Floating License Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
1.4.5 File Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
2 Atoll and Component Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.1 Installing Atoll Using the Setup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2 Installing the Atoll C++ Development Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.3 Setup Command Line Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4 Installing and Uninstalling Add-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.5 Installing and Uninstalling Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.6 Atoll Command Line Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.7 Troubleshooting and Other Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3 Distributed Calculation Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.1 Setting Up Calculation Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.1.1 Stopping and Starting the Distributed Calculation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
3.1.2 Running More Than One Distributed Calculation Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
3.1.3 Uninstalling the Distributed Calculation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
3.2 Setting Up Atoll to Access the Calculation Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3 Distributed Calculation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4 Managing Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.1 Atoll Database Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.2 Customising Atoll Database Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.2.1 Adding Custom Fields to Data Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
4.2.2 Setting User-defined Default Values for Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
4.2.3 Setting User-defined Choice Lists for Text Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
4.3 Atoll Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.4 Creating New Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.4.1 Creating a New Database Using the Atoll Management Console. . . . . . . . . . . . . . . . . . . . . . . . . .38
4.4.2 Creating a New Database Using Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
4.5 Upgrading Existing Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.5.1 Upgrading Databases for the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
4.5.2 Upgrading Databases Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
4.5.3 Adding a Technology in a Multi-RAT Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
4.6 Working With Multi-level Databases Using Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
© 2019 Forsk. All Rights Reserved. 3

Table of Contents
4.6.1 Creating Project Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

4.6.2 Archiving Project Databases to Master Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.6.3 Refreshing Project Databases from Master Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.7 Setting Database Access Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.8 Managing Data Modifications History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.8.1 Setting Up Data Modifications History Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.8.2 Enabling/Disabling Data Modifications History Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.8.3 Updating Data Modifications History after a Data Structure Upgrade . . . . . . . . . . . . . . . . . . . . . 51
4.8.4 Purging Old Data Modification Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.8.4.1 Purging Old Data Modification Records of a Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.8.4.2 Purging Old Data Modification Records of a Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.9 Appendices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.9.1 Appendix 1: Advanced Customisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.9.2 Appendix 2: Setting Up Databases for Co-planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5 Multi-user Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.1 Setting Up Multi-user Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.2 Components of Multi-user Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.2.1 Master Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.2.2 Master Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.2.3 Shared Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.2.4 Shared Path Loss Matrices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.2.5 Shared Microwave Link Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
5.2.6 User Atoll Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
5.3 Managing User Accounts and Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
5.3.1 Defining Database and Interface Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.3.2 Managing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
5.3.3 Resetting User Database Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
5.3.4 Managing Custom Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
5.4 Appendices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
5.4.1 Appendix 1: Checking Data Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
5.4.2 Appendix 2: Database Regionalisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
5.4.3 Appendix 3: Calculating Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
5.4.4 Appendix 4: Path Loss Matrices From Different Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6 Coordinate Systems and Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

6.1 Coordinate Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6.1.1 Definition of a Coordinate System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6.1.2 Types of Coordinate Systems in Atoll. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
6.1.3 Coordinate Systems File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.1.4 Creating a Coordinate System in Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
6.2 Measurement Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
6.3 BSIC Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
7 Atoll File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

7.1 Geographic Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
7.1.1 HDR Header File for BIL Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
7.1.1.1 HDR Header File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
7.1.1.2 Additional PRJ Projection File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
7.1.2 TFW Header File for TIFF Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
7.1.3 BPW/BMW Header Files for BMP Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
7.1.4 PGW Header File for PNG Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
7.1.5 JGW Header File for JPG Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
7.2 Path Loss Matrix File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
7.2.1 Pathloss.dbf File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
7.2.2 Pathloss.dbf File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4 © 2019 Forsk. All Rights Reserved.

7.2.3 LOS File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

7.3 Path Loss Tuning File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
7.3.1 Pathloss.dbf File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
7.3.2 Pathloss.dbf File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
7.3.3 PTS File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
7.4 Interference Matrix File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
7.4.1 CLC Format (One Value per Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
7.4.1.1 CLC File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
7.4.1.2 DCT File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
7.4.2 IM0 Format (One Histogram per Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
7.4.3 IM1 Format (One Value per Line, TX Name Repeated) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
7.4.4 IM2 Format (Co- and Adjacent-channel Probabilities) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
7.4.5 MNU Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
7.5 "Per Transmitter" Prediction File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
7.5.1 <per_transmitter_prediction>.dbf File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
7.5.2 <per_transmitter_prediction>.dbf File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
8 Administration and Usage Recommendations . . . . . . . . . . . . . . . . . . . . .103

8.1 Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.2 Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
8.3 Atoll ATL Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
8.4 Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
8.5 Calculation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
8.6 Atoll Administration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
8.7 Process Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
8.8 Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
8.9 Coverage Prediction Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
8.10 CW Measurements and Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
8.11 Antenna Patterns and Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
8.12 Traffic Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
8.13 Atoll API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
8.14 Performance and Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
9 Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

9.1 Contents of User Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
9.1.1 Geographic Data Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
9.1.2 Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
9.1.3 Map Centre and Zoom Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
9.1.4 Folder Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
9.1.5 Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
9.1.6 Automatic Neighbour Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
9.1.7 Automatic Frequency Planning Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
9.1.8 Automatic Scrambling Code Allocation Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
9.1.9 Automatic PN Offset Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
9.1.10 Automatic OFDM Resource Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
9.1.11 Microwave Radio Links Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
9.1.12 Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
9.2 Contents of Additional Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
9.2.1 Print Setup Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
9.2.2 Table Import/Export Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
9.2.3 Coverage Prediction Report Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
9.2.4 CW Measurement Import Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
9.2.5 Drive Test Data Import Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
9.3 Content of the Custom Predictions File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Table of Contents
9.4 Content of the "Value Intervals" Predictions Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
10 Initialisation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

10.1 Atoll Initialisation File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
10.1.1 General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
10.1.1.1 Managing Memory Allocation per Session in Atoll 64-bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
10.1.1.2 Changing the Default Metre-to-Feet Conversion Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
10.1.1.3 Changing the Default Mile-to-Metre Conversion Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
10.1.1.4 Modifying the Default Formats of Site and Transmitter Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
10.1.1.5 Disabling Automatic Renaming of Transmitters and Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
10.1.1.6 Setting the TIFF Colour Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
10.1.1.7 Creating an Event Viewer Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
10.1.1.8 Displaying Insufficient Permission Messages in the Event Viewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
10.1.1.9 Increasing the Maximum Printing Resolution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
10.1.1.10 Copying Externalised Calculation Results on Save As . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
10.1.1.11 Disabling External Storage of Numerical Coverage Prediction Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
10.1.1.12 Disabling Generation of Prediction Study Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
10.1.1.13 Exporting Predictions to Vector Files with a Display Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
10.1.1.14 Exporting Prediction Coordinates using the Projection Coordinate System. . . . . . . . . . . . . . . . . . . . . . . . 152
10.1.1.15 Restricting the List of Predictions for Creating Sector Traffic Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
10.1.1.16 Displaying Path Loss Calculation Details in the Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
10.1.1.17 Mapping Atoll Coordinate Systems with MapInfo/ESRI Vector Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
10.1.1.18 Exporting Coverage Prediction Polygons in Text Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
10.1.1.19 Defining Web Map Services Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
10.1.1.20 Improving Point Analysis Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
10.1.1.21 Excluding Vectors from Imported KML/KMZ Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
10.1.1.22 Combining Imported Zone Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
10.1.1.23 Check for Duplicate Cell Names During Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
10.1.1.24 Setting the Precision for the Antenna Pattern Verification at Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
10.1.1.25 Setting a High Precision Mode for Microwave Antenna Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
10.1.1.26 Setting the Threshold for the Electrical Tilt and Azimuth Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
10.1.1.27 Exporting Selected Data Tables to XML Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
10.1.1.28 Keeping the Original List Separator when Exporting in CSV Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
10.1.1.29 Opening Exported XLS Files Automatically in MS Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
10.1.1.30 Disabling Creation of New Documents from Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
10.1.1.31 Blocking Access to Macros and Add-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
10.1.1.32 Disabling Saving and Opening ZIP Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
10.1.1.33 Hiding the Propagation Models Folder in the Parameters Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
10.1.1.34 Forbidding Shared Antenna Modification in Multi-RAT Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
10.1.1.35 Enabling Notification for Donor Transmitter Parameter Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
10.1.1.36 Setting the Display Precision of Floating Point Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
10.1.1.37 Changing the Path to Linked Geo Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
10.1.1.38 Exporting/Importing Vector Data with a Display Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
10.1.1.39 Using Only Visible Geo Data in Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
10.1.1.40 Exporting BMP, TIF, and PNG Files with a TAB Reference File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
10.1.1.41 Exporting BIL Files with a PRJ Projection File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
10.1.1.42 Co-Planning: Linking the Sites Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
10.1.1.43 Disabling Normalisation of MIF/TAB Vector Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
10.1.1.44 Customising Performance Optimisation when Exporting Vector Files in TAB Format. . . . . . . . . . . . . . . 160
10.1.1.45 Adding the Duplicate Site to the Original Site’s Site List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
10.1.1.46 Moving Sites without Moving Antennas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
10.1.1.47 Real Altitude versus DTM Altitude in Sites’ Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
10.1.1.48 Using Only Visible Clutter Classes in Interference Prediction Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
10.1.1.49 Displaying % of Covered Clutter Classes w. r. t. the Focus Zone in Reports. . . . . . . . . . . . . . . . . . . . . . . . 162
10.1.1.50 Displaying % of Covered Traffic Classes w. r. t. the Focus Zone in Reports . . . . . . . . . . . . . . . . . . . . . . . . 162
10.1.1.51 Synchronising Private and Shared Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
10.1.1.52 Selecting the Logo 2 Check Box by Default in Print Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
10.1.1.53 Filtering Predictions by Technology When Reading the XML Studies File . . . . . . . . . . . . . . . . . . . . . . . . . 163
10.1.1.54 Enabling Event Viewer Messages for MapInfo File Import/Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
10.1.1.55 Setting the Resolution of Population Maps in Coverage Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . 163
10.1.1.56 Setting the Precision in Coverage Prediction Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
10.1.1.57 Including Pixel-free Ranges in Coverage Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
10.1.1.58 Changing Hot Spot Reference Surface in Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
10.1.1.59 Exporting Only Visible Value Interval Layers of Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
10.1.1.60 Avoiding Overlapping Pixels in Best Server Coverage Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
10.1.1.61 Using Legacy Coverage Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
10.1.1.62 Setting the Minimum ATL File Size Requiring Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
10.1.1.63 Loading, Activating, and Setting Add-ins as Visible . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
10.1.1.64 Defining Online Map URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
10.1.1.65 Changing the Default Cache Location for the Loaded Map Tiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
10.1.1.66 Defining the Microsoft Bing Tile Server for Online Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
10.1.1.67 Defining the Microsoft Bing Tile Server for Online Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

10.1.1.68 Defining MapQuest for Online Searches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167

10.1.1.69 Managing Carriage Returns in Imported TXT/CSV Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167
10.1.1.70 Deleting the Filtering Zone on Removing Filters From Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168
10.1.1.71 Disabling the Database and Data Exchange Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168
10.1.1.72 Enabling Atoll to Automatically Restart on Improper Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168
10.1.1.73 Specifying Default Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168
10.1.1.74 Specifying the Default Storage of Favourite Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169
10.1.1.75 Restoring Focus and Computation Zones of a Favourite View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169
10.1.1.76 Fixing Antenna Electrical Azimuth and Tilt Values on Document Update . . . . . . . . . . . . . . . . . . . . . . . . . .169
10.1.1.77 Limiting the Antenna Selection Assistant to the Antenna folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170
10.1.1.78 Simplified Cell Naming. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170
10.1.1.79 Disabling References to Atoll Live . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170
10.1.1.80 Enabling the Import of GSM OSS Data with the Atoll Live Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170
10.1.2 GUI Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
10.1.2.1 Defining the Parameters for the Default Sites Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171
10.1.2.2 Using a Unique Symbol for Remote Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171
10.1.2.3 Using the Transmitter Symbol for Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171
10.1.2.4 Keeping Transmitter Symbols From Changing on Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
10.1.2.5 Displaying Filled Symbols for Inactive Transmitters on the Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
10.1.2.6 Refreshing the Display Automatically When a New Station is Dropped . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
10.1.2.7 Hiding Information Displayed in the Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
10.1.2.8 Displaying Date and Time in the Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
10.1.2.9 Changing the Mouse Wheel Zoom Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
10.1.2.10 Setting the Maximum Number of Lines to Coverage Prediction Tool Tips . . . . . . . . . . . . . . . . . . . . . . . . .173
10.1.2.11 Changing the Display for Downlink Smart Antenna Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
10.1.2.12 Adding Exposure Analysis to the List of Multi-RAT Coverage Predictions (Hidden en 3.2.0.02, ces infos
sont dans TN013)173
10.1.2.13 Displaying Coverage Prediction Comments in the Legend Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
10.1.2.14 Displaying Leading Zeros in the CELL_IDENTITY Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
10.1.2.15 Making the Antenna Additional Electrical Downtilt Accessible . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
10.1.2.16 Increasing the Width of the Clutter Description Pane in the Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
10.1.2.17 Hiding the Technology Name in the Title Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
10.1.2.18 Displaying Objects’ Discrete Values with User-defined Colours. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
10.1.2.19 Avoiding Same Adjacent Cell Colours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
10.1.2.20 Displaying Vertical Beamwidth in Profile Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
10.1.2.21 Locking Site and Transmitter Shading Colours. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
10.1.2.22 Case-insensitive Grouping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
10.1.2.23 Setting Repeaters as Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
10.1.2.24 Hexagonal Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
10.1.2.25 Disabling Confirmation when Deleting a Site from the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177
10.1.3 Distributed Calculation Server Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
10.1.3.1 Detecting and Listing Distributed Calculation Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177
10.1.3.2 Setting the Distributed Calculation Server Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177
10.1.3.3 Modifying the Default Detection Time-out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178
10.1.3.4 Optimising Thread Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178
10.1.4 License Management Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
10.1.4.1 Setting an Alarm for the License End Date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178
10.1.4.2 Blocking Access to Technology Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178
10.1.4.3 Blocking Access to the AFP Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179
10.1.4.4 Blocking Access to the ACP Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179
10.1.4.5 Changing the NetHASP License Manager Idle Time Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
10.1.5 Database Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
10.1.5.1 Checking Data Integrity After Database Upgrade and Data Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
10.1.5.2 Checking Data Integrity on Open or Data Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
10.1.5.3 Preselecting "Refresh Unmodified Data Only" by Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181
10.1.5.4 Trimming Leading and Trailing Space Characters from Text Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181
10.1.5.5 Displaying Database Tables in the Event Viewer at Open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181
10.1.5.6 Allowing Null Entries in Non-nullable Custom Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181
10.1.5.7 Automatically Running GSM Subcell Audit at Open or Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181
10.1.5.8 Modifying the Default Database Connection Time-out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182
10.1.5.9 Changing the Database Export Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182
10.1.5.10 Making Atoll Case-Sensitive for Database Import From Planet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182
10.1.5.11 Setting the Sign for KClutter When Importing Data From Planet EV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
10.1.5.12 Setting the Clutter No Data Value for When Importing Data From Planet EV . . . . . . . . . . . . . . . . . . . . . . .183
10.1.5.13 Enabling/Disabling Password Prompt at Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
10.1.5.14 Archiving Data to Databases Using Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
10.1.5.15 Keeping Separate Work and Master Path Loss Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184
10.1.5.16 Enabling Partial Refresh from Recently Upgraded Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184
10.1.5.17 Setting the Type of Database Being Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184
10.1.5.18 Displaying Only the First Export to Database Error in a Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184
10.1.5.19 Include AMC Database Fields in Read/Write Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185
10.1.6 Common Calculation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Table of Contents
10.1.6.1 Setting the Antenna Patterns Modelling Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

10.1.6.2 Disabling Automatic Locking of Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
10.1.6.3 Enabling Shadowing Margin in Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
10.1.6.4 Setting a Default Value for the Cell Edge Coverage Probability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
10.1.6.5 Enabling Indoor Coverage in Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
10.1.6.6 Modifying the Resolution for the LOS Area Calculation Around a Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
10.1.6.7 Embedding Path Losses in New Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
10.1.6.8 Stopping Calculations on Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
10.1.6.9 Warning About Prediction Validity When Display Options are Modified . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
10.1.6.10 Reading Exact Altitudes From the DTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
10.1.6.11 Setting a Common Display Resolution For All Coverage Predictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
10.1.6.12 Setting the Priorities for GUI and Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
10.1.6.13 Setting the Number of Parallel Processors and Threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
10.1.6.14 Parallel Calculation of Monte Carlo Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
10.1.6.15 Performing Calculations in Read-Only Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
10.1.6.16 Identifying Transmitter, Repeater, and Remote Antenna Coverage Areas . . . . . . . . . . . . . . . . . . . . . . . . . 190
10.1.6.17 Disabling Rounding of Antennas’ Updated Half-power Beamwidth Values . . . . . . . . . . . . . . . . . . . . . . . . 190
10.1.6.18 Changing the Rounding Method Used for Profile Extraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
10.1.6.19 Disabling Calculations Over NoData Values for DTM and Clutter Classes . . . . . . . . . . . . . . . . . . . . . . . . . 191
10.1.6.20 Co-planning: Calculating Predictions in the Current Document Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
10.1.6.21 Co-planning: Calculating Predictions in Serial or in Parallel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
10.1.6.22 Forcing Neighbour Symmetry Only Inside Focus Zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
10.1.6.23 Using Poisson Distribution in Monte Carlo Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
10.1.6.24 Setting the Precision of Global Scaling Factor in Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
10.1.6.25 Calculating EIRP from Max Power in Signal Level Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
10.1.6.26 Excluding Filtered Transmitters from the List of Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
10.1.6.27 Changing the Weighting Factor of the Effective Inter-transmitter Distance . . . . . . . . . . . . . . . . . . . . . . . . 192
10.1.6.28 Extending the Maximum Inter-site Distance to Repeaters and Remote Antennas . . . . . . . . . . . . . . . . . . 193
10.1.6.29 Forcing the Real Inter-site Distance Threshold. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
10.1.6.30 Prioritising Individual Inter-site Distances in Neighbour Importance Calculation . . . . . . . . . . . . . . . . . . . 193
10.1.6.31 Keeping Assigned Neighbours that are not Symmetric with the Reference Transmitter . . . . . . . . . . . . . 193
10.1.6.32 Keeping Neighbours that Relate to Themselves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
10.1.6.33 Enabling and Disabling Per-site Path Loss Matrix Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
10.1.6.34 Defining a Global Maximum Path Loss Calculation Radius . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
10.1.6.35 Preserving Loss and Noise Figures with no Assigned Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
10.1.6.36 Linear Interpolation of Inter-technology IRF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
10.1.6.37 Changing the Real-Time Profile Drawing Method in Point Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
10.1.6.38 Modelling Non-Selective RF Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
10.1.7 GSM GPRS EDGE Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
10.1.7.1 Considering Inter-technology Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
10.1.7.2 Considering Overlapping Zones for IM Calculation Based on Traffic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
10.1.7.3 Setting the Default BSIC Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
10.1.7.4 Checking Database Consistency Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
10.1.7.5 Disabling the Maximum Range Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
10.1.7.6 Increasing the Memory Block Size for Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
10.1.7.7 Enabling the Support for Multi-band Transmitters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
10.1.7.8 Setting the Best Server Calculation Method in Same Priority HCS Layers . . . . . . . . . . . . . . . . . . . . . . . . . 197
10.1.7.9 Hiding AFP Advanced Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
10.1.7.10 Hiding AFP Hopping Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
10.1.7.11 Hiding Violations from Low Importance GSM Neighbours in AFP Results . . . . . . . . . . . . . . . . . . . . . . . . . 198
10.1.7.12 Hiding Violations Between Non-synchronised MALs-MAIOs in AFP Results . . . . . . . . . . . . . . . . . . . . . . . 198
10.1.7.13 Modifying the Thresholds for Important Violations in AFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
10.1.7.14 Selecting the Interference Matrices Used During the AFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
10.1.7.15 Defining the Maximum Number of Transmitters for Reuse Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
10.1.7.16 Defining the Maximum Number of Separation Violations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
10.1.7.17 Making Redundant Fields in the Transmitters Table Read-only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
10.1.7.18 Setting the Transmission Diversity Gain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
10.1.7.19 Deactivating Frequency Band Filtering in IM Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
10.1.7.20 Starting TRX Indexes at 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
10.1.7.21 Hiding the TRX Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
10.1.7.22 Listing TRX Types in Alphabetical Order in Subcells Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
10.1.7.23 Automatically Correcting Out-of-range Subcell Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
10.1.8 UMTS HSPA, CDMA2000, and TD-SCDMA Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
10.1.8.1 Suppressing Cell Name Carrier Suffixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
10.1.8.2 Disabling Macro-diversity (SHO) Gains Calculation for Ec/Io and Eb/Nt. . . . . . . . . . . . . . . . . . . . . . . . . . . 202
10.1.8.3 Calculating and Displaying Peak or Instantaneous HSDPA Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
10.1.8.4 Setting the Power to Use for Intra-cell Interference in HSDPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
10.1.8.5 Enabling Coverage Predictions of Connection Probabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
10.1.8.6 Setting the Calculation Method for HS-PDSCH CQI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
10.1.8.7 Enabling Orthogonality Factor in Pilot EC/NT Calculation in HSDPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
10.1.8.8 Setting the Maximum Number of Rejections for Mobiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
10.1.8.9 Setting the Maximum Number of Rejections for HSDPA Mobiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
10.1.8.10 Defining an Offset With Respect to The Thermal Noise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

10.1.8.11 Setting Precision of the Rasterisation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204

10.1.8.12 Defining the Number of Iterations Before Downgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205
10.1.8.13 Adjusting the Working of the Proportional Fair Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205
10.1.8.14 Displaying the Ec/I0 of Rejected Mobiles in Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206
10.1.8.15 Switching Back to the Old Best Server Determination Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206
10.1.8.16 Switching Back to the Old Radio Bearer Allocation Algorithm for Multi-carrier EVDO Rev.B . . . . . . . . . .206
10.1.8.17 Displaying Automatic Allocation Cost Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207
10.1.8.18 Selecting SC and PN Offset Allocation Strategies Available in the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . .207
10.1.8.19 Defining a Fixed Interval Between Scrambling Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207
10.1.8.20 Compressed Mode: Restricting Inter-carrier and Inter-technology Neighbour Allocation. . . . . . . . . . . . .207
10.1.8.21 Setting the Maximum AS Size for SC Interference Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208
10.1.8.22 Displaying Uplink Total Losses in Coverage by Signal Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208
10.1.8.23 Setting the Maximum UL Reuse Factor for HSUPA Users’ Noise Rise Estimation. . . . . . . . . . . . . . . . . . .208
10.1.8.24 Configuring HSUPA Resource Allocation for Active Set Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208
10.1.9 LTE, NB-IoT, WiMAX, Wi-Fi, and LPWA Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
10.1.9.1 Blocking Access to IEEE Parameters in WiMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209
10.1.9.2 Ensuring Compatibility of UL and DL Bearers between Reception Equipment . . . . . . . . . . . . . . . . . . . . . .209
10.1.9.3 Enabling Display of Signals per Subcarrier Point Analysis in LTE and NB-IoT . . . . . . . . . . . . . . . . . . . . . .209
10.1.9.4 Including Cyclic Prefix Energy in LTE and NB-IoT Signal Level Calculation . . . . . . . . . . . . . . . . . . . . . . . . .210
10.1.9.5 Excluding Cyclic Prefix Energy in WiMAX and Wi-Fi Signal Level Calculation . . . . . . . . . . . . . . . . . . . . . . .210
10.1.9.6 Ignoring Inter-Neighbour Preamble Index Collision in WiMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210
10.1.9.7 Ignoring Inter-Neighbour Physical Cell ID Collision in LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210
10.1.9.8 Renaming OPUSC Zone to PUSC UL in WiMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211
10.1.9.9 Deactivating Uniform Distribution of Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211
10.1.9.10 Taking Second Order Neighbours into Account in the AFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211
10.1.9.11 Excluding the Adjacent Channel Overlap from the AFP Cost Functions . . . . . . . . . . . . . . . . . . . . . . . . . . .211
10.1.9.12 Synchronised/Unsynchronised Interference Calculation in LTE and NB-IoT. . . . . . . . . . . . . . . . . . . . . . . .211
10.1.9.13 Setting PDCCH to 100% Loaded in LTE Interference Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212
10.1.9.14 Calculating EIRP from RS/NRS EPRE in LTE/NB-IoT Signal Level Predictions . . . . . . . . . . . . . . . . . . . . . .212
10.1.9.15 Extending the List of Server Selection Methods in Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . .212
10.1.9.16 Averaging the Uplink Noise Rise in dB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213
10.1.9.17 Deactivating Service Max Throughput Demand Downgrading in LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213
10.1.9.18 Displaying Pixels with Zero Throughput in Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213
10.1.9.19 Setting Uplink Noise Rise Control Parameters in LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213
10.1.9.20 Using the LTE ABS Patterns on Cell-edge Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214
10.1.9.21 Switching Between Carrier Aggregation/Multicarrier Operation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . .214
10.1.9.22 Switching Between LTE Multi-Server Scheduling Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214
10.1.9.23 Switching Between PCell/Anchor Cell Selection Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215
10.1.9.24 Displaying Grid-of-Beam Patterns in Logarithmic Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215
10.1.9.25 Allowing Multi-Cell Transmitters Using Different Frequencies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215
10.1.9.26 Changing the LTE Cell-Edge Determination Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215
10.1.9.27 Filtering LTE and NB-IoT Cell Groups Loaded From a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216
10.1.9.28 Allocating PRACH RSIs from Non-Overlapping Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216
10.1.9.29 Excluding DMRS Overhead from Cell Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216
10.1.9.30 Changing the Display Mode of the Number of Aggregated Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216
10.1.9.31 Aggregating SCell Throughputs Even When No Service From PCell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217
10.1.9.32 Displaying the Statistics Tab of the AFP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217
10.1.9.33 Defining the Ratio of NPDCCH to NPDSCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217
10.1.9.34 Blanking LTE PRBs for Inband NB-IoT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217
10.1.9.35 Limiting the Number of Co-Scheduled MU-MIMO Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217
10.1.9.36 Defining the Table Row Height for the Display of the Angular Distribution of Interference Diagrams . .218
10.1.10 3GPP Multi-RAT Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
10.1.10.1 BSIC, SC, and PCI Allocation with Inter-technology Neighbour Constraints . . . . . . . . . . . . . . . . . . . . . . . .218
10.1.10.2 Multi-RAT Technology Selection Default Behaviour. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218
10.1.11 Microwave Radio Link Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
10.1.11.1 Modifying the Default Format of Link Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218
10.1.11.2 Updating A>>B and B>>A Profiles in Real-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
10.1.11.3 Disabling Shielding Factor on Wanted Signal at Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
10.1.11.4 Considering XPIF value in Interference for Dual-Polar Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
10.1.11.5 Making the ITU-R P.530-5 Method Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
10.1.11.6 Applying Cross-Polar Discrimination Outage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220
10.1.11.7 Using Old Min C/I Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220
10.1.11.8 Solving Alignment Issue in Generated Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220
10.1.11.9 Setting the Maximum Number of Modulations in Generated Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220
10.1.11.10 Sorting Modulations by Rx Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220
10.1.11.11 Defining Default Configuration Files for Link Budgets Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221
10.1.11.12 Defining a Default Configuration File for the Channel Arrangement Display . . . . . . . . . . . . . . . . . . . . . . . .221
10.1.11.13 Defining a Default Template for Microwave Links Custom Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221
10.1.11.14 Considering ATPC for ANSI and ETSI Modes Similarly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222
10.1.11.15 Hiding Clutter from the Profile Analysis View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222
10.1.11.16 Changing the Decoupling Calculation Method for Co-site Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . .222
10.1.11.17 Calculating the Receiver Thermal Noise for the Radio Effective Bandwidth . . . . . . . . . . . . . . . . . . . . . . . .222

Table of Contents
10.1.11.18 Confirming a Delete Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

10.1.12 Measurement Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
10.1.12.1 Displaying Additional Information in Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
10.1.12.2 Setting the Number of Transmitters per Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
10.1.12.3 Recalculating Distances of Points From There Serving Cells at Import . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
10.1.12.4 Defining the BCCH and BSIC Columns for FMT Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
10.1.12.5 Importing Drive Test Data with Scrambling Codes as Integers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
10.1.12.6 Importing Drive Test Data for Active and Filtered Transmitters Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
10.1.12.7 Specifying the Location of the ACP.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
10.2 ACP Initialisation File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
10.2.1 Managing ACP Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
10.2.2 ACP GUI Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
10.2.2.1 Default Settings of the Optimisation Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
10.2.2.2 Default Settings of the Optimisation > Cost Control Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
10.2.2.3 Default Settings of the Optimisation > Advanced Cost Control Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
10.2.2.4 Automatically Creating Custom Zones on the Optimisation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
10.2.2.5 Default Settings of the Objectives Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
10.2.2.6 Default Settings of the Reconfiguration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
10.2.2.7 Default Settings of the Reconfiguration > Sites vertical tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
10.2.2.8 Defining the Inter-site Distance in Co-located Site Detection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
10.2.2.9 Defining the Inter-antenna Distance in Co-located Transmitter Detection . . . . . . . . . . . . . . . . . . . . . . . . . 235
10.2.2.10 Custom Columns on Reconfiguration > Sites Vertical Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
10.2.2.11 Default Settings of the Reconfiguration > Transmitters Vertical Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
10.2.2.12 Custom Columns on the Reconfiguration > Transmitters/Remotes Vertical Tabs . . . . . . . . . . . . . . . . . . 236
10.2.2.13 Default Settings of the Optimisation > EMF Exposure Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
10.2.2.14 Default Settings of the Optimisation > Multi-Storey Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
10.2.2.15 Controlling Antenna Pattern Smoothing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
10.2.2.16 Default Settings of the Antenna Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
10.2.2.17 Defining the Antenna Masking Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
10.2.2.18 Defining Reconfiguration Values Using Custom Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
10.2.2.19 Defining Site Class Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
10.2.2.20 Defining the Appearance of a Running Optimisation Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
10.2.2.21 Defining the Appearance of ACP Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
10.2.2.22 Defining New Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
10.2.2.23 Defining the Functionality of the Commit Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
10.2.2.24 Defining the Appearance of the Overlay Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
10.2.2.25 Defining the Appearance of the Graph Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
10.2.2.26 Defining the Default Font . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
10.2.2.27 Exporting Optimisation Results in XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
10.2.3 ACP Core Engine Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
10.2.3.1 Log File Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
10.2.3.2 Calculation Thread Pool Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
10.2.3.3 Number of Threads Used for Propagation Model Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
10.2.3.4 Memory Management Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
10.2.3.5 Automatic Stops of the Search Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
10.2.3.6 Considering Progressive Thresholds for Some Quality Objectives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
10.2.3.7 Macro Diversity Gains Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
10.2.3.8 Transmitter Altitude Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
10.2.3.9 Automatic Candidate Positioning Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
10.2.3.10 Setting a Minimum Inter-site Distance for Site Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
10.2.3.11 Balancing Speed, Memory Use, and Accuracy in Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
10.2.3.12 Accessing Raster Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
10.2.3.13 Filtering Clutter Class Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
10.2.3.14 Fixed Ratio Between Pilot Power and Max Power (UMTS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
10.2.3.15 Showing Initial/Final Total Poweror DL Load on Sectors Tab (UMTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
10.2.3.16 Custom Columns on the Sectors tab of the Optimisation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
10.2.3.17 Enabling Multi-technology Optimisation Including WiMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
10.2.4 EMF Exposure Core Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
10.2.5 Other Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
10.2.5.1 EMF and Multi-Storey Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
10.2.5.2 Validity of Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
10.2.5.3 Considering Zero-degree Electrical Tilts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
10.2.5.4 Linking Transmitters Operating on the Same Frequency Band . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Index of Initialisation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

AT340_AM_E3 Introduction
Introduction
This Administrator Manual explains how to install, configure, and deploy Atoll and how to set up back-end databases
and manage users in a multi-user environment. Database structures of the different technology modules are also
provided for reference.
For information about managing licenses, see the Atoll Licensing Guide.
About Atoll
Atoll is a multi-technology wireless network design and optimisation platform that supports wireless operators
throughout the network lifecycle, from initial design to densification and optimisation. Atoll offers unique
capabilities of using both predictions and live network data throughout the network planning and optimisation
process.
Atoll includes integrated single RAN–multiple RAT network design capabilities for both 3GPP and 3GPP2 radio
access technologies including 5G NR, LTE, NB-IoT, UMTS, GSM, and CDMA. It provides operators and vendors with
a powerful framework for designing and optimising current and future integrated multi-technology networks.
Atoll supports the latest technology advances such as massive MIMO, 3D beamforming, and mmWave propagation
for the design and roll-out of 5G networks.
Atoll Microwave is a state-of-the-art point-to-point and point-to-multipoint backhaul planning and optimisation
software. It allows designing large microwave link networks, according to ITU recommendations, industry
standards, and operator guidelines.
Atoll’s integration and customisation features help operators smoothly streamline planning and optimisation
processes. Atoll supports a wide range of implementation scenarios, from standalone to enterprise-wide server-
based configurations. Atoll has become the industry standard for radio network planning and optimisation.
If you are interested in learning more about Atoll, please contact your Forsk representative to inquire about our
training solutions.
About Forsk
Forsk is an independent software company providing operators and vendors with wireless network design and
optimisation products. Atoll, Forsk’s flagship product, is the market-leading wireless network planning and
optimisation software on the market; it allows operators to streamline planning and optimisation activities by
combining predictions and live network data.
With more than 9000 active licenses installed with 500+ customers in 140 countries, Atoll has become the industry
standard for wireless network design and optimisation.
Forsk distributes and supports Atoll directly from offices and technical support centres in France, USA, and China
as well as through a worldwide network of distributors and partners.

Introduction
Getting Help
The online help system that is installed with Atoll is designed to give you quick access to the information you need
to use the product effectively. It contains the same material as the Atoll 3.4.0 User Manual.
You can browse the online help from the Contents view, the Index view, or you can use the built-in Search feature.
You can also download manuals from the Forsk web site at:
http://downloads.forsk.com
Printing Help Topics
You can print individual topics or chapters from the online help.
To print help topics or chapters:
1. In Atoll, click Help > Help Topics.
2. In the Contents tab, expand the table of contents.
3. Right-click the section or topic that you want to print and click Print. The Print Topics dialog box appears.
4. In the Print Topics dialog box, select what you want to print:
 If you want to print a single topic, select Print the selected topic.
 If you want to print an entire section, including all topics and sections in that section, select Print the
selected heading and all subtopics.
5. Click OK.
About Atoll Documentation
The following PDF manuals are available to customers with a valid maintenance contract for Atoll and Atoll
Microwave and can be downloaded from the Forsk web site at:
http://downloads.forsk.com/
To read PDF manuals, download Adobe Reader from the Adobe web site at:
http://get.adobe.com/reader/
Hardcopy manuals are also available. For more information, contact to your Forsk representative.
Contacting Technical Support
Forsk provides global technical support for its products and services. To contact the Forsk support team, visit the
Forsk web site at:
http://downloads.forsk.com
Alternatively, depending on your geographic location, contact one of the following support teams:
Forsk US
For North and Central America, contact the Forsk US support team:
 Tel.: 1-888-GO-ATOLL (1-888-462-8655)
 Fax: 1-312-674-4822
 Email: support_us@forsk.com
Opening Hours: Monday to Friday 8.00 am to 8.00 pm (Eastern Standard Time)

AT340_AM_E3 Introduction
Forsk China
For Asia (except Japan), contact the Forsk China support team:
 Tel: +86 20 8557 0016
 Fax: +86 20 8553 8285
 Email: atollsupport@forsk.com.cn
Opening Hours: Monday to Friday 9.00am to 5.30pm (GMT+08:00) Beijing, Chongqing, Hong Kong, Urumqi.
Forsk Head Office

For all other regions, contact the Forsk Head Office support team:
 Tel.: +33 562 747 225
 Fax: +33 562 747 211
 Email: support@forsk.com
Opening Hours: Monday to Friday 9.00 am to 6.00 pm (GMT +1:00)

Introduction

AT340_AM_E3 Chapter 1: Getting Started
1 Getting Started
Atoll is an open, scalable, and flexible multi-technology network design and optimisation platform that supports
wireless operators throughout the network life cycle, from initial design to densification and optimisation.
Atoll supports a wide range of implementation scenarios from single-user standalone to enterprise-wide server-
based configurations using distributed and multi-threaded computing.
This manual explains how to install, configure, and deploy Atoll and how to set up back-end databases and manage
users in a multi-user environment. In this chapter, the following are explained:
This chapter covers the following topics:
◼ "Supported Technologies" on page 15
◼ "Supported Operating Systems" on page 15
◼ "Supported Database Management Systems" on page 16
◼ "Recommended Hardware and Software" on page 16
1.1 Supported Technologies

Atoll supports the following radio technologies:
◼ GSM/GPRS/EDGE
◼ UMTS HSPA
◼ CDMA2000 1xRTT/1xEV-DO
◼ TD-SCDMA
◼ LTE with and without NB-IoT
◼ 5G NR
◼ WiMAX
◼ Backhaul networks
Atoll also supports combined 3GPP Multi-RAT (GSM + UMTS + LTE NB-IoT) and 3GPP2 Multi-RAT (CDMA2000 +
LTE NB-IoT) technologies.
1.2 Supported Operating Systems

Atoll supports the following versions of Microsoft Windows operating systems:
Supported Operating Systems for Atoll 64-bit

◼ Microsoft Windows 10 Professional and Enterprise (64-bit)
◼ Microsoft Windows 8 and 8.1 Professional and Enterprise (64-bit)
◼ Microsoft Windows 7 Professional, Enterprise, and Ultimate (64-bit)
◼ Microsoft Windows Server 2016
◼ Microsoft Windows Server 2012 R2

Chapter 1: Getting Started

◼ Microsoft Windows Server 2008 R2 SP1
 Among other Microsoft Windows components, Atoll 64-bit uses the 64-bit
Microsoft Access Database Engine, which is included in 64-bit Microsoft Office,
and is also available as a free redistributable Microsoft Windows component from
the Forsk support website.
◼ If the computer on which you wish to install and run Atoll 64-bit already has
the MSI edition of Microsoft Office installed, you must upgrade it to Microsoft
Office 64-bit (version 2010 SP1 or newer).
◼ If you do not have Microsoft Office installed or if you have the Click-To-Run
edition of Microsoft Office, you can download and install the Microsoft
Access Database Engine 64-bit redistributable (version 2010 SP1) needed by
Atoll 64-bit from the Forsk support website.
Note: Installing the MSI version of 64-bit Microsoft Office or the Microsoft Access
Database Engine requires uninstalling any 32-bit Microsoft Office components that
may be installed on the computer.
Supported Operating Systems for Atoll 32-bit

◼ Microsoft Windows 10 Professional and Enterprise (32-bit and 64-bit)
◼ Microsoft Windows 8 and 8.1 Professional and Enterprise (32-bit and 64-bit)
◼ Microsoft Windows 7 Professional, Enterprise, and Ultimate (32-bit and 64-bit)
◼ Microsoft Windows Server 2008 R2 SP1
1.3 Supported Database Management Systems

In a multi-user environment, databases allow several users to share data without the risk of data inconsistency. In
a multi-user environment, Atoll ATL documents are connected to a central database, where users store their work
on a common project.
Atoll supports the following RDBMS:
◼ Oracle 11g and 12c (client versions 11.2.0.4 or later).
◼ Microsoft SQL Server 2005, 2008, 2012, 2014, and 2017
◼ Microsoft Access 2003 and later
Some databases require a local client component to be installed on the computer. The following table shows where
the database must be installed:
Database Client Component
Microsoft Access Not needed

Microsoft SQL server Not needed
Oracle Oracle Client 64-bit
1.4 Recommended Hardware and Software

Depending on your requirements, Atoll can be installed in the following configurations:
◼ Single-user standalone: Atoll installed on each individual user computer with a fixed license key plugged in
each computer.

◼ Multi-user thick client: Atoll installed on each individual user computer on a network with a floating license
management server that allocates license tokens to Atoll sessions run by users on their computers.
◼ Multi-user thin client: Atoll installed on servers connected to user computers and a floating license
management server on a network. The floating license management server allocates license tokens to Atoll
sessions run by the users on the servers. The servers can be Citrix-based, where users run Atoll sessions on
the servers through the Citrix interface.
This section provides guidelines for dimensioning client computers and servers on your network for optimum
performance with Atoll. This section lists the recommended hardware and software for:
◼
◼ "Single-user Standalone Configuration" on page 17

◼ "Multi-user Thick Client Configuration" on page 17
◼ "Multi-user Thin Client Configuration" on page 18
◼ "Floating License Servers" on page 19
◼ "File Servers" on page 20
1.4.1 Single-user Standalone Configuration
In a single-user standalone configuration, the Atoll installation is local, i.e.:

◼ Atoll is installed and run directly on the user workstation and all the core software and drivers are provided
with the Atoll installer program.
◼ The following data is stored locally: coverage prediction files, geographic data, and user projects.
The user license is managed locally (fixed license):
◼ A USB port must be available on the user workstation to plug a fixed license key dongle.
Figure 1.1: : Single-user Standalone Configuration
The following table lists the required/recommended hardware and software in a single-user standalone Atoll
configuration:
Atoll Workstation
Processor Core i7 at 2.5+ GHz
RAM 8 GB or more
Storage 512 GB1 (SSD recommended)
Operating System Microsoft Windows2
1. Depends on size of locally stored data.

2. See "Supported Operating Systems" on page 15.
1.4.2 Multi-user Thick Client Configuration
In a multi-user thick client configuration, the Atoll installation is local, i.e.:

◼ Atoll is installed and run directly on user workstations and all the base software and drivers are provided with
Atoll.
◼ The following data is stored on user workstations: coverage prediction files, geographic data, and user
projects.
The user licenses are managed locally (fixed licenses) or from a server (floating licenses):
◼ A USB port must be available on the user workstation to plug a fixed license key dongle.
◼ The nethasp.ini file must be available on the workstation to provide information on accessing a floating
license server through the network.
A connection with the central database is required during synchronisation operations, to exchange between users.
If you are working with an Oracle database, you must install the relevant Oracle clients on the user computers.
Figure 1.2: : Multi-user Thick Client Configuration
The following tables list the required/recommended hardware and software in a multi-user thick client
configuration:
Atoll Workstation Atoll Database
Processor Core i7 at 2.5+ GHz Xeon E3/E5 family or equivalent
RAM 8 GB or more 8 GB or more
Storage 1
512 GB (SSD recommended) 2 x 128 GB (RAID 1) or more2
Operating System Microsoft Windows3 Oracle: Windows, UNIX, Linux, Solaris
SQL Server 2017: Microsoft Windows, Linux4
1. Depends on size of locally stored data.

2. Tablespace of around 400 MB per 10,000 transmitters.
4. Refer to the requirements of the database vendor.
1.4.3 Multi-user Thin Client Configuration
Users can work with Atoll installed on application servers through thin clients such as Remote Desktop or Citrix.
In a multi-user thin client configuration, the Atoll installation is centralised, i.e.:
◼ Atoll is accessed via a thin client interface
◼ Server resources are used to run Atoll and perform calculations
◼ The following data is stored on a file server: coverage prediction files, geographic data, and user projects.

An asynchronous connection is required with the central database for data exchange between users.
The user licenses are managed through the network and a limited bandwidth (300+ kbps per user) is required
between servers and client workstations for satisfactory performance.
If you are working with an Oracle database, you must install the relevant Oracle clients on the user computers.
Figure 1.3: : Multi-user Thin Client Configuration
The following tables list the required/recommended hardware and software in a multi-user thin client Atoll
configuration:
Atoll Application Server Atoll Database Server
Processor Xeon E5/E7 family Xeon E3/E5 family or equivalent

2 cores per user at 2.5 GHz or more 4 cores or vCPUs
RAM 4+ GB per user (min 8 GB) 8 GB or more
Storage 256 GB (SSD recommended) 2 x 128 GB (RAID 1) or more1
Operating System Microsoft Windows2 Oracle: Windows, UNIX, Linux, Solaris

SQL Server 2017: Microsoft Windows, Linux3
Connectivity Gigabit Ethernet or better Gigabit Ethernet or better
Thin Client Configura- Remote Desktop -

tion Citrix XenApp versions 7.5 to 7.15 LTSR
Virtualisation VMWare ESXi 4.x / 5.x / 6.x -
RDBMS - Oracle 11g, 12c

Microsoft SQL Server 2008, 2012, 2014, 2016
2017
1. Tablespace of around 400 MB per 10,000 transmitters.

3. Refer to the requirements of the database vendor.
1.4.4 Floating License Servers
The license management server:

◼ Must be accessible to all the user computers or servers on the network in order to provide license tokens for
Atoll sessions.

◼ Must have a steady and reliable network connection.

◼ Must have the HASP License Manager or the Sentinel LDK Runtime Environment installed and running.
◼ Must have an appropriate fixed or floating license key.
For more information on managing licenses, see the Atoll License Management Guide.
1.4.5 File Servers
File servers can store shared data, such as geographic data, path loss matrices, Atoll configuration and initialisation
files, and user projects. The required hard disk space must be determined from the file sizes of this data.
1 or 10 Gigabit Ethernet is recommended for connecting user computers, application servers, database servers, and
file servers.
In a multi-client or multi-server configuration, the use of a file server can significantly improve data management by
providing a central repository for shared files. In this case, a higher bandwidth is required between the client
applicationsuser workstations and the file server (1 Gbps or higher).
In a single-user or single-server configuration, storing shared data locally instead of using a file server can improve
response time and calculation performance.

AT340_AM_E3 Chapter 2: Atoll and Component Installation
2 Atoll and Component Installation

The following sections describe the installation procedures for Atoll and its components. You need administrator
rights for installing Atoll.
For information about licenses and installing license management tools, see the Atoll License Management Guide.
◼ "Installing Atoll Using the Setup Wizard" on page 21
◼ "Installing the Atoll C++ Development Kit" on page 22
◼ "Setup Command Line Parameters" on page 23
◼ "Installing and Uninstalling Add-ins" on page 24
◼ "Installing and Uninstalling Macros" on page 25
◼ "Atoll Command Line Parameters" on page 26
◼ "Troubleshooting and Other Information" on page 27
2.1 Installing Atoll Using the Setup Wizard

Before installing Naos:
◼ If you are working work with fixed licenses, you must unplug the key before the installation and wait for the
installation to finish before plugging it back in.
◼ If you are installing Atoll 64-bit, make sure that the 64-bit Microsoft Access Database Engine is already
installed on the computer. For more information, see "Supported Operating Systems" on page 15.
To install Atoll:
1. Log on to the computer using a local Administrator account.
2. Run the Atoll setup program with elevated privileges (right-click and select Run as Administrator).
The setup program uses a wizard interface, with a step-wise description of the installation. You can:
◼ Click Next to proceed to the next step,
◼ Click Back to go back and modify previously set options, or
◼ Click Cancel to cancel the installation.
3. Click Next. The Select Destination Location dialog box appears.
4. Select the destination folder for the installation. The default installation folder is:
◼ "C:\Program Files\Forsk\Atoll", or
◼ "C:\Program Files (x86)\Forsk\Atoll" if you are installing a 32-bit version of Atoll on a 64-bit operating
system.
You can select a different location by clicking Browse.
5. Select Create a system restore point if you want to create a system restore point.
6. Click Next. The Select Components dialog box appears.
7. Select the components to install.
◼ Full installation: Atoll and all its components will be installed.
◼ Compact installation: Only Atoll will be installed.
◼ Custom installation: Atoll and the selected components will be installed.

Chapter 2: Atoll and Component Installation
8. Click Next.
If you selected the Distributed Calculation Server component for installation, the Logon Information dialog
box appears.
If you did not select this component, the Select Start Menu Folder dialog box appears. In which case, proceed
to step 8.
a. Enter the Domain name, Username, and Password.
This information will be used to run the distributed calculation service on the computer, and allow other
users of the domain to access this service.
b. Click Next. The Select Start Menu Folder dialog box appears
9. Click Next. The Ready to Install dialog box appears.
10.Review the installation parameters.
11.Click Install. Atoll and its selected components are installed on the computer.
If the following files do not already exist in the installation folder, default ones are created by the setup:
Path and filename
<Atoll installation folder>\Atoll.ini
<Atoll installation folder>\ACP.ini
<Atoll installation folder>\AntennaImport.ini
<Atoll installation folder>\CWMeasurementsImport.ini
<Atoll installation folder>\DriveTestDataImport.ini
<Atoll installation folder>\coordsystems\KpiImport.cfg
<Atoll installation folder>\coordsystems\UETraceConnection.cfg

<Atoll installation folder>\coordsystems\Favourites.cs
These files are not removed when Atoll is uninstalled.

If you work with fixed licenses and you installed the Driver for Fixed Licence Keys, restart the computer.
Restarting the computer is necessary for the driver to work.
If you work with fixed licenses, plug in the fixed license key.
 If you have installed Atoll on a Citrix server, you must publish the application to
make it accessible to users.
2.2 Installing the Atoll C++ Development Kit

The Atoll C++ Development Kit contains tools and documentation that provides access the Atoll API. This allows
software developers to write applications that integrate with the Atoll platform.
Before installing the Atoll C++ Development Kit:
◼ The development environment and Atoll must be installed before the Atoll C++ Development Kit. The following
development environments are supported:
◼ Visual Studio 2017 or later
◼ Visual Studio Code
◼ Python 2.7 or later or 3.6 or later.
To install the Atoll C++ Development Kit:
1. Log on to the computer using a local Administrator account.
2. Run the Atoll C++ Development Kit setup with elevated privileges (right-click and select Run as Administrator).
The setup program uses a wizard interface, with a step-wise description of the installation. You can,

◼ Click Next to proceed to the next step,

◼ Click Back to go back and modify previously set options, or
◼ Click Cancel to cancel the installation.
3. Click Next. The Select Destination Location dialog box appears.
4. Select the destination folder for the installation. The default installation folder is:
◼ "C:\Program Files\Forsk\Atoll", or
◼ "C:\Program Files (x86)\Forsk\Atoll" if you are installing a 32-bit version of Atoll on a 64-bit operating
system.
You can select a different location by clicking Browse.
5. Select Create a system restore point if you want to create a system restore point.
6. Click Next. The Ready to Install dialog box appears.
7. Review the installation parameters.
8. Click Install. The Atoll C++ Development Kit is installed on the computer.
 The Atoll Developer Reference Guide can be downloaded separately from the Forsk
support web site.
2.3 Setup Command Line Parameters

You can also install Atoll and its components from the command line. The Atoll setup program accepts optional
command line parameters, which can be useful to administrators, and to other programs calling the setup program.
For example, when automating the installation through batch files.
The following command line parameters are accepted by the Atoll setup program.
◼ /SILENT, /VERYSILENT
Instructs the setup to be silent or very silent. When the setup is silent the wizard window is not displayed but
the installation progress window is. When a setup is very silent the installation progress window is not
displayed. Everything else is normal. So, for example, error messages during installation are displayed, and
also the startup prompt.
If the setup is silent and it requires to restart the computer, but the /NORESTART option is not used (see
below), it will display a Reboot now? message box. If it is very silent it will reboot without asking.
◼ /NOCANCEL
Prevents the user from cancelling the installation by disabling the Cancel button and ignoring clicks on the
Close button. Useful along with /SILENT or /VERYSILENT.
◼ /NORESTART
Instructs the setup not to restart the computer even if necessary.
◼ /SAVEINF="file name"
Instructs the setup to save installation settings to the specified file. Use quotes if the file name contains
spaces.
◼ /LOADINF="file name"
Instructs the setup to load the settings from the specified file after having checked the command line. This
file can be prepared using the /SAVEINF command as explained above. Use quotes if the file name contains
spaces.
◼ /DIR="x:\folder name"
Overrides the default installation folder displayed on the Select Destination Location wizard page. Use quotes
if the folder name contains spaces.
◼ /GROUP="folder name"

Overrides the default start menu folder name displayed on the Select Start Menu Folder wizard page. Use
quotes if the folder name contains spaces.
◼ /LOG="file name"
Causes the setup to create a log file listing file installation and actions taken during the installation process.
This can be helpful for troubleshooting. For example, if you suspect a file is not being installed as it should be,
the log file will tell you if the file was actually skipped and why. Use quotes if the filename contains spaces. If
the file cannot be created, the setup will abort with an error message.
◼ /SVRACCOUNT="domainname\username"
The domain name and user name for installing the distributed calculation server.
◼ /SVRPASSWD=password
Password for installing the distributed calculation server.
◼ /TYPE=type name
Overrides the default setup type. The setup type names are:
◼ Full installation: full
◼ Compact installation: compact
◼ Custom installation: custom
For full and compact setup types, the /COMPONENTS parameters are ignored.
◼ /COMPONENTS="comma separated list of component names"
Overrides the default component settings. Using this command line parameter causes the setup to
automatically select a custom installation type. Only the specified components will be selected. Component
names are:
◼ Atoll: Atoll
◼ Export to Google Earth add-in: "Addins\GoogleEarth"
◼ Driver for fixed license keys: RainbowDongle
◼ Distributed calculation server: Atoll_Server
◼ Atoll Management Console: AMC
◼ C++ development kit: DevKit
Example: To install Atoll, the distributed calculation server, and the driver for fixed license keys:
/COMPONENTS="Atoll,Atoll_Server,RainbowDongle"
◼ /skipACEcheck
By default, the installer checks that all ACE components are installed. In some cases, this verification
produces an error even though the components are properly installed. You can use this option to skip the
verification and proceed with the installation.
2.4 Installing and Uninstalling Add-ins

The add-ins developed by Forsk have dedicated setup programs which are described in their own documentation.
Installed add-ins are automatically loaded by Atoll and appear in the Add-ins and Macros dialog box. If you wish that
a certain add-in not be loaded, and hence be unavailable for activation in this dialog box, you can do so by adding
an option in the Atoll.ini file. For more information, see "Loading, Activating, and Setting Add-ins as Visible" on
page 165.
To activate or deactivate an installed add-in in Atoll:
1. In Atoll, select Tools > Add-ins and Macros. The Add-ins and Macros dialog box appears.
2. Select the add-in’s check box to activate it, or clear the check box to deactivate it.
Add-ins installed by the Atoll setup are uninstalled when Atoll is uninstalled.

Available Add-ins
The following Atoll add-ins can be downloaded in their most recent version from the Forsk web site at:
http://www.forsk.com/support. For more information, contact to your Forsk representative.
◼ General add-ins:
◼ Export to Google Earth (installed with Atoll)
◼ Multistorey Prediction
◼ Easy Location Converter
◼ ArcView Grid ASCII Import
◼ Multi-RAT Converter
◼ Difference Plot
◼ Update Sites With Geo Data
◼ FCC Boundaries
◼ Incidence Angle Footprint
◼ Database add-ins:
◼ History Module
◼ Scenario Manager
◼ Geo Selector
2.5 Installing and Uninstalling Macros

Atoll can load and execute macros written in VBScript.
To load a macro in Atoll:
2. Click Add. The Open dialog box appears.
3. Navigate to the location where the macro you want to load is stored and select it.
4. Click Open. The New Script dialog box appears.
Figure 2.1: : New Script dialog box for Macros
5. Specify the script settings:

◼ Timeout: This is delay after which an unresponsive macro is stopped. To disable the macro timeout, set it
to 0. If you leave the timeout empty, a value of 24 days is used. The default value is 60 seconds.
◼ UTF-8 Encoding: Select this option if the macro file contains non-ASCII characters (for example: "°" or "μ").
6. Click OK. The loaded macro appears under Macros in the Add-ins and Macros dialog box.
To run a macro in Atoll:
2. Under Macros, expand the folder containing the macro you want to run.
3. Select the macro you want to run. The Run button becomes active.
4. Click the Run button.

Lists of macros available in Atoll can be stored in user configuration files. Macros listed in the user configuration
files are added to Atoll when the user configuration files are loaded. For more information, refer to "Contents of User
Configuration Files" on page 114.
To remove a macro from Atoll:
2. In the list of VBS files, select the one corresponding to the macro you want to remove.
3. Click Delete.
Other commands available in the Add-ins and Macros dialog box are:
◼ Edit: Edit the selected macro in the default text editor.
◼ Icon: Assign an icon to the selected macro. Icons assigned to macros appear in the Macros toolbar.
◼ Refresh: To reload the selected macro file.
Available Macros and Scripts

The following Atoll macros and scripts can be downloaded from the Forsk web site at http://www.forsk.com/
support.
For more information, contact to your Forsk representative.
◼ Macros:
◼ Predictions Slideshow
◼ Display Site Picture and Antenna Documentation
◼ Show Hide Repeaters and Remote Antennas
◼ Save Part of Document
◼ GSM to UMTS
◼ GSM to LTE
◼ UMTS to LTE
◼ CDMA2000 to LTE
◼ Show in Google Maps Street View
◼ Scripts:
◼ Update Pathloss Matrices
◼ Radio Data Import-Export
◼ Propagation Models Import-Export
◼ CW Measurements Import-Export
◼ Test Mobile Data Import-Export
2.6 Atoll Command Line Parameters

Atoll supports the following optional command line parameters:
Atoll.exe [-log "logfilename"] [-Ini "inifilename"] [-Cfg "cfgfilename"]

[-Provider providername -UserId username -Password password
-DataSource server -Project projectaccount]
◼ -log "logfilename"
Instructs Atoll to create a log file containing all the messages listed in the Events tab. This can be helpful for
troubleshooting. "logfilename" is the full path and file name of the log file inside quotes.
◼ -Ini "inifilename"
Instructs Atoll to load the specified initialisation file when run. This can be used to override the default loading
of the Atoll.ini file located in the Atoll installation folder. "inifilename" is the full path and file name of the
initialisation file inside quotes.

◼ -Cfg "cfgfilename"
Instructs Atoll to load the specified user configuration file when run. This can be used to override the default
loading of the Atoll.cfg file located in the Atoll installation folder. "cfgfilename" is the full path and file name
of the user configuration file inside quotes.
◼ -Stu "studiesfilename"
Instructs Atoll to load the specified studies XML file when run. This can be used to override the default loading
of the studies XML file located in "C:\Temp\studies.xml". "studiesfilename" is the full path and file name of the
studies XML file inside quotes.
◼ -Provider providername
Instructs Atoll to use the mentioned providername to access the database server:
Provider Atoll version providername
Microsoft Access 32-bit Microsoft.Jet.OLEDB.4.0

64-bit Microsoft.ACE.OLEDB.12.0
SQL Server 32/64-bit SQLOLEDB
Oracle (Oracle driver) 32/64-bit OraOLEDB.Oracle
◼ -DataSource server
Instructs Atoll to access the mentioned database server using the given provider.
◼ -UserId username
Instructs Atoll to access the mentioned Oracle database server using the mentioned username.
◼ -Password password
Instructs Atoll to access the mentioned Oracle database server using the mentioned password.
◼ -Project projectaccount
Instructs Atoll to access the mentioned Oracle database server using the mentioned projectaccount.
 The keywords Provider, Password, UserId, DataSource, and Project are case
sensitive.
2.7 Troubleshooting and Other Information

Read and follow carefully the instructions in "Installing Atoll Using the Setup Wizard" on page 21 for a smooth
installation.
If problems occur and you are unable to resolve them with the help of the following information, contact Forsk
support.
Microsoft Windows Updates

◼ It is recommended to install new Windows updates. However, it is also recommended to go through the
description of each update patch to see whether it might have a negative effect on your system or network.
Pay special attention to updates and patches related to networking.
◼ It is also recommended to keep the Windows updates uninstall folders, named "$NtUninstall...", under the
Windows folder, in case you have to uninstall a certain patch. Some of the update patches might require
uninstall folders of older patches to be available for their own installation.
Fixed license keys

◼ Fixed license keys cannot be used with "Server"-type operating systems. Therefore, you should not install the
driver for fixed license keys on:
◼ Microsoft Windows Server 2008 R2

◼ The current version of the driver for fixed license keys (Sentinel SuperPro driver) installed with Atoll is the
7.6.3.
◼ If Atoll is unable to access the fixed license key, even after a clean installation, try reinstalling the Sentinel
SuperPro driver manually. The driver’s setup program (SPI763.exe) is copied by the setup to the Sentinel
subfolder in the Atoll installation folder if you selected the Driver for Fixed Licence Keys component during
the installation. You can also download the driver from http://www.safenet-inc.com.
◼ Restart the computer when asked by the setup. Restarting the computer is necessary for the driver for fixed
license keys to work.
◼ If you get a protection key error message, verify that the fixed license key is correctly plugged in and that the
license has not expired.
◼ In case the fixed or the floating license key becomes unavailable, Atoll will ask the users currently accessing
the key to save their open documents before Atoll closes. If the key becomes available again, Atoll will let the
users continue working.
◼ Do not change the computer’s date.
Citrix
◼ If you have installed Atoll on a Citrix XenApp server, you must publish it to make it available to the users.
Atoll version and build

You can get information about Atoll by checking the application properties. To access the program properties, right-
click Atoll.exe in the Windows Explorer, select Properties from the context menu, and click the Details tab.
You can also get information about Atoll (version, build, type of license and remaining time before expiration, etc.)
by selecting Help > About Atoll in the main menu in Atoll.
Atoll file version and technology

ATL file properties store the Atoll version and build number in which the file was last saved, and the technologies
contained in the file. To access the ATL file properties, right-click the ATL file in the Windows Explorer, select
Properties from the context menu, and click the Details tab.
The Atoll version and build number in which the ATL file was last saved are stored in the Revision number property.
The technologies of the document are listed in the Category property.
Acknowledgement
◼ Atoll uses Inno Setup for installation. For more information, see http://www.jrsoftware.org/isinfo.php.
Uninstalling Atoll and its components

It is recommended to uninstall Atoll and its components through the Windows Control Panel.

AT340_AM_E3 Chapter 3: Distributed Calculation Servers
3 Distributed Calculation Servers

Distributed calculation enables you to distribute the calculation of path loss matrices over many computers in a
network. The distributed calculation service is an optional service that can be installed at the same time as Atoll.
For more information on installation, see "Atoll and Component Installation" on page 21.
A computer on which the distributed calculation service is installed and running is called a distributed calculation
server. This computer, the distributed calculation server, is visible to all the other computers on the network through
Atoll. You can set up as many distributed calculation servers as required.
The distributed calculation service does not have a user interface, and hence has lower memory requirements than
Atoll. The distributed calculation server uses the standard Atoll API to exchange data with the path loss calculator
and Atoll. The distributed calculation service supports dual-processor configurations and up to four threads.
Any version of Atoll can work with the distributed calculation service of the same or later version. Consequently, any
version of the distributed calculation service can work with the same or previous versions of Atoll (versions still
maintained by Forsk).
For distributed calculation server options available through the Atoll.ini file, see "Distributed Calculation Server
Options" on page 177.
◼ "Setting Up Calculation Servers" on page 29
◼ "Setting Up Atoll to Access the Calculation Servers" on page 31
◼ "Distributed Calculation Process" on page 31
3.1 Setting Up Calculation Servers

When installed, the distributed calculation service starts automatically and remains available as long as the
computer is turned on. The service does not require any active user session on the computer, i.e., the service keeps
running even when there is no user logged on. The service’s executable (AtollSvr.exe) is installed in the Atoll
installation folder.
The Atoll distributed calculation service is listed as Atoll Server in the Services management console under Control
Panel >Administrative Tools.
During calculations, the distributed calculation servers require access to geographic data for calculating the path
loss matrices. The distributed calculation service must be run with a user account that has sufficient privileges to
access the required data.
To modify the user account through which the distributed calculation service is run on a computer:
1. Log on to the computer with a user account with administrator rights.
2. Go to Control Panel > Administrative Tools > Services.
3. In the list of services, right-click the Atoll Server service. The context menu appears.
4. Select Properties. The Atoll Server Properties dialogue appears.

Chapter 3: Distributed Calculation Servers
Figure 3.1: : Atoll Server Properties
5. On the Log On tab, enter the user name and password for the user account through which you wish to run this
service.
6. Click OK.
3.1.1 Stopping and Starting the Distributed Calculation Server
To stop the distributed calculation service:

2. Go to Control Panel > Administrative Tools > Services.
3. In the list of services, right-click the Atoll Server service, and select Stop or Start from the context menu.
3.1.2 Running More Than One Distributed Calculation Service
By default, a single instance of the distributed calculation service is run. You can, however, run up to 9 additional
distributed calculation services (a total of 10 including the first one) manually. Each instance of the service can
calculate up to eight path loss matrices if the computer has eight processor cores available (one core per
calculation).
If the computer on which you are running the distributed calculation service has more than eight cores available, you
can use these cores for calculations by running more than one instance of the distributed calculation service. Atoll
can detect a total of 10 instances of the distributed calculation service. If you run more than 10 instances of the
distributed calculation service, they will not be detected by Atoll.
To run an additional instance of the distributed calculation service:
1. Run Command Prompt as administrator.
2. To create an instance of the service, type and run the following command:
sc create AtollCalcSvr1 binPath= "C:\Program Files\Forsk\Atoll\AtollSvr.exe"

start=auto DisplayName="Atoll DCS1" obj=<domain>\<account>
password=<password>
Where binPath should correspond to the location of the AtollSvr.exe file, DisplayName is the name of the
service as it will appear in the Windows list of services.

AT340_AM_E3 Chapter 3: Distributed Calculation Servers
3. To start the service created in step 2, type and run the following command:
net start AtollCalcSvr1
4. Repeat steps 2 and 3 for each new instance of the service that you want to run by replacing "AtollCalcSvr1"
and "Atoll DCS1" by "AtollCalcSvr2" and "Atoll DCS2", respectively, and so on.
You can verify that the new service instances appear in the list of services through Control Panel > Administrative
Tools > Services.
You can also run additional instances of the distributed calculation service by double-click the AtollSvr.exe file
located in the Atoll installation folder. For each new instance of the service, a command prompt window opens. To
stop an additional, manually run service, close the corresponding command prompt window.
3.1.3 Uninstalling the Distributed Calculation Server
To uninstall the distributed calculation service:

2. Stop the distributed calculation service:
a. Go to Control Panel > Administrative Tools > Services.
b. In the list of services, right-click the Atoll Server service, and select Stop from the context menu.
3. Unregister the service:
a. Select Start > Run. The Run dialogue appears.
b. Type "<Atoll Installation Path>\AtollSvr.exe /UnregServer". <Atoll Installation Path> is the path to the Atoll
installation folder.
c. Click Run.
This will remove the distributed calculation service from the computer.
3.2 Setting Up Atoll to Access the Calculation Servers

To activate distributed calculations in Atoll:
1. Select Tools > Distributed Calculations from the main menu. The Distributed Calculations dialogue appears.
2. Select the Activate distributed calculation check box.
a. To use all the available distributed calculation servers, click All.
b. To use selected distributed calculation servers only, click Detect.
Atoll searches for the available distributed calculation servers on the network. The available distributed
calculation servers are listed in the edit box.
c. Remove the distributed calculation servers that you do not wish to include.
3. Click OK. The selected distributed calculation servers are now available for path loss calculations.
3.3 Distributed Calculation Process

Once distributed calculations have been set up on the calculation server and on the user sides, the path loss
calculations run by the user are distributed over the available calculation servers. The calculation process is as
follows:
1. Atoll user runs path loss calculations.

Chapter 3: Distributed Calculation Servers
2. Atoll sends the needed network data to the available calculation servers.
3. Either Atoll sends the needed geographic data to the calculation servers or the servers access the geographic
data on a file server.
4. Distributed calculation servers calculate the path loss matrices one by one.
Distributed calculation servers that have spare threads start the calculations using these threads. If no thread
is available, the request is placed in a queue to wait for a thread to become available.
5. For each calculated path loss matrix, a confirmation is sent to the Atoll session. Any error or warning
messages generated are passed back to the Atoll session and displayed in the Event Viewer.
If an error occurs on any of the distributed calculation servers, Atoll transfers the calculations back to the local
computer. However, to avoid memory saturation, Atoll uses one thread on the local computer and calculates
the path loss matrices one by one. It does not attempt creating more than one thread.
6. In order to reduce the amount of data flow in the network, distributed calculation servers send the results
directly to the storage location (which can also be on a file server, not necessarily on the user’s computer that
requested the calculations).
7. Atoll user can then request the path loss matrices from the file server if they are needed for coverage
predictions.

AT340_AM_E3 Chapter 4: Managing Databases
4 Managing Databases
In Atoll, you can work with standalone documents, i.e., documents without any back-end database, or with
documents connected to databases. Standalone documents are more portable, however a back-end database is
required when working in a multi-user environment. In multi-user environments, several users work on the same
project and a central data storage is necessary for keeping the data modifications made by a team of radio planning
and optimisation engineers.
Atoll enables you to create databases, upgrade them to newer versions, archive and refresh data with databases,
manage and resolve data conflicts, and create and work with multi-level databases.
A database server can store one or more databases. For example, a GSM, a UMTS, and a microwave links database
can be stored on the same database server using the same RDBMS (Oracle, for example).
◼ "Atoll Database Templates" on page 33
◼ "Customising Atoll Database Structures" on page 34
◼ "Atoll Management Console" on page 36
◼ "Creating New Databases" on page 38
◼ "Upgrading Existing Databases" on page 41
◼ "Working With Multi-level Databases Using Oracle" on page 45
◼ "Setting Database Access Privileges" on page 49
◼ "Managing Data Modifications History" on page 50
4.1 Atoll Database Templates

All the radio technology modules available in Atoll (GSM, UMTS, LTE, CDMA2000, LTE, NB-IoT, 5G NR, TD-SCDMA,
WiMAX, Wi-Fi, LPWA, and Microwave Radio Links) are based on database templates. These templates are used for
creating Atoll documents with the appropriate data structure required for planning for any technology. Databases
(using RDBMS) can then be created from any Atoll document. These databases are hence also based on the data
structure defined by the Atoll database templates.
In each new major release, database templates undergo modifications required to support new features. These
modifications are applied to existing Atoll documents and databases by Atoll and the Atoll Management Console,
respectively. It is also possible to upgrade an existing database manually, but due to the complex nature of the
upgrade process, it is highly recommended to use the Atoll Management Console for upgrading existing databases.
Each database template is an MS Access MDB file located in the templates folder in the Atoll installation folder. For
the list of tables and fields, and their relationships, in each database template, see the Data Structure Reference
Guide.
 Database template files must not be modified without consulting Forsk customer
support.
The following table lists the types of fields used in Atoll database templates, their sizes, and the equivalent field
types and sizes in different RDBMS:

Chapter 4: Managing Databases
Atoll Oracle Equivalent Microsoft SQL Server Equivalent Microsoft

Access Equiva-
Field Type Length Field Type Length Field Type Length lent
Float 4 FLOAT 32 real 4 Single
Double 8 FLOAT 64 float 8 Double
Integer 4 NUMBER 11 int 4 Long Integer
Short 2 NUMBER 6 tinyint 1 Integer
Boolean 2 NUMBER 1 bit 1 Yes/No
Text Variable1 VARCHAR2 Variable1 varchar Variable 1

Text1
Memo Variable VARCHAR2 2000 varchar 4000 Memo
Binary Variable CLOB2 > 2000 image 16 OLE Object
BLOB3 Variable
1.Lengths for these fields are specified in parentheses in the database structure tables.
2.Character large object
3.Binary large object
 If you export the contents of an Atoll document, already connected to a database,

to another RDBMS (for example, if you export a document connected to an Oracle
database to SQL Server), some field types will be converted according to the above
table. This conversion does not have any impact on the document in Atoll.
For more information on the Atoll Management Console and upgrading databases, see "Atoll Management Console"
on page 36 and "Upgrading Existing Databases" on page 41, respectively.
4.2 Customising Atoll Database Structures

Atoll database structures can be customised by:
◼ Adding custom fields to data tables,
◼ Setting user-defined default values for fields, and
◼ Setting user-defined choice lists for text fields.
Custom fields, as well as user-defined default values and choice lists for standard and custom fields, are stored in
the CustomFields table.
4.2.1 Adding Custom Fields to Data Tables
 Do not add custom fields to data tables in the default document templates. It is
recommended to add them in copies of the default templates so that the original
database structure remains intact.
If you add custom fields to a default template of your current Atoll version (n-1), and
forget to add the same in the template of the next version (n), the Atoll Management
Console of the next version (n) will consider that these fields were intentionally
removed by the administrator. It will delete such custom fields from the database
during upgrade.
Custom fields can be added to data tables at different stages keeping in mind that:

◼ Custom fields added directly to the Atoll database templates (MDB files), using Microsoft Access 2003, will
be available in all new Atoll documents created from that template. A new database created by exporting such
a document will also contain these custom fields.
◼ Custom fields added to an Atoll document through the Atoll user interface will not be automatically added to
the corresponding Atoll database template. However, a new database created by exporting such a document
will contain these custom fields. For more information on adding custom fields to Atoll documents through
the user interface, see the User Manual.
◼ Custom fields added to an Atoll database will be available in all new Atoll documents created from that
database.
After adding a custom field to a data table, you can perform an Install/Repair on the database to propagate the
changes. For more information, see "Updating Data Modifications History after a Data Structure Upgrade" on
page 51.
To add a custom field to a data table:
1. Add the custom field to the definition of the data table by defining its name, type, and size.
2. Add a corresponding record in the CustomFields table and enter values for each of the following fields:
User Interface
Field Description
Caption
TABLE_NAME Database name of the data table that contains the field
COLUMN_NAME Name Database name of the field
DEFAULT_VALUE Default value User-defined default value (optional)

CHOICE_LIST Choice list User-defined choice list for text fields (optional)
CAPTION Legend Caption of the field as it will appear in the user interface (optional but recommended)
GROUP_NAME Group Semicolon-separated list of the names of groups to which the field belongs (optional)
CHOICE_TYPE Restricted 1: Custom field only accepts values listed in the choice list
0: Custom field accepts values other that those listed in the choice list
DISPLAY_TYPE Read-only 1: Custom field is read-only in the user interface
0: Custom field is modifiable in the user interface
 Custom fields are for information only and are not taken into account in
calculations. You can find these fields on the Other Properties tab of an object’s
Properties dialog box.
4.2.2 Setting User-defined Default Values for Fields
You can set your own default values for standard as well as custom fields using the CustomFields table. User-
defined default values entered in the CustomFields table have precedence over the predefined default values.
To enter a user-defined default value for any field, add a new record in the CustomFields table and enter values for
each of the following fields:
User Interface
Field Description
Caption
TABLE_NAME Database name of the data table that contains the field
COLUMN_NAME Name Database name of the field
DEFAULT_VALUE Default value User-defined default value
 For floating point default values, make sure that all the users use the same decimal
symbol.

4.2.3 Setting User-defined Choice Lists for Text Fields
You can set your own choice lists for standard as well as custom text fields using the CustomFields table. User-
defined choice lists entered in the CustomFields table have precedence over the predefined choice lists.
To enter a user-defined choice list for any text field, add a new record in the CustomFields table and enter values for
each of the following fields:
User Interface
Field Description
Caption
TABLE_NAME Database name of the data table that contains the text field
COLUMN_NAME Name Database name of the text field
CHOICE_LIST Choice list Choice list items, one per line
For example, you can replace the default choice list available for the SUPPORT_INFO field in the Sites table with a
different list of options corresponding to the different types of towers and pylons that may exist in your network.
 You can enter one of the choice list items in the DEFAULT_VALUE in order to set a
default value for the text field.
For custom text fields, you can set the CHOICE_TYPE to 1 if you want the custom
text field to only accept values listed in the choice list. By default, CHOICE_TYPE is
considered to be 0 meaning that users are allowed to enter values other than those
defined in the choice list.
4.3 Atoll Management Console

The Atoll Management Console provides the database administrator the possibility of globally managing the
database with the easy-to-use step-by-step procedures which use wizard interfaces. The Atoll Management
Console lets you:
◼ Create databases (see "Creating New Databases" on page 38)
◼ Upgrade database structures from one major version to the next (see "Upgrading Existing Databases" on
page 41)
◼ Work with multi-level databases (see "Working With Multi-level Databases Using Oracle" on page 45)
◼ Manage data modifications history in databases (see "Managing Data Modifications History" on page 50)
◼ Manage user accounts and access rights (see "Managing User Accounts and Access Rights" on page 62)
The Atoll Management Console supports:
◼ Oracle
◼ Microsoft SQL Server
The Atoll Management Console can be installed with Atoll. For more information, see "Atoll and Component
Installation" on page 21.
You can run the Atoll Management Console from the Windows Start menu program group or by double-clicking the
AMC.msc file in the management subfolder of the Atoll installation folder. The Atoll Management Console runs
using the Microsoft Management Console environment.
When the Atoll Management Console is run for the first time, you must register your database server in order to have
the databases installed on the server to be available in the Atoll Management Console.
To register a database server:
1. Open the Atoll Management Console.
2. In the left pane, right-click Database under Administration Atoll. The context menu appears.
3. Select Register a New Server from the context menu. The Data Link Properties dialog box appears.

Figure 4.1: : Data Link Properties dialog box - Provider Tab
4. On the Provider tab, select the provider for your database server and click Next.
5. On the Connection tab, enter the server name, user name, and password required to access the database
server.
Figure 4.2: : Data Link Properties dialog box - Connection Tab
6. Click Test Connection to verify that the information you entered is correct. An information message should
appear to indicate that the "Test connection succeeded" .
7. Click OK. The selected database server is registered and available in the Atoll Management Console. You now
have access to the features offered by the Atoll Management Console.
Figure 4.3: : Atoll Management Console
The tree in the left pane lists the registered database servers. Registered database servers can be connected ( )
or disconnected ( ).
The right pane lists the databases available on the connected database server currently selected in the left pane.
The current user can be the owner of one of the listed databases; his name appears between parentheses in the title

bar after the name of the database owner. One Oracle user can create and own one database. Therefore, for each
new database, you must create a new Oracle user who will own the new database.
The following details are available for databases created or upgraded using the Atoll Management Console:
◼ Name: name of the database preceded by an icon which indicates whether the database corresponds:
◼ to the current version of Atoll ( ), or
◼ to a previous version of Atoll not yet upgraded to the current version of Atoll ( )
◼ Owner: name of the database owner.
◼ Version: most recent Atoll version to which the corresponding database was upgraded.
 Only the databases corresponding to the current and previous major releases of
Atoll are listed. The version is indicated if the database has been upgraded via the
AMC.
◼ The databases corresponding to other major releases of Atoll are not listed.
◼ If the database server does not contain any database corresponding to the
current/previous major release of Atoll, no database is listed.
◼ Type: database type (MASTER or PROJECT).

A master database can have one or more project databases created from and connected to it. For more
information on master and project databases, see "Working With Multi-level Databases Using Oracle" on
page 45.
◼ Network: technology of the network modelled by the database (3GPP or 3GPP2 in case of multi-RAT).
◼ Shared Pathloss Directory: path to the shared path loss folder.
To view details of a database:
1. In the right pane, right-click the database in the list. The context menu appears.
2. Select Properties. The database Properties dialog box appears.
3. The Properties dialog box contains two tabs:
◼ General: This tab displays the Name, Description, Owner, Type, and Version of the database.
◼ Statistics: This tab displays the number of records in each table of the database.
4.4 Creating New Databases

New databases can be created using the Atoll Management Console or by directly exporting a document to a
database from Atoll. In this section, the following are explained:
◼ "Creating a New Database Using the Atoll Management Console" on page 38
◼ "Creating a New Database Using Atoll" on page 40
4.4.1 Creating a New Database Using the Atoll Management Console
You can create new databases using the Atoll Management Console.
 You must have administrator rights to the database and to the server for creating
new databases.
To create a new database:

1. In the Atoll Management Console window, in the left pane, right-click the database server on which you want

to create a new database. The context menu appears.

2. Select New > Database. The New Database Wizard dialog box appears.
Figure 4.4: : New Database Wizard
3. Click Next. The Specify the database owner page appears.

4. Select Use the current connection if you want to create a new database using the current user, or select Create
a new user and enter a Name and Password to create a new user that will be owner of the new database.

If your password must contain special characters, for example, !, ?, etc., type the
password inside double quotation marks: "mypassword!" instead of mypassword!
5. Click Next. The Name the database and specify a network type page appears.
6. Enter a Name for the new database and select the Network type. The Network type can be one of the database
templates installed with Atoll.
 Atoll and the Atoll Management Console must have the same version. This means
that the Atoll Management Console can create databases based on the database
templates installed with Atoll of the same version.
7. Click Next. The Specify units and coordinate systems page appears.
8. Select a Transmission power unit and a Reception threshold unit.

9. Under Coordinate systems, select a Cartographic projection system and the System to be used in the
database.
10.Click Next. The Ready to create database page appears. This page provides a summary of the selected
parameters.
11.Click Execute. The Atoll Management Console creates the new database with the defined parameters on the
selected database server.
A database created using the Atoll Management Console contains an ATOLL_ADMIN table with the following
structure:
Field Type Description
NAME Text (50) The name of the database
DESCRIPTION Text (255) Description of the database
ATOLL_VERSION Text (10) The current version of Atoll
ATOLL_BUILD Integer Current build of Atoll
ATOLL_DBTYPE Text (10) Type of Atoll database (i.e., Master or Project)
ATOLL_TEMPLATE Text (50) Atoll database template used to create the database
DBSCHEMA Memo An image of the schema of the original database
Among other uses, the ATOLL_ADMIN table is used to speed up the database upgrade to the next version. This table
stores the data required by the Atoll Management Console for database upgrade.
Databases created with Atoll, instead of the Atoll Management Console, and databases that have never been
upgraded using the Atoll Management Console contain a smaller ATOLL_ADMIN table, with just the NAME,
ATOLL_VERSION, and ATOLL_BUILD fields. Upgrading such databases using the Atoll Management Console can
take a long time because the Atoll Management Console must search for the data required for the upgrade in the
whole database.
For more information on upgrading databases, see "Upgrading Existing Databases" on page 41.
All the tables in a database created using the Atoll Management Console (except the COORDSYS and UNITS tables)
contain a non-modifiable, integer DB_RECORD_ID field. This field is used to store the ID of every record in the table.
It is not added to Microsoft Access databases.
4.4.2 Creating a New Database Using Atoll
You can create new databases in all supported RDBMS using Atoll.
To create a new database:
1. Run Atoll.
2. Create a new Atoll document or open an existing one. The new database will be created from this document.
3. Select Document > Database > Export. The Export to a Database dialog box appears.
4. In the Export to a Database dialog box, select the database type in the Save as type list.
 By setting an option in the Atoll.ini file, you can instruct Atoll to always use a defined
database type (MS Access, SQL Server, or Oracle). In this case, the Export to a
Database dialog box will be skipped and the database-specific authentication
dialog box will appear immediately. For more information, see "Setting the Type of
Database Being Used" on page 184.
5. Depending on the selected database type, enter the user name and password of the database owner.
6. Click Save. Atoll asks whether you want to connect the document to the new database.
7. Click Yes or No. Atoll creates a new database based on the document.
A database created using Atoll contains an ATOLL_ADMIN table with the following structure:

NAME Text (50) The name of the database
ATOLL_VERSION Text (10) The current version of Atoll
ATOLL_BUILD Integer Current build of Atoll
 Before creating the database, make sure that you have defined the coordinate
systems and units in the source document.
Before creating the database, make sure that you have added any required custom
fields. Custom fields of the source document are created in the new database.
If you want to add a custom field to the data structure after you have created the
database, you will have to add it directly in the database and not through Atoll.
Custom fields added to a database are available to users connected to the
database when they create a new Atoll document from the database or refresh an
existing one.
4.5 Upgrading Existing Databases

In each new major release, data structure changes must be made in the database in order to support the new
features added in the version. The data structures of standalone Atoll documents, i.e., documents not connected to
any database are upgraded when they are opened in the new Atoll version. You can upgrade databases using the
Atoll Management Console.
 Do not skip a major version of Atoll. For example, if you are currently using Atoll
3.2.x, you should first upgrade the database to Atoll 3.3.x before upgrading to Atoll
3.4.x. Upgrading your database will be simpler if you do not skip a major version. If
you skip or have skipped an intermediate major version, you must upgrade your
database twice in order to make it compatible with the new version.
If you are upgrading a database which was neither created nor already upgraded (at
least once) using the Atoll Management Console, see "Upgrading Databases for the
First Time" on page 43 first.
To upgrade a database using the Atoll Management Console:

1. In the Atoll Management Console window, in the right pane, right-click the database that you want to upgrade.
The context menu appears.
+ For Oracle databases, you can select multiple databases by pressing CTRL. This
allows you to upgrade multiple databases in one pass. After the upgrade, a log
displays any errors encountered on each individual database.
2. Select Upgrade Database. The Database Upgrade Wizard dialog box appears with the current database
version and the version to which the database will be upgraded.
3. Click Next. The Name the database page appears.
4. Enter a Name and description for the database.
5. Click Next.
The Database Upgrade Wizard reads the database to determine the Atoll database template using which it
was created. If there is more than one template corresponding to the network, select the template to be used
for the upgrade and click Next.
The Atoll Management Console upgrades the database.

 If some of the tables in a database have been replaced by views, the Database
Upgrade Wizard asks to select the views to upgrade. Select the views that you want
the Atoll Management Console to upgrade and click Execute.
If, for example, the definition of a view is given by the condition:
Select Field1, Field2 from Table1 where (Condition1);
The wizard first upgrades the schema of Table1 and then upgrades the definition
of the view. The upgraded definition will take the newly added fields into account.
When you upgrade a 3GPP Multi-RAT database, the Atoll Management Console
adds any missing tables to the database. For example, a database created by
exporting a 3GPP Multi-RAT document containing only GSM contains only GSM
tables. When upgraded, the Atoll Management Console will add the UMTS and LTE
tables to the database as well.
Obsolete fields in the data structure are automatically deleted from the database by the Atoll Management Console
during the upgrade.
 If you use the Atoll Management Console’s history management tool, you must
repair the upgraded database in order to continue using this tool. For more
information, see "Managing Data Modifications History" on page 50.
Once the database has been upgraded to the new version,

1. Install the new Atoll versions for the end-users, and
2. Ask all the end-users to fully refresh data in their Atoll documents from the database.
When users open their existing documents in the new Atoll version, they are asked whether they want to
upgrade the documents’ data structures to the new version or to disconnect the documents from the
database. On selecting the upgrade option, Atoll upgrades the document data structures to make them
compatible with the new version.
 The data structure of an Atoll document not connected to any database is

automatically upgraded to the new Atoll version when the document is opened and
saved in the new version.
Once saved, it is not possible to open the document in an earlier Atoll version.
The data structure of an Atoll document connected to a database not yet upgraded
to the new version can be upgraded by:
◼ Either opening the document in the new Atoll version, disconnecting it from
the database, and saving it in the new version, or
◼ Upgrading the database to the new version and then opening and saving the
document in the new Atoll version.
Once disconnected from its database, it is not possible to reconnect the document
to any database.
Obsolete fields in the data structure of a document not connected to any database
are automatically deleted by Atoll when the document is saved in the new version.
If the database has been upgraded to the new version but an Atoll document
connected to the database has not yet been upgraded, it is possible to open the
document in the previous Atoll version as read-only. It is also not possible to
interact with the upgraded database (archive, refresh, etc., are not allowed). To
make the document write-accessible in the previous Atoll version, it must be
disconnected from the upgraded database.
It is possible to upgrade an existing database manually (not recommended) by adding and deleting tables and fields
as required by the new version. For information on manually upgrading a database, see "Upgrading Databases
Manually" on page 43.

4.5.1 Upgrading Databases for the First Time
If you want to upgrade a database which was neither created nor already upgraded (at least once) using the Atoll
Management Console, you must first upgrade the database to the same version as the current version of the
database. This is required so that the Atoll Management console adds the required information to the database to
make it upgradable to newer versions.
To upgrade the database:
1. Before installing the new version of Atoll, install the Atoll Management Console (if not already installed)
compatible with the existing version of Atoll.
2. Upgrade the database (as described in "Upgrading Existing Databases" on page 41) using the Atoll
Management Console to the existing version of Atoll.
The Atoll Management Console adds additional fields to the ATOLL_ADMIN table and DB_RECORD_ID fields
in all the tables, as described in "Creating a New Database Using the Atoll Management Console" on page 38.
Once the Atoll Management Console has performed the necessary modifications, you can upgrade the
database to the new Atoll version.
3. Install the new version of Atoll and the Atoll Management Console.
4. Upgrade the database (as described in "Upgrading Existing Databases" on page 41), using the new version of
the Atoll Management Console, to the new version of Atoll.
When a new version of the Atoll Management Console is installed, the setup overwrites the Windows registry key
that stores the information about the Admin.dll file, and the existing version of the Atoll Management Console can
no longer be used.
If you have already installed the new version of the Atoll Management Console, you will have to register the old
Admin.dll again, upgrade the database to the existing version, register the new Admin.dll, and upgrade the database
to the new version using the new Atoll Management Console.
 For the Atoll Management Console to be able to recognise obsolete or deleted

fields from database tables, it is imperative that the ATOLL_ADMIN table exist in
the database. This means that when upgrading a database for the first time using
the Atoll Management Console, the database administrator will have to remove the
obsolete fields manually. Once the Atoll Management Console has been used to
upgrade a database, it will be able to recognise obsolete or deleted fields in the
following upgrades.
4.5.2 Upgrading Databases Manually
Due to the complex nature of the database upgrade process, it is highly recommended to use the Atoll Management
Console for upgrading existing databases. You should only proceed with a manual upgrade of your database, as
described below, if and only if an automatic upgrade using the Atoll Management Console is not possible.
The following procedure is not recommended for customised Atoll databases and only suits very simple databases.
Parameters and settings (triggers, views, user privileges, custom fields, etc.) defined in advanced database
configurations are lost following the manual database upgrade.
1. In the previous version of Atoll, create a new document from the database.
2. In the new version of Atoll, open the document created in step 1. Atoll upgrades the document data structure
to make it compatible with the new version.
3. Using the upgraded document, create a new database as explained in "Creating a New Database Using Atoll"
on page 40.

 If you are upgrading your database using a script based on the data structure
modifications listed in the Data Structure Reference Guide, you must:
◼ Add the ATOLL_ADMIN table to the database. For more information on this
table, see "Creating a New Database Using the Atoll Management Console" on
page 38.
◼ For LTE databases, rename the smart antenna models and equipment as
follows:
◼ Delete existing smart antenna equipment ("Optimum Beamforming Smart
Antenna") from the SmartAntennas table.
◼ Delete existing smart antenna model ("Optimum Beamformer") from the
SmartAntennasModels table.
◼ Create a new smart antenna equipment ("Conventional Beamforming
Smart Antenna") in the SmartAntennas table. Set the smart antenna model
for this equipment to "Conventional Beamformer."
4.5.3 Adding a Technology in a Multi-RAT Database
A multi-RAT document can be based on multiple technologies in 3GPP and 3GPP2 documents. Provided such a
document has already been exported to a database, you can add a technology to the corresponding database
through the Atoll Management Console.
1. Start the Atoll Management Console.
2. When the Atoll Management Console opens, right-click on Database in the left pane. The context menu
appears.
3. Select Register a New Server. The Data Link Properties dialog box is displayed.
4. On the Provider tab, select an OLE DB provider and click Next.
5. On the Connection tab, specify a database in the Select or enter a database name field.
6. Click the Test Connection button. If the connection is successful, click OK to close the Data Link Properties
dialog box.
7. Upgrade the database if necessary, as explained in "Upgrading Existing Databases" on page 41.
8. In the right pane, right-click the database you want to upgrade with an additional technology and select Multi-
RAT: View/Add Technologies. The Technologies in the Multi-RAT Database dialog box appears.
Figure 4.5: : Example of technologies in 3GPP databases
9. Select the technology you want to add and click OK.
 You cannot deselect a technology already present in a multi-RAT database.
A new record is added to the networks table for each technology added to the database.

4.6 Working With Multi-level Databases Using Oracle

Atoll Management Console allows you to set up and work with multi-level databases using Oracle. In this optional
database architecture, the master database is not directly accessible to end-users. Groups of end-users work with
their respective project databases which are in turn connected to the master database. The end-users archive data
to and refresh data from their respective project databases, and the database administrator manages the
connections and data exchange between the project databases and the master database.
For example, you can have a country-wide master database and more than one regional project databases. End-
users can here work with their local region’s project database, and would not have to unnecessarily load country-
wide data.
Figure 4.6: : Working With a Single Level Database
Project databases are intermediate databases created from a common master database. A project database
contains the original master database, that remains hidden from the end-users, and an copy of the master database
accessible to the end-users. When a user modifies a record, only its accessible copy is modified in the project
database. The original value in the master database remains unchanged until the database administrator archives
all the modifications from the project databases to the master database.
Figure 4.7: : Working With Project Databases
Project databases can be used to improve performance and ensure data security and reliability. Instead allowing all
the end-users to work directly with the master database, one or many project databases can be created with copies
of the entire master database or a part of the master database corresponding to a given physical location or region.
Creating and working with project databases restricts the number of users who have access to the master
database. This reduces the risk of conflicts in the database as only the database administrator can archive
modifications from project databases to the master database.
For example, if a country-wide network database is accessible to all end-users:
◼ The probability of human error increases with the number of users who can modify data.
◼ The probability of conflicts increases with the number of users accessing the database.
◼ The performance is reduced because the entire network is loaded every time a user accesses the database.

◼ For routine city-wide planning, an end-user does not require the entire country’s database to be loaded.
Project databases can be created using filters on sites, thus allowing users to work with regional databases. A
possible scenario is depicted in the figure below:
Figure 4.8: : Multiple Project Databases From a Single Master Database
Multi-level databases can be set up using the Atoll Management Console. In this section, the following are
explained:
◼ "Creating Project Databases" on page 46
◼ "Archiving Project Databases to Master Databases" on page 48
◼ "Refreshing Project Databases from Master Databases" on page 48
4.6.1 Creating Project Databases
You can create project databases using the Atoll Management Console.
 For creating a project database, you must have enough rights to be able to create
new tables in the master database schema.
To create a project database from an existing master database:

1. In the Atoll Management Console window, in the right pane, right-click the master database from which you
want to create a project database. The context menu appears.
2. Select Create a Project Database. The Project Database Creation Wizard dialog box appears.
3. Click Next. The Specify the server and the owner of the project database page appears.
4. Select the Destination server for the project database.
5. Under Owner, select Current user if you want to create the new project database using the current user, or
select Create a new user and enter a User name and Password to create a new user that will be owner of the
new project database.
 Some versions of Oracle let you create a new user through this dialog box but the
new user is not assigned DBA rights, which makes the new user unable to create
the project database. Therefore, it is recommended to create the new user with DBA
rights directly in the database before create the project database using the Atoll
Management Console using the new user account.

6. Click Next. The Name the database page appears.

7. Enter a Name and Description for the new project database.
8. Click Next. The Specify the sites to include in the project database page appears.
9. On this page, choose from one of the following options:
◼ Include all the sites of the master database
Select this option if you want to create a project database that contains all the data of the master database.
◼ Include a site list contained in the master database
Select this option if you want to create a project database containing the network data corresponding to
the sites included in a site list of the master database, and select a site list. This option is only available
when at least one site list exists in the master database.
◼ Select the sites to include using an SQL condition
Select this option if you want to create a project database containing the network data corresponding to
the sites that verify an SQL condition (for example, sites that have a common parameter or flag), and enter
the SQL condition.
10.Click Next. The Atoll Management Console creates the new project database with the defined parameters on
the selected database server.
The project database will have the type PROJECT listed in the Atoll Management Console window.
A project database created using the Atoll Management Console contains an ATOLL_ADMIN_PRJ table, in addition
to the ATOLL_ADMIN table, with the following structure:
NAME Text (50) The name of the project database

MASTER_CONNECTION Text (255) Connection parameters to the master database
MASTER_DBSCHEMA Text (50) The name of the original schema of the master database.
Oracle databases do not support the dot (".") character in schema names.
SEL_METHOD Short Data extraction method used to select the sites to include in the project database
SEL_PARAM Text (255) Site selection method parameters (the SQL condition, if any)
SEL_PGON Memo Site selection polygon (if used)
You can view the details stored in the ATOLL_ADMIN_PRJ table in the project database properties. To view the
above details of a project database:
1. In the right pane, right-click the project database in the list. The context menu appears.
2. Select Properties. The database Properties dialog box appears.
3. The Properties dialog box contains three tabs:
◼ General tab: The General tab displays the Name, Description, Owner, Type, and Version of the database.
◼ Project Database tab: Under Source master database, the Project Database tab displays the Connection
settings to and the Owner of the master database. Under Site selection, this tab displays the site filtering
Method and Settings used for creating the project database.
◼ Statistics tab: The Statistics tab displays the number of records in each table of the project database.
The project database contains a copy of all the original tables of the master database. The names of the original
tables are prefixed with "O_". For example, the ANTENNAS table of the master database is stored in the project
database under the name O_ANTENNAS. The COORDSYS and UNITS are not copied to the project database
because their contents cannot be different from those of the master database.
All the tables in a project database contain a non-modifiable, integer O_RECORD_ID field and a Boolean O_CHANGED
field. The O_RECORD_ID field is used to locate records in the master database. Modified records are archived in
master database using the O_RECORD_ID of the project database and DB_RECORD_ID of the master database. The
O_CHANGED field is set to TRUE for records modified in the project database.

4.6.2 Archiving Project Databases to Master Databases
Changes made in the project databases can be archived to the master database using the Atoll Management
Console. The Archive dialog box lets you select changes you want to archive.
Before archiving the database, check that the structure of the O_ tables are consistent with the main tables in the
project database.
To archive the changes from a project database to its master database:
1. In the Atoll Management Console window, in the right pane, right-click the project database from which you
want to archive changes to its master database. The context menu appears.
2. Select Archive. If pending changes exist, the Archive dialog box appears. The Archive dialog box lists the
records of the project database for which the O_CHANGED field is TRUE.
3. In the Archive dialog box, you can do the following:
◼ Select a site list in Filter by site list to filter the pending changes by a site list.
◼ Click Archive All to archive all the changes to the master database.
◼ Select the check boxes to the left of the changes that you want to archive and click Archive Sel. to archive
only the selected changes.
◼ Click Undo All to overwrite all the changes in the project database with data from the master database.
◼ Select the check boxes to the left of the changes that you want to undo and click Undo Sel. to overwrite
only the selected changes in the project database with data from the master database.
◼ Select the Check conflicts check box to see whether conflicts occurred during the archive.
A conflict occurs when the project database contains a different original value of a field than the current
value of the field in the master database. This can occur if the master database has been updated with
changes from another source and the project database has not yet been refreshed with data from the
master database.
Figure 4.9: : Archiving Changes in Master Databases
Under Errors, Atoll Management Console displays errors that occurred during archive.
4. Once archive is complete, click Close.
4.6.3 Refreshing Project Databases from Master Databases
Project databases can be refreshed with data from the master database using the Atoll Management Console.
To refresh a project database with data from its master database:
1. In the Atoll Management Console window, in the right pane, right-click the project database that you want to
refresh with data from its master database. The context menu appears.

2. Select Refresh. If pending changes exist, the Refresh a Project Database dialog box appears.
3. In the Refresh a Project Database dialog box, you can:
◼ Select Refresh unmodified data only to keep any changes in the project database and only update
unmodified records from the master database. During the refresh, the Atoll Management Console will
reload records from the master database for which the O_CHANGED field is FALSE in the project database.
◼ Select Cancel your changes and reload all data from the master database to overwrite modified and
unmodified records in the project database with data from the master database.
1. Click OK. The project database is refreshed with data from the master database.
4.7 Setting Database Access Privileges

You can assign different levels of privileges to different users for accessing (reading/writing) tables and views of a
database. You can grant user privileges for Database, Table, Column, and Row levels keeping the following in mind:
◼ Database Level:
Users trying to create a new Atoll document from a database are provided a list of available databases to
select from. The list can be limited to a few databases based on the user connection properties (log in).
◼ Table Level:
For consistency reasons, all the tables available in an Atoll database must be readable by all the users who
have access to the database. However, write access (INSERT, DELETE, UPDATE) can be granted on a limited
number of tables.
◼ Column Level:
Similar to table level, all the columns of all the tables in an Atoll database must be readable and selectable by
all the users who have access to the database. Different write permissions can be granted for columns of the
tables. For example, custom fields can be assigned read and write permissions without restrictions.
◼ Row Level:
Row level permissions can be set by defining custom views on Atoll tables. Access to these views can be
based on user connection properties (log in), on external table references, or on the geographic locations of
sites (e.g., through polygons, or when using the spatial features of databases).
All of these permissions can be set as regular SELECT, INSERT, UPDATE, and DELETE privileges on database
objects. Triggers can also be used to prevent users making certain actions on the database.
Different permissions for different users can be granted directly or through database roles. Database roles enable
you to define permission templates, which can then be assigned to existing or new users of the database.
You can use the Atoll Management Console for defining user access rights to database tables and elements in the
Atoll GUI. For more information on managing user access rights, see "Managing User Accounts and Access Rights"
on page 62.

4.8 Managing Data Modifications History

The Atoll Management Console allows you to keep and manage the history of modifications made in the network
data by different users. The history management tool keeps track of all the modifications made in the following Atoll
tables:
Technologies Tracked Tables
GSM GPRS EDGE Sites, Transmitters, TRGs, TRXs, Repeaters, SecondaryAntennas, Neighbours, Neigh-
boursExt
UMTS HSPA Sites, Transmitters, CDMACells, Repeaters, SecondaryAntennas, Neighbours, Neigh-

boursExt
CDMA2000 1xRTT 1xEV-DO Sites, Transmitters, CDMACells, Repeaters, SecondaryAntennas, Neighbours, Neigh-
boursExt
LTE Sites, Transmitters, T4GCells, Repeaters, SecondaryAntennas, Neighbours, Neighbour-

sExt
WiMAX/Wi-Fi Sites, Transmitters, WCells, Repeaters, SecondaryAntennas, Neighbours, NeighboursExt
5G Multi-RAT sites, xgtransmitters, utransmitters, gtransmitters, ctransmitters, xgcells5gnr, xgcellslte,

xgcellsnbiot, ucells, ccells, gtrgs, gtrxs, xgrepeaters, urepeaters, grepeaters, crepeaters,
xgsecondaryantennas, usecondaryantennas, gsecondaryantennas, csecondaryanten-
nas, xgneighbours, xggneighbours, xguneighbours, xgcneighbours, gxgneighbours,
uxgneighbours, cxgneighbours, uneighbours, gneighbours, cneighbours, guneighbours,
ugneighbours
3GPP sites, ltransmitters, utransmitters, gtransmitters, lcells, ucells, gtrgs, gtrxs, lrepeaters,
urepeaters, grepeaters, lsecondaryantennas, usecondaryantennas, gsecondaryanten-
nas, lneighbours, uneighbours, gneighbours, lneighext, uneighext, gneighext, guneigh-
bours, ugneighbours, glneighbours, lgneighbours, ulneighbours, luneighbours
3GPP2 sites, ltransmitters, ctransmitters, lcells, ccells, lrepeaters, crepeaters, lsecondaryanten-

nas, csecondaryantennas, lneighbours, cneighbours, lneighext, cneighext, lcneighbours,
clneighbours
Microwave Radio Links/Backhaul Sites, MWLinks, MWHubs, MWPmp, MWMultiHops, MWMultiHopsLinks, MWRepeaters,
MWOTLinks, MWPorts, BHNodes, BHSegments, BHSegmentsMedia
You can, however, enable or disable history management for table as required (see "Enabling/Disabling Data
Modifications History Management" on page 51 for more information). You can also purge old data modifications
history (see "Purging Old Data Modification Records" on page 52 for more information).
The history management tool is available for Oracle and SQL Server databases. The following section describes
how to set up the history management tool using the Atoll Management Console.
4.8.1 Setting Up Data Modifications History Management
When you set up history management for any database, the Atoll Management Console adds new tables to the
database structure. For each tracked table, it adds a corresponding history table that has the same name as the
tracked table with the suffix "_H". Each history table has the same structure as the corresponding tracked table, but
with the following four additional fields. These fields enable the Atoll Management Console to store the
modifications made by users to each tracked table:

HISTORY_ID Integer A unique ID of the modification history record
MODIFIED_BY Text (50) The user who made the modification
MODIFIED_DATE Date The date when the modification was made

HISTORY_STATUS Text (10) Status of the modification history record
The above fields are also added to all the tracked tables in order to store information about the latest modification.
Therefore, opening any tracked table, you can see when a record was last modified, by whom, and the type of
modification.

To set up data modifications history management for a database:

1. In the right pane of the Atoll Management Console window, right-click the database for which you want to set
up data modifications history management and select Manage Data Modifications History from the context
menu. The Data Modifications History Management dialog box appears.
2. Click Yes when asked whether you want to make your database compatible with the data modifications
history tool.
The Atoll Management Console updates the database structure to make it compatible with the data
modifications history tool. Data modifications history is enabled for the database.
Once finished, the Data Modifications History Management dialog box appears (see Figure 4.10 on page 52).
This dialog box lists all the tables for which the data modifications history management has been enabled, the
total numbers of records in these tables, and the status of the history management.
All the modifications made in the tables listed in "Managing Data Modifications History" on page 50 are stored in
the history tables added to the database.
If you want, you can disable the data modifications history management for any table. For more information, see
"Enabling/Disabling Data Modifications History Management" on page 51.
4.8.2 Enabling/Disabling Data Modifications History Management
You can enable or disable data modifications history management for any table. You can enable or disable history
management for each individual table. When history management is enabled for a table, the MODIFIED_BY,
MODIFIED_DATE, and HISTORY_STATUS fields are updated with each modification, and a copy of each modification
is stored in the history table corresponding to the table. When history management is disabled for a table, the
MODIFIED_BY, MODIFIED_DATE, and HISTORY_STATUS fields are still updated with each modification, but the
history of modifications is not stored in the corresponding history table.
To enable data modifications history management for a table:
1. In the Atoll Management Console window, in the right pane, right-click the database for which you want to
enable data modifications history management. The context menu appears.
2. Select Manage Data Modifications History. The Data Modifications History Management dialog box appears.
3. In the Data Modifications History Management dialog box, right-click the table for which you want to enable
data modifications history management. The context menu appears.
4. Select Enable in the context menu.
Data modifications history management is now enabled for this table. The Status in the Data Modifications
History Management dialog box is set to OK for this table.
To disable data modifications history management for a table:
1. In the Atoll Management Console window, in the right pane, right-click the database for which you want to
disable data modifications history management. The context menu appears.
2. Select Manage Data Modifications History. The Data Modifications History Management dialog box appears.
3. In the Data Modifications History Management dialog box, right-click the table for which you want to enable
data modifications history management. The context menu appears.
4. Select Disable in the context menu.
History management is now disabled for this table. The Status in the Data Modifications History Management
dialog box is set to Deactivated for this table.
4.8.3 Updating Data Modifications History after a Data Structure Upgrade
When you modify the structure of a tracked database table (for which data modifications history management is
enabled), either automatically upgrading your database using the Atoll Management Console, or manually by adding
or removing fields, or by modifying a field type, the corresponding data modifications history management table
becomes invalid and has to be updated to match the new structure of the tracked table.

The Status column of the Data Modifications History Management dialog box shows an error for the tracked table
whose history management table does not match its structure.
To update the data modifications history management tables:
1. In the Atoll Management Console window, in the right pane, select one or several databases whose tables you
want to update. The context menu appears.
2. Right-click the selection and select Manage Data Modifications History. The Data Modifications History
Management dialog box appears.
3. In the Data Modifications History Management dialog box, right-click the table that you want to update. The
context menu appears.
4. Select Install/Repair in the context menu.
The Atoll Management Console repairs the data structure of the history management table to match the
structure of the corresponding tracked table.
4.8.4 Purging Old Data Modification Records
History management tables store the lists of all the modifications made by all the users. These tables can therefore
quickly become very large and require a lot of disk space. You can purge old data modifications history (records)
from these tables in order to gain disk space.
In this section, the following is explained:
◼ "Purging Old Data Modification Records of a Table" on page 52.
◼ "Purging Old Data Modification Records of a Database" on page 53.
4.8.4.1 Purging Old Data Modification Records of a Table

To purge old data modification records from a history management table:
1. In the Atoll Management Console window, in the right pane, right-click the database in which you want to purge
old data modifications history. The context menu appears.
2. In the context menu, select Manage Data Modifications History. The Data Modifications History Management
dialog box appears (see Figure 4.10 on page 52).
Figure 4.10: : Data Modifications History Management dialog box
3. In the Data Modifications History Management dialog box, right-click the table for which you want to purge
4. In the context menu, select Purge. The table record purge dialog box appears (see Figure 4.11 on page 53).

Figure 4.11: : Table Record Purge dialog box
5. Under Purge data modifications recorded before, move the slider to select from which date onwards you want
to keep the data modification history records.
All the data modification history records before this date will be deleted. The fields under Record Information
indicate the number of Records that will be left after the purge and the corresponding Size.
6. Under Options, select the Keep creation and deletion records check box if you want to keep the records
related to creation and deletion.
7. Click Purge. All the history records before the selected date are deleted from the history management table.
If you selected the Keep creation and deletion records check box, creation and deletion records before the
selected date are not deleted.
4.8.4.2 Purging Old Data Modification Records of a Database

To purge old data modification records from all the history management tables of a database:
1. In the Atoll Management Console window, in the right pane, right-click the database in which you want to purge
2. In the context menu, select Manage Data Modifications History. The Data Modifications History Management
dialog box appears (see Figure 4.10 on page 52).
3. In the Data Modifications History Management dialog box, click the Scheduler button. The database record
purge dialog box appears (see Figure 4.12 on page 54).

Figure 4.12: : Database Record Purge dialog box
4. Under Conditions, select the records to purge:

◼ None: select this option if you do not want data modification records to be purged.
◼ Keep only the last N records: if you select this option, enter the number of most recent records you want
to keep. All older records will be purged.
◼ Keep only records of N last months: if you select this option, enter the number of months prior to which all
records will be purged.
◼ Keep creation and deletion records: select this check box if you want to keep all the creation and deletion
records, independent of the above options.
5. If you wish to purge records now, click the Run now button.
6. If you wish to schedule regular purges, under Scheduling, define the purge frequency:
a. Period: Select the frequency of the scheduled regular purges.
b. Day: Select the day of the week (Monday to Sunday), month (1 to 28), or year (1 to 365), depending on the
purge periodicity defined in Period, on which the scheduled purges will run.
c. Time: Enter the time, i.e., the hour (0 to 23) and minutes (0 to 59) at which scheduled purges will run.
Scheduled regular purges will delete all the data modification records according to the criteria defined under
Conditions.
7. Set the Off/On slider to On to activate the scheduled purges.
Setting the Off/On slider to Off allows you to suspend scheduled purges while keeping the scheduler settings.
8. Click the Update button to store the schedule parameters.
The current purge status is shown under Status. Status information includes:
◼ Last execution: Time of execution of the last purge.
◼ Result: Whether the last purge was successful or not.
◼ Next execution: Time of execution of the next scheduled purge.
You can click the View logs under Status to view the history of past purges (see Figure 4.12 on page 54).
9. Click the Close button.
Scheduled regular purges are programmed as a scheduled job in Oracle using the DBMS_SCHEDULER.create_job
function. The following SQL string generates scheduled job:
"BEGIN DBMS_SCHEDULER.create_job ("

"job_name => 'AHMS_%s',"

"job_type => '%s',"
"job_action => '%s',"
"start_date => SYSTIMESTAMP,"
"repeat_interval => '%s',"
"end_date => NULL,"
"enabled => %s,"
"comments => '%s'); END;"
Here:
Parameter Description
job_name AHMS_<schema_name>
job_type PLSQL_BLOCK
job_action Actual PL-SQL code for the purge
start_date SYSTIMESTAMP
repeat_interval Frequency of the scheduled purge

For example, once a month, on the 15th, at 1:30am: "freq=month;monthday=15;byhour=1;byminute=30"
end_date NULL
enabled TRUE or FALSE, based on the user input
comments Custom character string with codes for easy identification of the scheduler type
4.9 Appendices
The first appendix shows how to use SQL for Oracle database customisation and the second appendix shows how
to set up databases for co-planning taking the example of GSM and UMTS MS Access databases.
4.9.1 Appendix 1: Advanced Customisation
You can use SQL in order to manage access to and share the Sites table (example 1), or to restrict the connection
to a set of transmitters for some users (example 2). To implement the following two examples, you must log on as
the owner of the tables through SQL Plus 8.
Example 1: Managing Site Sharing

Assumptions:
◼ Connection string = AtollDB
◼ GSM Project account = AtollADMINGSM, password = ADMINGSM
◼ UMTS Project account = AtollADMINUMTS, password = ADMINUMTS
◼ Common Project account = AtollADMIN, password = ADMIN
To share the Sites table:
1. Create the AtollADMIN.SITES table and copy all sites from AtollADMINGSM.SITES to AtollADMIN.SITES.
SQL > connect AtollADMIN/ADMIN@AtollDB;

SQL > create table AtollADMIN.SITES as select * from AtollADMINGSM.SITES;
SQL > create unique index AtollADMIN_SITES on AtollADMIN.SITES(NAME);
2. Replace the AtollADMINGSM.SITES table by an AtollADMINGSM.SITES view.

SQL > connect AtollADMINGSM/ADMINGSM@AtollDB;

SQL > drop table AtollADMINGSM.SITES;
SQL > grant delete on AtollADMIN.SITES to AtollADMINGSM with grant option;
SQL > grant insert on AtollADMIN.SITES to AtollADMINGSM with grant option;
SQL > grant select on AtollADMIN.SITES to AtollADMINGSM with grant option;
SQL > grant update on AtollADMIN.SITES to AtollADMINGSM with grant option;
SQL > create view AtollADMINGSM.SITES as select * from AtollADMIN.SITES;
3. Follow the same procedure for UMTS (AtollADMIN.SITES already created).
SQL > connect AtollADMINUMTS/ADMINUMTS@AtollDB;

SQL > drop table AtollADMINUMTS.SITES;
SQL > grant delete on AtollADMIN.SITES to AtollADMINUMTS with grant option;
SQL > grant insert on AtollADMIN.SITES to AtollADMINUMTS with grant option;
SQL > grant select on AtollADMIN.SITES to AtollADMINUMTS with grant option;
SQL > grant update on AtollADMIN.SITES to AtollADMINUMTS with grant option;
SQL > create view AtollADMINUMTS.SITES as select * from AtollADMIN.SITES;
4. Commit.
SQL > commit;
Example 2: Managing Users by Postal Code

To restrict access to transmitters for some users by postal code:
1. Add a ‘POSTCODE’ field to the SITES table.
SQL > alter table SITES add (POSTCODE number);
2. Rename the SITES table to be able to hide it by a view.
SQL > rename SITES to PRIVATE_SITES;
3. Create a POSTCODETABLE table to link users and postcodes (one user can be linked to several postcodes).
SQL > create table POSTCODETABLE (USERNAME varchar2(30), POSTCODE number);
You can fill this table using this instruction.
SQL > insert into POSTCODETABLE values (‘USER1’, 75);
4. Create a view owned by this user hiding the actual SITES table through these commands.
SQL > create view SITES as

select * from PRIVATE_SITES
where POSTCODE in
(select POSTCODE from POSTCODETABLE where USERNAME =USER)
with check option;
"with check option" is very important as it specifies that insert and update operations performed through the
view must result in rows that the view query can select.
5. Hide the TRANSMITTERS table, so that Atoll can only select transmitters whose associated sites are present
in the SITES view.
SQL > rename TRANSMITTERS to PRIVATE_TRANSMITTERS;

SQL > create view TRANSMITTERS as

select * from PRIVATE_TRANSMITTERS
where SITE_NAME in (select NAME from SITES);
6. Commit.
SQL > commit;
 The error message "ORA-01402: view WITH CHECK OPTION - clause violation"
appears if you try to archive a record that does not match the project.
4.9.2 Appendix 2: Setting Up Databases for Co-planning
Two co-planning approaches are possible in Atoll:

◼ Co-planning GSM, UMTS, and LTE using a unified multi-technology data structure, i.e., working with a 3GPP
Multi-RAT document.
◼ Co-planning any two radio technologies (GSM, UMTS, LTE, 5G NR, CDMA2000, TD-SCDMA, and WiMAX), with
two separate data structures, by linking Atoll documents.
In terms of database, while the first approach provides an integrated multi-technology co-planning environment, the
second requires setting up sharing of the Sites table between the databases of the two technologies being co-
planned. The Sites table must be shared between the databases of the two technologies being co-planned so that
the sites where sectors of both technologies are installed are listed only once in a common Sites table. In other
words, the Sites tables in the databases of the two technologies must be views of a common Sites table.
This section describes table sharing between GSM and UMTS, although the same description can be applied to any
two radio technology modules of Atoll
You can create views to share tables that have the same structure in the databases of the two technologies being
co-planned, i.e., the Sites and Antennas tables. In the following, we assume that the Sites tables of the GSM and
UMTS documents contain the same data and that two users, named GSMUser and UMTSUser in this example, exist
in the databases.
To set up a shared Sites table for a GSM-UMTS co-planning project in Oracle or SQL Server:
1. Make backups of the GSM and UMTS documents.
2. Open the GSM document in Atoll.
3. Delete all the transmitters from the Transmitters table and all the sites from the Sites table.
4. Export the GSM document to the database by entering the user name and password for GSMUser.
5. Log in as GSMUser to the database.
6. Delete the Sites table.
7. Open the UMTS document in Atoll.
8. Export the UMTS document to the database by entering the user name and password for UMTSUser.
9. Log in as UMTSUser to the database.
10.Right-click the Sites table and select Create a View from the context menu. The Create View dialog box
appears.
a. Enter Sites as the view name.
b. Enter GSMUser as the name of the schema which will contain the view.
c. Select Table as object type.
d. Enter UMTSUser as the name of the schema you want to use.
e. Select Sites as the object used to model the view.
11.Click Create. The view of the Sites table from UMTSUser is created in GSMUser. The GSMUser Sites table is
now the same as UMTSUser Sites table.
12.Set up user privileges for the Sites view in GSMUser to allow each user to Import, Update, Delete, and Select.

To set up a shared Sites table for a GSM-UMTS co-planning project in Microsoft Access:
1. Make backups of the GSM and UMTS documents.
2. Open the GSM document in Atoll.
3. Delete all the transmitters from the Transmitters table and all the sites from the Sites table.
4. Export the GSM document to a Microsoft Access database (GSM.mdb).
5. Open GSM.mdb in Microsoft Access.
6. Delete the Sites table.
7. Open the UMTS document in Atoll
8. Export the UMTS document to a Microsoft Access database (UMTS.mdb).
9. Open GSM.mdb in Microsoft Access.
10.In Microsoft Access 2003 and earlier, select File > Get External Data > Link Tables. In Microsoft Access 2007
and later, select External Data > Access Database.
11.In Microsoft Access 2003 and earlier, the Link dialog box appears. Select UMTS.mdb. In Microsoft Access
2007 and later, the Get External Data - Access Database dialog box appears, specify UMTS.mdb as data
source and select Link to data source by creating a linked table.
12.Click OK. The Link Tables dialog box appears.
13.Select the Sites table.
14.Click OK. Microsoft Access creates a Sites table in GSM.mdb which is linked to the Sites table in UMTS.mdb.
The tables contain the same data.
Once the linked Sites table has been created in the GSM database, you have to define the relations of this table with
the other tables in the database. See the Data Structure Reference Guide for detailed information on database tables.
 The UMTS Sites table has more fields than the GSM Sites table. Therefore, you
should replace the GSM Sites table with the UMTS one.
When you upgrade one by one the databases that share the Sites table, any triggers
that you might have set on the Sites table of the database that is upgraded first
might be overwritten by the triggers set on the Sites table of the database upgraded
last. In order to avoid the triggers being overwritten, you can rename the triggers on
the Sites table of the database upgraded first (by adding, for example, the database
technology as prefix to the trigger names) before upgrading the other database(s).
Ensuring Database Consistency Between Linked Documents

When users work with two Atoll documents and databases at the same time, it is important to have a protection
mechanism against database inconsistencies. If a user archives the changes made in one document but forgets to
archive the changes made in the other, this can create inconsistencies between the two networks.
To ensure database consistency, you can save or archive the linked documents at the same time, i.e., when a user
saves or archives one document, Atoll automatically saves or archives the other. This can be done using a macro
triggered by the save or archive operation.

AT340_AM_E3 Chapter 5: Multi-user Environments
5 Multi-user Environments
A multi-user environment is where more than one user work simultaneously on an Atoll project, sharing data over a
network. In large, structured multi-user environments, groups of users can work on specific parts of a common,
large-scale project. For example, different user groups can work on different regions of a country-wide network.
◼ "Setting Up Multi-user Environments" on page 59
◼ "Components of Multi-user Environments" on page 59
◼ "Managing User Accounts and Access Rights" on page 62
5.1 Setting Up Multi-user Environments

The general process of setting up a multi-user environment is described below. Each component is described in
detail in "Components of Multi-user Environments" on page 59.
1. Create the master Atoll document with the required network data and geographic data. For more information,
see "Master Atoll Document" on page 60 and "Shared Geographic Data" on page 61.
2. Export the master Atoll document to a new database and keep the document connected to the new database.
For more information, see "Master Database" on page 61.
3. Create the private path loss matrices folder for the master Atoll document and calculate the private path loss
matrices. For more information, see "Shared Path Loss Matrices" on page 61.
4. Create user Atoll documents from the master database. For more information, see "User Atoll Documents" on
page 62.
5. In the user Atoll documents, add the required geographic data and set the master Atoll document’s private
path loss matrices folder as the shared path loss matrices folder of the user documents.
 The Atoll administrator should regularly update the shared path loss matrices.
As the users work on the network and archive changes in the database, the Atoll
administrator should regularly run data integrity checks on the master Atoll
document after loading modified data from the master database. For more
information, see "Appendix 1: Checking Data Integrity" on page 68.
5.2 Components of Multi-user Environments

Figure 5.1 on page 60 shows the components of a multi-user environment.

Chapter 5: Multi-user Environments
Figure 5.1: : Components of Multi-user Environments
In this section, the following are explained:

◼ "Master Atoll Document" on page 60
◼ "Master Database" on page 61
◼ "Shared Geographic Data" on page 61
◼ "Shared Path Loss Matrices" on page 61
◼ "Shared Microwave Link Profiles" on page 62
◼ "User Atoll Documents" on page 62
5.2.1 Master Atoll Document
It is the source Atoll document that contains the entire project’s network data. It is created and maintained by the
Atoll administrator. This document is initially used to create the radio network database with which all the end-users
work. The master Atoll document allows the administrator to globally manage all the data shared by the end-users.
The master Atoll document is also used for calculating path loss matrices for the transmitters of the entire network
and keeping the path loss matrices up to date with the user modifications to the radio network data. The document
also contains the required geographic data for path loss calculations. Geographic data are usually located on file
servers and linked to the document, not embedded in the ATL file. The private path loss matrices of this document
are used as shared path loss matrices by the end-users. The shared path loss matrices folder is usually located on
a file server accessible to all the users on the network.
For exceptionally large networks, you can also work with more than one master Atoll document (for example, one
master document per region). However, the multi-user environment set up remains the same. Master Atoll
documents should not have redundant radio network data (same sites, for example), and should ideally cover
different geographical regions. For more information on regionalisation, see "Appendix 2: Database Regionalisation"
on page 69.
 If you wish to add custom fields in the Atoll document, you should first add the field
in the database, and then update your Atoll document from the database. Custom
fields added in an Atoll document connected to a Microsoft Access database are
automatically added to the database. However, this is not the case with other
RDBMS, such as Oracle.

5.2.2 Master Database
The master database stores the radio network data shared by all the end-users. It can be created by exporting the
radio network data in the master Atoll document to a database from Atoll (for more information, see "Creating a New
Database Using Atoll" on page 40). An empty database can also be created using the Atoll Management Console,
and populated with data later on (for more information, see "Creating a New Database Using the Atoll Management
Console" on page 38).
Only radio network data are stored in the database, i.e., sites, transmitters, antennas, etc. Parameters related to
geographic data files, their paths, folder configurations, prediction definitions, zones, traffic maps, measurements
can be stored in user configuration files (see "Configuration Files" on page 113 for details).
For large networks, you can subdivide the network’s master database into regions. For more information on
regionalisation, see "Appendix 2: Database Regionalisation" on page 69. For more information on database
management, see "Managing Databases" on page 33. The recommended database server configuration is provided
in "Recommended Hardware and Software" on page 16.
 The same database server can be used to store one or more master databases
corresponding to different technologies. For example, a GSM database and a UMTS
database can be stored on the same database server using the same RDBMS
(Oracle, for example).
5.2.3 Shared Geographic Data
Geographic data files are usually stored on a file server accessible to and shared by all the users working on the
same network. User configuration files (CFG or GEO) are used to store the parameters related to geographic data.
For more information, see "Configuration Files" on page 113.
The administrator can set up different user configuration files (CFG) for separate user groups. User configuration
files can be created so that only the geographic data required by a user are loaded. It is possible to load a user
configuration file automatically when running Atoll. User configuration files can be shared and exchanged between
users working on the same project. For more information, see "Atoll Command Line Parameters" on page 26.
Geographic data files are usually large files, and it is recommended that these be stored externally and not
embedded in Atoll documents. The recommended file server configuration is provided in "Recommended Hardware
and Software" on page 16.
 If users modify geographic data locally, for example edit clutter or traffic in their
respective projects, they should store these modified geographic data locally so
that the modifications do not impact other users.
5.2.4 Shared Path Loss Matrices
Shared path loss matrices are usually stored on a file server accessible to and shared by all the users working on
the same project. These path losses are calculated using the master Atoll document by the Atoll administrator. The
private path loss matrices of the master Atoll document are used as shared path loss matrices by the end-users.
The Atoll administrator is the owner of the shared path loss matrices, and must have read/write access to the
shared path loss matrices folder. End-users should have read-only access to this folder.
It is the administrator’s duty to regularly update the master Atoll document with the modifications made to the
master database by the end-users, and to calculate the shared path loss matrices using the master Atoll document
on a routine basis. This task can be carried out using a macro. For more information, see "Appendix 3: Calculating
Path Loss Matrices" on page 70.
Shared path loss matrices are available for use in calculations to all the end-users. However, end-users are not
allowed to modify the shared path loss matrices.

 The shared path loss matrices must be unlocked in order for users to be able to
work with them. You can check whether path loss matrices are unlocked in the
Propagation tab of the Transmitters folder’s properties dialog box.
5.2.5 Shared Microwave Link Profiles
Shared microwave link profiles are usually stored on a file server accessible to and shared by all the users working
on the same project. These profiles are calculated using the master Atoll document by the Atoll administrator. The
private profile data of the master Atoll document is used as shared profile data by the end-users.
The Atoll administrator is the owner of the shared profiles, and must have read/write access to the shared profiles
folder. End-users should have read-only access to this folder.
It is the administrator’s duty to regularly update the master Atoll document with the modifications made to the
master database by the end-users, and to calculate the shared profile extraction using the master Atoll document
on a routine basis. This task can be carried out using a macro.
5.2.6 User Atoll Documents
User Atoll documents are created from the master database. These can contain the entire project network data or
only a part of it. User documents are the working documents of the Atoll end-users connected to the master
database, the geographic data, and the shared path loss matrices folder.
You should load data from the master database in each user Atoll document and save it before setting the shared
path loss matrices folder for the document. For any modifications made by end-users in their Atoll documents that
render some shared path losses invalid, Atoll calculates the invalid path loss matrices locally for the end-users and
stores them in their private path loss matrices location. Shared path loss matrices are only used in calculations if
valid private path loss matrices are not available. Therefore, in order to use shared path loss matrices, you must
delete the corresponding private path loss matrices.
If users are going to work on regions of a network, the regionalisation should be set up before creating the user
documents. For more information on regionalisation, see "Appendix 2: Database Regionalisation" on page 69.
 If you wish to add custom fields in the Atoll document, you should first add the field
in the database, and then update your Atoll document from the database. Custom
fields added in an Atoll document connected to a Microsoft Access database are
automatically added to the database. However, this is not the case with other
RDBMS, such as Oracle.
5.3 Managing User Accounts and Access Rights

The Atoll Management Console enables you to create and delete database user accounts, edit user account
information, and define user access rights to different components of a project such as database tables, and radio
data and parameters in Atoll.
In order to be able to manage user accounts and access rights using the Atoll Management Console, you first have
to make the database compatible with the user management tool. This is done automatically when the user
management tool is run on a database for the first time. The database has to be of the same version as the Atoll
Management Console being used to manage user accounts and access rights.
To make your database compatible with the user management tool:
1. In the Atoll Management Console window, right-click the database whose user accounts you wish to manage.
2. Select Manage Users. The User Management dialog box appears.

3. Click Yes when asked whether you want to make your database compatible with the user management tool.
The Atoll Management Console adds a GUIUserRights table in the database with the following structure:
ATOLL_USER Text (50) Name of the user account
RIGHTS Memo Semi-colon separated set of interface access rights
Each user’s interface access rights are stored in a unique record in the GUIUserRights table. The contents of the
RIGHTS field have the following syntax:
RADIOPARAMS;CALCPARAMS;PROPAGMODELS;PASSWORD
The syntax is explained in detail in "Defining Database and Interface Access Rights" on page 63.
If interface access rights are not defined for a database, i.e., the GUIUserRights table does not exist, all the users
have unrestricted access to the Atoll interface.
If interface access rights are defined for a database, and a user creates a document from the database or opens a
document connected to the database, Atoll retrieves the interface access rights for the user when he enters his user
name and password to access the database.
If the database is not reachable, the user is not listed in the GUIUserRights table, or if the password is not correct,
the user’s interface access rights are set to read-only by default (for more information, see "Defining Database and
Interface Access Rights" on page 63). If the user is listed in the GUIUserRights table, his interface access rights are
read and applied to the Atoll interface (table grids and properties dialog boxes). A message is displayed in the Event
Viewer window to inform the user of his interface access rights. It is possible to remove interface access
restrictions by disconnecting the document from the database. However, a disconnected document cannot be
reconnected to the database.
The GUIUserRights table is also stored in the Atoll document, and is updated when the document is saved. Hence,
users can work on their documents without actually being connected to the database, and still have their usual
interface access rights applied in the document.
 Atoll does not ask for the user name and password when a document is opened
using the API. The interface access rights stored in the document are used.
When database connection properties are modified for a document, for example, when a different user enters his
user name and password in the connection properties, Atoll reads and applies the interface access rights defined
for the new user.
5.3.1 Defining Database and Interface Access Rights
For any existing user account, you can set the database and Atoll interface access rights using the Atoll
Management Console.
To manage database and Atoll interface access rights for an existing user account:
1. In the right-hand pane of the Atoll Management Console window, right-click a database. A context menu
appears.
2. In the context menu, select Manage Users. The User Management dialog box appears.

Figure 5.2: : Managing User Accounts and Access Rights
3. Under Projects, select the projects for which you want to manage user accounts. You can select multiple
projects by pressing CTRL.
4. Under List of users, select the user accounts whose database and interface access rights you want to set. You
can select multiple users by pressing CTRL.
Users who have database access rights in the selected database are marked with the green icon ( ). Users
who do not have any database access rights in the selected database (Category = No Access) are marked with
the red icon ( ). Locked (deactivated) user accounts are marked with a yellow lock icon ( ). For more
information on locked user accounts, see "Managing User Accounts" on page 66.
5. You can set the Filter list to:
◼ All users: Users with access ( ), without access ( ), or locked ( )
◼ Users with access ( )

◼ Administrators: Users with administrator rights among the users with access
◼ Standard users: Users with standard rights among the user with access
◼ Read-only users: Users with read-only access rights among the users with access
6. Under Database rights, you can select a database access Rights category:
◼ No access: User without read and write access to the database. The database is not visible to these users
and they are not allowed to create Atoll documents based on this database.
◼ Read only: Users allowed to create Atoll documents from the database but without write permissions to
any table of the database, i.e., users cannot archive changes made in the Atoll document to the database.
◼ Standard: Users with read and write access to some tables of the database containing radio network data
(see table below).
◼ Super-User: Users with read and write access to all the tables of the database.
Database access rights are stored in the user account properties in Oracle. If you are working with an RDBMS
other than Oracle, you will not be able to set database access rights. You can, however, still set interface
access rights as explained below.

Technologies Tracked Tables
GSM GPRS EDGE Sites, SitesLists, SitesListsNames, Transmitters, TXLists, TXListsNames, TRGs, TRXs,
Repeaters, SecondaryAntennas, Neighbours, NeighboursExt, NeighboursConstraints,
NeighboursConstraintsExt
UMTS HSPA Sites, SitesLists, SitesListsNames, Transmitters, TXLists, TXListsNames, CDMACells,

CDMA2000 1xRTT 1xEV-DO Sites, SitesLists, SitesListsNames, Transmitters, TXLists, TXListsNames, CDMACells,
LTE Sites, SitesLists, SitesListsNames, Transmitters, TXLists, TXListsNames, T4GCells,

NeighboursConstraintsExt, lcagroups, lcagroupdefs, lcompsets, lcompsetdefs,
lmbsfnareas, lmbsfnareadefs
WiMAX/Wi-Fi Sites, SitesLists, SitesListsNames, Transmitters, TXLists, TXListsNames, WCells,

3GPP sites, siteslists, siteslistsnames, ltransmitters, utransmitters, gtransmitters, ltxlists, ltx-

listsnames, utxlists, utxlistsnames, gtxlists, gtxlistsnames, lcells, ucells, gtrgs, gtrxs, lre-
peaters, urepeaters, grepeaters, lsecondaryantennas, usecondaryantennas,
gsecondaryantennas, lneighbours, uneighbours, gneighbours, lneighext, uneighext,
gneighext, guneighbours, ugneighbours, glneighbours, lgneighbours, ulneighbours,
luneighbours, lneighextconstraints, uneighextconstraints, gneighextconstraints, lca-
groups, lcagroupdefs, lcompsets, lcompsetdefs, lmbsfnareas, lmbsfnareadefs
3GPP2 sites, siteslists, siteslistsnames, ltransmitters, ctransmitters, ltxlists, ltxlistsnames, ctx-

lists, ctxlistsnames, lcells, ccells, lrepeaters, crepeaters, lsecondaryantennas, csecond-
aryantennas, lneighbours, cneighbours, lneighext, cneighext, lcneighbours, clneighbours,
lneighextconstraints, cneighextconstraints, lcagroups, lcagroupdefs, lcompsets, lcomp-
setdefs, lmbsfnareas, lmbsfnareadefs
Microwave Radio Links/Backhaul Sites, SitesLists, SitesListsNames, MWLinks, MWHubs, MWPmp, MWMultiHops,
MWMultiHopsLinks, MWRepeaters, MWOTLinks, MWPorts, BHNodes, BHSegments,
BHSegmentsMedia
7. Under Interface rights, you can select interface access rights for:
◼ Access to radio data:
◼ Full: (RADIOPARAMS = ALL) Users with read and write access to all the tables and properties dialog
boxes.
◼ Standard: (RADIOPARAMS = STD) Users with read and write access to radio network data tables and
properties dialog boxes including sites, transmitters, cells, carrier aggregation groups, carrier
aggregation group definitions, CoMP sets, CoMP set definitions, MBSFN areas, MBSFN area definitions,
subcells, repeaters, remote antennas, secondary antennas, intra- and inter-technology neighbours and
exceptional pairs, site and transmitter lists, microwave point-to-point, point-to-multipoint, and multi-hop
links, microwave repeaters, microwave hubs.
◼ Read only: (RADIOPARAMS = NONE) Users with read-only access to tables and properties dialog boxes,
i.e., users are not allowed to modify radio network data and parameters.
 Database access rights and access rights to radio data in Atoll can be set
independently. For example, a user can have full access rights in the interface but
not be allowed to archive changes to the database.
However, access rights in the interface should only be granted if the user has at
least read-only access to the database.
◼ Access to calculation parameters:

◼ All: (CALCPARAMS = ALL) Users with read and write access to all coverage predictions, their calculation
settings, and to microwave calculation settings (Models, Objectives, and Clutter Categories tabs of the
Properties dialog box of the Microwave Radio Links folder).
◼ Standard: (CALCPARAMS = STD) Users with access to customised coverage predictions only, and
allowed to modify coverage conditions and display settings. These users do not have access to the
microwave calculation settings mentioned above.

◼ Customised only: (CALCPARAMS = NONE) Users with access to customised coverage predictions only,
but not allowed to modify coverage conditions and display settings. These users do not have access to
the microwave calculation settings mentioned above.
◼ Access to propagation models:
◼ Full: (PROPAGMODELS = ALL) Users with read and write access to all propagation models and their
properties.
◼ Read only: (PROPAGMODELS = NONE) Users with read-only access to the properties of all the
propagation models. Adding and deleting propagation models is also not allowed.
◼ Password confirmation:
◼ Yes: (PASSWORD = STD) Atoll will ask users for password when opening a document connected to this
database or creating a new document from this database.
◼ No: (PASSWORD = NONE) Atoll will not ask users for password when opening a document connected to
this database or creating a new document from this database.
8. Click OK. The database and interface access rights of the selected user are saved in the database.
5.3.2 Managing User Accounts
You can create and edit user accounts using the Atoll Management Console.
To create a new user account:
1. In the right-hand pane of the Atoll Management Console window, right-click a database and select Manage
Users. The User Management dialog box appears (see Figure 5.2 on page 64).
2. Under Users, click Create. The User Creation/Edition dialog box appears.
Figure 5.3: : User Creation/Edition dialog box
3. Under Identification:
◼ Enter a User name, a Password, and Confirm your password.
◼ Select a Tablespace, a Temporary tablespace, and a Profile.
4. Under Advanced:
◼ Select Use operating system authentication if you want to use OS authentication prefix with the user name.
◼ Select "Unlimited tablespace" privilege if you want to assign this system privilege to the user or specify a
Quota in megabytes.
5. Click OK. The new user account is created.
To edit a user account:

2. Under List of users, select the user account whose information you want to edit.
3. Under Users, click Edit. The Create/Edit User dialog box appears (Figure 5.3 on page 66).
4. Under Identification, modify the user’s Password and the assigned Tablespace, Temporary tablespace, and
Profile.
5. Under Advanced:
◼ Select Use operating system authentication if you want to use OS authentication prefix with the user name.
◼ Select "Unlimited tablespace" privilege if you want to assign this system privilege to the user or specify a
Quota in megabytes.
6. Click OK. The new account information is saved.
To deactivate (lock) a user account:
2. Under List of users, select the user account you want to deactivate.
3. Under Users, click Edit. The Create/Edit User dialog box appears (Figure 5.3 on page 66).
4. Under Advanced, select the Account locked check box.
5. Click OK. The user account is deactivated and can no longer be used.
To delete a user account:
2. Under List of users, select the user account you want to deactivate.
3. Under Users, click Delete. The user account is deleted.
5.3.3 Resetting User Database Permissions
The permissions reset feature in the Atoll Management Console enables you to rebuild user database permissions
while keeping existing role assignments. It is particularly useful after a major Atoll upgrade or after tables were
added as a result of a project customization, and for all unforeseen reasons which can require fixing user database
permissions.
The reset process does not remove any object privileges assigned prior to rebuilding the database. It just looks for
new objects and assigns permissions based on existing user profiles ("Administrator", "Standard", "Read-only",
"Super-user").
To reset user permissions for all users:
2. Under Database rights, click Reset.
3. Acknowledge the message informing you about the rebuilding process duration.
 The duration of the database rebuild depends on the number of users and on the
database processing speed.
5.3.4 Managing Custom Permissions
It is possible to assign permissions to user roles for one or several specific database columns. When using a third
party add-in or an external tool, this allows users who are in a read-only role to still archive changes on specific
fields.

 Custom permissions do not allow read-only users to archive changes from within
the Atoll user interface.
To assign custom permissions to a read-only user:

4. In an external database configuration tool, run an SL query to assign write permissions to a specific column
of a database for the read-only user.
5. In the right-hand pane of the Atoll Management Console window, right-click the database and select Manage
6. Under List of users, select the user accounts that belong to the user role.
7. Under Database rights, click Reset.
8. Acknowledge the message informing you about the rebuilding process duration.
 The duration of the database rebuild depends on the number of users and on the
database processing speed.
To revoke custom permissions for a user:

2. Under List of users, select the user accounts that belong to the user role.
3. Under Database rights, select No Access and click Apply.
4. In an external database configuration tool, run an SL query to remove the custom permissions from the role.
5. In the Atoll Management Console window, reassign the Read only role to the selected users.
5.4 Appendices
The following appendices provide additional information on:
◼ "Appendix 1: Checking Data Integrity" on page 68
◼ "Appendix 2: Database Regionalisation" on page 69
◼ "Appendix 3: Calculating Path Loss Matrices" on page 70
◼ "Appendix 4: Path Loss Matrices From Different Sources" on page 70
5.4.1 Appendix 1: Checking Data Integrity
Atoll includes data consistency and integrity checking tools that allow you to check data consistency between the
different Atoll tables (Sites, Transmitters, etc.). It is recommended that the Atoll administrator runs data integrity
checks regularly on the master Atoll document after it is updated with data modifications in the master database.
To perform data integrity check:
◼ In Atoll, select Document > Data Audit > Integrity Check.
Atoll searches for records with integrity problems which can occur with objects that have foreign keys.
Integrity problems occur when records refer records that do not exist. For example, transmitters located on
sites that do not exist in the Sites table, transmitters referring to an antenna that does not exist in the Antennas
table, etc.). Records with integrity problems can be deleted when found.
To perform undefined record check:
◼ In Atoll, select Document > Data Audit > Undefined Record Check.

Atoll searches for undefined records such as sites without transmitters, transmitters without subcells, TRXs,
and neighbours in GSM, transmitters without cells, and cells without neighbours in UMTS, CDMA2000, TD-
SCDMA, LTE, WiMAX, and Wi-Fi. Atoll lists all the undefined records found in the Event Viewer.
To perform duplicate record check:
◼ In Atoll, select Document > Data Audit > Duplicate Record Check.
Atoll searches for records that have the same identifier. For example, sites with the same name, transmitters
with the same name, etc. Atoll lists all the duplicate records in the Event Viewer.
To perform microwave data check:
1. In Atoll, select Document > Data Audit > Microwave Data Check. The Microwave Data Check dialog box
appears.
2. In the Microwave Data Check dialog box, select the data to check.
3. Select List all the checks to list all the checks in the Event Viewer.
4. Click OK.
Atoll searches the microwave links tables for problems related to the selected checks. Atoll lists the problems
found in the Event Viewer.
 If you fix any problems in the Atoll document, you must archive the changes in the
database in order to fix the problems for all the users working with that database.
5.4.2 Appendix 2: Database Regionalisation
You can subdivide the network into regions in the following ways:
◼ Static regionalisation using multi-level databases
Static regionalisation can be based on site lists, SQL filters, or geographic zones in the form of filtering
polygons. Static regionalisation is carried out by creating project databases from the master database, i.e.,
multi-level databases as explained in "Working With Multi-level Databases Using Oracle" on page 45.
Static regionalisation requires manual synchronisation between the master database and the regional project
databases using the Atoll Management Console. In a multi-level database environment, end-users work with
project databases, refreshing and archiving data as they continue to work on their respective regions of the
network. Data archive and refresh between the project databases and the master database are performed by
the administrator alone.
◼ Advantage: High performance.
◼ Disadvantage: Manual Synchronisation between the master and the project databases.
◼ Dynamic regionalisation using Oracle Spatial or Oracle Locator
Dynamic regionalisation can be based on Oracle Spatial, which does not create separate regional databases
from the master database, but rather lets the different users work with the master database directly while
managing their access privileges according to their user connection properties. In an Atoll multi-user
environment, you can create such regionalisation without installing Oracle Spatial. You can implement this
solution using Oracle Locator, which is provided in the standard Oracle installation.
Specific documents explaining how to set up this regionalisation, using Oracle, in any Atoll master database
are available on demand from Forsk. These documents provide scripts for creating different types of users,
e.g., the administrator, advanced user, read-only user, etc., and give examples of how to set up regions in the
network and how to assign user rights to each region.
◼ Advantage: Once set up, does not require administrator intervention.
◼ Disadvantage: Slow performance (archiving data in the database takes a long time).

5.4.3 Appendix 3: Calculating Path Loss Matrices
You can calculate only the invalid path loss matrices or all the path loss matrices in Atoll or using a macro.
 You should only calculate the shared path loss matrices when they are not being
accessed by users.
To calculate invalid path loss matrices only:

1. Right-click the Transmitters folder. The context menu appears.
2. Select Calculations > Calculate Path Loss Matrices.
Atoll calculates path loss matrices for all active transmitters in the folder or subfolder. Only invalid and
nonexistent matrices are calculated.
To calculate all the path loss matrices (valid and invalid):
1. Right-click the Transmitters folder. The context menu appears.
2. Select Calculations > Force Path Loss Matrix Calculation.
Atoll calculates all the path loss matrices for all active transmitters in the folder or subfolder.
You can write a script or macro to update path loss matrices automatically at regular intervals. The script or macro
should:
1. Start Atoll (Start).
2. Open the master Atoll document (Open).
3. Refresh the contents of the document with data from the database (Refresh).
4. Calculate path loss matrices (Calculate).
5. Save the master Atoll document (Save).
6. Close Atoll (Exit).
A path loss update macro is available from Forsk on demand.
+ You should also make regular backups of the master Atoll document. The above
macro could also create a backup ATL file of the master Atoll document on a
regular basis. This file can be overwritten daily, whenever path losses are
calculated.
5.4.4 Appendix 4: Path Loss Matrices From Different Sources
Atoll calculates path loss matrices and creates path loss matrix storage files using the propagation models
assigned to transmitters. Atoll can also work with path loss matrices calculated by other tools. To use path loss
matrices from different sources, make sure that the path loss matrices are:
◼ Available in a format compatible with Atoll. File formats are described in "Path Loss Matrix File Format" on
page 89.
◼ Stored at the location set in the Atoll document.
◼ Valid. If the path loss matrices are not valid, Atoll will automatically calculate them the next time they are used.
 Path loss matrices calculated by other tools should include antenna pattern
attenuation (i.e., should be masked) in order to be consistent with the path loss
matrices calculated by Atoll.
The shared path loss matrices architecture can contain path loss matrices from different sources. The Pathloss.dbf
file provides the means to manage several sources of path loss matrices. This file stores, among other information,
the validity status and the location (path) of the path loss matrix files for each transmitter.

Let us assume that users of group A wish to work with the path loss matrices generated by Atoll only, and users of
group B wish to work with path loss matrices generated by a different tool for a part of the network and with path
loss matrices generated by Atoll where the matrices from the other tool are not available.
Let us assume that the shared path loss matrices folder where Atoll stores the generated path loss matrices files
is C:\Path_Loss_Internal, and the folder where the other tool stores its path loss matrices is C:\Path_Loss_External.
The Pathloss.dbf file in the Path_Loss_Internal folder will store the path to the LOS files for each transmitter in the
network. This folder can be set as the shared path loss matrices folder in the ATL files of group A users.
To set up the shared path loss matrices folder for group B users, you must create a new folder with a Pathloss.dbf
file in it. This folder can be called C:\Path_Loss_Mixed. The Pathloss.dbf file in this folder can be a copy of the
Pathloss.dbf file in the Path_Loss_Internal folder with the paths to the LOS files modified. For example, if the path
loss matrices generated by the other tool include Transmitter_1, the Pathloss.dbf file in the Path_Loss_Mixed folder
will have all the same entries as Pathloss.dbf file in the Path_Loss_Internal folder except for the path for the
Transmitter_1 path loss matrices file. Figure 5.4 on page 71 explains this concept.
Figure 5.4: : Path Loss Architecture for Multiple Source Path Loss Matrices
Once the Pathloss.dbf file in the Path_Loss_Mixed folder is updated with the correct paths corresponding to the
different transmitters, the Path_Loss_Mixed folder can be set as the shared path loss matrices folder in the ATL files
of group B users.
If a group B user changes some parameters which make some path loss matrices invalid, Atoll will recalculate the
private path loss matrices with the propagation models assigned to the transmitters. The external path loss matrix
will no longer be used.


AT340_AM_E3 Chapter 6: Coordinate Systems and Units
6 Coordinate Systems and Units

Atoll is designed for international environments and can be configured to use a variety of coordinate systems and
measurement units.
◼ "Coordinate Systems" on page 73
◼ "Measurement Units" on page 80
◼ "BSIC Format" on page 81
6.1 Coordinate Systems

A map or a geo-spatial database is a flat representation of data collected over a curved surface. Projection is a
means of producing all or part of a spheroid on a flat surface, which cannot be done without distortion. It is up to
the cartographer to choose the characteristic (distance, direction, scale, area, or shape) that he wants to produce
accurately on a flat surface at the expense of the other characteristics, or to make a compromise on several
characteristics. The projected zones are referenced using cartographic coordinates (metre, yard, etc.). Two
projection methods are widely used:
◼ The Lambert Conformal-Conic Method: A portion of the earth is projected on a cone conceptually secant at
one or two standard parallels. This projection method is useful for representing countries or regions that have
a predominant east-west expanse.
◼ The Universal Transverse Mercator (UTM) Method: A portion of the earth is projected on a cylinder tangent
to a meridian (which is transverse or crosswise to the equator). This projection method is useful for mapping
large areas that are oriented north-south.
A geographic system is not a projection, but a representation of a location on the surface of the earth in geographic
coordinates (degree-minute-second, gradient) with the latitude and longitude with respect to a meridian (e.g., Paris
for NTF system and Greenwich for ED50 system). Locations in a geographic system can be converted into other
projections.
 References:
1. Snyder, John. P., Map Projections Used by the US Geological Survey, 2nd
Edition, United States Government Printing Office, Washington, D.C., 313
pages, 1982.
2. http://www.colorado.edu/geography/gcraft/notes/gps/gps_f.html
3. http://www.epsg.org/Geodetic.html
4. http://geodesie.ign.fr/contenu/fichiers/documentation/pedagogiques/
transfo.pdf (French)
6.1.1 Definition of a Coordinate System
A geographic coordinate system is a latitude and longitude coordinate system. The latitude and longitude are
related to an ellipsoid, a geodetic datum, and a prime meridian. The geodetic datum provides the position and
orientation of the ellipsoid relative to the earth.

Chapter 6: Coordinate Systems and Units
Cartographic coordinate systems are obtained by transforming each (latitude, longitude) value into an (easting,
northing) value. A projection coordinate system is obtained by transforming each (latitude, longitude) value into an
(easting, northing) value. Projection coordinate systems are geographic coordinate systems that provide longitude
and latitude, and the transformation method characterised by a set of parameters. Different methods might require
different sets of parameters. For example, the parameters required for Transverse Mercator coordinate systems
are:
◼ The longitude of the natural origin (central meridian)
◼ The latitude of the natural origin
◼ The False Easting value
◼ The False Northing value
◼ A scaling factor at the natural origin (central meridian)
Basic definitions are presented below.
Geographic Coordinate System

The geographic coordinate system is a datum and a meridian. Atoll enables you to choose the most suitable
geographic coordinate system for your geographic data.
Datum
The datum consists of the ellipsoid and its position relative to the WGS84 ellipsoid. In addition to the ellipsoid,
translation, rotation, and distortion parameters define the datum.
Meridian
The standard meridian is Greenwich, but some geographic coordinate systems are based on other meridians. These
meridians are defined by the longitude with respect to Greenwich.
Ellipsoid
The ellipsoid is the pattern used to model the earth. It is defined by its geometric parameters.
Projection
The projection is the transformation applied to project the ellipsoid of the earth on to a plane. There are different
projection methods that use specific sets of parameters.
Projection Coordinate System

The projection coordinate system is the result of the application of a projection to a geographic coordinate system.
It associates a geographic coordinate system and a projection. Atoll enables you to choose the projection
coordinate system matching your geographic data.
6.1.2 Types of Coordinate Systems in Atoll
Depending on the working environment, there can be either two or four coordinate systems used in Atoll. If you are
working with stand-alone documents, i.e., documents not connected to databases, there are two coordinate
systems used in Atoll:
◼ Projection coordinate system
◼ Display coordinate system
If you are working in a multi-user environment, Atoll uses four coordinate systems:
◼ Projection coordinate system for the Atoll document
◼ Display coordinate system for the Atoll document
◼ Internal projection coordinate system for the database
◼ Internal display coordinate system for the database
Projection Coordinate System

The projection coordinate system is the coordinate system of the available raster geographic data files. You should
set the projection coordinate system of your Atoll document so that it corresponds to the coordinate system of the

available raster geographic data. You can set the projection coordinate system of your document in the Options
dialog.
All the raster geographic data files that you want to import and use in an Atoll document must have the same
coordinate system. You cannot work with raster geographic data files with different coordinate systems in the same
document.
 If you import vector geographic data (e.g., traffic, measurements, etc.) with
different coordinate systems, it is possible to convert the coordinate systems of
these data into the projection coordinate system of your Atoll document.
The projection coordinate system is used to keep the coordinates of sites (radio network data) consistent with the
geographic data.
When you import a raster geographic data file, Atoll reads the geo-referencing information from the file (or from its
header file, depending on the geographic data file format), i.e., its Northwest pixel, to determine the coordinates of
each pixel. Atoll does not use any coordinate system during the import process. However, the geo-referencing
information of geographic data files are considered to be provided in the projection coordinate system of the
document.
Display Coordinate System

The display coordinate system is the coordinate system used for the display, e.g., in dialogs, in the Map window
rulers, in the status bar, etc. The coordinates of each pixel of geographic data are converted to the display
coordinate system from the projection coordinate system for display. The display coordinate system is also used
for sites (radio network data). You can set the display coordinate system of your document in the Options dialog.
If you import sites data, the coordinate system of the sites must correspond to the display coordinate system of
your Atoll document.
If you change the display coordinate system in a document which is not connected to a database, the coordinates
of all the sites are converted to the new display system.
 If the coordinate systems of all your geographic data files and sites (radio network
data) are the same, you do not have to define the projection and display coordinate
systems separately. By default, the two coordinate systems are the same.
 If you want to export an XML document with a coordinate system that is different
from the coordinate system used by the document, you must disconnect the
document from the database before changing the coordinate system.
Internal Coordinate Systems

The internal coordinate systems are the projection and the display coordinate systems stored in a database. The
projection and display coordinate systems set by the administrator in the central Atoll project are stored in the
database when the database is created, and cannot be modified by users. Only the administrator can modify the
internal coordinate systems manually by editing the entries in the CoordSys and the Units tables. All Atoll
documents opened from a database will have the internal coordinate systems of the database as their default
projection and display coordinate systems.
When exporting an Atoll project to a database, the currently chosen display coordinate system becomes the internal
display coordinate system for the database, and the currently chosen projection coordinate system becomes the
internal projection coordinate system for the database.
Although Atoll stores both the coordinate systems in the database, i.e., the projection and the display coordinate
systems, the only relevant coordinate system for the database is the internal display coordinate system because
this coordinate system is the one used for the coordinates of sites (radio network data).
Users working on documents connected to a database can modify the coordinate systems in their documents
locally, and save these changes in their documents, but they cannot modify the coordinate systems stored in the
database.
If you change the display coordinate system in a document which is not connected to a database, the coordinates
of all the sites are converted to the new display system.

If you change the display coordinate system in a document which is connected to a database, the coordinates of all
the sites are converted to the new coordinate system in the Atoll document locally but not in the database because
the internal coordinate systems cannot be changed.
Atoll uses the internal coordinates systems in order to keep the site coordinates consistent in the database which
is usually accessed by a large number of users in a multi-user environment.
6.1.3 Coordinate Systems File Format
The Coordsystems folder located in the Atoll installation directory contains all the coordinate systems, both
geographic and cartographic, offered in the tool. Coordinate systems are grouped by regions. A catalogue per region
and a "Favourites" catalogue are available in Atoll. The Favourites catalogue is initially empty and can be filled by
the user by adding coordinate systems to it. Each catalogue is described by an ASCII text file with .cs extension. In
a .cs file, each coordinate system is described in one line. The line syntax for describing a coordinate system is:
Code = "Name of the system"; Unit Code; Datum Code; Projection Method Code,
Projection Parameters; "Comments"
Examples:
4230 = "ED50"; 101; 230; 1; "Europe - west"
32045 = "NAD27 / Vermont"; 2; 267; 6, -72.5, 42.5, 500000, 0, 0.9999643; "United

States - Vermont"
You should keep the following points in mind when editing or creating .cs files:
◼ The identification code enables Atoll to differentiate coordinates systems. In case you create a new
coordinate system, its code must be an integer value higher than 32767.
◼ When describing a new datum, you must enter the ellipsoid code and parameters instead of the datum code
in brackets. There can be 3 to 7 parameters defined in the following order: Dx, Dy, Dz, Rx, Ry, Rz, S. The syntax
of the line in the .cs file will be:
Code = "Name of the system"; Unit Code; {Ellipsoid Code, Dx, Dy, Dz, Rx, Ry, Rz,
S}; Projection Method Code, Projection Parameters; "Comments"
◼ There can be up to seven projection parameters. These parameters must be ordered according to the
parameter index (see "Projection Parameter Indices" on page 79). Parameter with index 0 is the first one.
Projection parameters are delimited by commas.
◼ For UTM projections, you must provide positive UTM zone numbers for north UTM zones and negative
numbers for south UTM zones.
◼ You can add all other information as comments (such as usage or region).
Codes of units, data, projection methods, and ellipsoids, and projection parameter indices are listed in the tables
below.
Unit Codes
Code Cartographic Units Code Geographic Units

0 Metre 100 Radian
1 Kilometre 101 Degree
2 Foot 102 Grad
3 Link 103 ArcMinute
4 Chain 104 ArcSecond

Code Cartographic Units Code Geographic Units
5 Yard -1 Unspecified
6 Nautical mile
7 Mile
-1 Unspecified
Datum Codes
Code Datum Code Datum
121 Greek Geodetic Reference System 1987 260 Manoca
125 Samboja 261 Merchich
126 Lithuania 1994 262 Massawa
130 Moznet (ITRF94) 263 Minna
131 Indian 1960 265 Monte Mario
171 RGF93 266 M'poraloko
181 Luxembourg 1930 267 North American Datum 1927
201 Adindan 268 NAD Michigan
202 Australian Geodetic Datum 1966 269 North American Datum 1983
203 Australian Geodetic Datum 1984 270 Nahrwan 1967
204 Ain el Abd 1970 271 Naparima 1972
205 Afgooye 272 New Zealand Geodetic Datum 1949

206 Agadez 273 NGO 1948
207 Lisbon 274 Datum 73
208 Aratu 275 Nouvelle Triangulation Francaise
209 Arc 1950 276 NSWC 9Z-2

210 Arc 1960 277 OSGB 1936
211 Batavia 278 OSGB 1970 (SN)
212 Barbados 279 OS (SN) 1980

213 Beduaram 280 Padang 1884
214 Beijing 1954 281 Palestine 1923
215 Reseau National Belge 1950 282 Pointe Noire
216 Bermuda 1957 283 Geocentric Datum of Australia 1994
217 Bern 1898 284 Pulkovo 1942
218 Bogota 285 Qatar
219 Bukit Rimpah 286 Qatar 1948
221 Campo Inchauspe 287 Qornoq
222 Cape 288 Loma Quintana
223 Carthage 289 Amersfoort
224 Chua 290 RT38
225 Corrego Alegre 291 South American Datum 1969
226 Cote d'Ivoire 292 Sapper Hill 1943
227 Deir ez Zor 293 Schwarzeck
228 Douala 294 Segora
229 Egypt 1907 295 Serindung
230 European Datum 1950 296 Sudan
231 European Datum 1987 297 Tananarive 1925
232 Fahud 298 Timbalai 1948

Code Datum Code Datum
233 Gandajika 1970 299 TM65
234 Garoua 300 TM75
235 Guyane Francaise 301 Tokyo
236 Hu Tzu Shan 302 Trinidad 1903
237 Hungarian Datum 1972 303 Trucial Coast 1948
238 Indonesian Datum 1974 304 Voirol 1875
239 Indian 1954 305 Voirol Unifie 1960
240 Indian 1975 306 Bern 1938
241 Jamaica 1875 307 Nord Sahara 1959
242 Jamaica 1969 308 Stockholm 1938
243 Kalianpur 309 Yacare
244 Kandawala 310 Yoff
245 Kertau 311 Zanderij
247 La Canoa 312 Militar-Geographische Institut
248 Provisional South American Datum 1956 313 Reseau National Belge 1972
249 Lake 314 Deutsche Hauptdreiecksnetz
250 Leigon 315 Conakry 1905
251 Liberia 1964 322 WGS 72

252 Lome 326 WGS 84
253 Luzon 1911 611 Hong Kong 1980
254 Hito XVIII 1963 674 SIRGAS 2000
255 Herat North 901 Ancienne Triangulation Francaise

256 Mahe 1971 902 Nord de Guerre
257 Makassar 903 NAD 1927 Guatemala/Honduras/Salvador (Pan-

ama Zone)
258 European Reference System 1989 1026 Taiwan Datum 1997
Projection Method Codes
Code Projection Method Code Projection Method
0 Undefined 9 New Zealand Map Grid
1 No projection: Longitude / Latitude 10 Hotine Oblique Mercator
2 Lambert Conformal Conical 1SP 11 Laborde Oblique Mercator
3 Lambert Conformal Conical 2SP 12 Swiss Oblique Cylindrical
4 Mercator 13 Oblique Mercator
5 Cassini-Soldner 14 UTM Projection
6 Transverse Mercator 15 Albers Equal Area Conic
7 Transverse Mercator South Oriented 16 American Polyconic
8 Oblique Stereographic
Ellipsoid Codes
Code Name Major Axis Minor Axis
1 Airy 1830 6377563.396 6356256.90890985
2 Airy Modified 1849 6377340.189 6356034.44761111
3 Australian National Spheroid 6378160 6356774.71919531
4 Bessel 1841 6377397.155 6356078.96261866

Code Name Major Axis Minor Axis
5 Bessel Modified 6377492.018 6356173.50851316
6 Bessel Namibia 6377483.865 6356165.38276679
7 Clarke 1858 6378293.63924683 6356617.98173817
8 Clarke 1866 6378206.4 6356583.8
9 Clarke 1866 Michigan 6378693.7040359 6357069.45104614
10 Clarke 1880 (Benoit) 6378300.79 6356566.43
11 Clarke 1880 (IGN) 6378249.2 6356515
12 Clarke 1880 (RGS) 6378249.145 6356514.86954978
13 Clarke 1880 (Arc) 6378249.145 6356514.96656909
14 Clarke 1880 (SGA 1922) 6378249.2 6356514.99694178
15 Everest 1830 (1937 Adjustment) 6377276.345 6356075.41314024
16 Everest 1830 (1967 Definition) 6377298.556 6356097.5503009
17 Everest 1830 (1975 Definition) 6377301.243 6356100.231
18 Everest 1830 Modified 6377304.063 6356103.03899315
19 GRS 1980 6378137 6356752.31398972
20 Helmert 1906 6378200 6356818.16962789
21 Indonesian National Spheroid 6378160 6356774.50408554
22 International 1924 6378388 6356911.94612795

23 International 1967 6378160 6356774.71919530
24 Krassowsky 1940 6378245 6356863.01877305
25 NWL 9D 6378145 6356759.76948868
26 NWL 10D 6378135 6356750.52001609

27 Plessis 1817 6376523 6355862.93325557
28 Struve 1860 6378297 6356655.84708038
29 War Office 6378300.583 6356752.27021959

30 WGS 84 6378137 6356752.31398972
31 GEM 10C 6378137 6356752.31398972
32 OSU86F 6378136.2 6356751.51667196
33 OSU91A 6378136.3 6356751.61633668
34 Clarke 1880 6378249.13884613 6356514.96026256
35 Sphere 6371000 6371000
Projection Parameter Indices
Index Projection Parameter Index Projection Parameter
0 UTM zone number 4 Scale factor at origin
0 Longitude of origin 4 Latitude of 1st parallel
1 Latitude of origin 5 Azimuth of central line
2 False Easting 5 Latitude of 2nd parallel
3 False Northing 6 Angle from rectified to skewed grid

6.1.4 Creating a Coordinate System in Atoll
Atoll provides a large default catalogue of coordinate systems. However, it is possible to add new geographic and
cartographic coordinate systems. New coordinate systems can be created from scratch or initialised based on
existing ones.
To create a new coordinate system from scratch:
1. Select Document > Properties. The Properties dialogue opens.
2. Select the Coordinates tab.
3. Click the Browse button ( ) to the right of Projection. The Coordinate Systems dialogue appears.
4. Click New. The Coordinate System dialogue appears.
5. In the Coordinate System dialogue:
a. Select the coordinate systems catalogue to which you want to add the new coordinate system.
b. Under General, enter a Name for the new coordinate system and select a Unit. In Use, you can enter
comments about its usage. Atoll assigns the code automatically.
c. Under Category, select the Type of coordinate system. Enter the longitude and latitude for a geographic
coordinate system, or the type of projection and its set of associated parameters for a cartographic
coordinate system (false easting and northing, and the first and second parallels).
d. Under Geo, specify the meridian and choose a Datum for the coordinate system. The associated ellipsoid
is automatically selected. You can also describe a geodetic datum by selecting "<Customised>" in the
Datum list. In this case, you must select an Ellipsoid and enter parameters (Dx, Dy, Dz, Rx, Ry, Rz, and S)
needed for the transformation of the datum into WGS84.
6. Click OK. The new coordinate system is added to the selected coordinate system catalogue.
To create a new coordinate system based on an existing system, select a coordinate system in the Coordinate
Systems dialogue before clicking New in step 4. The new coordinate system is initialised with the values of the
selected coordinate system.
6.2 Measurement Units

In the Atoll documents, you can define measurement units for reception, transmission, antenna gain, distance,
height and offset, and temperature. You can accept the default measurement units, or you can change them using
the document properties dialogue.
Transmission and Reception Power Units

Depending on the working environment, Atoll can use either one or two measurement units for the transmission/
reception power.
If you are working with stand-alone documents, i.e., documents not connected to databases, there is only one
measurement unit used in Atoll for display. It corresponds to the transmission/reception power unit defined in the
Atoll document.
If you are working in a multi-user environment, Atoll uses two measurement units:
◼ A measurement unit for display in the Atoll document. It corresponds to the transmission/reception power
unit defined in the current Atoll document. It is used for the display in the dialogues and in the tables, e.g.,
reception thresholds (coverage prediction properties, microwave link properties, etc.), and received signal
levels (measurements, point analysis, coverage predictions, microwave link properties, etc.).
◼ An internal measurement unit for the database. The internal unit is the transmission/reception power unit
stored in the database. It corresponds to the transmission/reception power unit used in the master Atoll
document when the database is created. Users working in documents connected to a database can modify
the transmission/reception power unit and save this change in their documents locally, but they cannot modify
the internal power unit stored in the database. Only the administrator can modify it manually by editing the
entry in the Units tables.

Antenna Gain Units

Depending on the working environment, Atoll can use either one or two measurement units for the antenna gain.
If you are working with stand-alone documents, i.e., documents not connected to databases, there is only one
measurement unit used in Atoll for display. It corresponds to the antenna gain unit defined in the Atoll document.
If you are working in a multi-user environment, Atoll uses two measurement units:
◼ A measurement unit for display in the Atoll document. It corresponds to the antenna gain unit defined in the
current Atoll document and it is used for the display in the dialogues and in the tables.
◼ An internal measurement unit for the database. The internal unit is the antenna gain unit stored in the
database. It corresponds to the antenna gain unit used in the master Atoll document when the database is
created. Users working in documents connected to a database can modify the antenna gain unit and save this
change in their documents locally, but they cannot modify the antenna gain unit stored in the database. Only
the administrator can modify it manually by editing the entry in the Units tables.
Distance Units
Atoll uses the distance unit defined in the current Atoll document as display unit of the distances in the dialogues,
in the tables, and in the status bar.
Metre is used as the internal measurement unit for the distance in all Atoll documents whether they are connected
to databases or not. The internal measurement unit is not stored in the database and cannot be changed.
Height and Offset Units

Atoll uses the height and offset unit defined in the current Atoll document as display unit of the heights and the
offsets in the dialogues, in the tables, and in the status bar.
Metre is used as the internal measurement unit for the heights and offsets in all Atoll documents whether they are
connected to databases or not. The internal measurement unit is not stored in the database and cannot be changed.
Temperature Units
Atoll uses the temperature unit defined in the current Atoll document as display unit of the temperatures in the
dialogues and in the tables.
Degree Celsius is used as the internal measurement unit for the temperature in all Atoll documents whether they are
connected to databases or not. The internal measurement unit is not stored in the database and cannot be changed.
6.3 BSIC Format

Depending on the working environment, there can be either one or two types of BSIC formats. If you are working with
stand-alone documents, i.e., documents not connected to databases, there is only one BSIC format:
◼ Display BSIC format
If you are working in a multi-user environment, Atoll uses two types of formats:
◼ Display BSIC format for the Atoll document
◼ Internal BSIC format for the database
The display format is used for the display in dialogs and tables. You can set the display format for your document
from the Transmitters folder’s context menu.
The internal format is the BSIC format stored in a database. The BSIC format set by the administrator in the central
Atoll project is stored in the database when the database is created, and cannot be modified by users. Only the
administrator can modify the internal format manually by editing the corresponding entry in the Units tables. All Atoll
documents opened from a database will have the internal format of the database as their default BSIC format.
Users working on documents connected to a database can modify the format in their documents locally, and save
this change in their documents, but they cannot modify the format stored in the database.

+ Atoll expects the BSIC format in the database to be the octal format. If that is not
the case, do the following:
In the Atoll database, update the setting of UNITS.BSIC_FORMAT to 1.
In your ATL project (and in any ATL project created from the previous database
configuration), go to the Parameters tab, select GSM Network Settings > BSICs >
Format > Octal and save the ATL file.

AT340_AM_E3 Chapter 7: Atoll File Formats
7 Atoll File Formats

Radio network data in Atoll includes the following, depending on the technology used in the network being planned:
◼ Site: The geographic location of transmitters (sectors, installed antennas, other equipment). A site can have
one or more transmitters.
◼ Antenna: The radiation patterns and gains for antennas installed at transmitters.
◼ Transmitter: A group of radio devices installed at a site with there transmission/reception characteristics
(antennas, feeders, TMAs, other equipment). A transmitter can have one or more cells or subcells.
◼ Cell: An RF carrier available at a transmitter in UMTS, CDMA2000, TD-SCDMA, LTE, WiMAX, and Wi-Fi
networks. A cell is fully defined by the "transmitter-carrier" pair. Each cell in these networks is independent, i.e.,
has its own identifier, power levels, performance characteristics.
◼ TRX: An RF carrier available at a transmitter in GSM networks. A transceiver (TRX) can carry one ARFCN which
can correspond to the BCCH (7 traffic timeslots) or TCH (8 traffic timeslots).
◼ Subcell: A subcell is a group of TRXs with the same radio characteristics. A subcell is fully defined by the
"transmitter-TRX type" pair.
◼ Base station: This is the generic name for a cell site ("site-transmitter-cell" or "site-transmitter-subcells").
Technology-specific names can be BTS, Node-B, eNode-B, etc.
◼ RF repeater: An RF repeater receives, amplifies, and retransmits RF carriers both in downlink and uplink. The
repeater receives signals from a donor transmitter which it retransmits using a coverage-side antenna with
amplification.
◼ Remote antenna: Transmitter antennas located at a remote location with respect to the transmitter’s site.
◼ Microwave link: A point-to-point link using microwave frequencies used for backhaul in radio access networks
or for fixed wireless access.
◼ PMP microwave link: A group of microwave links originating from a common node to serve more than one
location.
◼ Passive microwave repeater: A passive microwave repeater receives and retransmits microwave signals
without amplification. Passive repeaters do not have power sources of their own. Active repeaters, on the
other hand, amplify the received signal. Reflectors are examples of passive repeaters.
◼ "Geographic Data Files" on page 83
◼ "Path Loss Matrix File Format" on page 89
◼ "Path Loss Tuning File Format" on page 93
◼ "Interference Matrix File Formats" on page 94
◼ ""Per Transmitter" Prediction File Format" on page 101
7.1 Geographic Data Files

Atoll supports multiple types of geographic data, including DTM (Digital Terrain Model), clutter, scanned images,
vector data, traffic maps, population, and custom geographic data. Atoll offers import/export filters for the most
commonly used geographic data formats.
The following tables summarise the supported vector/raster formats.

Chapter 7: Atoll File Formats
"Raster and Vector" Formats
Geographic Data Types

Import Georeferencing
File Format Clutter Clutter Raster Popula- Web Map
Export DTM Traffic Maps (World File)
Classes Heights Images tion Services
Atoll Geo Data Both User profile densities Vector Embedded

(AGD) Sector traffic maps
Planet Both 16-bit 16-bit 16-bit User profile density 1, 4, 8, 24- Index file
Sector traffic maps bit
User profile raster
(16-bit)
User density raster
(16-bit)
"Vector" Formats

SHP Both User profile density Vector

Sector traffic maps
MapInfo Both User profile density Vector

(MIF, TAB) Sector traffic maps
"Raster" Formats

BIL Both 8, 16, 32- 8-bit 8, 16, 32- User profile raster (8- 1, 4, 8, 24- 8, 16, 32- HDR file
bit bit bit) User density ras- bit bit
ter (16, 32-bit)
TIFF Both 8, 16-bit 8-bit 8, 16-bit User profile raster (8- 1, 4, 8, 24- 8, 16, 32- Yes TFW file
bit), User density ras- bit bit
ter (16, 32-bit)
BMP Both 8-bit 8-bit 8-bit User profile raster (8- 1, 4, 8, 24- 8, 32-bit Yes BPW or BMW file
bit) User density ras- bit
ter (16, 32-bit)
DXF Import User profile density Embedded

Sector traffic maps
Erdas Imagine Import 8, 16, 32- 8-bit 8, 16, 32- User profile raster (8- 1, 4, 8, 24- 8, 16, 32- Embedded
(IMG) bit bit bit) bit bit
User density raster
(16, 32-bit)
ArcView ASCII Export ASCII ASCII ASCII ASCII ASCII ASCII Embedded
Grid (TXT)
Vertical Map- Both GRD GRC GRD User profile raster Raster Vector Embedded
per User density raster Images
(GRD, GRC)
ECW Import 24-bit ERS file
PNG Both All Yes PGW file
JPEG Both All Yes JGW file

 World files (e.g. TFW, BPW) are header files used for the georeferencing of raster
files. See next sections for more information on World file types generated by Atoll.
The smallest supported resolution for raster files is 1 m. There is no restriction on
the resolution of images.
DTM, clutter classes, and clutter height maps must have an integer resolution.
All the raster maps you want to import in an ATL document must be represented in
the same projection system.
Specific header files are used to describe how data is organised within any of these geographic data file formats.
This section describes the following header file formats:
◼ "HDR Header File for BIL Files" on page 85
◼ "TFW Header File for TIFF Files" on page 87
◼ "BPW/BMW Header Files for BMP Files" on page 88
◼ "PGW Header File for PNG Files" on page 88
◼ "JGW Header File for JPG Files" on page 88
7.1.1 HDR Header File for BIL Files
7.1.1.1 HDR Header File

The HDR file is a text file that contains meta-data describing the organisation of the BIL file. The header file is made
of rows, each row having the following format:
keyword value
where ‘keyword’ corresponds to an attribute type, and ‘value’ defines the attribute value.
Keywords required by Atoll are described below. Other keywords are ignored.
ulxmap x coordinate of the centre of the upper-left pixel.

ulymap y coordinate of the centre of the upper-left pixel.
xdim x size in metre of a pixel.
ydim y size in metre of a pixel.
ncols Number of columns in the image.
nrows Number of rows in the image.
nbits Number of bits per pixel per band:
16 ou 32 for DTMs or clutter heights (altitude in metres).
8 for clutter classes file (clutter code).
16 for path loss matrices (path loss in dB).
32 for calculation results (field value in dBm, dBµV and DBµV/m).
nbands Number of spectral bands in the image:
1 for DTM, clutter heights, clutter classes, etc.
1 for any picture using a colour table.
3 for RGB pictures.
byteorder Byte order in which image pixel values are stored. Accepted
values are M (Motorola byte order) or I (Intel byte order).
layout Must be ‘bil’.
bandrowbytes Number of bytes per band per row.
totalrowbytes Total number of bytes of data per row.
skipbytes Byte to be skipped in the image file in order to reach the
beginning of the image data. Default value is 0.

Four additional keywords can optionally be managed.
pixeltype Type of data read (in addition to the length)
This can be:
SIGNEDINT Signed integer 8, 16, or 32 bits
FLOAT Real 32 or 64 bits
 If no pixeltype parameter is available, then the default value is UNSIGNEDINT (8, 16,
or 32 bits).
In some cases, this keyword can be replaced by datatype defined as follows:
datatype Type of data read (in addition to the length).
This can be:
Unumber Undefined number of bits (8, 16, or 32 bits)
Inumber Integer number of bits (8, 16, or 32 bits)
Rnumber Real number of bits (32 or 64 bits)
The other optional keywords are: valueoffset, valuescale, and nodatavalue.

By default, integer data types are chosen with respect to the pixel length (nbits).
valueoffset Real value to be added to the read value (Vread).

valuescale Scaling factor to be applied to the read value.
So, we have = V read  valuescale + valueoffse
nodatavalue Value corresponding to “NO DATA”.
DTM Sample
Here, the data is 20 m.
nrows 1500
ncols 1500
nbands 1
nbits 8 or 16
byteorder M
layout bil
skipbytes 0
ulxmap 975000
ulymap 1891000
xdim 20.00
ydim 20.00
Clutter Classes Sample
nrows 1500
ncols 1500
nbands 1
nbits 8
byteorder M

layout bil
skipbytes 0
ulxmap 975000
ulymap 1891000
xdim 20.00
ydim 20.00
7.1.1.2 Additional PRJ Projection File

When you export BIL files, Atoll will generate an additional PRJ projection file if the lines below are included in the
Atoll.ini file:
[RasterExport]
ExportBILAsESRI = 1 #default=0
Sample PRJ Projection File
984_UTM_Zone_31N",
GEOGCS["GCS_WGS_1984",
DATUM["D_WGS_1984",
SPHEROID["WGS_1984",6378137,298.257223563]],
PRIMEM["Greenwich",0],
UNIT["Degree",0.017453292519943295]],
PROJECTION["Transverse_Mercator"],
PARAMETER["latitude_of_origin",0],
PARAMETER["central_meridian",3],
PARAMETER["scale_factor",0.9996],
PARAMETER["false_easting",500000],
PARAMETER["false_northing",0],
UNIT["Meter",1]]
7.1.2 TFW Header File for TIFF Files
TFW files contain the spatial reference data of associated TIFF files. The TFW file structure is simple; it is an ASCII
text file that contains six lines. You can open a TFW file using any ASCII text editor. The TFW file structure is as
follows:
Line Description
1 x dimension of a pixel in map units
2 1 amount of translation
3 amount of rotation
4 negative of the y dimension of a pixel in map units
5 x-axis map coordinate of the centre of the upper-left pixel
6 y-axis map coordinate of the centre of the upper-left pixel
1. Atoll does not use the lines 2 and 3 when importing a TIFF format geographic file.
100.00
0.00
0.00
-100.00

60000.00
2679900.00
7.1.3 BPW/BMW Header Files for BMP Files
The header file is a text file that describes how organised in the BMP file. The header file is made of rows, each row
having the following description:
Line Description
2 amount of translation

Atoll supports BPW and BMW header file extensions for Import, but exports headers with BPW file extensions.
100.00
0.00
0.00
-100.00
60000.00
2679900.00
7.1.4 PGW Header File for PNG Files
A PNG world file (PGW file) is a plain text file used by geographic information systems (GIS) to provide
georeferencing information for raster map images in PNG format. The world file parameters are:
Line Description

7.1.5 JGW Header File for JPG Files
A JPEG world file (JGW file) is a plain text file used by geographic information systems (GIS) to provide
georeferencing information for raster map images in JPEG format. The world file parameters are:

Line Description
7.2 Path Loss Matrix File Format

When path loss matrices are stored externally, i.e., outside the ATL file, the path loss matrices folder contains a
‘pathloss.dbf’ file containing the calculation parameters of the transmitters and one LOS (path loss results) file per
calculated transmitter. The path loss matrices folder also contains a LowRes folder with another pathloss.dbf file
and one LOS (path loss results) file per transmitter that has an extended path loss matrix.
The formats of the pathloss.dbf and LOS files are described here.
7.2.1 Pathloss.dbf File Format
The pathloss.dbf file has a standard DBF (dBase III) format. The file can be opened in Microsoft Access, but it should
not be modified without consulting the Forsk customer support.
For general information, the format of DBF files in any Xbase language is as follows:
 Notations used in the following tables: FS = FlagShip; D3 = dBaseIII+; Fb = FoxBase;

D4 = dBaseIV; Fp = FoxPro; D5 = dBaseV; CL = Clipper
DBF Structure
Byte Description Remarks
0...n DBF header (see next part for size, byte 8)
n+1 1st record of fixed length (see next parts); 2nd record (see next part for size, byte10) …; last record If .dbf is not empty
last optional: 0x1a (eof byte)
DBF Header
The DBF header size is variable and depends on the field count.
Byte Size Contents Description Applies to
00 1 0x03 plain .dbf FS, D3, D4, D5, Fb, Fp, CL
0x04 plain .dbf D4, D5 (FS)

0x05 plain .dbf D5, Fp (FS)
0x43 with .dbv memo var size FS
0xB3 with .dbv and .dbt memo FS

0x83 with .dbt memo FS, D3, D4, D5, Fb, Fp, CL
0x8B with .dbt memo in D4 format D4, D5
0x8E with SQL table D4, D5

0xF5 with .fmp memo Fp
01 3 YYMMDD Last update digits All
04 4 ulong Number of records in file All
08 2 ushort Header size in bytes All
10 2 ushort Record size in bytes All
12 2 0,0 Reserved All
14 1 0x01 Begin transaction D4, D5
0x00 End Transaction D4, D5
0x00 ignored FS, D3, Fb, Fp, CL
15 1 0x01 Encrypted D4, D5
0x00 normal visible All
16 12 0 (1) multi-user environment use D4,D5
28 1 0x01 production index exists Fp, D4, D5
0x00 index upon demand All
29 1 n language driver ID D4, D5
0x01 codepage437 DOS USA Fp
0x02 codepage850 DOS Multi ling Fp
0x03 codepage1251 Windows ANSI Fp

0xC8 codepage1250 Windows EE Fp
30 2 0,0 reserved All
32 n*32 Field Descriptor (see next paragraph) all

+1 1 0x0D Header Record Terminator all
Field descriptor array in the DBF header (32 bytes for each field):
0 11 ASCI field name, 0x00 termin all
11 1 ASCI field type (see next paragraph) all
12 4 n,n,n,n Fld address in memory D3
n,n,0,0 offset from record begin Fp
0,0,0,0 ignored FS, D4, D5, Fb, CL
16 1 byte Field length, bin (see next paragraph) all \ FS,CL: for C field type
17 1 byte decimal count, bin all / both used for fld lng
18 2 0,0 reserved all
20 1 byte Work area ID D4, D5
0x00 unused FS, D3, Fb, Fp, CL
21 2 n,n multi-user dBase D3, D4, D5
0,0 ignored FS, Fb, Fp, CL
23 1 0x01 Set Fields D3, D4, D5
0x00 ignored FS, Fb, Fp, CL
24 7 0...0 reserved all
31 1 0x01 Field is in .mdx index D4, D5

Field type and size in the DBF header, field descriptor (1 byte):
Size Type Description/Storage Applies to
C 1...n Char ASCII (OEM code page chars) all

rest= space, not \0 term.
n = 1...64kb (using deci count) FS
n = 1...32kb (using deci count) Fp, CL
n = 1...254 all
D8 Date 8 ASCII digits (0...9) in the YYYYMMDD format all
F 1...n Numeric ASCII digits (-.0123456789) FS, D4, D5, Fp

variable pos. of float.point
n = 1...20
N 1...n Numeric ASCII digits (-.0123456789) all

fix posit/no float.point
n = 1...20 FS, Fp, CL
n = 1...18 D3, D4, D5, Fb
L1 Logical ASCII chars (YyNnTtFf space) FS, D3, Fb, Fp, CL
ASCII chars (YyNnTtFf?) D4, D5 (FS)
M 10 Memo 10 digits repres. the start block posit. in .dbt file, or 10 spaces if all
no entry in memo
V 10 Variable Variable, bin/asc data in .dbv FS

4bytes bin= start pos in memo
4bytes bin= block size
1byte = subtype
1byte = reserved (0x1a)
10 spaces if no entry in .dbv
P 10 Picture binary data in .ftp Fp
structure like M
B 10 Binary binary data in .dbt D5

structure like M
G 10 General OLE objects D5, Fp

structure like M
22 short int binary int max +/- 32767 FS
44 long int binary int max +/- 2147483647 FS
88 double binary signed double IEEE FS
Each DBF record (fixed length):
Byte Size Description Applies to
0 1 deleted flag "*" or not deleted " " All
1…n 1… x-times contents of fields, fixed length, unterminated. All

For n, see (2) byte 10…11
7.2.2 Pathloss.dbf File Contents
The DBF file provides information that is needed to check validity of each path loss matrix.

TX_NAME Text Name of the transmitter
FILE_NAME Text Name (and optionally, path) of .los file
MODEL_NAME Text Name of propagation model used to calculate path loss
MODEL_SIG Text Signature (identity number) of model used in calculations. You can check it in the propagation
model properties (General tab).
The Model_SIG is used for the purpose of validity. A unique Model_SIG is assigned to each
propagation model. When model parameters are modified, the associated model ID changes.
This enables Atoll to detect path loss matrix invalidity. In the same way, two identical prop-
agation models in different projects do not have the same model ID1.
ULXMAP Float X-coordinate of the top-left corner of the path loss matrix upper-left pixel
ULYMAP Float Y-coordinate of the top-left corner of the path loss matrix upper-left pixel
RESOLUTION Float Resolution of path loss matrix in metre
NROWS Float Number of rows in path loss matrix
NCOLS Float Number of columns in path loss matrix
FREQUENCY Float Frequency band
TILT Float Transmitter antenna mechanical tilt
AZIMUTH Float Transmitter antenna azimuth
TX_HEIGHT Float Transmitter height in metre
TX_POSX Float X-coordinate of the transmitter
TX_POSY Float Y-coordinate of the transmitter

ALTITUDE Float Ground height above sea level at the transmitter in metre
RX_HEIGHT Float Receiver height in metre
ANTENNA_SI Float Logical number referring to antenna pattern. Antennas with the same pattern will have the
same number.
MAX_LOS Float Maximum path loss stated in 1/16 dB. This information is used, when no calculation radius
is set, to check the matrix validity.
CAREA_XMIN Float Lowest x-coordinate of centre pixel located on the calculation radius2
CAREA_XMAX Float Highest x-coordinate of centre pixel located on the calculation radius
CAREA_YMIN Float Lowest y-coordinate of centre pixel located on the calculation radius
CAREA_YMAX Float Highest y-coordinate of centre pixel located on the calculation radius
WAREA_XMIN Float Lowest x-coordinate of centre pixel located in the computation zone3
WAREA_XMAX Float Highest x-coordinate of centre pixel located in the computation zone
WAREA_YMIN Float Lowest y-coordinate of centre pixel located in the computation zone
WAREA_YMAX Float Highest y-coordinate of centre pixel located in the computation zone
LOCKED Boolean Locking status

0: path loss matrix is not locked
1: path loss matrix is locked.
INC_ANT Boolean Atoll indicates if losses due to the antenna pattern are taken into account in the path loss
matrix.
0: antenna losses not taken into account
1: antenna losses included
1. In order to benefit from the calculation sharing feature, users must retrieve the propagation models from the same central
database. This can be done using the Open from database command for a new document or the Refresh command for an
existing one. Otherwise, Atoll generates different model_ID (even if same parameters are applied on the same kind of model)
and calculation sharing become unavailable due to inconsistency.
2. These coordinates enable Atoll to determine the area of calculation for each transmitter.
3. These coordinates enable Atoll to determine the rectangle including the computation zone.

7.2.3 LOS File Format
The LOS (path loss results) files are binary files with a standard row-column structure. Data are stored starting from
the southwest to the northeast corner of the area. The file contains 16-bit signed integer values in the range [-32768;
+32767] with a 1/16 dB precision. "No data" values are represented by +32767.
7.3 Path Loss Tuning File Format

Atoll can tune path losses calculated by propagation models using CW measurements or drive test Data. Path
losses are tuned by merging measurement data with propagation results on pixels corresponding to the
measurement points and the pixels in the vicinity. Path losses surrounding the measurement points are smoothed
for homogeneity.
Measuremment paths that are used for path loss tuning are stored as a catalogue in a folder containing a
pathloss.dbf file and one PTS (path loss tuning) file per transmitter. A tuning file can contain several measurement
paths.
For more information on the path loss tuning algorithm, see the Technical Reference Guide.
7.3.1 Pathloss.dbf File Format
See "Pathloss.dbf File Format" on page 89.
7.3.2 Pathloss.dbf File Contents
The DBF file provides information about the measured transmitters involved in the tuning.
FILE_NAME Text Name (and optionally, path) of .pts file
AREA_XMIN Float Not used
AREA_XMAX Float Not used
AREA_YMIN Float Not used

AREA_YMAX Float Not used
7.3.3 PTS File Format
The PTS (path loss tuning) files contain a header and the list of measurement points.
Header:
◼ 4 bytes: version
◼ 4 bytes: flag (can be used to manage flags like active flag)
◼ 50 bytes: GUID
◼ 4 bytes: number of points
◼ 255 bytes: original measurement name (with prefix "Num" for drive test data and "CW" for CW measurements)

◼ 256 bytes: comments

◼ 4 bytes: X_RADIUS
◼ 4 bytes: Y_RADIUS
◼ 4 bytes: gain = measurement gain - losses
◼ 4 bytes: global error
◼ 4 bytes: rx height
◼ 4 bytes: frequency
◼ 8 bytes: tx Position
List of measurement points:
◼ 4 bytes: X
◼ 4 bytes: Y
◼ 4 bytes: measurement value
◼ 4 bytes: incidence angle.
7.4 Interference Matrix File Formats

Interference matrices are used by GSM, LTE, and WiMAX AFPs (automatic frequency planning tools). Interference
matrices can be imported and exported using the following formats:
◼ GSM: CLC, IM0, IM1, IM2
◼ LTE and WiMAX: IM2, TXT, CSV
Interference matrix files must contain interference probability values between 0 and 1, and not in precentage
(between 0 and 100%). When interference matrix files are imported, Atoll does not check their validity and imports
interference probability values for loaded transmitters only.
In the following format descriptions and samples, lines starting with the "#" are considered as comments.
 In GSM interference matrices:

The interferer TRX type is not specified and is always considered to be BCCH.
Subcells have different powers defined as offsets with respect to the BCCH. For
subcells other than the BCCH, if the power offset of a subcell is X dB, then its
interference histogram will be shifted by X dB with respect to the BCCH interference
histogram.
If no power offset is defined on the interfered TRX type, it is possible to set "All".
For each interfered subcell-interferer subcell pair, Atoll saves probabilities for
several C/I values (6 to 24 values), including five fixed ones: –9, 1, 8, 14, and 22 dB.
Between two fixed C/I value, there can be up to three additional values (this number
depends on the probability variation between the fixed values). The C/I values have
0.5 dB accuracy and probability values are calculated and stored with an accuracy
of 0.002 for probabilities between 1 and 0.05, and with an accuracy of 0.0001 for
probabilities lower than 0.05.
7.4.1 CLC Format (One Value per Line)
The CLC format uses wo ASCII text files: a CLC file and a DCT file. Interference matrices are imported by selecting
the CLC file to import. Atoll looks for the associated DCT file in the same directory and uses it to decode transmitter
identifiers. If no DCT file is available, Atoll assumes that the transmitter identifiers are the transmitter names, and

the columns 1 and 2 of the CLC file must contain the names of the interfered and interfering transmitters instead of
their identification numbers.
7.4.1.1 CLC File Format

The CLC file consists of two parts. The first part is a header used for format identification. It must start with and
contain the following lines:
# Calculation Results Data File.

# Version 1.1, Tab separated format. Commented lines start with #.
The second part details interference histogram of each interfered subcell-interfering subcell pair. The lines after the
header are considered as comments if they start with "#". If not, they must have the following format:
<Column1><tab><Column2><tab><Column3><tab><Column4><tab><Column5><newline>
The 5 tab-separated columns are defined in the table below:
Column Name Description
Column1 Interfered transmitter Identification number of the interfered transmitter. If the column is empty, its
value is identical to the one of the line above.
Column2 Interfering transmitter Identification number of the interferer transmitter. If the column is null, its value
is identical to the one of the line above.
Column3 Interfered TRX type Interfered subcell. If the column is null, its value is identical to the one of the line
above. In order to save storage, all subcells with no power offset are not dupli-
cated (e.g. BCCH, TCH).
Column4 C/I threshold C/I value. This column cannot be null.
Column5 Probability C/I > Threshold Probability to have C/I the value specified in column 4 (C/I threshold). This field
must not be empty.
The columns 1, 2, and 3 must be defined only in the first line of each histogram.
Sample

# Remark: C/I results do not incorporate power offset values.
# Fields are:
##------------#------------#------------#-----------#------------------#
#| Interfered | Interfering| Interfered | C/I | Probability |
#| Transmitter| Transmitter| Trx type | Threshold | C/I >= Threshold |
##------------#------------#------------#-----------#------------------#
#
# Warning, The parameter settings of this header can be wrong if
# the "export" is performed following an "import". They
# are correct when the "export" follows a "calculate".
#
# Service Zone Type is "Best signal level of the highest priority HCS layer".
# Margin is 5.
# Cell edge coverage probability 75%.
# Traffic spreading was Uniform
##---------------------------------------------------------------------#
1 2 TCH_INNER 8 1
9 0.944
10 0.904

11 0.892
14 0.844
15 0.832
16 0.812
17 0.752
22 0.316
25 0.292
1 2 BCCH,TCH1 8 1
9 0.944
10 .904
13 0.872
14 0.84
17 0.772
1. If the TCH and BCCH histograms are the same, they are not repeated. A single record indicates that the histograms belong to
TCH and BCCH both.
7.4.1.2 DCT File Format

The .dct file is divided into two parts. The first part is a header used for format identification. It must start with and
# Calculation Results Dictionary File.

The second part provides information about transmitters taken into account in AFP. The lines after the header are
considered as comments if they start with "#". If not, they must have the following format:
<Column1><tab><Column2><newline>
Column Name Type Description
Column1 Transmitter name Text Name of the transmitter
Column2 Transmitter Identifier Integer Identification number of the transmitter

Column3 BCCH during calculation Integer BCCH used in calculations
Column4 BSIC during calculation Integer BSIC used in calculations
Column5 % of vic’ coverage Float Percentage of overlap of the victim service area
Column6 % of int’ coverage Float Percentage of overlap of the interferer service area
The last four columns describe the interference matrix scope. One transmitter per line is described separated with
a tab character.
Sample
# Calculation Results Dictionary File.

# Fields are:
##-----------#-----------#-----------#-----------#---------#---------#
#|Transmitter|Transmitter|BCCH during|BSIC during|% of vic'|% of int'|
#|Name |Identifier |calculation|calculation|coverage |coverage |
##-----------#-----------#-----------#-----------#---------#---------#
#


#
# Service Zone Type is "Best signal level per HCS layer".
# Margin is 5.
# Cell edge coverage probability is 75%.
# Traffic spreading was Uniform (percentage of interfered area)
##---------------------------#
Site0_0 1 -1 -1 100 100
Site0_1 2 -1 -1 100 100
Site0_2 3 -1 -1 100 100
Site1_0 4 -1 -1 100 100
Site1_1 5 -1 -1 100 100
Site1_2 6 -1 -1 100 100
Site2_0 7 -1 -1 100 100
Site2_1 8 -1 -1 100 100
7.4.2 IM0 Format (One Histogram per Line)
This file contains one histogram per line for each interfered/interfering subcell pair. The histogram is a list of C/I
values with associated probabilities.
The .im0 file consists of two parts. The first part is a header used for format identification. It must start with and

The second part details interference histogram of each interfered subcell-interferer subcell pair. The lines after the
<Column1><tab><Column2><tab><Column3><tab><Column4><newline>
Column1 Interfered transmitter Name of the interfered transmitter.
Column2 Interfering transmitter Name of the interferer transmitter.
Column3 Interfered TRX type Interfered subcell. In order to save storage, all subcells with no power offset are
not duplicated (e.g. BCCH, TCH).
Column4 C/I probability C/I value and the probability associated to this value separated by a space char-
acter. This entry cannot be null.
Sample

# Fields are:
#------------------------------------------------------------------------
#Transmitter Interferer TRX type {C/I Probability} values
#------------------------------------------------------------------------

#
#
# Margin is 5.
##---------------------------------------------------------------------#
#
Site0_2 Site0_1 BCCH,TCH-10 1 -9 0.996 -6 0.976 -4 0.964 -1 0.936
0 0.932 1 0.924 4 0.896 7 0.864 8 0.848
9 0.832 10 0.824 11 0.804 14 0.712 17 0.66
Site0_2 Site0_3 BCCH,TCH-10 1 -9 0.996 -6 0.976 -4 0.972 -1 0.948
0 0.94 1 0.928 4 0.896 7 0.856 8 0.84
11 0.772 13 0.688 14 0.636 15 0.608 18 0.556
Site0_3 Site0_1 BCCH,TCH-10 1 -9 0.996 -6 0.98 -3 0.948 0 0.932
1 0.924 4 0.892 7 0.852 8 0.832 9 0.816
10 0.784 11 0.764 14 0.644 15 0.616 18 0.564
Site0_3 Site0_2 BCCH,TCH-9 1 -6 0.972 -3 0.964 -2 0.96 0 0.94
1 0.932 4 0.904 7 0.876 8 0.86 9 0.844
11 0.804 13 0.744 14 0.716 15 0.692 18 0.644
7.4.3 IM1 Format (One Value per Line, TX Name Repeated)
This file contains one C/I threshold and probability pair value per line for each interfered/interfering subcell pair. The
histogram is a list of C/I values with associated probabilities.
The .im1 file consists of two parts. The first part is a header used for format identification. It must start with and

The second part details interference histogram of each interfered subcell-interferer subcell pair. The lines after the
<Column1><tab><Column2><tab><Column3><tab><Column4><tab><Column5><newline>
Column1 Interfered transmitter Name of the interfered transmitter.
Column2 Interfering transmitter Name of the interferer transmitter.

Column3 Interfered TRX type Interfered subcell. In order to save storage, all subcells with no power offset are
not duplicated (e.g. BCCH, TCH).
Column4 C/I threshold C/I value. This column cannot be null.
Column5 Probability C/I > Threshold Probability to have C/I the value specified in column 4 (C/I threshold). This field
must not be empty.

Sample

# Fields are:
#------------------------------------------------------------------------
#Transmitter Interferer TRX type C/I Probability
#------------------------------------------------------------------------
#
#
# Margin is 5.
##---------------------------------------------------------------------#
Site0_2 Site0_1 BCCH,TCH -10 1
Site0_2 Site0_1 BCCH,TCH -9 0.996
Site0_2 Site0_1 BCCH,TCH 0 0.932
...
7.4.4 IM2 Format (Co- and Adjacent-channel Probabilities)
IM2 files contain co-channel and adjacent-channel interference probabilities for each interfered transmitter –
interfering transmitter pair. In GSM, there is only one set of values for all the subcells of the interfered transmitter.
Each line must have the following format:
<Column1><SEP><Column2><SEP><Column3><SEP><Column4><newline>
Where the separator (<SEP>) can either be a tab or a semicolon.

The four columns are defined in the table below:
Column1 Interfered transmitter Name of the interfered transmitter
Column2 Interfering transmitter Name of the interferer transmitter
Column3 Co-channel probability Co-channel interference probability
Column4 Adjacent-channel probability Adjacent channel interference probability

Sample

# Fields are:
#------------------------------------------------------------------------
#Transmitter Interferer Co-channel Adjacent channel
#------------------------------------------------------------------------
#
#
# Margin is 5.
##---------------------------------------------------------------------#
Site0_2 Site0_1 0.226667 0.024
Site0_2 Site0_3 0.27 0.024
Site0_3 Site0_1 0.276 0.02
Site0_3 Site0_2 0.226 0.028
The columns in the sample above are separated with a tab. These columns can also be separated with a semilcolon:
Site0_2;Site0_1;0.226667;0.024
Site0_2;Site0_3;0.27;0.024
Site0_3;Site0_1;0.276;0.02
Site0_3;Site0_2;0.226;0.028
7.4.5 MNU Format
An MNU file is used for importing clutter classes or raster traffic files in TIFF, BIL, and IMG formats. It gives the
mapping between the clutter or traffic class code and the class name. It is a text file with the same name as the
clutter or traffic file with MNU extension. It must be stored at the same as the clutter or traffic file. It has the same
structure as the menu file used in the Planet format.
Class code Integer (>0) Identification code for the clutter (or traffic) class
Class name Text (50) Name of the clutter (or traffic) class. It can contain spaces.
Either space or tab can be used as the separator.

An MNU file associated to a clutter classes file:
0 none
1 open
2 sea
3 inland_water

4 residential
5 meanurban
7.5 "Per Transmitter" Prediction File Format

When a coverage prediction is calculated by value intervals it is stored externally, i.e., outside the ATL file. A
corresponding ’<doc_name>\{<GUID>}’ folder is actually created where the ATL document is located, as soon as the
latter is saved.
The calculation of the coverage prediction is either global or "per transmitter".
◼ When the calculation is global, the results are stored in two files for the entire prediction: one HDR file and one
BIL file (both identified by the prediction name).
◼ When a calculation is "per transmitter", one HDR file and one BIL file are created for each transmitter in the
prediction (both identified by the transmitter’s name). In some "per transmitter" predictions, an additional DBF
file is created for the entire prediction (identified by the prediction name). The DBF file contains information
on each transmitter and a pointer to each transmitter’s specific HDR and BIL files.
In LTE, when a Cell Identifier Collision Zones (DL) prediction is calculated by value intervals with the display
type set "No. of interferers per cell", the HDR file and the BIL file are created for each cell in the prediction (both
identified by the cell’s name).
The format and the content of the DBF file is described here.
 In both cases, an XML file describing the prediction is also created in the
corresponding ’<doc_name>\{<GUID>}’ folder.
7.5.1 <per_transmitter_prediction>.dbf File Format
The format of ‘<per_transmitter_prediction>.dbf’ files is identical to the format described in "Pathloss.dbf File
Format" on page 89.
7.5.2 <per_transmitter_prediction>.dbf File Contents
The ‘<per_transmitter_prediction>.dbf’ files generated in specific ’{<GUID>}’ folders provide information that is
needed to check the validity of each "per transmitter" prediction> calculated by value intervals.
FILE_NAME Text Name of the transmitter’s BIL result file
RESOLUTION Float Resolution of the calculation, same as ’xdim’ and ’ydim’ in the HDR file
AREA_XMIN Float Same as ’ulxmap’ in the HDR file
AREA_XMAX Float Same as ’ulxmap’ + ’xdim’ * ’ncols’ in the HDR file
AREA_YMIN Float Same as ’ulymap’ in the HDR file
AREA_YMAX Float Same as ’ulymap’ + ’ydim’ * ’nrows’ in the HDR file
NBITS Float Same as ’nbits’ in the HDR file
NBANDS Float Same as ’nbands’ in the HDR file
BYTE_ORDER Float Same as ’byteorder’ in the HDR file

BAND_ROW_BYTES Float Same as ’bandrowbytes’ in the HDR file
TOTAL_ROW_BYTES Float Same as ’totalrowbytes’ in the HDR file
SKIP_BYTES Float Same as ’skipbytes’ in the HDR file
DATA_TYPE Text Same as ’datatype’ in the HDR file
NO_DATA_VALUE Same as ’nodatavalue’ in the HDR file

AT340_AM_E3 Chapter 8: Administration and Usage Recommendations
8 Administration and Usage Recommendations

There are various ways that you can set up your environment to work with Atoll. This section provides a series of
recommendations that will help you optimise the performance and usage of the product.
◼ "Geographic Data" on page 103
◼ "Path Loss Matrices" on page 104
◼ "Atoll ATL Documents" on page 105
◼ "Databases" on page 106
◼ "Calculation Server" on page 106
◼ "Atoll Administration Files" on page 107
◼ "Process Memory" on page 108
◼ "Printing" on page 108
◼ "Coverage Prediction Calculations" on page 109
◼ "CW Measurements and Drive Test Data" on page 109
◼ "Antenna Patterns and Import" on page 109
◼ "Traffic Maps" on page 110
◼ "Atoll API" on page 110
◼ "Performance and Memory" on page 110
8.1 Geographic Data
Location of the Geographic Data

◼ In multi-user environments, it is recommended to place all the geographic data on a file server accessible to
all the users. This approach avoids the need to replicate the geographic data on all the workstations.
◼ Geographic data should either be located on each server or accessible through a fast network connection, e.g.,
1 Gbps.
◼ You can restrict access to the geographic data locations by assigning read/write access rights to
administrators and read-only rights to end-users.
Link or Embed
◼ Only embed geographic data in ATL files if you wish to make a portable document. In all other cases, it is
recommended to link geographic data files to the Atoll documents.
◼ It is recommended to set the paths to linked geographic data files using the Universal Naming Convention
(UNC).
Following the UNC, an absolute path, such as "C:\Program Files\Forsk\Geo Data\...", is represented as
"\\Computer\C\Program Files\Forsk\Geo Data\...", where "Computer" is the computer name, and "C" is the
share name of disk C.
Example:

Chapter 8: Administration and Usage Recommendations
Absolute Path C:\Program Files\Forsk\Geo Data\...
Relative Path \Program Files\Forsk\Geo Data\...
UNC Path \\Computer\C\Program Files\Forsk\Geo Data\...
If you define paths to geographic data files using UNC, Atoll will be able to keep track of the linked files even
if the Atoll document is moved to another computer.
Size of Tiles
◼ Some network planning tools require geographic data to be available in small tiles in order to work more
efficiently. For a country-wide project, this can lead to hundreds of files describing the geographic data. Atoll
is designed to optimise memory consumption, which enables it to perform efficiently with regional tiles (1 tile/
file per region). Merging small tiles to build a regional tile can improve performance greatly.
◼ The recommended file size is between 100 and 200 MB
◼ Erdas Imagine Pyramids files can be bigger.
◼ ECW files can be of any size (no limitations).
Recommended Formats
◼ In order to improve performance, it is recommended to use uncompressed DTM and clutter files, for example,
BIL files. Using compressed geographic data files, for example, compressed TIF or Erdas Imagine, can cause
performance reduction due to decompression of these files in real time. If you are using compressed
geographic data files, it is strongly recommended to:
◼ Either, hide the status bar that displays geographic data information in real time. You can hide the status
bar from the View menu.
◼ Or, disable the display of some of the information contained in the status bar, such as altitude, clutter class,
and clutter height using an option in the Atoll.ini file, see "Hiding Information Displayed in the Status Bar"
on page 172.
◼ The following table shows the recommended file formats for different geographic data:
Geographic data type Recommended file format
Scanned maps ECW
Vectors SHP
8.2 Path Loss Matrices
Shared Path Loss Matrices

Shared path loss matrices should be accessible through a fast network connection, e.g., 1 Gbps. These results are
accessed by Atoll during calculations, and should be available to user sessions through a fast network connection,
i.e., 30 Mbps at least per user session.
You can restrict access to the shared path loss matrices folder by assigning read/write access rights to
administrators and read-only rights to end-users.
Private Path Loss Matrices

Atoll synchronises the private path loss matrices with the shared path loss matrices. If private path loss matrices
are invalid, and the corresponding shared path loss matrices are valid, Atoll deletes the invalid private path loss
matrices and uses the shared ones. You can make Atoll verify and remove private path loss matrices, valid or invalid,
whose corresponding shared path loss matrices are valid. This can be useful for disk space management.
For more information, see "Synchronising Private and Shared Path Loss Matrices" on page 162.
Link or Embed
Only embed path loss matrices in ATL files if you wish to make a portable document. In all other cases, it is
recommended to link path loss matrices to the Atoll documents.

Externalising path loss matrices to shared or private path loss folders will keep the ATL file size reasonable, which
will result in less fragmentation. Externalising path loss matrices does not reduce the performance of display and
calculations in Atoll.
If you define paths to the private and shared path loss matrices folders using UNC, Atoll will be able to keep track
of the linked files even if the Atoll document is moved to another computer.
Calculating Path Loss Matrices in Multi-RAT Documents

When the path loss matrices in multi-RAT documents using the RunPathloss API function, the path loss matrices of
each technology are calculated simultaneously using the same number of threads. For example, if 4 threads are
used to calculate path loss matrices, and there are 3 technologies (GSM, UMTS, and LTE), a total of 12 threads will
be used to calculate the path loss matrices at the same time. This can lead to the following problems:
◼ Insufficient CPU resources
◼ Insufficient memory
◼ Insufficient licenses if external propagation models are used.
To avoid these problems when using the RunPathloss API function to calculate path loss matrices in multi-RAT
documents, use the following work-arounds:
◼ Use the Distributed Calculation Server, even locally.
◼ In your script or macro, deactivate the transmitters of the technologies for which you do not want to calculate
the path loss matrices and reactivate them afterwards. Repeat it for all technologies.
◼ Lower the number of threads using the NumberOfThreadsPathloss option in RemoteCalculation section in
Atoll.ini. For example, you can set the option to 2 to use a maximum of 6 threads (3*2) during path loss
calculation using the RunPathloss function.
 Resource saturation during the calculation of path loss matrices for multi-RAT
documents only occurs when using the RunPathloss API function in a macro or
script. When calculating path loss matrices for a multi-RAT document using Atoll,
this does not occur.
Allocating Memory to Prediction Calculations

When calculating predictions, Atoll divides the calculation zone into blocks that are processed successively. The
size of these blocks is determined by the amount of memory that is allocated to the process. A significant
performance gain can therefore be obtained by allocating more memory for calculating predictions, which reduces
the total number of blocks.
To specify the amount of memory that you want to allocate to prediction calculation in the Atoll.ini file, see
"Increasing the Memory Block Size for Predictions" on page 196.
8.3 Atoll ATL Documents
General
◼ It is recommended to define a rule for making backups of your Atoll ATL documents at regular intervals.
◼ Do not skip a major Atoll version. For example, if you are currently using Atoll 3.2, you should first upgrade the
ATL document to Atoll 3.3 before upgrading to Atoll 3.4.
Upgrading your document will be simpler if you do not skip a major version. If you skip or have skipped an
intermediate major version, you should upgrade your document twice in order to make it compatible with the
new version.

8.4 Databases
General
◼ In order to use Atoll with Oracle, you must create Oracle users and schema with names in uppercase.
◼ Create backups of the database before upgrading.
◼ It is recommended to define a rule for making backups of the database at regular intervals.
◼ Do not skip a major Atoll version. For example, if you are currently using Atoll 3.2, you should first upgrade the
database to Atoll 3.3 before upgrading to Atoll 3.4.
Upgrading your database will be simpler if you do not skip a major version. If you skip or have skipped an
intermediate major version, you must upgrade your database twice in order to make it compatible with the new
version.
Tables and Fields

◼ Table and field names are case sensitive.
◼ Table and field names should not be more than 30 characters long.
◼ Table and field names should only use alphanumeric characters (A-Z, a-z, 0-9) and underscores (_).
◼ Table and field names must not start with a numeric character (0-9).
◼ Table and field names must not contain an SQL or RDBMS-specific keyword, such as ORDER, DATE, etc.
◼ Table and field names must not contain spaces or special characters, such as periods (.), exclamation marks
(!), colons (:), semi-colons (;), interrogation marks (?), parentheses (()), brackets ({}), square brackets ([]), etc.
◼ Boolean fields, system or user-defined, should always have default values assigned.
◼ The CustomFields table enables you to define default values, choice lists, and read/write access for any field
in any table in Atoll, including user-defined fields that you add to the Atoll tables. The values defined in this
table have priority over the internal predefined default values. If you define floating point default values, make
sure that all the users have the same decimal separator.
◼ If you wish to add custom fields in the Atoll document, you should first add the field in the database, and then
update your Atoll document from the database.
◼ When setting up your database for the first time, try to anticipate user requirements in terms of custom fields
in Atoll tables. Some requirements of the different user groups can be satisfied if a few general-purpose user-
defined fields are added in Atoll tables when setting up the database.
For example, if you add three user-defined fields (one of type integer, float, and text (limited size)) to the Sites
and Transmitters tables, users will be able to use these for sorting, filtering, grouping, or other purposes. This
approach can help the database function a long time before users require the addition of other custom fields.
◼ To improve performance, if your projects allow it, reduce the size of the fields corresponding to the sites and
transmitters’ names.
◼ To improve performance, unless absolutely necessary, do not add user-defined fields of Text type. Rather, use
numeric field types, which allow sorting and other functions. If you must add Text fields, allocate them the
appropriate size that would suffice. For example, a 255-character long Text type field would, for the most part,
occupy disk space for no purpose.
◼ To improve performance, you should avoid adding custom fields to the neighbour management tables.
8.5 Calculation Server
Computation Server Stability and Resource Management

In certain conditions, as described below, Atoll users might experience a decrease in server performance and
stability in a multi-user Citrix environment. The principal difference observed might be the inability to run multiple
Atoll sessions on the server without getting error messages, general application failures, or server crashes. Such
problems can occur when the number of Atoll sessions on the server, carrying out calculations, increases to more
than four.

Causes of Instability and Loss of Performance

This general instability and low performance of the servers is due to:
◼ Insufficient memory resources: globally and per process (Atoll session)
◼ Insufficient CPU resources
◼ Network congestion
Atoll can process four simultaneous path loss matrices calculations, which means high CPU and RAM resource
consumption, and as path loss calculations share the amount of memory allocated to the Atoll session, the total
memory requirement can exceed the Microsoft Windows’ (32-bit editions) limit of 2 GB per process. This is
especially the case with large Atoll documents and propagation models that require considerable memory.
Troubleshooting and Solution

As the cause of this problem is resource saturation on the server, resource consumption should be controlled in
order to avoid memory and CPU overloading as follows:
◼ To reduce the impact of a large number of simultaneous path loss calculations, a Distributed Calculation
Server should be set up. Using the Distributed Calculation Server, path loss calculations can be performed
outside Atoll. Using the Distribution Calculation Server has the following advantages:
◼ Path loss calculations are limited to four parallel instances regardless of the number of Atoll sessions
running on the server. This notably improves the memory and CPU consumption.
◼ A queuing system, integrated in the Distributed Calculation Server, manages the calculation requests from
different Atoll sessions.
◼ A failover mechanism automatically switches and hands over the path loss calculations back to Atoll in
case a problem occurs.
◼ Path loss calculations are carried out by a separate process (AtollSvr), which has its own memory
allocation apart from Atoll, i.e., the amount of memory needed for calculations does not impacts the Atoll
memory allocation.
This set up can introduce considerable improvements in both the number of Atoll sessions per server and the
calculations. A server with four processors (eight threads with hyper-threading) can accommodate four
simultaneous path loss calculations and use the other four threads for Atoll sessions. Atoll’s interface will also be
more efficient and the overall processing time for various tasks will be improved.
 In order to prevent users from deactivating the use of the Distributed Calculation
Server, and hence bypassing the resource control procedure established above, the
Atoll.ini file should be set made read-only for end-users.
Apart from the above setup, you can also make some other system improvements:
◼ To avoid error messages caused by requesting a large number of files over the network, the following
Microsoft Windows registry parameter can be modified in order to dedicate more resources to network read/
write operations:
IRQSTACKSIZE should be set to 30 instead of 11, for example.
◼ To avoid ‘out of memory’ problems, the Pagefile size should be increased so that the server does not run out
of global memory when supporting more than 10 Atoll sessions simultaneously. This is different from the
2 GB per process limit. Virtual memory can be increased from 8 GB to 16 GB, for example.
◼ For 32-bit Windows operating systems, you can also increase the default Windows memory allocation limit
from 2 GB to 3 GB as explained in "Process Memory" on page 108.
8.6 Atoll Administration Files

There is no specific order in which configuration and initialisation files should be created or installed on Atoll
workstations and servers. It is sufficient to have these files created and placed in the right locations before running
Atoll to have the predefined configuration available for all workstations and servers.

If you have already configured these files for one installation, and you are setting up another installation, you can
copy these files to their respective locations on the new installation to have the exact configuration and set-up as
the first. If you do not copy these files, or create them, you will not have the same configuration of the new
installation, but apart from that you will be able to work with Atoll normally. These files are optional.
Initialisation File (INI)

It is highly recommended that the Atoll initialisation file be created and modified only by the administrator.
If you are using a central server, state the actual number of processors in the INI file.
For more information about initialisation options, see "Initialisation Files" on page 147.
User Configuration File (CFG)
Use Atoll to create these files and avoid modifying these files manually as human errors can create problems.
Uncheck image visibility to avoid loading unnecessary data in the memory.
You can set up your configuration files with Atoll in the following manner:
◼ A common configuration file that points to the geographic data, macros, and other common parameters in
your Atoll documents.
◼ Separate configuration files can be created for separate projects, which would store their respective coverage
prediction studies parameters, traffic information, and other technology-specific parameters.
◼ Separate configuration files based on, and for, different groups of users. These groups can be, for example,
for different regions, different radio technologies, or certain operations such as performing certain types of
coverage predictions, running the AFP, and so on.
For more information about CFG files, see "Configuration Files" on page 113.
Custom Predictions File

◼ Coverage prediction studies can easily be duplicated within Atoll. Before creating study templates, and the
XML studies file, make sure that this study template is aimed at serving a number of users. This means, avoid
creating study templates unless these will be needed for a long time by a number of users. You can use the
configuration files to store your created coverage prediction studies locally. And, you can also use the study
duplicate feature to create copies of existing coverage prediction studies.
8.7 Process Memory
32-bit Operating Systems

Atoll can support 3 GB address space on a properly configured 32-bit system. For more information, please refer to
the following URL: http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx (/3GB section
in “Memory Support and Windows Operating Systems”).
The following link provides information on how you can setup your Windows Server 2003 systems to activate the
3 GB switch at startup: http://technet.microsoft.com/en-us/library/bb124810.aspx.
64-Bit Operating Systems

The 64-bit editions of Microsoft Windows provide 4 GB of memory per process.
8.8 Printing
You should place different layers of geographic and radio data in a definite order when printing a project or a section
of the project. The following order should be followed:
1. Visible objects of the Data tab

All the visible objects of the Data tab are displayed above those in the Geo tab. However, it is strongly
recommended to place vector layers on the top of coverage prediction plots. You can do this by transferring
these vector layers to the Data tab using the context menu. For performance reasons, it is advised to place
vector layers on top of raster layers before printing a project. Sites and Transmitters must be on the very top,
above all other layers. You should place sites and sectors on the top, then vector layers, and then raster layers.
2. Unidimensional vectors (points)
3. Open polygonal vectors (lines, i.e., roads and other linear items, etc.)
4. Closed polygonal vectors (surfaces, i.e., zones and areas, etc.)
5. Multi-format maps (vector or raster maps, i.e., population, rain, generic maps, traffic, etc.)
6. Transparent raster maps (clutter class maps, etc.)
7. Non-transparent maps (images, DTM, clutter height maps, etc.)
8.9 Coverage Prediction Calculations

◼ If you do not want Atoll to calculate the shadowing margin during a coverage prediction, it is advised to clear
the Shadowing taken into account check box. This approach is more efficient in terms of performance than
selecting this option and setting the Cell edge coverage probability to 50%.
◼ To improve memory consumption and optimise the calculation times, you should set the display resolutions
of coverage predictions according to the precision required. The following table lists the levels of precision
that are usually sufficient:
Size of the coverage prediction Display resolution
City Center 5m
City 20 m
County 50 m
State 100 m
Country According to the size
8.10 CW Measurements and Drive Test Data

◼ It is recommended to use Fast Display in order to increase display speed. This option is available in the Display
tab of the Properties dialogues for CW Measurements and Drive Test Data folders. Although this approach
only displays measurement points as small squares, it can have a significant impact on performance
depending on the number of measurement points in the Atoll document.
◼ When performing a CW measurements drive test campaign, please follow the recommended procedure
described in the Measurements and Model Calibration Guide.
8.11 Antenna Patterns and Import

◼ Antenna names used in some tools, such as NetAct, can be different from those used in their corresponding
antenna files. To solve this issue, you can create a new file, named "Index", containing the list of antenna
names, which would in fact be the pattern (antenna file) names. You should place this file at the same location
as the antenna patterns (files). This will replace the antenna names with the new antenna names.

◼ Some Kathrein antenna pattern files might have names different from the antenna pattern names present
inside the file. You will have to replace the name of the pattern inside the file by the name of the pattern file
itself, in order to import these antennas correctly.
◼ A Planet Index file contains the path to and the name of each antenna file available. Creating such an Index
file when there are hundreds of antenna patterns available can be a difficult task. You can easily create the
index file from the Microsoft Windows command prompt. You can open the Command Prompt window by
selecting Start > Run, entering "cmd" and pressing ENTER. In the Command Prompt window, navigate to the
directory containing the antenna pattern files, enter the following command and press ENTER:
dir /b > Index
This will create a file called "Index" in the same directory as the antenna patter files containing a list of all the
antenna pattern file names, with one name per line. The file will also contain a line with its own name, so,
before importing this file into Atoll, you should use a text editor to remove the line containing the file name
"Index."
◼ The electrical tilt, which can be defined in the antenna properties dialogues in Atoll, is an additional electrical
downtilt. It might be redundant to define an additional electrical downtilt for antennas whose patterns already
include electrical tilt. Users should verify whether the antenna patterns of the antennas in their projects, do not
already include the effect of an electrical tilt.
8.12 Traffic Maps

◼ User profile environment-based traffic maps should only be used for a precision on traffic that is of the same
level as the statistical clutter available in a project.
◼ For higher precision on traffic data, you should use sector traffic maps or user density traffic maps. User
density traffic maps provide you with a means to define a density for each set of service, terminal type, and
mobility type.
◼ Sector traffic maps are best suited for traffic data issued by the OMC.
8.13 Atoll API

Correct functioning of Atoll when using Atoll through the API is guaranteed during interactive user sessions only.
Atoll is an application that requires creating tool bars, creating menus, reading user profile options from the
Windows’ registry, accessing printers, etc., even when it is accessed through the API. The same is true for add-ins
working with Atoll.
Even though it is possible to load and use Atoll when there is no user session open on a computer, its correct
functioning is not guaranteed. Unexpected errors can occur. Particularly, creating objects through CreateObject or
CoCreateInstance might fail.
Therefore, the correct functioning of Atoll requires an open user session on the computer.
8.14 Performance and Memory
Memory Refresh
◼ You can avoid memory fragmentation while working with Atoll documents by saving the Atoll document from
time to time, closing and restarting Atoll, and reopening the document.

This advice is applicable to any application running under Microsoft Windows because many common DLL
files are accessed by applications, and unloading and reloading these DLL files refreshes the memory
allocation.
◼ If you are working in a Citrix XenApp environment, you should restart your Citrix server every week or fortnight.
The exact time should be determined by the administrator depending on the state of the network (LAN).
◼ In certain cases, it might be more appropriate to start working on a completely fresh ATL file. If you have been
working on your existing ATL file for a long time, it might become unnecessarily large and might contain some
useless remains from your earlier operations, e.g., traces of records that no longer exist in the database, etc.
You can completely refresh your project by following these steps:
a. Open the existing ATL file in Atoll that you want to replace.
b. Create a CFG file from your existing ATL file with all the required information, e.g., geographic data set,
coverage prediction parameters, neighbour allocation parameters, etc. For more information, refer to
"Configuration Files" on page 113.
c. Close the old ATL file.
d. Create a new ATL from the database to create a fresh ATL file.
e. Import the CFG file in the new ATL file.
You now have a clean ATL file to work with, which has all the same information as the old ATL file, and takes
up less space on the hard disk, has less fragmented data, and improved performance.
Memory Allocation
◼ If you have to open several large ATL files simultaneously on the same computer, it is better to open each in
a separate Atoll session rather than to open them all in the same Atoll window. Each Atoll session on the same
computer has its own memory space allocated by the operating system. Each computer consumes a single
license token independent of the number of Atoll sessions opened simultaneously.
◼ For 32-bit Windows operating systems, you can also increase the default Windows memory allocation limit
from 2 GB to 3 GB as explained in "Process Memory" on page 108.
Storage
◼ To increase performance, it is strongly recommended to use a local storage device for path loss files,
preferably an SSD device.
◼ Coverage predictions calculated over large areas require more memory. If you are working on an Atoll ATL
document covering a large area, with coverage predictions calculated over the entire network, this document
will require more memory for loading all the coverage predictions. You can reduce memory consumption by
making copies of your Atoll document, and keeping a few coverage predictions in each copy. These ATL files
will be faster to load and work with compared to a single ATL file with all the coverage predictions.
Large coverage predictions can take up a considerable amount of memory even if they are not displayed on
the map.
◼ Externalise DTM, clutter, path loss matrices, and any other data that can be externalised, so that the ATL file
size does not become unnecessarily large.
Path Loss Calculation

◼ When calculating predictions, Atoll divides the calculation zone into blocks that are processed successively.
The size of these blocks is determined by the amount of memory that is allocated to the process. A significant
performance gain can therefore be obtained by allocating more memory, which reduces the total number of
blocks for a prediction. For more information, see "Increasing the Memory Block Size for Predictions" on
page 196.
◼ Before starting path loss calculation, verify that the calculation radii and resolutions assigned to the different
types of transmitters are consistent. For example, calculating path loss matrices of picocells over large
calculation radii would only waste memory and disk space.
◼ For calculating path loss matrices over large areas, you should use the dual resolution feature in Atoll. Define
short calculation radii and fine resolutions for the main path loss matrices, and large calculation radii and low
resolutions for extended path loss matrices. This approach decreases the calculation time significantly
compared to calculating just one matrix per transmitter using a fine resolution. The main path loss matrices
should be calculated using the same resolution as the resolution of the geographic data available. The
extended path loss matrices can be calculated using a lower resolution, e.g., twice the resolution of the
geographic data.

Regionalisation
◼ Use database regionalisation or site lists if you are working on smaller parts of a large network. Atoll loads
only the data necessary for your working area. If you load a large network, Atoll will load a lot of data that might
not be necessary all the time, such as the neighbour relation data.
Performance and Memory Issues in Co-planning Projects

Co-planning with Atoll requires that both technology documents be open in the same Atoll window at the same time.
However, loading, for example, a GSM and a UMTS document can cause memory saturation especially if the
documents contain large, country-wide networks. To decrease the amount of memory used by Atoll in such cases,
you can:
◼ Load vector layers in main document only. Loading vectors in the linked document is not necessary and only
consumes more memory.
◼ Avoid loading neighbours and custom fields which are not required. This can be performed by creating views
in the database.

AT340_AM_E3 Chapter 9: Configuration Files
9 Configuration Files
Configuration files can be used to store parameter and display settings. These files are optional, not required for
working with Atoll, but are useful means for making work easier.
This chapter describes the formats of these files in detail:
◼ User configuration files (UTF-8 encoded XML-format GEO or CFG files)
A user configuration file containing only the geographic data settings can be saved with a GEO extension. A
user configuration file containing the geographic data settings and other parameter settings can be saved
with a CFG extension.
User configuration files must be created using Atoll to ensure correct syntax and structure. It is possible to
edit the contents of these files in an XML editor and make changes if required (for example, to update the
paths to geographic data files). For more information on how to create and load user configuration files in
Atoll, see the User Manual.
These files can store:
◼ Geographic data settings
◼ Filtering, focus, computation, printing, and geographic export zones
◼ Map centre and zoom level
◼ Folder configurations
◼ List of coverage predictions in the Predictions folder and their settings
◼ Automatic neighbour allocation parameters
◼ Automatic frequency planning parameters (GSM GPRS EDGE documents)
◼ Automatic scrambling code allocation parameters (UMTS HSPA and TD-SCDMA documents)
◼ Automatic PN offset allocation parameters (CDMA2000 documents)
◼ Automatic OFDM resource allocation parameters (LTE, WiMAX, Wi-Fi)
◼ Microwave link parameters
◼ Full paths to macro files
 Projection and display coordinate systems are stored in the database, not in user
configuration files.
Simulation settings are not stored in user configuration files.
For more information on the contents of user configuration files, see "Contents of User Configuration Files"
on page 114.
A user configuration file can be automatically loaded when Atoll is run if:
◼ The file is identified in the command line parameter -Cfg "cfgfilename" (see "Atoll Command Line
Parameters" on page 26 for more information), or
◼ The file is named "Atoll.cfg" and is located in the Atoll installation folder. This file will be ignored if a user
configuration file is loaded through the command line parameter.
◼ Additional configuration files (UTF-8 encoded XML-format CFG files or plain text INI files)
The following parameter settings can be stored in additional configuration files with a CFG extension:
◼ Print setup configuration
◼ Table import/export configuration
◼ Coverage prediction report configuration

Chapter 9: Configuration Files
The following parameter settings can be stored in specific INI files:

◼ CW measurement import configuration
◼ Drive test data import configuration
For more information on the contents of additional configuration files, see "Contents of Additional
Configuration Files" on page 141.
◼ Custom predictions file (UTF-8 encoded XML files)
This file (one for all customised predictions) contains the list and parameter settings of customised coverage
predictions. By default, t
A studies.xml file can be automatically loaded when Atoll is run if:
◼ The file is identified in the command line parameter -Stu "studiesfilename" (see "Atoll Command Line
Parameters" on page 26 for more information), or
◼ The file is named "Studies.xml" and is located in the Atoll installation folder. This file will be ignored if a user
configuration file is loaded through the command line parameter.
The custom predictions file must be created using Atoll to ensure correct syntax and structure. It is possible
to edit the contents of this file in an XML editor and make changes if required. For more information on
working with customised predictions in Atoll, see the User Manual.
For more information on the contents of the custom predictions file, see "Content of the Custom Predictions
File" on page 145.
◼ Predictions files calculated by Value Intervals (UTF-8 encoded XML files)
These files (one per prediction) contain the parameter settings of the coverage predictions calculated with the
display type (on the General tab of the Properties dialog box) set to "Value intervals". By default, these files
are named "<prediction_name>.XML" and are located in
"C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}".
9.1 Contents of User Configuration Files

The descriptions and examples provided below for each parameter set can help understand the format and function
of the user configuration files. The following details are available:
◼ "Geographic Data Set" on page 114
◼ "Map Centre and Zoom Level" on page 119
◼ "Zones" on page 118
◼ "Folder Configuration" on page 119
◼ "Coverage Predictions" on page 127
◼ "Automatic Neighbour Allocation Parameters" on page 129
◼ "Automatic Frequency Planning Parameters" on page 131
◼ "Automatic Scrambling Code Allocation Parameters" on page 132
◼ "Automatic PN Offset Allocation Parameters" on page 134
◼ "Microwave Radio Links Parameters" on page 137
◼ "Macros" on page 140.
9.1.1 Geographic Data Set
The following parameters are saved for various geographic data types:
◼ <DegreeFormat>: Format used to display degrees, minutes, and seconds for geographic coordinate systems
◼ Population, geoclimatic parameters, vector traffic maps, and other vector layers:

◼ <Name>: Name of the folder

◼ <Display>: (Different combinations of the following parameters exist in different display settings.)
◼ Display type <type>, selected field <FieldSelector>, field description <FieldDesc> containing <FieldId>
(same as <FieldSelector>) and <FieldTitle>, visibility flag <visible>, and visibility range between
<minZoom> and <maxZoom>
◼ <SymbolFont> properties, such as: font name <Name>, font size <Size>, font colour <Color>, background
colour <BackColor>, and font style <Style>
◼ <LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour
<Color>, label font background colour <BackColor>, and label font style <Style>
◼ <Items> properties, such as for each item: <Value>, <Min>, <Max>, <Legend>, <MainColor>,
<SecondaryColor>, <LineStyle>, <LineWidth>, and <FillStyle>
◼ <AddToLegend>: Add to legend option checked or not
◼ <Type>: Data type properties, such as <Name>, <Formats>, <Type>, and <Integrable>
◼ <File>: Contains the file format, path, coordinate system information.
◼ <Format> of and <Path> to linked files, if any
◼ Coordinate system information for vector format data including: <CoordinateSystemName>,
<CoordinateSystemCode>, <EllipsoidCode>, <EllipsoidMajorRadius>, <EllipsoidMinorRadius>,
<DatumCode>, <DatumShiftX>, <DatumShiftY>, <DatumShiftZ>, <DatumRotationX>, <DatumRotationY>,
<DatumRotationZ>, <DatumScaleFactor>, <ProjectionMethod>, <ProjectionZone>,
<ProjectionLongitudeOrigin>, <ProjectionLatitudeOrigin>, <ProjectionFalseEasting>,
<ProjectionFalseNorthing>, <ProjectionScaleFactor>, <ProjectionFirstParallel>,
<ProjectionSecondParallel>, and <ProjectionAngle>
◼ Clutter Classes:
◼ Displate type <type>, selected field <FieldSelector>, field description <FieldDesc> containing <FieldId>
(same as <FieldSelector>) and <FieldTitle>, transparency level <Opacity>, visibility flag <visible>, and
visibility range between <minZoom> and <maxZoom>
◼ <Attributes>, such as: <records> and <fields>, which are,
◼ Common: CODE, COLOR, NAME, HEIGHT, INDOOR
◼ Under <GSM>: STDDEV, COVERI_STDDEV, TX_DIV_GAIN, ANT_HOP_GAIN
◼ Under <UMTS>: STDDEV, EC_IO_STDDEV, EB_NT_DL_STDDEV, EB_NT_UL_STDDEV, ALPHA, FORTHO,
SM_GAIN_FACTOR, STTD_GAIN_OFFSET
◼ Under <LTE>: STDDEV, COVERI_STDDEV, MIMO_GAIN_FACTOR, DIV_GAIN_OFFSET_DL,
DIV_GAIN_OFFSET_UL
◼ Under <1XRTT>: STDDEV, EC_IO_STDDEV, EB_NT_DL_STDDEV, EB_NT_UL_STDDEV, ALPHA, FORTHO
◼ Under <TD-SCDMA>: STDDEV, EC_IO_STDDEV, EB_NT_DL_STDDEV, EB_NT_UL_STDDEV, FORTHO_UL,
FORTHO_DL, ANGULAR_SPREAD
◼ Under <IEEE_802.16e>: STDDEV, COVERI_STDDEV, MIMO_GAIN_FACTOR, STTD_OFFSET_DL,
STTD_OFFSET_UL
◼ Under <Wi-Fi>: STDDEV, COVERI_STDDEV, MIMO_GAIN_FACTOR, STTD_OFFSET_DL, STTD_OFFSET_UL
◼ <DefaultValues>, for the fields stated above.
◼ Clutter Heights and Digital Terrain Models:
(same as <FieldSelector>) and <FieldTitle>, transparency level <opacity>, visibility flag <visible>, and
visibility range between <minZoom> and <maxZoom>

◼ <File>: <Format> and <Path> to linked files, if any
Sample
Sample with display set to value intervals.
<?xml version="1.0" encoding="UTF-8"?>

<Atoll>
<Geodataset version="2">
<DegreeFormat>0</DegreeFormat>
<Population> // or <GeoClimaticParams> or <Vectors>
<Name>Population</Name> // or <Name>Geoclimatic Parameters</Name>
or <Name>Vectors</Name>
<Display>
<minZoom>500</minZoom>
<maxZoom>20000000</maxZoom>
<visible>Yes</visible>
<Type>ByIntervals</Type>
<FieldSelector>80000001</FieldSelector>
<FieldDesc>
<FieldId>80000001</FieldId>
<FieldTitle>Population (inhab./km²)</FieldTitle>
</FieldDesc>
<SymbolFont>
<Name>Wingdings</Name>
<Size>-120</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</SymbolFont>
<LabelFont>
<Name>MS Shell Dlg</Name>
<Size>-83</Size>
<Style>0</Style>
</LabelFont>
<Items>
<Item>
<Min>900.</Min>
<Max>1000.</Max>
<Legend>900 <=Population(Density) <1 000</Legend>
<MainColor>255 96 0</MainColor>
<SecondaryColor>255 0 0</SecondaryColor>
</Item>
</Items>
</Display>
<AddToLegend>0</AddToLegend>

<Type>
<Name>Population</Name>
<Formats>15</Formats>
<Type>800</Type>
<Integrable>1</Integrable>
</Type>
<Files/>
</Population> // or </GeoClimaticParams> or </Vectors>
<ClassifiedClutter UseOnlyDefault="0">
<Display>
<FieldDesc>
<FieldTitle>Height (m)</FieldTitle>
</FieldDesc>
<Opacity>50</Opacity>
<Items>
<Item>
<Min>54.</Min>
<Max>56.</Max>
<Legend>54 <=Height (m) <56</Legend>
<LineStyle>5</LineStyle>
<LineWidth>10</LineWidth>
<FillStyle>1</FillStyle>
</Item>
</Items>
</Display>
<Attributes>
<fields>
<field length="1" type="uint" name="CODE"/>
<field length="4" type="int" name="COLOR"/>
<field length="50" type="text" name="NAME"/>
<field length="4" type="real" name="HEIGHT"/>
<field length="2147483647" type="text" name="INDOOR"/>
</fields>
<records/>
</Attributes>
<Name>Clutter Classes</Name>
<DefaultValues>
</DefaultValues>
</ClassifiedClutter>
<Altitudes> // or <BuildingHeights>

<Name>Digital Terrain Model</Name> // or <Name>Clutter Heights</Name>

<Display>
<FieldDesc>
<FieldTitle>Altitude</FieldTitle>
</FieldDesc>
<Items>
<Item>
<Min>900.</Min>
<Max>1000.</Max>
<Legend>900 <=Altitude <1 000</Legend>
</Item>
</Items>
</Display>
</Altitudes> // or </BuildingHeights>
</Geodataset>
</Atoll>
9.1.2 Zones
The user configuration files store the coordinates of the vertices of the filtering, focus, computation, printing, and
geographic export zone polygons, i.e., the points forming these polygons. The first and the last points have the same
coordinates.
Sample
The following sample has rectangular computation and focus zones of the same size.

<Atoll>
<CalculationZone>
<Point>35950.000000 -15445.000000</Point>
<Point>33.000000 -15445.000000</Point>
<Point>33.000000 -33.000000</Point>
<Point>35950.000000 -33.000000</Point>
<Point>35950.000000 -15445.000000</Point>
</CalculationZone>

<FocusZone>
<Point>35950.000000 -15445.000000</Point>
<Point>33.000000 -15445.000000</Point>
<Point>33.000000 -33.000000</Point>
<Point>35950.000000 -33.000000</Point>
<Point>35950.000000 -15445.000000</Point>
</FocusZone>
<Atoll>
9.1.3 Map Centre and Zoom Level
The following parameters are saved:

◼ <MapPosition>: X and Y coordinates of the centre of the map window and the zoom level.
Sample

<Atoll>
<MapPosition CenterX="609433" CenterY="5632019" Scale="250000"/>
</Atoll>
9.1.4 Folder Configuration
The following parameters are saved for the following folders:

◼ Sites folder:
◼ <Display>:
(same as <FieldSelector>) <FieldTitle> and <FieldDBName>, visibility flag <Visible>, and visibility range
between <MinZoom> and <MaxZoom>
◼ <SymbolFont> properties, such as font name <Name>, font size <Size>, font colour <Color>, background
◼ <LabelFont> properties, such as label font name <Name>, label font size <Size>, label font colour
◼ <Items> properties, such as for each <Item>: <Value>, <Legend>, <MainColor>, <SecondaryColor>,
<Symbol>, and <SymbolSize>
◼ <DataTips>: List of <items> displayed in tip texts
◼ <Labels>: List of <items> displayed in labels
◼ <DefaultConfiguration>: The default configuration for the folder, this tag contains the default configuration
<Filter>, <Groups>, and <Sort> criteria
◼ <Configuration>: If any configuration exists for the folder, this tag contains the configuration <Name> and
the <Filter>, <Groups>, and <Sort> criteria
◼ Antennas folder:

◼ Transmitters, Multi-Hops, and Point to Multipoint folders:
◼ <Display>:
◼ Displate type <Type>, selected field <FieldSelector>, field description <FieldDesc> containing <FieldId>
(same as <FieldSelector>) <FieldTitle> and <FieldDBName>, visibility flag <Visible>, and visibility range
between <MinZoom> and <MaxZoom>
◼ <LabelFont> properties, such as label font name <Name>, label font size <Size>, label font colour
◼ <Items> properties, such as for each <Item>: <Value>, <Legend>, <MainColor>, <SecondaryColor>,
<Symbol>, and <SymbolSize>
◼ <OFDM_AFP>: LTE, WiMAX, and Wi-Fi frequency allocation constraint weights:
◼ <Techno>: Name of the technology
◼ <NeighbourWeight>: Weight of the first order neighbour relation
◼ <InterNeighbourWeight>: Weight of the relation between two neighbours of a common cell
◼ <IMWeight>:Weight of the interference matrices relation
◼ <DistanceWeight>: Weight of the distance-based relation
◼ <PCI_Alloc>: LTE physical cell ID allocation constraint weights:
◼ <SecondNeighbourWeight>: Weight of the second order neighbour relation
◼ <IDWeight>: Weight of the physical cell ID constraint
◼ <PSSWeight>: Weight of the PSS ID constraint
◼ <SSSWeight>: Weight of the same SSS ID per site constraint
◼ <ULDMRSSGWeight>: Weight of the UL DMRS (PCI Mod 30) collision constraint
◼ <DLRSSCaWeight>: Weight of the single antenna port DL CRS (PCI Mod 6) collision constraint
◼ <PCFICHREGWeight>: Weight of the PCFICH REG (PCI Mod (N_RB/2)) collision constraint
◼ <PI_Alloc>: WiMAX preamble index allocation constraint weights:
◼ <SecondNeighbourWeight>: Weight of the second order neighbour relation
◼ <IndexWeight>: Weight of the preamble index constraint
◼ <SegmentWeight>: Weight of the segment constraint
◼ <PermBaseWeight>: Weight of the same cell permbase per site constraint
◼ Links folder:

◼ <Display>: Contains visibility flag <visible>, and visibility range between <minZoom> and <maxZoom>
◼ <DefaultConfiguration>: The default configuration for the folder
◼ <LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>,
label font background colour <BackColor>, and label font style <Style>
◼ <SiteDisplay> properties, such as:
◼ <Symbol>: Symbol used for microwave links
◼ <ShowText>: Caption for microwave links shown or not
◼ <RepeaterDisplay> properties, such as:
◼ CW Measurements folder:
◼ <Distance>: The minimum <Min> and maximum <Max> distance for measurement filtering
◼ <DistanceUnit>: The distance unit
◼ <Measure>: The minimum <Min> and maximum <Max> measured level for filtering
◼ <MeasureUnit>: The measurement unit
◼ <Angle>: The minimum <Min> and maximum <Max> angle for measurement filtering
◼ <Relative>: Whether the angle is relative to each transmitter’s azimuth or an absolute value
◼ <Clutter>: For each <Class>, its <Code> and whether it is in the <Filter> or not
◼ <Advanced>: Any advanced filter used for filtering
◼ <PathLosses>: Path loss tuing parameters, i.e., <ParallelAxisRadius>, <PerpendicularAxisRadius>,
<GlobalMargin>, <LocalMargin>, and <Threshold>
◼ <Display>:
◼ Displate type <Type>, selected field <FieldSelector>, visibility flag <Visible>, and visibility range between
<MinZoom> and <MaxZoom>
◼ <Items> properties, such as for each <Item>: <Legend>, <MainColor>, <SecondaryColor>, <Symbol>, and
<SymbolSize>
◼ Drive Test Data folder:
◼ <Techno>: Name of the technology (if exported from a 3GPP Multi-RAT document.
◼ <Clutter>: For each <Class>, its <Code> and whether it is in the <Filter> or not
◼ <Advanced>: Any advanced filter used for filtering
◼ <PathLosses>: Path loss tuing parameters, i.e., <ParallelAxisRadius>, <PerpendicularAxisRadius>,
<GlobalMargin>, <LocalMargin>, and <Threshold>
◼ <Display>:
◼ Displate type <Type>, selected field <FieldSelector>, visibility flag <Visible>, and visibility range between
<MinZoom> and <MaxZoom>

◼ <Items> properties, such as for each <Item>: <Legend>, <MainColor>, <SecondaryColor>, <Symbol>, and
<SymbolSize>
◼ Propagation Models and Smart Antenna Models folders:
Sample

<Atoll>
<FoldersConfigurations>
<Sites>
<Name>Sites</Name>
<Display>
<Type>ByValues</Type>
<FieldDesc>
<FieldTitle>Vendor</FieldTitle>
</FieldDesc>
<SymbolFont>
<Size>-120</Size>
<Style>32</Style>
</SymbolFont>
<LabelFont>
<Size>-80</Size>
<Style>33</Style>
</LabelFont>
<Items>
<Item>
<Value>Vendor</Value>
<Legend>Vendor</Legend>


<Symbol>164</Symbol>
<SymbolSize>120</SymbolSize>
</Item>
</Items>
<DataTips>
<Item>0</Item>
</DataTips>
<Labels>
<Item>0</Item>
</Labels>
</Display>
<DefaultConfiguration>
<Groups>Type</Groups>
</DefaultConfiguration>
</Sites>
<Antennas>
<Name>Antennas</Name>
<Filter>([CONSTRUCTOR]= Kathrein)</Filter>
<Configuration>
<Name>Conf</Name>
<Filter>([CONSTRUCTOR]= Kathrein)</Filter>
</Configuration>
</Antennas>
<Transmitters> // or <MWMultiHops> // or <MWHubs>
<Name>Transmitters</Name> // or <Name>Multi-Hops</Name> //
or <Name>Point to Multipoint</Name>
<Display>
<Type>ByValues</Type>
<FieldDesc>
<FieldTitle>Automatic</FieldTitle>
</FieldDesc>
<Items>
</Items>
<DataTips>
<Item>0</Item>
</DataTips>
</Display>
<DefaultConfiguration/>
</Transmitters> // or </MWMultiHops> // or </MWHubs>

<MWLinks>
<Name>Links</Name>
<Display>
</Display>
<LabelFont>
<Size>-83</Size>
<Style>0</Style>
</LabelFont>
<SiteDisplay>
<SymbolFont>
<Size>80</Size>
<Style>0</Style>
</SymbolFont>
<LabelFont>
<Size>-80</Size>
<Style>0</Style>
</LabelFont>
</SiteDisplay>
<ShowText>0</ShowText>
<RepeaterDisplay>
<SymbolFont>
<Size>80</Size>
<Style>0</Style>
</SymbolFont>
</RepeaterDisplay>
</MWLinks>
<CWMeasurements>
<Distance>
<Min>0.</Min>
<Max>1000.</Max>

</Distance>
<DistanceUnit>0</DistanceUnit>
<Measure>
<Min>-105.</Min>
<Max>-90.</Max>
</Measure>
<MeasureUnit>0</MeasureUnit>
<Angle>
<Min>-180.</Min>
<Max>180.</Max>
</Angle>
<Relative>Yes</Relative>
<Clutter>
<Class>
<Code>1</Code>
<Filter>Yes</Filter>
</Class>
</Clutter>
<Advanced>([DIST]> 500)</Advanced>
<PathLosses>
<ParallelAxisRadius>200.</ParallelAxisRadius>
<PerpendicularAxisRadius>100.</PerpendicularAxisRadius>
<GlobalMargin>30.</GlobalMargin>
<LocalMargin>30.</LocalMargin>
<Threshold>-130.</Threshold>
</PathLosses>
<Display>
<FieldSelector>Error (P-M) (dB)</FieldSelector>
<SymbolFont>
<Size>-120</Size>
<Style>0</Style>
</SymbolFont>
<LabelFont>
<Size>-83</Size>
<Style>0</Style>
</LabelFont>
<Items>
<Item>
<Min>-20.</Min>
<Legend>Error (P-M) (dB) >=-20</Legend>

</Item>
</Items>
<DataTips>
<Item>M (dBm)</Item>
</DataTips>
<Labels>
<Item>M (dBm)</Item>
</Labels>
</Display>
</CWMeasurements>
<TestMobileData>
<Techno>GSM</Techno>
<Clutter>
<Class>
<Code>1</Code>
<Filter>Yes</Filter>
</Class>
</Clutter>
<Advanced></Advanced>
<PathLosses>
<ParallelAxisRadius>200.</ParallelAxisRadius>
<PerpendicularAxisRadius>100.</PerpendicularAxisRadius>
<GlobalMargin>30.</GlobalMargin>
<LocalMargin>30.</LocalMargin>
<Threshold>-130.</Threshold>
</PathLosses>
<Display>
<FieldSelector>Ec_I0</FieldSelector>
<SymbolFont>
<Size>-120</Size>
<Style>0</Style>
</SymbolFont>
<LabelFont>
<Size>-83</Size>
<Style>0</Style>
</LabelFont>
<Items>

<Item>
<Min>-60.</Min>
<Legend>Ec_I0 >=-60</Legend>
</Item>
</Items>
</Display>
</TestMobileData>
<PropagationModels> // or <SmartAntennasModels>
<Name>Propagation Models</Name> // or <Name>Smart Antenna Models</Name>
</PropagationModels> // or </SmartAntennasModels>
</FoldersConfigurations>
</Atoll>
9.1.5 Coverage Predictions
The list of coverage predictions available in the Predictions folder and the following parameters are saved:
◼ General tab:
◼ <Techno>: Name of the technology
◼ <Resolution>: Prediction resolution
◼ <Configuration>: <Filter>, <Groups>, and <Sort> criteria for the prediction
◼ <LockedStudy>: Locked or not
◼ Conditions tab: Depend on technologies and prediction types.
◼ <Reliability>: Cell edge coverage probability
◼ <Indoor>: Clutter indoor losses checked or not
◼ <WithShadowing>: Shadowing margin taken into account or not
◼ ...
◼ Display tab:
◼ Display type <type>, selected field <FieldSelector>, field description <FieldDesc> containing <FieldId>
(same as <FieldSelector>) and <FieldTitle>, visibility flag <visible>, opacity <Opacity>, and visibility range
between <minZoom> and <maxZoom>
Sample
GSM coverage by signal level

<Atoll>
<Studies>

<CoverageTRXStudy>
<Techno>GSM</Techno>
<Name>GSM: Coverage by Signal Level 0</Name>
<Display>
<Items>
<Item>
<Min>-75.</Min>
<Legend>Best Signal Level (dBm) >=-75</Legend>
</Item>
<Item>
<Min>-85.</Min>
</Item>
<Item>
<Min>-95.</Min>
</Item>
<Item>
<Min>-105.</Min>
</Item>
</Items>
<DataTips>

<Item>c0000000</Item>
<Item>c0000001</Item>
</DataTips>
</Display>
<Resolution>50</Resolution>
<GUID>{52D66F26-5710-4F4B-A327-6DAFF337AB21}</GUID>
<LockedStudy>0</LockedStudy>
<ComputeHisto>1</ComputeHisto>
<HistoPerTx>0</HistoPerTx>
<HistoLabel></HistoLabel>
<Conditions>
<FieldDbm>
<Min>-105.</Min>
</FieldDbm>
<Reliability>0.75</Reliability>
<TRXType>BCCH</TRXType>
<DefTrgThreshold>1</DefTrgThreshold>
<Indoor>0</Indoor>
<WithShadowing>0</WithShadowing>
</Conditions>
</CoverageTRXStudy>
</Studies>
</Atoll>
9.1.6 Automatic Neighbour Allocation Parameters
The following parameters are saved for intra-technology (intra-carrier and inter-carrier) and inter-technology
automatic neighbour allocations:
◼ <ANP_options>: Intra-technology (intra-carrier) neighbour allocation parameters
◼ <ANP_IL_options>: Intra-technology inter-carrier neighbour allocation parameters (UMTS HSPA and
CDMA2000 documents)
◼ <ANP_IT_options>: Inter-technology neighbour allocation parameters
A <Techno></Techno> tag is also present if the user configuration is exported from a 3GPP Multi-RAT
document. This tag contains the name of the technology to which the parameters belong.
The following parameters are saved:
◼ Parameters common to all technologies:
◼ <numMax>: Maximum number of neighbours to allocate
◼ <useCoSite>: Force co-site transmitters/cells as neighbours or not
◼ <useAdjacent>: Force adjacent transmitters/cells as neighbours or not
◼ <symetric>: Force symmetry between neighbours or not
◼ <keepNeighbs>: Reset existing neighbours or keep them
◼ <MaxDist>: Maximum distance between sites
◼ <PercentCoverage>: Coverage conditions: Minimum percentage of covered area
◼ <UseShadowing>: Coverage conditions: Take shadowing into account or not
◼ <reliability>: Coverage conditions: Cell edge coverage probability
◼ <applyConstraints>: Force exceptional pairs as neighbours or not

◼ <covBased>: Not implemented yet

◼ <minCov>: Neighbour importance: minimum factor for coverage
◼ <maxCov>: Neighbour importance: maximum factor for coverage
◼ <minAdj>: Neighbour importance: minimum factor for adjacency
◼ <maxAdj>: Neighbour importance: maximum factor for adjacency
◼ <minCos>: Neighbour importance: minimum factor for co-site
◼ <maxCos>: Neighbour importance: maximum factor for co-site
◼ <minDistImportance>: Neighbour importance: minimum factor for distance
◼ <maxDistImportance>: Neighbour importance: maximum factor for distance
◼ <resolution>: Resolution used for coverage calculation for overlapping (-1 means the default resolution
defined in the properties of the Predictions folder is used)
◼ <UseIndoor>: Coverage conditions: Use indoor losses defined per clutter class or not
◼ <UseGlobalThreshold>: Coverage conditions for WiMAX and LTE: Whether to use a global minimum
preamble C/N or RSRP, or per-cell values
◼ Parameters specific to GSM GPRS EDGE:
◼ <minField>: Coverage conditions: Minimum BCCH signal level
◼ <margin>: Coverage conditions: Margin for the minimum signal level (Handover start)
◼ <traffic>: Coverage conditions: Take traffic into account or not
◼ <deltaMax>: Coverage conditions: Handover end
◼ Parameters specific to UMTS HSPA, TD-SCDMA, and CDMA2000 1xRTT 1xEV-DO:
◼ <minField>: Coverage conditions: Minimum pilot signal level
◼ <margin>: Coverage conditions: Margin for the minimum signal level (Ec/I0 margin)
◼ <traffic>: Coverage conditions: Take traffic into account or not
◼ <deltaMax>: Coverage conditions: Handover end
◼ <EcIoMin>: Coverage conditions: Minimum Ec/I0
◼ <usePmax>: Coverage conditions: Use maximum power or not
◼ <PerCentMaxPower>: Coverage conditions: Percentage of maximum power to consider in calculations
◼ <EcIoMax>: Coverage conditions: Maximum Ec/I0
◼ <useEcIoMax>: Coverage conditions: Use maximum Ec/I0 or not
◼ <TDrop>: TDrop value (TD-SCDMA documents, intra-technology neighbour allocation only)
◼ Parameters specific to WiMAX 802.16e and LTE:
◼ <HOStart>: The handover start margin (intra-technology neighbour allocation only)
◼ <HOEnd>: The handover end margin (intra-technology neighbour allocation only)
◼ <BSmargin>: RSRP margin from the best server (inter-technology neighbour allocation only)
Sample
UMTS HSPA inter-technology, intra-carrier neighbour allocation parameters:

<Atoll>
<ANP_options>
<Techno>UMTS</Techno>
<numMax>16</numMax>
<resolution>-1</resolution>
<minField>-10500</minField>
<margin>500</margin>
<useCoSite>1</useCoSite>
<useAdjacent>1</useAdjacent>

<traffic>0</traffic>
<symetric>0</symetric>
<keepNeighbs>0</keepNeighbs>
<MaxDist>10000</MaxDist>
<PercentCoverage>1000</PercentCoverage>
<UseShadowing>0</UseShadowing>
<reliability>7500</reliability>
<UseIndoor>0</UseIndoor>
<deltaMax>1200</deltaMax>
<applyConstraints>0</applyConstraints>
<covBased>1</covBased>
<minDistImportance>100</minDistImportance>
<maxDistImportance>1000</maxDistImportance>
<minCov>1000</minCov>
<maxCov>3000</maxCov>
<minAdj>3000</minAdj>
<maxAdj>6000</maxAdj>
<minCos>6000</minCos>
<maxCos>10000</maxCos>
<UseGlobalThreshold>0</UseGlobalThreshold>
<EcIoMin>-1400</EcIoMin>
<usePmax>0</usePmax>
<PerCentMaxPower>5000</PerCentMaxPower>
<EcIoMax>-700</EcIoMax>
<useEcIoMax>0</useEcIoMax>
</ANP_options>
</Atoll>
9.1.7 Automatic Frequency Planning Parameters
The following parameters are saved for automatic frequency planning (GSM GPRS EDGE documents):
◼ <defSeparations__CONF_CO_SITE_BB>: Default co-site separation rule for two BCCH type TRXs.
◼ <defSeparations__CONF_CO_CELL_BB>: Default co-transmitter separation rule for two BCCH type TRXs.
◼ <defSeparations__CONF_NEIGH_BOUR_BB>: Default neighbour separation rule for two BCCH type TRXs.
◼ <defSeparations__CONF_CO_SITE_BT>: Default co-site separation rule for a BCCH and a TCH type TRX.
◼ <defSeparations__CONF_CO_CELL_BT>: Default co-transmitter separation rule for a BCCH and a TCH type
TRX.
◼ <defSeparations__CONF_NEIGH_BOUR_BT>: Default neighbour separation rule a for BCCH and a TCH type
TRX.
◼ <defSeparations__CONF_CO_SITE_TT>: Default co-site separation rule for two TCH type TRXs.
◼ <defSeparations__CONF_CO_CELL_TT>: Default co-transmitter separation rule for two TCH type TRXs.
◼ <defSeparations__CONF_NEIGH_BOUR_TT>: Default neighbour separation rule for two TCH type TRXs.
◼ <freezeState>: Last minute resource freezing options available in the AFP launch wizard
◼ <numMinutes>: Target time alloted to the AFP
◼ <useDTX>: Consider the effect of discontinuous transmission or not
◼ <dtxVocalFactor>: Voice activity factor for discontinuous transmission
◼ <AfpBasedOnInterference>: Load all potential interferers or not

◼ <AfpBasedOnSeparations>: Load all the subcells potentially involved in separation constraints or not
◼ <IM_calculate__WithTraffic>: Whether traffic spreading is uniform or based on the maps used in the default
traffic capture (for interference matrices calculation)
◼ <IM_calculate__BestServerZoneMargin>: Margin in case of Best signal level per HCS layer (for interference
matrices calculation)
◼ <IM_calculate__ServiceZoneType>: All or Best signal level per HCS layer (for interference matrices
calculation)
◼ <IM_calculate__reliability_X_10000>: Cell edge coverage probability (for interference matrices calculation)
◼ <TakeTfFromCapt>: Whether traffic loads are read from the default traffic capture or from the Subcells table
◼ <preferedSenario>: Scenario type, i.e., modification of existing TRXs allowed or not
Sample

<Atoll>
<AFP_options>
<defSeparations__CONF_CO_SITE_BB>2</defSeparations__CONF_CO_SITE_BB>
<defSeparations__CONF_CO_CELL_BB>3</defSeparations__CONF_CO_CELL_BB>
<defSeparations__CONF_NEIGH_BOUR_BB>2</defSeparations__CONF_NEIGH_BOUR_BB>
<defSeparations__CONF_CO_SITE_BT>2</defSeparations__CONF_CO_SITE_BT>
<defSeparations__CONF_CO_CELL_BT>3</defSeparations__CONF_CO_CELL_BT>
<defSeparations__CONF_NEIGH_BOUR_BT>1</defSeparations__CONF_NEIGH_BOUR_BT>
<defSeparations__CONF_CO_SITE_TT>1</defSeparations__CONF_CO_SITE_TT>
<defSeparations__CONF_CO_CELL_TT>2</defSeparations__CONF_CO_CELL_TT>
<defSeparations__CONF_NEIGH_BOUR_TT>1</defSeparations__CONF_NEIGH_BOUR_TT>
<freezeState>0</freezeState>
<numMinutes>1000</numMinutes>
<useDTX>0</useDTX>
<dtxVocalFactor>70</dtxVocalFactor>
<AfpBasedOnInterference>1</AfpBasedOnInterference>
<AfpBasedOnSeparations>1</AfpBasedOnSeparations>
<IM_calculate__WithTraffic>0</IM_calculate__WithTraffic>
<IM_calculate__BestServerZoneMargin>5</IM_calculate__BestServerZoneMargin>
<IM_calculate__ServiceZoneType>1</IM_calculate__ServiceZoneType>
<IM_calculate__reliability_X_10000>7500</IM_calculate__reliability_X_10000>
<TakeTfFromCapt>1</TakeTfFromCapt>
<preferedSenario></preferedSenario>
</AFP_options>
</Atoll>
9.1.8 Automatic Scrambling Code Allocation Parameters
The following parameters are saved for automatic scrambling code allocation (UMTS HSPA and TD-SCDMA
documents):
◼ <MinEcI0>: Minimum Ec/I0 constraint (not used in TD-SCDMA)
◼ <margin>: Ec/I0 margin (not used in TD-SCDMA)
◼ <reliability>: Cell edge coverage probability (not used in TD-SCDMA)
◼ <DistanceMin>: Default re-use distance

◼ <Strategy0>: Clustered strategy available or not

◼ <Strategy1>: Distributed per Cell strategy available or not
◼ <Strategy2>: One Cluster/SYNC_DL Code per Site strategy available or not
◼ <Strategy3>: Distributed per Site strategy available or not
◼ <Strategy>: Scrambling code allocation strategy
◼ <FromScratch>: Reset all already allocated codes or not
◼ <UseCurrentNghbs>: Use existing first-order neighbours or not
◼ <NghbOrder>: The order of neigbours to take into account, i.e., 1st, 2nd, or 3rd
◼ <ComputeNghbs>: Calculate neighbours using the addition Ec/I0 conditions or not
◼ <UseMaxCodes>: Use a maximum of codes or not
◼ <UseShadowing>: Shadowing taken into account or not (not used in TD-SCDMA)
◼ <SameCodeForCarriers>: Allocate carriers identically or not
◼ <NbClusterPerSite>: Number of transmitters per site among which a cluster should be distributed
◼ <ClustNghbs>: Additional constraint of taking into account the first-order neighbours in other clusters
◼ <Clust2ndNghbs>: Additional constraint of taking into account the second-order neighbours in other clusters
◼ <NbCodesPerCluster>: The number of scrambling codes in one cluster/SYNC_DL
◼ <UseDistance>: Take the minimum reuse distance into account or not
◼ <UseExcepPairs>: Take exceptional pairs into account or not
◼ <minField>: Minimum pilot signal level constraint (not used in TD-SCDMA)
◼ <usePmax>: Use the maximum downlink transmission power or not (not used in TD-SCDMA)
◼ <PerCentMaxPower>: The percentage of the maximum downlink power is <usePmax> is set to 0 (not used in
TD-SCDMA)
◼ <Max1stNghbCost>: The maximum cost of 1st order neighbours
◼ <Max2ndNghbCost>: The maximum cost of 2nd order neighbours
◼ <Max3rdNghbCost>: The maximum cost of 3rd order neighbours
◼ <CoplanCost>: The cost for inter-technology neighbours
◼ <MaxCoClusterCost>: The maximum cost for same-cluster/SYNC_DL neighbours
◼ <MaxDistCost>: The maximum cost for a minimum reuse distance constraint violation
◼ <ExcepPairCost>: The cost for exceptional pair constraint violation
◼ <UseCloseNghbs>: Take the Close Neighbours constraint into account or not (TD-SCDMA only)
◼ <CloseDistance>: Maximum distance within which close neighbours are located (TD-SCDMA only)
◼ <CloseImportance>: Minimum importance value of close neighbour (TD-SCDMA only)
◼ <MaxCloseCost>: Maximum cost of a close neighbour relation (TD-SCDMA only)
Sample

<Atoll>
<SCP_options>
<MinEcI0>-1500.</MinEcI0>
<margin>500.</margin>
<reliability>5000.</reliability>
<DistanceMin>200000.</DistanceMin>
<Strategy0>1</Strategy0>

<Strategy>0</Strategy>
<FromScratch>1</FromScratch>
<UseCurrentNghbs>1</UseCurrentNghbs>
<NghbOrder>1</NghbOrder>
<ComputeNghbs>0</ComputeNghbs>
<UseMaxCodes>1</UseMaxCodes>
<SameCodeForCarriers>0</SameCodeForCarriers>
<NbClusterPerSite>3</NbClusterPerSite>
<ClustNghbs>0</ClustNghbs>
<Clust2ndNghbs>0</Clust2ndNghbs>
<NbCodesPerCluster>8</NbCodesPerCluster>
<UseDistance>1</UseDistance>
<UseExcepPairs>1</UseExcepPairs>
<Max1stNghbCost>100</Max1stNghbCost>
<Max2ndNghbCost>50</Max2ndNghbCost>
<Max3rdNghbCost>5</Max3rdNghbCost>
<CoplanCost>100</CoplanCost>
<MaxCoClusterCost>50</MaxCoClusterCost>
<MaxDistCost>100</MaxDistCost>
<ExcepPairCost>100</ExcepPairCost>
<UseCloseNghbs>1</UseCloseNghbs>
<CloseDistance>80000.</CloseDistance>
<CloseImportance>3000.</CloseImportance>
<MaxCloseCost>100</MaxCloseCost>
</SCP_options>
</Atoll>
9.1.9 Automatic PN Offset Allocation Parameters
The following parameters are saved for automatic PN offset allocation (CDMA2000 documents):
◼ <MinEcI0>: Minimum Ec/I0 constraint
◼ <TDrop>: Value for the TDrop
◼ <reliability>: Cell edge coverage probability
◼ <DistanceMin>: Default re-use distance
◼ <Strategy0>: PN Offset per Cell strategy available or not
◼ <Strategy1>: Adjacent PN-Cluster per Site strategy available or not
◼ <Strategy2>: Distributed PN-Cluster per Site strategy available or not
◼ <Strategy>: PN offset allocation strategy
◼ <FromScratch>: Reset all already allocated codes or not
◼ <UseCurrentNghbs>: Use existing neighbours or not
◼ <NghbOrder>: The order of neigbours to take into account, i.e., 1st, 2nd, or 3rd

◼ <ComputeNghbs>: Calculate neighbours using the addition Ec/I0 conditions or not

◼ <UseShadowing>: Shadowing taken into account or not
◼ <SameCodeForCarriers>: Allocate same PN offset to cells of the same transmitter or not
◼ <PilotIncr>: Value for the PILOT_INC
◼ <PNClusterSize>: Number of PN offsets per cluster
◼ <UseDistance>: Take the minimum reuse distance into account or not
◼ <UseExcepPairs>: Take exceptional pairs into account or not
◼ <UseMaxCodes>: Use a maximum of codes or not
◼ <minField>: Minimum pilot signal level constraint
◼ <usePmax>: Use the maximum downlink transmission power or not
◼ <PerCentMaxPower>: The percentage of the maximum downlink power is <usePmax> is set to 0
◼ <Max1stNghbCost>: The maximum cost of 1st order neighbours
◼ <Max2ndNghbCost>: The maximum cost of 2nd order neighbours
◼ <Max3rdNghbCost>: The maximum cost of 3rd order neighbours
◼ <CoplanCost>: The cost for inter-technology neighbours
◼ <MaxDistCost>: The maximum cost for a minimum reuse distance constraint violation
◼ <ExcepPairCost>: The cost for exceptional pair constraint violation
Sample

<Atoll>
<PNO_options>
<DistanceMin>200000.</DistanceMin>
<Strategy>2</Strategy>
<FromScratch>1</FromScratch>
<UseCurrentNghbs>1</UseCurrentNghbs>
<NghbOrder>1</NghbOrder>
<ComputeNghbs>1</ComputeNghbs>
<SameCodeForCarriers>0</SameCodeForCarriers>
<PilotIncr>4</PilotIncr>
<PNClusterSize>3</PNClusterSize>
<UseExcepPairs>1</UseExcepPairs>
<UseMaxCodes>1</UseMaxCodes>
<MinEcI0>-1600.</MinEcI0>
<TDrop>-1800.</TDrop>
<reliability>6000.</reliability>
<Max1stNghbCost>100</Max1stNghbCost>
<Max2ndNghbCost>50</Max2ndNghbCost>
<Max3rdNghbCost>5</Max3rdNghbCost>

<CoplanCost>100</CoplanCost>
<MaxDistCost>100</MaxDistCost>
<ExcepPairCost>100</ExcepPairCost>
</PNO_options>
</Atoll>
9.1.10 Automatic OFDM Resource Allocation Parameters
The following parameters are saved for automatic allocation of resources in OFDM networks:
◼ <UseNeighbs>: Neighbours taken into account or not
◼ <UseDistance>: Distance taken into account or not
◼ <UseIM>: Interference matrices taken into account or not
◼ <BasedOnFrqPlan>: Frequency plan taken into account or not
◼ <SameSegPerTx>: Allocate the same segment to co-transmitter cells or not
◼ <MinDistance>: Minimum global reuse distance
◼ <SiteStrategy>: Per-site or free allocation for SSS ID (LTE) and cell permbase (WiMAX)
◼ <UniformIDDistribution>: Uniform physical cell ID or preamble index distribution active or not
◼ <RangeType>: Physical cell ID, preamble index, or zone permbase allocation domain (restricted = 0, entire = 1,
custom = 2, or per-cell = 3)
◼ <ExcludedPis>: List of excluded physical cell IDs, preamble indexes, or zone permbases for custom allocation
domain type
Automatically allocated resources in OFDM networks include:
◼ LTE: Frequency and physical cell ID allocation parameters
◼ WiMAX: Frequency, preamble index, and zone permbase allocation parameters
◼ Wi-Fi: Frequency allocation parameters
Sample

<Atoll>
<OFDM_AFP_options>
<UseNeighbs>1</UseNeighbs>
<UseIM>1</UseIM>
<BasedOnFrqPlan>1</BasedOnFrqPlan>
<SameSegPerTx>0</SameSegPerTx>
<MinDistance>100.</MinDistance>
<SiteStrategy>1</SiteStrategy>
<UniformIDDistribution>1</UniformIDDistribution>
<RangeType>2</RangeType>
<ExcludedPis></ExcludedPis>
</OFDM_AFP_options>
</Atoll>

9.1.11 Microwave Radio Links Parameters
The following parameters are saved for microwave radio links:

◼ <QualityModel>: Quality model used for calculations
◼ <QualityObjective0>, <QualityObjective1>, <QualityObjective2>, <QualityObjective3>: Quality objectives
◼ <AvailabilityObjective0>, <AvailabilityObjective1>, <AvailabilityObjective2>, <AvailabilityObjective3>:
Availability objectives
◼ <RainModel>: Rain model used
◼ <RBER>: Residual BER
◼ <ALFA1>: Value of alpha 1
◼ <ALFA2>: Value of alpha 2
◼ <RefDelayM>: Reference delay for minimum phase
◼ <refDelayNM>: Reference delay for non-minimum phase
◼ <EquipPercent>: Availability objectives ratio for equipment
◼ <RainPercent>: Availability objectives ratio for rain
◼ <kMoy>: Average value of k
◼ <kMin>: Minimum value of k
◼ <UseAtpc>: Use automatic power control or not
◼ <P0Method>: Multi-path occurence method
◼ <IgnoreXPD>: Ignore cross-polar discrimination
◼ <IgnorePR>: Ignore passive repeaters
◼ <WhichBER>: BER to calculate
◼ <BER1>: Value of BER 1
◼ <BER2>: Value of BER 2
◼ <Rec838>: Rain model recommendations version
◼ <UseK1Global>: Use the global value for k1
◼ <UseK2Global>: Use the global value for k2
◼ <CALC_LINK_PORTS>: Calculate for given link ports
◼ <MultilineShared>: Shared multi-channel frequency diversity
◼ <NoAcm>: Signal enhancements
◼ <InterferenceDistanceMax>: Maximum distance for interference filtering
◼ <InterferenceDropMin>: Local min threshold degradation
◼ <InterferenceDropMinGlobal>: Global min threshold degradation
◼ <InterferenceCalcGo>: Interference calculation in the direction from site A to site B
◼ <InterferenceCalcReturn>: Interference calculation in the direction from site B to site A
◼ <InterferenceCalcUplink>: Interference calculation in the uplink
◼ <InterferenceCalcDownlink>: Interference calculation in the downlink
◼ <InterferenceRainSurfCorrelation>: Interference correlation surface area
◼ <InterferenceAutoWeight>: Automatic interference weighting
◼ <InterferenceUseAtpc>: Power control for interference calculation
◼ <InterferenceWidth>: Interfered wanted bandwidth
◼ <InterferenceOverShoot>: Interference over shoot calculation
◼ <CochannelOnly>: Interfered bandwidth co-channel only
◼ <IgnoreIntraLinkInterference>: Ignore interference between channels of the same link
◼ <Resolution>: Interfering profile calculation step
◼ <INTERF_DETAIL>: Calculation details (none, uplink, downlink, both)

◼ <ClutterCategory0> through <ClutterCategory36>: Bitsets for clutter category properties

◼ <ClutterDryCategory0> through <ClutterDryCategory36>: Soil type
Sample

<Atoll>
<Microwave>
<QualityModel>6</QualityModel>
<QualityObjective0>3</QualityObjective0>
<AvailabilityObjective0>3</AvailabilityObjective0>
<RainModel>5</RainModel>
<RBER>1.e-012</RBER>
<ALFA1>10</ALFA1>
<ALFA2>1</ALFA2>
<RefDelayM>6.30000019</RefDelayM>
<refDelayNM>6.30000019</refDelayNM>
<EquipPercent>33.</EquipPercent>
<RainPercent>33.</RainPercent>
<kMoy>1.33</kMoy>
<kMin>0.88</kMin>
<UseAtpc>0</UseAtpc>
<P0Method>1</P0Method>
<IgnoreXPD>1</IgnoreXPD>
<IgnorePR>0</IgnorePR>
<WhichBER>5</WhichBER>
<BER1>1.e-003</BER1>
<BER2>1.e-006</BER2>
<Rec838>1</Rec838>
<UseK1Global>1</UseK1Global>
<UseK2Global>1</UseK2Global>
<CALC_LINK_PORTS>selected</CALC_LINK_PORTS>
<MultilineShared>0</MultilineShared>
<NoAcm>1</NoAcm>
<InterferenceDistanceMax>50000.</InterferenceDistanceMax>
<InterferenceDropMin>1.</InterferenceDropMin>
<InterferenceDropMinGlobal>3.</InterferenceDropMinGlobal>
<InterferenceCalcGo>1</InterferenceCalcGo>
<InterferenceCalcReturn>1</InterferenceCalcReturn>
<InterferenceCalcUplink>0</InterferenceCalcUplink>
<InterferenceCalcDownlink>0</InterferenceCalcDownlink>
<InterferenceRainSurfCorrelation>100.</InterferenceRainSurfCorrelation>
<InterferenceAutoWeight>0</InterferenceAutoWeight>
<InterferenceUseAtpc>0</InterferenceUseAtpc>
<InterferenceWidth>250</InterferenceWidth>

<InterferenceOverShoot>0</InterferenceOverShoot>
<CochannelOnly>0</CochannelOnly>
<IgnoreIntraLinkInterference>1</IgnoreIntraLinkInterference>
<Resolution>50</Resolution>
<INTERF_DETAIL>both</INTERF_DETAIL>
<ClutterCategory0>0</ClutterCategory0>
<ClutterDryCategory0>B</ClutterDryCategory0>
<ClutterDryCategory15>E</ClutterDryCategory15>

<ClutterDryCategory26>A</ClutterDryCategory26>
</Microwave>
</Atoll>
9.1.12 Macros
The following parameters are saved for macros:

◼ <Path>: Full path to the macro file
◼ <Language>: Language in which the macro is written
◼ <Timeout>: The target time allocated to macro execution
Sample

<Atoll>
<Macros>
<File>
<Path>C:\TestsAddin\testEvents.vbs</Path>
<Language>VBScript</Language>

<Timeout>3600</Timeout>
</File>
</Macros>
</Atoll>
9.2 Contents of Additional Configuration Files

Complete descriptions of the different additional configuration files are provided below.
9.2.1 Print Setup Configuration
The following parameters are saved for print setup:

◼ Page tab <Page>:
◼ Paper size and orientation <Paper size="" orientation=""/>, margins <Margins right="" left="" bottom=""
top="">, scaling with the fit to page option <Scale fitToPage="">
◼ Components tab:
◼ Rulers and area inside focus zone only <Map>: <Map insideFZonly="" rulers=""/>
◼ Legend <Legend>: Legend flag, outer and inner position, and inside map flag <LegendPos enable=""
majorPos="" minorPos="" insideMap=""/>
◼ Comments <Comments>: Comments flag, vertical and horizontal position, and the inside map flag
<Position vPos="" enable="" hPos="" insideMap=""/>, comment text <text>, and font details <font height=""
weight="" charset="" face="" italic=""/>
◼ Header/Footer tab:
◼ Header logo <Logo>: Logo flag, vertical and horizontal position, and the inside map flag <Position vPos=""
enable="" hPos="" insideMap=""/>, logo image <bitmap>, and logo width and height in pixels <Dimensions
width="" height=""/>
◼ Header title <Title>: Header flag, vertical and horizontal position, and the inside map flag <Position vPos=""
enable="" hPos="" insideMap=""/>, title text <text>, and font details <font height="" weight="" charset=""
face="" italic=""/>
◼ Footer logo <LogoBottom>: Logo flag, vertical and horizontal position, and the inside map flag <Position
vPos="" enable="" hPos="" insideMap=""/>, logo image <bitmap>, and logo width and height in pixels
<Dimensions width="" height=""/>
◼ Footer text <Footer>: Footer flag, vertical and horizontal position, and the inside map flag <Position vPos=""
enable="" hPos="" insideMap=""/>, footer text <text>, and font details <font height="" weight="" charset=""
face="" italic=""/>
Sample

<PrintConfiguration version="1">
<Page>
<Paper size="" orientation="1"/>
<Margins right="2000" left="2000" bottom="2000" top="2000"/>
<Scale fitToPage="1">12 495</Scale>
</Page>
<Map insideFZonly="1" rulers="1"/>
<Legend>

<LegendPos enable="0" majorPos="3" minorPos="0" insideMap="0"/>

</Legend>
<Comments>
<Position vPos="1" enable="0" hPos="1" insideMap="0"/>
<text></text>
<font height="14" weight="400" charset="1" face="MS Shell Dlg" italic="0"/>
</Comments>
<Logo>
<bitmap></bitmap>
<Dimensions width="46" height="18"/>
</Logo>
<Title>
<text></text>
</Title>
<LogoBottom>
<bitmap></bitmap>
<Dimensions width="46" height="18"/>
</LogoBottom>
<Footer>
<text></text>
</Footer>
</PrintConfiguration>
9.2.2 Table Import/Export Configuration
The following parameters are saved for table import/export:

◼ Header flag <TITRE>
◼ Field separator <FLD_SEPARATOR>
◼ Decimal symbol <DEC_SEPARATOR>
◼ Fields available in the table (field legends) <FIELDS>
◼ Fields selected for import/export (field legends) <CHOOSEN_FIELDS>
Sample

<TITRE>1</TITRE>
<FLD_SEPARATOR><tab></FLD_SEPARATOR>
<DEC_SEPARATOR>.</DEC_SEPARATOR>
<FIELDS>
Site
Transmitter
...

</FIELDS>
<CHOOSEN_FIELDS>
Site
Transmitter
...
</CHOOSEN_FIELDS>
9.2.3 Coverage Prediction Report Configuration
The following parameters are saved for coverage prediction reports:

◼ Columns selected in the Columns to be displayed dialogue <SelectedFields> including the field titles <Field>
<Title>
Sample

<ReportConfiguration>
<SelectedFields>
<Field>
<Title>Surface (km²)</Title>
</Field>
<Field>
<Title>% of Covered Area</Title>
</Field>
...
</SelectedFields>
</ReportConfiguration>
9.2.4 CW Measurement Import Configuration
More than one CW measurement import configurations can be saved in a single CWMeasurementsImport.ini file.
The following parameters are saved in the CWMeasurementsImport.ini files:
◼ Configuration name in square brackets
◼ First measurement row (Header)
◼ Separator (Separator)
◼ Decimal symbol (DecimalSeparator)
◼ Type of files for which the configuration has been defined (Pattern)
◼ Column containing the X coordinates (Xindex)
◼ Column containing the Y coordinates (Yindex)
◼ Column containing the measurement values (MeasIndex)
◼ Unit of the measurement values (Unit)
◼ Frequency of the measurements (Frequency)
◼ Height of the receiver used for measurements (Height)
◼ Gain of the receiver used for measurements (Gain)
◼ Losses of the receiver used for measurements (Losses)
◼ Total number of columns in measurement files (NbCol)

◼ Column types (Col0 to ColNbCol)

The column type indexes are as follows:
Type Index
Text 0
Integer 1
Real 2
Date 3
<Ignore> 4
Sample
[ConfigurationName]
Header=2
Separator=tab
DecimalSeparator=.
Pattern=*.txt
Xindex=1
Yindex=2
MeasIndex=4
Unit=0
Frequency=2110
Height=1.5
Gain=0
Losses=0
NbCol=23
Col0=1
Col3=4
Col5=0
...
9.2.5 Drive Test Data Import Configuration
More than one drive test data import configurations can be saved in a single DriveTestDataImport.ini file.
The following parameters are saved in the DriveTestDataImport.ini files:
◼ Configuration name in square brackets
◼ First measurement row (Header)
◼ Separator (Separator)
◼ Decimal symbol (DecimalSeparator)
◼ Type of files for which the configuration has been defined (Pattern)
◼ Column containing the X coordinates (Xindex)
◼ Column containing the Y coordinates (Yindex)
◼ Unit of the measurement values (Unit)
◼ Height of the receiver used for measurements (Height)
◼ Gain of the receiver used for measurements (Gain)
◼ Losses of the receiver used for measurements (Losses)
◼ First identifier (GenericNameIdOne)
◼ Second identifier (GenericNameIdTwo)

◼ Format of the second identifier (IdFormat)

◼ Wireless technology (Techno)
◼ Total number of columns in measurement files (NbCol)
◼ Column types (Col0 to ColNbCol)
The column type indexes are as follows:
Type Index
Text 0
Integer 1
Long Integer 2
Single 3
Double 4
Date 5
<Ignore> 6
Sample
[ConfigurationName]
Header=2
Separator=tab
DecimalSeparator=.
Pattern=*.*
Xindex=1
Yindex=2
Unit=0
Height=1.5
Gain=0
Losses=0
GenericNameIdOne=
GenericNameIdTwo=BSID
IdFormat=Decimal
Techno=IEEE 802.16e
NbCol=21
Col0=1
Col3=1
Col4=4
...
9.3 Content of the Custom Predictions File

The content of the custom predictions file (by default, studies.XML in the installation folder) is identical to the
content found between the <Studies> and </Studies> tags in the configuration file. For more information, see
"Coverage Predictions" on page 127.

9.4 Content of the "Value Intervals" Predictions Files

The content of the XML files for coverage predictions calculated by value intervals (by default,
prediction_name>.XML in the C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>} folder) is identical to the
content found between the <Studies> and </Studies> tags in the configuration file. For more information, see
"Coverage Predictions" on page 127.

AT340_AM_E3 Chapter 10: Initialisation Files
10 Initialisation Files
Initialisation files can be used to store operational and working environment settings. These files are optional, not
required for working with Atoll, but are useful means for selecting required calculation methods and other settings.
This chapter describes the formats of these files in detail:
◼ Atoll initialisation file (Atoll.ini)
This file contains conventions, calculation settings, and other options for Atoll. For more information on these
options, see "Atoll Initialisation File" on page 147.
Atoll.ini can be automatically loaded when Atoll is run when it is:
a. Identified in the command line parameter -Ini "inifilename" (see "Atoll Command Line Parameters" on
page 26 for more information), or
b. Located in the Atoll installation folder. This file will be ignored if an initialisation file is loaded through the
command line parameter.
 You can open the Atoll.ini file in the Atoll installation folder for editing by pressing
CTRL+SHIFT+i. If no Atoll.ini file exists, a blank Atoll.ini file is created.
You must restart Atoll in order to take into account modifications made in Atoll.ini.
A given Atoll.ini section, for example [GUIUserRights] or [LTE], must occur only once
in the file, with all options pertaining to that section listed under it. If you enter the
same section twice, only the first occurrence of the section will be read and loaded
by Atoll.
◼ ACP initialisation file (ACP.ini)

This file contains calculation settings and other options for the Atoll ACP module. For more information on
these options, see "ACP Initialisation File" on page 224.
10.1 Atoll Initialisation File

The following main groups of options are available:
◼ "General Options" on page 148
◼ "GUI Options" on page 171
◼ "Distributed Calculation Server Options" on page 177
◼ "License Management Options" on page 178
◼ "Database Options" on page 180
◼ "Common Calculation Options" on page 185
◼ "GSM GPRS EDGE Options" on page 195
◼ "UMTS HSPA, CDMA2000, and TD-SCDMA Options" on page 201
◼ "LTE, NB-IoT, WiMAX, Wi-Fi, and LPWA Options" on page 209
◼ "3GPP Multi-RAT Options" on page 218
◼ "Microwave Radio Link Options" on page 218
◼ "Measurement Options" on page 223
◼ "Specifying the Location of the ACP.ini File" on page 224

Chapter 10: Initialisation Files
 The Atoll initialisation file is a powerful tool. You should not modify any option until
and unless you are absolutely sure of what you are doing.
10.1.1 General Options
10.1.1.1 Managing Memory Allocation per Session in Atoll 64-bit

You can set a Working Set Memory limit per Atoll session. This upper limit may be useful for Atoll application servers
in order to avoid any one Atoll session from using all available memory. Setting a Working Set Memory limit will
make Atoll retrieve additional memory, if needed, from the paging file rather than from the physical memory (RAM).
 Atoll 64-bit is able to efficiently use up to 4 terabytes of memory on Microsoft

Windows Server 2012 Standard and Datacenter versions. For a detailed list of
memory limits of different versions of Microsoft Windows, see the Microsoft article
at this URL:
https://docs.microsoft.com/fr-fr/windows/desktop/Memory/memory-limits-for-
windows-releases
The maximum amount of usable memory for Atoll 64-bit is determined by the size of available physical memory and
the paging file. In Windows operating systems, the memory allocated to any process is either part of the physical
memory or of the paging file. In order to track the memory consumption of a process, two memory usage indicators
are available:
◼ Committed Memory: The amount of memory allocated either from the physical memory or from the paging
file. This information is available in the Windows Performance Monitor (Perfmon) under the "Process->Virtual
Bytes" counter.
◼ Working Set Memory: The amount of committed memory allocated from the physical memory. The working
set memory is less than or equal to the committed memory. This information is available in the Windows
Performance Monitor (Perfmon) under the "Process->Working Set" counter.
You can set a maximum working set memory per Atoll session by adding the following lines to the Atoll.ini file:
[Memory]
MaximumWorkingSetSize = N
Where N is the maximum working set memory size in MB.

If you set the maximum working set memory to N MB, Atoll will retrieve N MB of memory from the physical memory,
if available, and any additional amount of memory from the paging file, if available. If the amount of retrievable
memory from the paging file is not enough, or if the paging file does not exist on the server, Atoll will try to obtain
the additional amount of memory from the physical memory cache, if available.
 A large paging file is recommended.
If required, multiple Atoll shortcuts can also be created, each using a dedicated Atoll.ini file. This enables you to
define different values for the maximum working set memory option in different Atoll.ini files and assign different
memory limits to different users. Once you have created different Atoll.ini files with different values for this option,
you can point to these Atoll.ini files in the path defined in the Atoll shortcut. For more information, see "Atoll
Command Line Parameters" on page 26.
You can also monitor the amount of memory used by an Atoll session using:
◼ The Event Viewer: You can have the maximum working set size defined for the Atoll session displayed in the
Atoll Event Viewer. To do so, add the following lines to the Atoll.ini file:
[Memory]

DisplayMaximumWorkingSetSize = 1
DisplayMaximumWorkingSetSize is set to 0 by default.

◼ The Windows Task Manager: You can monitor the Working Set Memory used by an Atoll session in real time
in the Windows Task Manager's Details tab under the "Working set (memory)" counter.
◼ The Windows Performance Monitor (Perfmon): You can monitor the Working Set Memory used by an Atoll
session in real time in the Windows Performance Monitor via the "Process->Working Set" counter.
10.1.1.2 Changing the Default Metre-to-Feet Conversion Factor

By default, Atoll converts 1 metre to 3.28084 feet. You can add the following lines to the Atoll.ini file to change this
factor:
[Units]
MeterToFeetFactor = value
10.1.1.3 Changing the Default Mile-to-Metre Conversion Factor

By default, Atoll converts 1 mile to 1609.344 metres. You can add the following lines to the Atoll.ini file to change
this value:
[Units]
MilesToMeterFactor = value
10.1.1.4 Modifying the Default Formats of Site and Transmitter Names

Through the Atoll.ini file, it is possible to specify the default naming conventions for sites and transmitters.
By default, when a site is created, it is named Site<number>, where <number> is the sequential number of that site.
You can specify your own prefix for the default site name by adding the following lines to the Atoll.ini file:
[Site]
Prefix = <prefix>
When the Prefix parameter is specified, new sites are named <prefix><number> instead of Site<number>.
By default, when a transmitter is created, it is named <sitename>_<number>, where <sitename> is the name of the
site where the transmitter is located and <number> is the sequential transmitter sector identifier on that site. You
can specify a prefix and a suffix for the default transmitter name by adding the following lines to the Atoll.ini file:
[Transmitter]
Prefix = <prefix>
Suffix = <suffix>
◼ When the Prefix parameter is specified, new transmitters are named <prefix>_<number> instead of
<sitename>_<number>.
◼ When the Suffix parameter is specified, new transmitters are named <sitename>_<suffix><number> instead of
<sitename>_<number>.
◼ When both the Prefix and Suffix are specified, new transmitters are named <prefix>_<suffix><number> instead
of <sitename>_<number>.
◼ If you omit the Prefix or Suffix parameters (or if you use Prefix = <AUTO>) the default naming method is used.
It is also possible to remove the underscore character ("_") from the transmitter name. For example, new
transmitters can be named <sitename><number> instead of <sitename>_<number>. To remove the underscore, add
the following lines to the Atoll.ini file:
[Transmitter]

Underscore = 0
By default, Underscore is set to 1. When Underscore is set to 0, the underscore character is omitted in new
transmitter names.
You can also specify whether the sequential <number> identifier that is appended to transmitter name should be a
numeric (0-9) or an alphabetic (a-z or A-Z) character. You can also specify whether the numbering sequence starts
with 0, 1 or any other value, or whether the alphabetical sequence starts with a, A (to specify upper or lower case),
or any other character. The following lines define these options in the Atoll.ini file:
[Transmitter]
SuffixIsNum = 0|1
First = <numeric_value>
FirstCharSuffix = <character>
◼ When SuffixIsNum = 1 , new transmitter names are appended with a numeric suffix. The parameter First
specifies the number of the first transmitter in the numbering sequence. For example, if SuffixIsNum = 1 and
First = 0, then the transmitter names will be appended with 0, 1, and 2.
◼ When SuffixIsNum = 0, new transmitter names are appended with a letter. The parameter FirstCharSuffix
specifies the letter of the first transmitter in the alphabetic sequence. For example, if SuffixIsNum = 0 and
FirstCharSuffix = a, then the transmitter names will be appended with a, b, and c.
By default, SuffixIsNum is set to 1, First is set to 1, and FirstCharSuffix is set to A.
10.1.1.5 Disabling Automatic Renaming of Transmitters and Cells

When the name of a site is modified, Atoll automatically renames the transmitters, cells, repeaters, and remote
antennas related to that site according to the new site name. By the same logic, when the name of a transmitter is
modified, Atoll automatically renames the cells, repeaters, and remote antennas related to that transmitter.
Automatic renaming is enabled by default. However, it can be disabled by adding the following lines to the Atoll.ini
file:
[AutoRename]
Transmitters = 0
3GCells = 0
Repeaters = 0
◼ "Transmitters" refers to transmitter renaming when the site name is changed.

◼ "3Gcells" refers to cell renaming in 3G and 4G when the transmitter name is changed.
◼ "Repeaters" refers to repeater and remote antenna renaming when the transmitter name is changed.
10.1.1.6 Setting the TIFF Colour Convention

In the default palette, the first colour indexes represent the useful information and the remaining colour indexes
represent the background. You can export TIFF files with a palette containing the background colour at index 0 along
with other colour indices representing the foreground. This can be helpful when working on TIFF files exported by
Atoll in other tools. To do so, the Atoll.ini file must contain these lines:
[TiffExport]
PaletteConvention = Gis
10.1.1.7 Creating an Event Viewer Log File

You can define a log file path and file name in Atoll.ini in order to save all the warning, error, and information
messages displayed in the Event Viewer window to a log file. To do this, add the following lines to Atoll.ini:
[EventsObserver]

LogPath = FullPath\LogFile.log
The path should be the full path to the log file, which can be, for example, "\\Server\Drive\Root\Folder\Atoll\" or
"C:\Program Files\Forsk\Atoll\" (without quotation marks). "LogFile.log" will be created by Atoll as an ASCII text file,
and can have any file name and extension. Atoll will overwrite any already existing log file with the same name. If
Atoll is unable to overwrite the existing log file, it will not create any log.
You can also start Atoll, specifying a log file, by starting it with "Atoll.exe -log LogFile.log", either from the command
line, or by modifying the shortcut parameters. If you have a log file defined in the Atoll.ini file, and run Atoll with the
-log option in the command line, the command line log file will have priority over the one mentioned in the Atoll.ini
file.
The option available in Atoll.ini is more suitable for running Atoll using macros. Apart from these options, you also
have the possibility to save the messages in the Event Viewer to a log file during an Atoll session (via context menu
of Event Viewer).
10.1.1.8 Displaying Insufficient Permission Messages in the Event Viewer

By default, a message is displayed in the Event Viewer when a user attempts to load an add-in for which he does not
have the necessary permissions. If you do not want insufficient permission messages to appear in the Event viewer,
add the following lines to the Atoll.ini file:
[EventsObserver]
ShowAddinAccessDeniedMsg = 0
ShowAddinAccessDeniedMsg is set to 1 by default.
10.1.1.9 Increasing the Maximum Printing Resolution

By default, Atoll limits the printing resolution to 150 dpi (dots per inch) to improve performance and consume less
memory when printing. If you want Atoll to print your maps in a higher resolution than 150 dpi, you can add the
following lines to the Atoll.ini file:
[Print]
MaxDPI = 300
300 dpi is given as an example only.
10.1.1.10 Copying Externalised Calculation Results on Save As

By default, when you save a copy of an Atoll document (File > Save As) with the following linked externalised
calculation results: private path loss matrices, path loss tuning measurement points catalog files, coverage
prediction numerical results, or microwave link profiles, a dialog box allows you to choose from the following
options:
◼ Make copies of the externalised calculation results with the new document
◼ Do not retrieve externalised calculation results for the new document
To set the default option and suppress this dialog box, add the following lines to the Atoll.ini file:
[Settings]
CopyExternalResultsDialog = 0
CopyExternalResults = value
CopyExternalResultsDialog is set to 1 by default. This means that the dialog box appears by default. Setting
CopyExternalResultsDialog to 0 hides the dialog box and the externalised calculation results are managed
according to the value of the CopyExternalResults option:
◼ 0: Do not retrieve externalised calculation results for the new document
◼ 1: Make copies of the externalised calculation results with the new document

CopyExternalResultsDialog is ignored when Atoll is run in non-interactive mode, for example using the API, and the
externalised calculation results are managed according to the value of the CopyExternalResults option.
10.1.1.11 Disabling External Storage of Numerical Coverage Prediction Results

The calculation results of coverage predictions that are displayed by value intervals are stored in external .studies
files that contain the numerical values. This allows you to change the prediction’s display thresholds without having
to recalculate it. It also enables the comparison of numerical values between predictions. You can disable storage
of numerical results in external files by clearing the Store prediction numerical results check box in the Predictions
Properties dialog box. You can also define the default value of this check box by adding the following lines to the
Atoll.ini file:
[Studies]
NumericalResults = value
When NumericalResults is set to 0, the Store prediction numerical results check box is cleared by default. When
NumericalResults is set to 1, the Store prediction numerical results check box is checked by default.
10.1.1.12 Disabling Generation of Prediction Study Files

When the prediction calculations generate external .studies files, it also generates an .svr.bil file, which allows you
to reimport the results into Atoll. You can disable the generation of this file by adding the following lines to the
Atoll.ini file:
[Studies]
ExportStudySvrFiles = 0
The default value for ExportStudySvrFiles is 1.
10.1.1.13 Exporting Predictions to Vector Files with a Display Configuration File

By default, when exporting a coverage prediction to a vector file with Atoll, the corresponding display configuration
file (.cfg) is simultaneously exported with the same file name and is saved in the same directory as the exported
vector-format file.
You can disable this behaviour by adding the following lines to the Atoll.ini file:
[Studies]
EnableStudyCompanionFileExport = 0
EnableStudyCompanionFileExport is set to 1 by default.
10.1.1.14 Exporting Prediction Coordinates using the Projection Coordinate System

When exporting a coverage prediction to a raster file in "Text Files (*.txt) format, you can export the prediction
coordinates using the Projection coordinate system (instead of the Display system) by adding the following lines
to the Atoll.ini file:
[Studies]
CoordSystemForTextExportIsProjection = 1
CoordSystemForTextExportIsProjection is set to 0 by default.

10.1.1.15 Restricting the List of Predictions for Creating Sector Traffic Maps
When you create a sector traffic map, i.e., traffic map based on cell coverage areas, Atoll uses an existing best
server coverage prediction in order to be able to distribute the live traffic data geographically. Atoll lets you select
the best server coverage prediction on which the traffic map will be based. In the list of available best server
coverage predictions, Atoll lists all the best server coverage prediction available in the Predictions folder, whether
they were created using a margin or without.
If you want Atoll to list only the best server coverage predictions that were created without a margin, i.e., with 0 dB
margin, you can add the following lines to the Atoll.ini file:
[Studies]
SelectNullMarginOnly = 1
SelectNullMarginOnly is set to 0 by default, which means that Atoll lists all the best server coverage predictions
available.
10.1.1.16 Displaying Path Loss Calculation Details in the Event Viewer

During path loss calculations, Atoll displays details about these calculations in the Tasks tab of the Event Viewer.
These details cannot be copied or saved. If you want access to these details, or to a summary of these details, once
the calculations have finished, you can add the following lines to the Atoll.ini file:
[Pathlosses]
DisplayInvalidityCause = 1
DisplayIndividualSuccessOrFailure = 1
DisplayOverallSuccessOrFailure = 1
Setting the DisplayInvalidityCause option to 1 will display the cause for which path losses were calculated for each
transmitter, setting DisplayIndividualSuccessOrFailure to 1 will display whether the path loss calculation succeeded
or failed for each transmitter, and setting DisplayOverallSuccessOrFailure to 1 will display the total number of path
loss matrices calculated, the number of path loss matrices calculated successfully, and the number of calculations
that failed.
These details are listed in the Events tab of the Event Viewer.
10.1.1.17 Mapping Atoll Coordinate Systems with MapInfo/ESRI Vector Files

It is now possible to define a mapping between the coordinate systems in Atoll and the coordinate systems defined
in the header files of MapInfo (MIF) and ESRI (PRJ) vector files that you want to import. You can define a mapping
between the two coordinate systems by adding the following lines to the Atoll.ini file:
[MITAB]
Coordinate system definition in the header file = Coordinate system code in Atoll
In this way, Atoll is able to exactly detect the coordinate system used by the vector file being imported. In MIF files,
the CoordSys clause defines the coordinate systems, datum, unit, and other information. The coordinate system
definition is different in the PRJ files. The syntax used in Atoll.ini follows the syntax of the CoordSys clause in MIF
files. Using the same syntax for MIF and PRJ files, Atoll is able to read the detect the coordinate systems for both
MapInfo and ESRI vector files.
The coordinate system codes in Atoll are stored in the CS files in the coordsystems folder. To access the coordinate
system codes through Atoll:
1. Select Tools > Options. The Options dialog box opens.
2. On the Coordinates tab, click the browse button (...) to the left of the Projection field. The Coordinate Systems
dialog box opens.
3. Select a coordinate system in the pane.
4. Click the Properties button. The Coordinate System properties dialog box opens.
The coordinate system code is available in the properties dialog box.

A few examples of such mapping are given below.
[MITAB]
; NTF
Earth Projection 1, 107 = 4275
; Tokyo
Earth Projection 1, 97 = 4301
; WGS 84 / UTM zone 31N
Earth Projection 8, 104, "m", 3, 0, 1, 500000, 0 = 32631
Earth Projection 8, 104, "m", 135, 0, 0.9996, 500000, 0 = 32653
Earth Projection 8, 104, "m", 141, 0, 0.9996, 500000, 0 = 32654
; NTF (Paris) / France II étendue
Earth Projection 3, 1002, "m", 0, 46.8, 45.8989188889, 47.69601444, 600000, 2200000
= 27595
10.1.1.18 Exporting Coverage Prediction Polygons in Text Format

You can export coverage predictions in the form of polygons to text format files.
 Enabling this option influences the export feature for all exportable vector fomats
(MIF, TAB, AGD, SHP, TXT). When this option is enabled, only the largest polygon is
exported for coverage layers having more than one polygon.
You can enable this feature by adding the following lines to the Atoll.ini file:
[Studies]
EnableLBS = 1
Setting EnableLBS to 1 adds a new coverage prediction export format "LBS Polygon Files (*.txt)" to Atoll. The
polygons are exported in a comma separated values format.
10.1.1.19 Defining Web Map Services Servers

Web Map Services allow you to directly import geographic data from specialised servers into Atoll. The list of WMS
servers can be defined in the Atoll.ini file as follows:
[WMS]
S1 = Server1
S2 = Server2
...
SN = ServerN
You can define any number of servers by incrementing the index N. These servers will be available in the WMS data
import dialog box in Atoll.
10.1.1.20 Improving Point Analysis Performance

You can improve the performance, i.e. the calculation speed, of the Point Analysis tool by restricting the number of
transmitters for which the received signal levels are calculated. To restrict the number of transmitters considered
in the Point Analysis tool, add the following lines to the Atoll.ini file:
[Perfos]
PtAnalysisNbServersMax = <number>

PtAnalysisMargin = <margin>
PtAnalysisNbServersMax allows you to define the maximum number of servers (i.e. transmitters or cells) to
consider when calculating the received signal levels. <number> is the maximum number of servers and is set to 100
by default. If PtAnalysisNbServersMax is set to zero, then no restriction is considered.
PtAnalysisMargin allows you to define a margin with respect to the best server signal level. Atoll calculates the
signal levels from all servers within a Y dB margin from the best server signal level. The default value is 30 dB.
In addition to the above, you can also set the maximum number of servers displayed in the Point Analysis window
and, consequently, the maximum number of arrows displayed in the Map window (from the pointer location). To set
this number, add the following lines to the Atoll.ini file:
[Perfos]
PtAnalysisNbServersDisplayed = Z
PtAnalysisNbServersDisplayed is set to 100 by default. It affects all tabs and reports of the Point Analysis tool in
GSM, LTE, WiMAX, and WiFi. Only the Reception tab is impacted in UMTS, CDMA2000, and TD-SCDMA.
10.1.1.21 Excluding Vectors from Imported KML/KMZ Files

By default, when a KML or KMZ file is imported in anAtoll document, the placemarks and vectors are both imported.
By defining the following option in the Atoll.ini file, you can import KML and KMZ files without vectors:
[Import]
LoadKMLVectors = 0
LoadKMLVectors is set to 1 by default, which means that vectors are imported along with placemarks.
10.1.1.22 Combining Imported Zone Files

By default, when you import a geographic data set user configuration file containing zones using Tools > User
Configuration > Load, the imported zones replace the existing ones. If you wish to merge the zones being imported
with the existing ones, add the following option in the Atoll.ini file:
[Import]
ShowOptionMergeZone = 1
ShowOptionMergeZone is set to 0 by default. When the option is set to 1, a Combine with existing zones option is
available in the User Configuration dialog box.
10.1.1.23 Check for Duplicate Cell Names During Import

When importing a series of cells from a CSV file, you can configure Atoll to display a warning message when two
cells have the same name. This avoids problems because Atoll expects cell names to be unique.
The verification of cell names can slow down the import process.
To enable the verification of duplicate cell names during the when importing cells, add the following option in the
Atoll.ini file:
[Import]
WarningSameValues = 1
WarningSameValues is set to 0 by default.

10.1.1.24 Setting the Precision for the Antenna Pattern Verification at Import
Atoll checks whether the vertical and horizontal patterns are correctly aligned at the extremities. The antenna
patterns are correctly aligned when:
◼ the horizontal pattern attenuation at 0° is the same as the vertical pattern attenuation at the pattern electrical
tilt angle, and
◼ the horizontal pattern attenuation at 180° is the same as the vertical pattern attenuation at the 180° less the
pattern electrical tilt angle.
By default, the option is inactive, i.e., the pattern attenuations are considered the same if they differ less than 100 dB.
If you want to change this default precision, add the following lines to the Atoll.ini file:
[Antenna]
PrecisionTimes10 = X
Where X is the required precision in dB multiplied by 10. For example, if you want to set the precision to 0.5 dB, X
will be 0.5  10 = 5 .
10.1.1.25 Setting a High Precision Mode for Microwave Antenna Pattern

By default, antenna patterns are stored with a one degree accuracy where each antenna diagram table contains 360
attenuation values. During calculations, Atoll interpolates attenuation values for higher precision angles.
You can configure Atoll to store higher precision diagrams specifically for microwave antennas where each antenna
diagram contains 3600 attenuation values (a value for every 0.1 degrees). When this option is enabled, during the
calculations, Atoll selects the closest defined attenuation value instead of interpolating the value.
To enable the high precision mode, add the following lines to the Atoll.ini file:
[Antenna]
HighResolutionAntennaPattern = 1
HighResolutionAntennaPattern is set to 0 by default.
10.1.1.26 Setting the Threshold for the Electrical Tilt and Azimuth Audit
By default, the electrical tilt and azimuth audit produces a report that lists antennas for which the difference between
either the calculated electrical tilt and the value defined in the vertical pattern, or the calculated electrical azimuth
and the value defined in the horizontal pattern, exceeds 1.5°. You can modify this threshold, in degrees, by adding
the following lines to the atoll.ini file:
[Antenna]
AntennaPatternConsistencyDifference = <value in degrees>
AntennaPatternConsistencyDifference is set to 1.5 by default.
10.1.1.27 Exporting Selected Data Tables to XML Files

If you want to select the tables that you want to export to XML files, add the following lines to the Atoll.ini file:
[Export]
AdvancedXML = 1
AdvancedXML is set to 0 by default.

10.1.1.28 Keeping the Original List Separator when Exporting in CSV Format
Before exporting in CSV format, Atoll verifies if the list separator symbol is identical to the decimal or digit grouping
symbols defined in your regional settings.
By default, Atoll will change the list separator if it is found to be identical to the decimal symbol or the digit grouping
symbols. You can force Atoll to keep the original list separator symbol by adding the following option in the Atoll.ini
file:
[Export]
AlwaysUseListSeparatorInCSV = 1
AlwaysUseListSeparatorInCSV is set to 0 by default.
10.1.1.29 Opening Exported XLS Files Automatically in MS Excel

When you export an entire data table, or selected columns, to an MS Excel file, Atoll can automatically run MS Excel
once the export is complete and open the XLS file created by the export in MS Excel. To enable this feature, add the
following option in the Atoll.ini file:
[Export]
AutoOpenWithExcel = 1
AutoOpenWithExcel is set to 0 by default.
10.1.1.30 Disabling Creation of New Documents from Templates

You can disable the creation of new Atoll documents from templates by adding the following lines to the Atoll.ini file:
[GUIUserRights]
EnableNewDocFromTemplate = 0
EnableNewDocFromTemplate is set to 1 by default.
10.1.1.31 Blocking Access to Macros and Add-ins

You can block access to the Add-ins and Macros dialog box by adding the following lines to the Atoll.ini file:
[GUIUserRights]
EnableMacrosAddins = 0
EnableMacrosAddins is set to 1 by default.
10.1.1.32 Disabling Saving and Opening ZIP Files

You can block access to the File > Save to Zip and File > Open From Zip menus by adding the following lines to the
Atoll.ini file:
[GUIUserRights]
EnableZip = 0
EnableZip is set to 1 by default.

10.1.1.33 Hiding the Propagation Models Folder in the Parameters Explorer

You can hide the Propagation Models folder in the Parameters explorer by adding the following lines to the Atoll.ini
file:
[GUIUserRights]
HidePropagationModelsFolder = 1
HidePropagationModelsFolder is set to 0 by default.
10.1.1.34 Forbidding Shared Antenna Modification in Multi-RAT Documents

When all technologies are not present in a multi-RAT document (3GPP or 3GPP2), you can forbid the modification
of shared antenna parameters by adding the following lines to the Atoll.ini file:
[GUIUserRights]
AllowSharedParameterModification = 0
The following message will be displayed in the Events viewer:

"Modifying a shared antenna is only allowed if all technologies from the database are being used in the current
document".
AllowSharedParameterModification is set to 1 by default.
10.1.1.35 Enabling Notification for Donor Transmitter Parameter Modifications

Atoll can notify you whenever a donor transmitter parameter, which has an impact on a repeater, is modified. To
activate the notification, add the following lines to the Atoll.ini file:
[Transmitter]
CheckImpactOnRepeaters = 1
CheckImpactOnRepeaters is set to 0 by default, which means that no notifications are displayed.
10.1.1.36 Setting the Display Precision of Floating Point Values

Most floating point values in Atoll are formatted for displaying two digits after the decimal point. However, in case
of documents connected to databases (other than MS Access), some non-formatted floating point values can be
displayed with too many digits after the decimal point.
You can set the display precision for non-formatted floating point values in Atoll dialog boxes and tables. For
example, in order to display two digits after the decimal point, you can add the following lines to the Atoll.ini file:
[Grids]
NbDecimals = 2
This option applies to most non-formatted floating point parameters in Atoll, i.e., excluding geographic coordinates,
formatted floating point values, and certain values where decimal precision is important.
NbDecimals is set to -1 by default. This corresponds to maximum precision, i.e., all the digits after the decimal point
available in the database are displayed.
10.1.1.37 Changing the Path to Linked Geo Data Files

You can change the path to a linked geographic data file by clicking the Find button in the Properties dialog boxes
of the file. By default, the Find button in the Properties dialog box is available only for missing geographic data files,
i.e., the linked files that Atoll is unable to locate and load. However, you can enable the Find button even for available
geographic data files by adding the following lines to the Atoll.ini file:

[Geo]
FindGeoButtonAlwaysActive = 1
FindGeoButtonAlwaysActive can be useful when you have changed the location of a geographic data file, and you
wish to change the path to the new location. It is set to 0 by default.
 When changing the path to a linked geographic data file, you must provide the new
path to the same file. This option does not allow linking to another file instead. In
order to link to another file, you must follow the normal file import procedure.
10.1.1.38 Exporting/Importing Vector Data with a Display Configuration File

By default, when you export vector data from an Atoll document, the corresponding display configuration file (CFG)
of the edited vector layer is simultaneously exported. The exported display configuration file will have the same file
name and will be saved in the same directory as the exported vector-format file.
You can disable this behaviour by adding the following lines to the Atoll.ini file:
[Geo]
VectorDisplayConfigurationCompanionFile = 0
VectorDisplayConfigurationCompanionFile is set to 1 by default. When you import vector data in an Atoll document,
the same option enables you to simultaneously import the corresponding display configuration file (CFG). The
display configuration file will only be imported if it has the same file name and if it is located in the same directory
as the imported vector-format file.
10.1.1.39 Using Only Visible Geo Data in Prediction Reports

By default, Atoll takes into account all the geographic data when generating prediction reports, whether the
geographic data is visible on the map or not. You can change the default behaviour for population, traffic, and
generic geographic data by adding the following lines to the Atoll.ini file:
[Geo]
ReportObeysVisibility = 1
ReportObeysVisibility is set to 0 by default.
10.1.1.40 Exporting BMP, TIF, and PNG Files with a TAB Reference File
When exporting BMP, TIF, and PNG files, Atoll can export the georeference information in a TAB file instead of the
default respective World files (BPW or BMW for BMP, TFW for TIF, and PGW for PNG). If you want Atoll to export the
georeference information in a TAB file when you export in BMP, TIF, and PNG formats, add the following lines to the
Atoll.ini file:
[RasterExport]
GeorefWithTAB = 1
GeorefWithTAB is set to 0 by default.
10.1.1.41 Exporting BIL Files with a PRJ Projection File

When you export a BIL file, you can force Atoll to generate an additional PRJ projection file for compatibility with
ESRI. To enable this functionality, add the following lines to the Atoll.ini file:
[RasterExport]
ExportBILAsESRI = 1

ExportBILAsESRI is set to 0 by default.
10.1.1.42 Co-Planning: Linking the Sites Folder

You can link the Sites folder, in addition to the Transmitters and Predictions folders, of a document to another
(main) document using the File > Link With command by adding the following lines to the Atoll.ini file:
[CoPlanning]
LinkSites = 1
LinkSites is set to 0 by default.
10.1.1.43 Disabling Normalisation of MIF/TAB Vector Files

When importing vector files, Atoll normalises all the vectors in the files based on the convention that a vector whose
vertices coordinates are defined clockwise creates a filled polygon, and a vector whose vertices coordinates are
defined counter-clockwise creates a hole. MapInfo vectors do not follow the same convention, and hence their
normalisation at the time of import can take a long time. If you want to disable this normalisation when importing
MIF and TAB vector files, add the following lines to the Atoll.ini file:
[MITAB]
DisableNormalization = 1
DisableNormalization is set to 0 by default.
10.1.1.44 Customising Performance Optimisation when Exporting Vector Files in TAB Format
When you export vector files in TAB format, the performance is optimised by default , i.e. the export process is less
time-consuming. If the resulting TAB files do not meet the quality level you were expecting, you can disable the
performance optimisation feature by adding the following lines to the Atoll.ini file :
[MITAB]
OptimizedTABExport = 0
OptimizedTABExport is set to 1 by default.
10.1.1.45 Adding the Duplicate Site to the Original Site’s Site List
When you duplicate a site, you can choose to add the duplicate site to the site list (if any) of the original site by
adding the following lines to the Atoll.ini file:
[Site]
AddToSiteListOnDuplicate = 1
AddToSiteListOnDuplicate is set to 0 by default.
10.1.1.46 Moving Sites without Moving Antennas

By default, when an existing site is moved, its transmitters and antennas are relocated relative to the new
coordinates of the site. You can force antennas to keep their coordinates when the site moves by adding the
[GUI]
MoveSiteMethod = 1

MoveSiteMethod is set to 0 by default. The following behaviour occurs when you move a site according to the value
of MoveSiteMethod:
MoveSiteMethod Behaviour
0 The relative coordinates of the antennas follow the coordinates of the site.
1 The absolute coordinates of the antennas do not change.
2 A dialog box appears asking you whether to move the antennas with the site or not.
10.1.1.47 Real Altitude versus DTM Altitude in Sites’ Properties
10.1.1.47.1 Duplicate/Moved Sites

By default, when an existing site is duplicated/moved in the map (or when its coordinates are modified from its
Properties dialog box or from the Sites table) while a Real altitude is defined, the same Real altitude is inherited by
the duplicate/moved site. You can force Atoll to clear the duplicate/moved site’s Real field or to populate it with the
duplicate/moved site’s own DTM value by adding the following lines to the Atoll.ini file:
[Site]
ResetAltitude = 0|1|2
ResetAltitude is set to 0 by default. The following occurs to the duplicate/moved site according to the setting of
ResetAltitude:
ResetAltitude Real field of duplicate/moved sites
0 The Real field of the duplicate/moved site inherits the original site’s Real altitude.
1 The Real field of the duplicate/moved site is cleared.
2 The Real field of the duplicate/moved site inherits the duplicate/moved site’s own DTM value.
 If a site’s coordinate(s) and its real altitude are modified at the same time (from the
site’s Properties dialog box or from the Sites table), the new value in the Real field
will be kept even if ResetAltitude is set to 1 or 2.
10.1.1.47.2 New Sites

By default, when you create/drop a new site, repeater, remote antenna, or any type of link in the map, the Real field
in the sites’ Properties dialog boxes is cleared by default. You can force Atoll to populate it with the actual DTM
value by setting ResetAltitude to 2.
ResetAltitude Real field of new sites
1 The Real field of the new site is cleared.
2 The Real field of the new site inherits the site’ own DTM value.
10.1.1.48 Using Only Visible Clutter Classes in Interference Prediction Reports

By default, Atoll takes into account all the clutter classes when generating reports on interference-based coverage
predictions, whether the clutter classes are visible on the map or not. You can change the default behaviour by
[Clutter]
OnlyVisibleClassesInInterferenceReport = 1

OnlyVisibleClassesInInterferenceReport is set to 0 by default. The visibility of clutter classes on the map can be
managed through the Display tab of the Properties dialog box of the Clutter Classes folder. Using this option, you
can exclude clutter classes which are not relevant in interference prediction reports, for example, water.
10.1.1.49 Displaying % of Covered Clutter Classes w. r. t. the Focus Zone in Reports

In coverage prediction reports, Atoll displays the percentages of covered clutter classes with respect to the total
surface area of all the clutter classes covered by the prediction. If you want Atoll to display the percentages of
covered clutter classes with respect to the total surface area of all the clutter classes within the Focus Zone, add
[Clutter]
PerClassPercentagesRelativeToCoverageInReport = 0
PerClassPercentagesRelativeToCoverageInReport is set to 1 by default.
10.1.1.50 Displaying % of Covered Traffic Classes w. r. t. the Focus Zone in Reports

In coverage prediction reports, Atoll displays the percentages of covered environment traffic classes with respect
to the total surface area of all the environment traffic classes covered by the prediction. If you want Atoll to display
the percentages of covered environment traffic classes with respect to the total surface area of all the environment
traffic classes within the Focus Zone, add the following lines to the Atoll.ini file:
[Traffic]
PerClassPercentagesRelativeToCoverageInReport = 0
PerClassPercentagesRelativeToCoverageInReport is set to 1 by default.
10.1.1.51 Synchronising Private and Shared Path Loss Matrices

When calculations are run, Atoll verifies whether the shared and private path loss matrices are valid. You can force
Atoll to delete private path loss matrices by adding the following lines to the Atoll.ini file:
[Pathlosses]
FullResyncPrivShared = 0|1|2
◼ When FullResyncPrivShared is set to 0: invalid private path loss matrices are deleted if shared path loss
matrices are valid when running calculations or checking the validity of path loss matrices (Propagation tab
of the transmitter Properties dialog box). Valid private path loss matrices are preserved.
◼ When FullResyncPrivShared is set to 1: in addition to the 0 setting, valid private path loss matrices are deleted
if shared path loss matrices are valid when checking the validity of path loss matrices.
◼ When FullResyncPrivShared is set to 2: in addition to the 1 setting, valid private path loss matrices are deleted
if shared path loss matrices are valid when running calculations. This setting is not compatible with the use
of tuned path loss matrices.
FullResyncPrivShared is set to 1 by default.
If you have private path loss matrices tuned using measurement data, setting
+
◼
FullResyncPrivShared to 2 will force Atoll to delete them automatically when
calculations are run.
◼ You should set FullResyncPrivShared to 1 when working with tuned private
path loss matrices.

10.1.1.52 Selecting the Logo 2 Check Box by Default in Print Setup

Print setup parameters are stored in the Atoll documents, and you can save the print setup parameters in CFG files
(see "Print Setup Configuration" on page 141). If you wish to have the Logo 2 check box selected by default for any
new Atoll document, add the following lines to the Atoll.ini file:
[Print]
LogoFooterChecked = 1
LogoFooterChecked is set to 0 by default.
10.1.1.53 Filtering Predictions by Technology When Reading the XML Studies File
In the XML studies file, some common CDMA coverage predictions can be available for CDMA2000 and UMTS, or
some common OFDMA coverage predictions can be available for WiMAX and LTE. If you want to filter the
customised predictions stored in the XML studies file by technology, e.g. separate the WiMAX and LTE coverage
predictions, and load only the predictions specific to the technology of the current Atoll document, add the following
lines to the Atoll.ini file:
[Studies]
CustomStudiesFilteredByTechno = 1
CustomStudiesFilteredByTechno is set to 0 by default. This option is only relevant for reading the XML studies file.
Atoll always writes the technology type in the XML studies file when customised coverage predictions are saved in
it.
10.1.1.54 Enabling Event Viewer Messages for MapInfo File Import/Export

You can enable the display of Event Viewer information, warning, or error messages related to MapInfo files by
[MITAB]
EnableMessages = 1
EnableMessages is set to 0 by default. Atoll does not display any message related to MapInfo file import and export.
10.1.1.55 Setting the Resolution of Population Maps in Coverage Prediction Reports

Atoll uses the default resolution, defined in the Predictions folder’s Properties dialog box, for rasterisation of the
population maps. In order to use a different resolution for higher or lower precision, you can add the following lines
[Population]
ReportResolution = X
Where X is the resolution for the conversion of population map vectors into raster.
 If you set ReportResolution to a very precise (low) value, the performance

(calculation speed) can be considerably decreased depending on the size of the
population maps in the document. It is recommended to set this parameter to an
optimum value, i.e., just precise enough to get the required accuracy.
10.1.1.56 Setting the Precision in Coverage Prediction Reports

You can set the precision of the floating point values displayed in the absolute value columns of coverage prediction
reports by adding the following lines to the Atoll.ini file:

[Studies]
ReportDecimalPlacesAbsolute = X
Where X is the number of digits following the decimal.

You can set the precision of the floating point values displayed in the percentage value columns of coverage
prediction reports by adding the the following lines to the Atoll.ini file:
[Studies]
ReportDecimalPlacesPercent = X
Where X is the number of digits following the decimal.

If these parameters are set to -1, the values are displayed with the default decimal settings of each column.
10.1.1.57 Including Pixel-free Ranges in Coverage Prediction Reports

By default, the ranges which do not contain any pixels do not appear in the coverage prediction reports. You can
include these ranges in coverage prediction reports by adding the following lines to the Atoll.ini file.
[Studies]
ShowIntervalsWithNoCoverageInReport = 1
ShowIntervalsWithNoCoverageInReport is set to 0 by default.
10.1.1.58 Changing Hot Spot Reference Surface in Prediction Reports

In a coverage prediction report, Atoll displays the percentage of hot spots covered by each coverage layer (display
thresholds) with as reference the hot spot surface area covered by the whole prediction. If you want Atoll to display
the percentage of hot spots covered by each coverage layer (display thresholds) with as reference the hot spot
surface area, add the following lines to the Atoll.ini file:
[Studies]
UseFullHotSpotSurfaceOnReport = 1
UseFullHotSpotSurfaceOnReport is set to 1 by default.
10.1.1.59 Exporting Only Visible Value Interval Layers of Coverage Predictions

By default, Atoll exports all the layers (levels) of a coverage prediction being exported. For some coverage
predictions (coverage predictions displayed by value intervals and not by discrete values, excluding GSM coverage
predictions by coding schemes, throughput, and CQI), you can export only the visible levels by adding the following
[Studies]
ExportOnlyVisibleLevels = 1
ExportOnlyVisibleLevels is set to 0 by default, which means that when a coverage prediction is exported, Atoll will
export all of its levels whether they are visible or not.
 Atoll exports only visible coverage predictions. If a coverage prediction consists of

only one level, the visibility check box of that level also controls the visibility check
box of the prediction itself. This means that if the visibility check box of the only
level of such a prediction is cleared, the prediction will itself be hidden and will not
be exported.

10.1.1.60 Avoiding Overlapping Pixels in Best Server Coverage Prediction

In best server coverage predictions, i.e., Coverage by Transmitter with option "Best server" and a margin of 0 dB,
some pixels can be covered by more than one transmitter if the received signal level from two or more transmitters
is exactly the same. To avoid this, add the following lines to the Atoll.ini file:
[Studies]
NoOverlapOnBestServer = 1
NoOverlapOnBestServer is set to 0 by default. When NoOverlapOnBestServer is set to 1, Atoll arbitrarily selects one
of the best servers on such pixels. This option can be useful, for example, when calculating population statistics
based on a best server coverage prediction. When a pixel is covered by more than one best server, the population
belonging to that pixel is counted as many times as the number of best servers, which can give erroneous
percentages of covered population.
10.1.1.61 Using Legacy Coverage Prediction Reports

If you want to revert to the old report layout, you can add the following lines to the Atoll.ini file:
[Studies]
ReportMethod = 0
ReportMethod is set to 1 by default.
10.1.1.62 Setting the Minimum ATL File Size Requiring Compression

You can set the file size above which Atoll should compress data in ATL files by adding the following lines to the
Atoll.ini file:
[Compression]
StartSizeInMB = X
Where X is the file size in MB. Atoll will compress the ATL file if it is larger than X. By default, StartSizeInMB is set
to 200.
10.1.1.63 Loading, Activating, and Setting Add-ins as Visible

Installed add-ins are automatically loaded by Atoll and appear in the Add-ins and Macros dialog box. You can
change this default behaviour for each individual add-in as follows:
◼ If you want an add-in neither to be loaded (i.e., deactivated) nor be available in the Add-ins and Macros dialog
box, add the following lines to the Atoll.ini file:
[Add-ins]
Add-in Name = 0
◼ If you want an add-in to be loaded, activated, and accessible in the Add-ins and Macros dialog box for
activation/deactivation, add the following lines to the Atoll file:
[Add-ins]
Add-in Name = 1
◼ If you want an add-in to be loaded and activated, but only shown in the Add-ins and Macros dialog box for
information (impossible to deactivate), add the following lines to the Atoll.ini file:
[Add-ins]
Add-in Name = 2

◼ If you want to set an add-in to be mandatory for Atoll, add the following lines to the Atoll.ini file:
[Add-ins]
Add-in Name = 3
Any add-in set to option 3 will be loaded and activated, but only shown in the Add-ins and Macros dialog box
for information (impossible to deactivate). Atoll will not run if it is unable to load this add-in.
Add-in Name is the name of the add-in as it appears in the Add-ins and Macros dialog box. Atoll fails to start if for
some reason it is unable to load an add-in whose status is set to 3. The default status for add-ins is 1.
10.1.1.64 Defining Online Map URLs

Online maps allow you to display map data from the Internet in Atoll. You can define a list of online map URLs in the
Atoll.ini file as follows:
[OnlineMaps]
Name1 = City1
URL1 = http://...
Name2 = City2
URL2 = http://...
...
NameN = CityN
URLN = http://...
You can define any number of online map URLs by incrementing the index N. These URLs will be available in the
online map import dialog box in Atoll.
If you need to use a proxy server for accessing online maps, you must specify the IP address of the proxy server by
[HTTP_REQUEST]
Proxy = IP_address
By default, the Proxy option is empty.
10.1.1.65 Changing the Default Cache Location for the Loaded Map Tiles
The map tiles that you load into Atoll are stored in a specific cache directory named after the corresponding tile
server. By default, the location of this cache is "%TEMP%\OnlineMaps". You can change this location by adding the
[OnlineMaps]
TilesCachePath = new_path
10.1.1.66 Defining the Microsoft Bing Tile Server for Online Maps
If you want to define the Microsoft Bing Maps Server for online maps, you must request a Bing Maps key from
Microsoft and use it with the following option in the Atoll.ini file:
[OnlineMaps]
BingKey = key
BingMetadataUrl=http://dev.virtualearth.net/REST/V1/Imagery/Metadata/%s
You must request your key from Microsoft. When BingKey is specified with a valid key, "Bing" becomes available
under Provider in the Add a Tile Server dialog box. A Type and a Language must also be defined before you can
validate.

◼ Type: available choices are "Aerial", "Road", and "Hybrid"

◼ Language: default languages are "English", "French", and "Japanese".
More languages can be selected if they are defined with the following options in the same section of the
Atoll.ini file:
BingCultureX = culture
For example: X = 0, culture = "pa-Arab"
BingLanguageX = language
For example: X = 0, language = "Punjabi (Arabic)"
 X = 0 is equivalent to 4th position in the Language list (after the 3 default languages)
culture and language settings can be found in the Culture and Language columns
at the following URL: http://msdn.microsoft.com/en-us/library/hh441729.aspx
The BingMetadataUrl value specifies the URL for the Bing metadata. You can change this value if Microsoft changes
its default URL.
10.1.1.67 Defining the Microsoft Bing Tile Server for Online Searches
By default, when you search for a point on the map by its full or partial postal address, Atoll returns specific search
results. If you want to force Atoll to return a list of results based on the Microsoft Bing Maps server, you must
request a Bing Maps key from Microsoft and use it with the following option in the Atoll.ini file:
[OnlineSearch]
BingKey = key
BingLocationUrl=http://dev.virtualearth.net/REST/v1/Locations/
The BingLocationUrl value specifies the URL for the Bing location queries. You can change this value if Microsoft
changes its default URL.
10.1.1.68 Defining MapQuest for Online Searches

By default, when you search for a point on the map by its full or partial postal address, Atoll returns specific search
results. If you want to force Atoll to return a list of results based on the MapQuest server, you must request a key
from MapQuest and use it with the following option in the Atoll.ini file:
[OnlineSearch]
MapQuestKey = key
10.1.1.69 Managing Carriage Returns in Imported TXT/CSV Files

By default when you export the content of a table in TXT or CSV formats, the carriage returns (e.g. in a "Comments"
frame) are replaced by "\n" characters in the exported file. When you import this file in an Atoll document, these "\n"
characters are in turn replaced by carriage returns.
If you want, you can force Atoll to replace carriage returns by spaces instead of "\n" characters in the exported tables
by adding the following lines to the Atoll.ini file:
[Export]
NewLineEscapeSequence = " "

10.1.1.70 Deleting the Filtering Zone on Removing Filters From Tables

By default, when you remove filters applied to tables, Atoll keeps the filters applied on through the map using the
filtering zone. To remove the filtering zone as well when removing filters from tables, add the following lines to the
Atoll.ini file:
[Settings]
KeepFilterZoneOnRemoveFilter = 0
KeepFilterZoneOnRemoveFilter is set to 1 by default.
10.1.1.71 Disabling the Database and Data Exchange Commands

You can disable the Database and Data Exchange commands in Atoll’s Document menu by adding the following
[Settings]
EnableDataExchangeCommands = 0
EnableDataExchangeCommands is set to 1 by default.
10.1.1.72 Enabling Atoll to Automatically Restart on Improper Exit

If you wish Atoll to restart automatically after it closes unexpectedly, add the following lines to the Atoll.ini file:
[System]
RestartOnImproperExit = 1
RestartOnImproperExit is set to 0 by default. If set to 1, Atoll restarts following an improper exit without using any
command line options that may be defined for its shortcut.
10.1.1.73 Specifying Default Folders

Whenever Atoll loads, saves, imports, or exports the following files, Atoll opens a file selector dialog box.
◼ Atoll documents (opening, opening as zip, saving, saving as zip).
◼ User configuration files (loading and saving).
◼ Zones (importing).
◼ Predictions (generating and exporting single and multiple predictions).
◼ Geo files (exporting vector files, zones, terrain sections, clutter, population, traffic, DTM, and so on).
◼ Grid views, XML, and generic files (importing and exporting).
You can specify default paths for the various folders used for saving Atoll files by adding the following lines in the
Atoll.ini file:
[DefaultFolders]
RootFolder = <path shortcut>
ATLFilesFolder = <path for loading and saving Atoll documents>
UserConfigurationFilesFolder = <path for loading and saving configuration files>
ImportFolder = <path for importing files and zones>
PredictionExportFolder = <path for generating and exporting predictions>
GeoExportFolder = <path for exporting and saving geo files>
DataExchangeImportFolder = <path for importing grid views and XML files>
DataExchangeExportFolder = <path for exporting grid views and XML files>
CustomReportExportFolder = <path for exporting microwave custom reports>
You can use RootFolder as a global shortcut, which can be used in the other folder paths. For example:
RootFolder = \\Server\Path

ATLFilesFolder = {RootFolder}\ATL
You can use the shortcut {UserLogin} to replace the Windows user name. For example:
RootFolder = \\Server\Path
ATLFilesFolder = {RootFolder}\ATL\{UserLogin}
In this case, if the user name is JSmith, then the default directory for ATL files is:
\\Server\Path\ATL\JSmith
10.1.1.74 Specifying the Default Storage of Favourite Views

You can specify whether favourite views are created and stored in the user profile or in the current document by
adding the following lines in the Atoll.ini file:
[FavouriteViews]
DefaultStorage = 0|1
◼ When DefaultStorage is set to 0, favourite views are created and stored in the user profile.
◼ When DefaultStorage is set to 1, favourite views are created and stored in the document.
DefaultStorage is set to 0 by default, which means that favourite views are created and stored in the user profile.
10.1.1.75 Restoring Focus and Computation Zones of a Favourite View

You can save the definition of a computation zone and a focus zone in favourite views and restore those zones when
applying a favourite view by adding the following lines to the Atoll.ini file:
[FavouriteViews]
UpdateFocusAndComputationZone = 1
UpdateFocusAndComputationZone is set to 0 by default, which means that the computation zone and focus zone
are not saved in the favourite views.
10.1.1.76 Fixing Antenna Electrical Azimuth and Tilt Values on Document Update
Antenna electrical azimuths and tilts are used in calculations to determine the attenuation due to antenna patterns
in different directions. Therefore, it is important that these values be correct. When you update Atoll documents
from version 3.2 to 3.3, you can have Atoll check and fix any erroneous values in the Antennas table.
◼ If you want Atoll to ignore any errors in the electrical azimuths and tilts, add the following lines to the Atoll.ini
file:
[Antenna]
CheckOrFixElecAzAndTilt = 0
◼ If you want Atoll to notify you about any errors in the electrical azimuths and tilts, add the following lines to
the Atoll.ini file:
[Antenna]
◼ If you want Atoll to notify you about any errors in the electrical azimuths and tilts and fix these errors, add the
[Antenna]
◼ If you want Atoll to notify you about any errors in the electrical azimuths and tilts and set the electrical
azimuths to 0, add the following lines to the Atoll.ini file:

[Antenna]
By default, CheckOrFixElecAzAndTilt is set to 0.
10.1.1.77 Limiting the Antenna Selection Assistant to the Antenna folder

By default, the Antenna Selection Assistant limits its display to the list of antennas that are displayed in the
Antennas folder. This means that you can create and apply a user configuration file to filter the Antennas folder,
which then limits antenna selection to a subset of the full antenna database.
You can set the Antenna Selection Assistant to display all available antennas, regardless of the user configuration
of the Antennas folder, by adding the following lines to the Atoll.ini file.
[Antenna]
LimitChoiceToAntennaFolder = 0
By default, LimitChoiceToAntennaFolderConfig is set to 1.
10.1.1.78 Simplified Cell Naming

In networks where there is only one cell per transmitter, you can use a simplified naming convention where the
default name of the first cell is the same as the name of the transmitter. To enable this option, add the following
For LTE, WiFi, WiMax, and LPWA networks:
[OFDMCells]
DefaultFirstCellNameIsTxName = 1
For UMTS, CDMA2000, and TD-SCDMA networks:
[3GCells]
DefaultFirstCellNameIsTxName = 1
The default value for DefaultFirstCellNameIsTxName is 0. When this option is enabled, if other cells are created for
a transmitter, then they are named with the standard naming convention (Transmitter name followed by the carrier).
10.1.1.79 Disabling References to Atoll Live

Atoll Live enables you to use live network measurement data, such as Key Performance Indicators (KPI) and User
Equipment (UE) traces, including MDT traces (Minimisation of Drive Tests), for network planning and optimisation
in Atoll. Atoll Live requires a specific license.
You can hide all references to the Atoll Live module, including KPIs, and UE traces, in Atoll by adding the following
[Licenses]
Live = 0
By default, Live is set to 1.
10.1.1.80 Enabling the Import of GSM OSS Data with the Atoll Live Module
The Atoll Live module for GSM can import files from OSS systems into your GSM document. You can use the OSS
configuration management tools from various vendors to obtain and export the data.
To enable this capability, add the following lines to the Atoll.ini file:

[GSM_Live]
GsmLiveGui=1
By default, GsmLive is set to 0.
10.1.2 GUI Options
10.1.2.1 Defining the Parameters for the Default Sites Symbol

You can define the parameters of the default symbol used for displaying sites on the map through the Atoll.ini file.
You can define the parameters as follows:
[SitesSymbol]
FontName = Name of the font
Symbol = Character used for the site symbol from the character set of the font
Size = Character size in number of pts
Color = Colour of the symbol
The default sites symbol is used when a new document is created in Atoll. To know the name of the font to use, and
to set the symbol, you can use the Windows’ Character Map tool. You can use the copy/paste features to set the
symbol in the Atoll.ini file.
Example:
[SitesSymbol]
FontName = Wingdings
Symbol = ¤
Size = 12
Color = 0
10.1.2.2 Using a Unique Symbol for Remote Antennas

By default, remote antennas are displayed using the same symbol on the map as transmitters. If you wish to display
remote antennas using a unique, non-modifiable symbol, add the following lines to the Atoll.ini file:
[RemoteAntennas]
FrozenSymbol = 1
FrozenSymbol is set to 0 by default.
10.1.2.3 Using the Transmitter Symbol for Repeaters

By default, repeaters are displayed using a unique symbol on the map. If you wish to display repeaters using the
same symbol as that of the transmitters, add the following lines to the Atoll.ini file:
[Repeaters]
FrozenSymbol = 0
FrozenSymbol is set to 1 by default.

10.1.2.4 Keeping Transmitter Symbols From Changing on Search

When using the Search Tool, all the transmitters that do not fulfil the search criteria are displayed as grey lines on
the map. If you want these transmitters to keep their original symbols, add the following lines to the Atoll.ini file:
[Transmitter]
ChangeSymbolOnSearch = 0
ChangeSymbolOnSearch is set to 1 by default.
10.1.2.5 Displaying Filled Symbols for Inactive Transmitters on the Map

By default, Atoll empties the symbols of inactive transmitters, repeaters, and remote antennas on the map. If you
wish to display filled symbols for inactive transmitters, repeaters, and remote antennas on the map, add the
[Transmitter]
EmptySymbolWhenInactive = 0
EmptySymbolWhenInactive is set to 1 by default.
10.1.2.6 Refreshing the Display Automatically When a New Station is Dropped

You can have Atoll refresh the display automatically each time a new station or a group of stations is dropped on
the map by adding the following lines to the Atoll.ini file:
[Transmitter]
AutoSynchronizeDisplay = 1
AutoSynchronizeDisplay is set to 0 by default.
10.1.2.7 Hiding Information Displayed in the Status Bar

Using compressed geo data formats (TIFF, Erdas Imagine, ECW) can cause performance loss due to real-time
decompression. Performance can be improved by either hiding the Status Bar or by hiding some of the information
displayed in the Status Bar (altitude, clutter class, or clutter height). To hide information in the Status Bar, add the
following lines to the Atoll.ini:
[StatusBar]
DisplayZ = 0
DisplayClutterClass = 0
DisplayClutterHeight = 0
DisplayZ, DisplayClutterClass and DisplayClutterHeight respectively refer to the display of altitude, clutter class, and
clutter height.
10.1.2.8 Displaying Date and Time in the Event Viewer

You can instruct Atoll to display the date, and time with milliseconds in the Event viewer. To display this information,
[EventsObserver]
milliseconds = 1
date = 1
milliseconds is set to 0 by default.

date is set to 1 by default.
10.1.2.9 Changing the Mouse Wheel Zoom Method

In Atoll, you can zoom in and out on the map window directly by rotating the mouse wheel. This is the default zoom
method using the mouse wheel. You can change this zoom method to require the Ctrl key to be pressed while
rotating the mouse wheel in order to zoom in and out on the map window.
To change the mouse wheel zoom method, add the following lines to the Atoll.ini file:
[Settings]
ZoomWithCtrlKey = 1
ZoomWithCtrlKey is set to 0 by default.
10.1.2.10 Setting the Maximum Number of Lines to Coverage Prediction Tool Tips
If you have more than one coverage prediction displayed on the map, the tool tips display the tip text for all the
coverage predictions available at a pixel up to 30 lines by default. You can change this default number of tool tip
text lines through the following option in the Atoll.ini file:
[Studies]
MultiplePlotsTipTextLines = X
X is the number of lines to display in the tool tips. By default, MultiplePlotsTipTextLines is set to 30. If you set it to
a very large value, however, the tool tip might not display correctly.
10.1.2.11 Changing the Display for Downlink Smart Antenna Results

The downlink smart antenna simulation results, i.e, the angular distributions of downlink transmitted power density,
calculated during Monte Carlo simulations using the Optimum Beamformer and Conventional Beamformer can be
displayed in two different ways. By default, these diagrams take into account the antenna pattern of the single
antenna element. If you want to these diagrams to represent the average array correlation matrices alone
(symmetric about the horizontal axis), add the following option in the Atoll.ini file:
[SAModel]
DrawSingleElementPattern = 0
H
DrawSingleElementPattern is set to 1 by default, and the displayed diagram is g n     S   R Avg  S  . When you set
H
DrawSingleElementPattern to 0, the diagram displayed will represent S   R Avg  S  .
10.1.2.12 Adding Exposure Analysis to the List of Multi-RAT Coverage Predictions (Hidden en
3.2.0.02, ces infos sont dans TN013)
The maximum permissible exposure (MPE) to electromagnetic fields (EMF) can be analysed in single-RAT and
multi-RAT documents. A multi-RAT exposure analysis is a combination of the corresponding single-RAT exposure
analyses.
You can include "Exposure Analysis" in the list of coverage predictions available in single-RAT and multi-RAT
documents by adding the following lines to the Atoll.ini file:
[Studies]
ExposureStudy = 1
When Exposure Analysis predictions are enabled, "Exposure Analysis" appears in the list of predictions in all types
of single-RAT (except TD-SCDMA and Wi-Fi) and multi-RAT (including 3GPP2) documents.

10.1.2.13 Displaying Coverage Prediction Comments in the Legend Window

You can display the contents of the Comments box of coverage prediction properties in the Legend window by
[Studies]
CommentsInLegend = 1
The comments are displayed between the name of the coverage prediction and the thresholds. CommentsInLegend
is set to 0 by default.
10.1.2.14 Displaying Leading Zeros in the CELL_IDENTITY Field

By default, Atoll does not display leading zeros in the CELL_IDENTITY field of the Transmitters table in GSM and the
Cells tables in UMTS, CDMA2000, and TD-SCDMA. For example, cell identity "00678" is displayed as "678". If you
want Atoll to display leading zeros, you must set the minimun number of digits the CELL_IDENTITY field should
contain by adding the following lines to the Atoll.ini file:
[Display]
CellIDNbDigits = X
Where X is the number of digits that the CELL_IDENTITY field should contain. For example, CellIDNbDigits = 5 means
that Atoll will display at least five digits in the CELL_IDENTITY field by adding leading zeros where required. This
means that Atoll will display "00678" in the above example. However, if the CELL_IDENTITY field contains a number
that has more than X digits, all the digits will still be displayed. For example, all seven digits in "9376562" will still be
displayed even if CellIDNbDigits is set to 5.
10.1.2.15 Making the Antenna Additional Electrical Downtilt Accessible

By default, Atoll does not allow modification of the Additional Electrical Downtilt for transmitters, station templates,
repeaters, and remote antennas. To make this parameter accessible in the GUI, add the following lines to the Atoll.ini
file:
[Antenna]
REDTDisplay = 1
REDTDisplay is set to 0 by default.
10.1.2.16 Increasing the Width of the Clutter Description Pane in the Status Bar
You can increase the width of the clutter description pane in the Status bar (bottom right), to display the descriptions
of clutter classes with long names, by adding the following lines to the Atoll.ini file:
[StatusBar]
ClutterPaneWidth = X
ClutterPaneWidth is set to 100 by default, which means 100% of its default width. To increase the width to, for
example, twice the original width, set ClutterPaneWidth to 200.
10.1.2.17 Hiding the Technology Name in the Title Bar

The names of the technologies corresponding to the current active document are displayed in the title bar. You can
hide the technology names by adding the following lines to the Atoll.ini file:
[DocTitle]
UseTechnoName = 0

UseTechnoName is set to 1 by default.
10.1.2.18 Displaying Objects’ Discrete Values with User-defined Colours

When objects are displayed by discrete values, Atoll applies colours automatically on 36-colour cycles. As opposed
to shading, this is particularly useful to distinguish neighbouring zones which have very close colour values. By
setting some options in the Atoll.ini file, you can configure Atoll to loop on as many user-defined colours as you
want.
For instance if you insert the following lines to the Atoll.ini file, Atoll will loop on 12 colour values (PaletteColor0
through PaletteColor11) the next time you display objects by discrete values.
[Display]
PaletteColor0 = 141 211 199
You can also override user-defined colours, if any, and force shading (from red to blue) by setting the following
option in the Atoll.ini file.
[Display]
DiscreteValueColoring = Shading
10.1.2.19 Avoiding Same Adjacent Cell Colours

To avoid confusion when displaying neighbours on the map, Atoll assigns a colour for each cell that is different from
the colours of the nearest neighbouring cells. By default, Atoll considers the 50 nearest neighbours.
If you are encountering issues where adjacent cell colours are too similar and causing confusion, you can increase
the number of neighbours that are considered for colour allocation by adding the following lines to the Atoll.ini file:
[Display]
MaxColorNeighbours = <value>
In addition to this setting, you must define enough distinct palette colours to cover the number of neighbours
considered, as explained in "Displaying Objects’ Discrete Values with User-defined Colours" on page 175. For
example, if you set MaxColorNeighbours to 100, then you must define PaletteColor1 to at least PaletteColor100.
10.1.2.20 Displaying Vertical Beamwidth in Profile Analysis

You can configure Atoll to display the vertical beamwidth (-3 dB upper and lower limits in the vertical plane) as well
as the actual tilt in the geographic profile view of the Profile Analysis tool. You can configure this display mode by
[GeoProfileDisplay]
Beamwidth = 1

BeamwidthColor = 128 128 128

Upper3dbColor = 255 0 0
Lower3dbColor = 196 0 196
The geographic profile displays clutter classes and the Fresnel ellipsoid by default. When the Beamwidth option is
set to 1, the option is enabled and three additional lines are added to the diagram:
◼ Thick upper and lower lines: These lines todicate the upper and lower -3 dB beamwidth limit in the vertical
plane.
◼ Thick central line: This line indicates the axis of minimal loss, which coincides with the actual tilt axis of the
antenna (combining the physical and electrical tilt).
You can specify the colors of the lines with the BeamWidthColor, Upper3dbColor, and Lower3dbColor options.
The vertical beamwidth is widest in the azimut axis of the antenna. If you move the position of the Point Analysis
tool off of the antenna azimut axis, the vertical beamwidth diminishes and disappears when the vertical beamwidth
loss exceeds -3 dB.
10.1.2.21 Locking Site and Transmitter Shading Colours

By default, when you refresh the map view (F5), the colour shading legend for discrete values is also refreshed based
on the values that exist in the table. Unused values are deleted from the legend. Newly added values that did not
already exist in the legend are assigned a default colour.
You can lock the shading legend so that when the display is refreshed, the colour assignments for discrete values
are not recalculated by setting the following option in the Atoll.ini file.
[Display]
LockTransmittersDisplay = 1
LockSitesDisplay = 1
The default value for LockTransmittersDisplay and LockSitesDisplay is 0.
10.1.2.22 Case-insensitive Grouping

By default, the "Group by" feature is case-sensitive, which means that items labelled "a" and items labelled "A" are
grouped into two different categories. You can make the feature case-insensitive by adding the following lines to
the Atoll.ini file:
[Display]
CaseInsensitiveGroups = 1
CaseInsensitiveGroups is set to 0 by default.
10.1.2.23 Setting Repeaters as Default

By default, remote antennas are the coverage-side default equipment when dropped on the map. You can make
repeaters the default type by adding the following lines to the Atoll.ini file:
[Display]
RepeaterDefaultType = 1
RepeaterDefaultType is set to 0 by default.
10.1.2.24 Hexagonal Design

The Hexagonal Design folder and the corresponding Radio toolbar button are no longer available by default. You
can make them available by adding the following lines to the Atoll.ini file:

[Explorer]
ShowCellularSchemaFolder = 1
ShowCellularSchemaFolder is set to 0 by default.
10.1.2.25 Disabling Confirmation when Deleting a Site from the Map

By default, when you delete a site from the map, a dialog box asks for a confirmation. You can disable this dialog
box by adding the following lines to the Atoll.ini file:
[Site]
AskConfirmDeleteSite = 0
AskConfirmDeleteSite is set to 1 by default.
10.1.3 Distributed Calculation Server Options
10.1.3.1 Detecting and Listing Distributed Calculation Servers

You can use Atoll to detect distributed calculation servers and list them in the Atoll.ini file. A computer, serving as
a distributed calculation server, can run up to 10 instances of Atollsvr, the distributed calculation application. The
distributed calculation server names can be listed in the Atoll.ini file in the following format:
[RemoteCalculation]
NumberedServers = Server1NameN; Server2NameN; ...
Here Server1Name and Server2Name refer to the names of the computers being used as calculation servers, and N
is a number from 0 to 9. This means, for example, that Server1 can run up to 10 instances of the distributed
calculation application, and all these instances can be listed in the NumberedServers option (Server1Name0;
Server1Name1; Server1Name2; ...). Using this option, you can assign distributed calculation servers to different
groups of users working with two different Atoll.ini files. For example, user group 1 can use Server1Name0 to
Server1Name4, and group 2 can use Server1Name5 to Server1Name9.
If an error occurs on any of the distributed calculation servers, Atoll transfers the calculations back to the local
computer. However, to avoid memory saturation, Atoll uses one thread on the local computer and calculates the
path loss matrices one by one. It does not attempt creating more than one thread.
10.1.3.2 Setting the Distributed Calculation Server Priority

By default, the Atoll distributed calculation server (AtollSvr.exe) runs with a normal process priority. However, it is
possible to modify its priority, in both service and application modes, and set it higher or lower. You can do this by
[RemoteCalculation]
AtollSvrPriority = -1, 0, 1 or 2
You can choose between four possible priority levels:

◼ -1: Below Normal priority
◼ 0: Normal priority
◼ 1: Above Normal priority
◼ 2: High priority
This option works for both, application and service, modes of the distributed calculation server.

 The distributed calculation server (AtollSvr.exe) must be restarted in order to take

into account the new value for the AtollSvrPriority option.
The Realtime priority mode has not been implemented for reasons of stability.
10.1.3.3 Modifying the Default Detection Time-out

The default time-out (2 seconds) for locating calculation servers within the network might be too short in certain
cases. You can increase this time-out by adding the following lines to the Atoll.ini file:
[RemoteCalculation]
DetectTimeOut = 5000
In this example, the detection time-out is set to 5000 ms.
10.1.3.4 Optimising Thread Calculation

The following option sets the policy for load balancing multiple sessions on a single distributed calculation server.
You can change this behaviour by setting the following option in the Atoll.ini file:
[RemoteCalculation]
MultiUserDCS = 1
You can choose between two distribution policies:

◼ 0: Calculation speed is normal, but load balancing might not be optimal. This is recommended for
environments where DCS is mainly used in batch mode (for example when calculations are automatically run
at night). This is the default mode.
◼ 1: Calculation speed is slower, but threads are more evenly distributed. This is recommended when multiple
users use the distributed calculation server interactively.
10.1.4 License Management Options
10.1.4.1 Setting an Alarm for the License End Date

You can set a warning message about the License end date to appear a certain number of days before this date.
The Atoll.ini file should contain the following lines:
[License]
TimeBombNotice = X
X is the number of days prior to the temporary License end date you want Atoll to warn you. When no information is
given in the Atoll.ini file, Atoll warns the user 30 days before the License end.
10.1.4.2 Blocking Access to Technology Modules

This option is useful when working with a floating License management system where a floating License server
manages and distributes tokens between several Atoll users. This option can also be useful in setting different
License rights to users.
To block access to the different technology modules, add the corresponding lines to the [License] section of the
Atoll.ini file:

To block access to... Add
GSM GPRS EDGE GSM = 0
UMTS HSPA UMTS = 0
CDMA2000 CDMA = 0
TD-SCDMA TD-SCDMA = 0
WiMAX and Wi-Fi WiMAX = 0
LTE LTE = 0
NB-IoT NB-IoT = 0
5G NR 5GNR = 0
LPWA LPWA = 0
Microwave Radio Links MW = 0
Backhaul BH = 0
Measurements Measures = 0
You can also block access to GSM, UMTS, or LTE radio access technologies in 3GPP Multi-RAT documents using
these options.
10.1.4.3 Blocking Access to the AFP Module

You can block access to the AFP licenses for users or user groups. To block access to the AFP module, add the
corresponding lines to the [License] section of the Atoll.ini file:
[License]
GSM_AFP = 0
LTE_AFP = 0
5GNR_AFP = 0
WiMAX_AFP = 0
In order to carry out a Wi-Fi frequency planning using the AFP module, you must have access to the WiMAX AFP
module license, i.e. WiMAX_AFP must not be set to 0.
10.1.4.4 Blocking Access to the ACP Module

You can block access to the ACP licenses for users or user groups. To block access to the ACP module, add the
corresponding lines to the [License] section of the Atoll.ini file:
[License]
ACP_GSM = 0
ACP_UMTS = 0
ACP_LTE = 0
ACP_5GNR = 0
ACP_CDMA = 0
ACP_WiMAX = 0
ACP_LPWA = 0
In order to carry out a combined GSM and UMTS optimisation using the ACP module, you must have access to both
ACP module Licenses, i.e. ACP_GSM and ACP_UMTS must both not be set to 0.
In order to carry out a Wi-Fi optimisation using the ACP module, you must have access to the WiMAX ACP module
license, i.e. ACP_WiMAX must not be set to 0.

10.1.4.5 Changing the NetHASP License Manager Idle Time Setting

The floating license manager has an idle time parameter with 10 minutes as default value. Atoll sessions
consuming floating licenses from a license manager server reset this idle time parameter to its initial value every
minute. If you are performing time-consuming calculations on Atoll connected to a floating license server, and
consuming a license, it might occur that Atoll does not get the chance to reset the idle time value to its initial value.
In this case, a new Atoll session can steal the license actually allocated to an already running session. This might
cause problems in the case where all the licenses are used, the Atoll session performing heavy calculations does
not get the chance to initialise the idle time parameter for its license, and a new Atoll session is launched on another
computer. In such a situation, the floating license manager considers that the already running session has been
inactive or closed, and the license allocated to the already running Atoll session is allocated to the new session.
You can modify the default idle time parameter value to a higher value to avoid this effect. To set a different default
value for the idle time parameter, add the following lines to the Atoll.ini file:
[License]
IdleTime = X
Where X is the time in minutes. The idle time can be set to infinity by defining IdleTime = 0.
10.1.5 Database Options
10.1.5.1 Checking Data Integrity After Database Upgrade and Data Refresh
You can configure Atoll to perform a database integrity check when you open anAtoll document connected to a
database that was recently upgraded to a new version or when you refresh data in anAtoll document from the
database.
After an integrity check, if any problems are detected, a dialog box allows the user to correct any discrepancies.
To configure this option, add the following lines to the Atoll.ini file:
[Refresh]
ControlIntegrity = <setting>
where <setting> is one of the following values:

◼ 0: An integrity check is not performed after a database upgrade or a data refresh.
◼ 1: After a database upgrade or a data refresh, a dialog box asks whether to perform an integrity check. If no
integrity problems are found, a message is displayed in a dialog box.
◼ 2: After a database upgrade or a data refresh, an integrity check is performed automatically and silently. If no
integrity problems are found, a message is displayed in the Events viewer.
ControlIntegrity is set to 0 by default.
10.1.5.2 Checking Data Integrity on Open or Data Refresh

When opening a document from the database or refreshing data from the database, this option forces Atoll to
perform a series of SQL queries that ensures that consistent data can be read from the database.
To turn this feature on, add the following lines to the Atoll.ini file:
[Database]
IntegrityChecker = 1
When this option is enabled, Atoll applies a series of SELECT filters to the database to guarantee data integrity and
to avoid integrity problems in the future.
By default, IntegrityChecker is set to 0.

10.1.5.3 Preselecting "Refresh Unmodified Data Only" by Default

By default, when refreshing a document from the database, the Refresh dialog box preselects the Archive your
changes in the database option. You can specify that Refresh unmodified data only is preselected by default
instead by adding the following lines to Atoll.ini.
[Refresh]
RefreshUnmodifiedDataOnlyByDefault = 1
RefreshUnmodifiedDataOnlyByDefault is set to 0 by default.
10.1.5.4 Trimming Leading and Trailing Space Characters from Text Fields
Atoll does not allow leading and trailing spaces in text fields such as names, custom fields, and so on. By default,
space characters at the beginning and at the end of text fields are automatically trimmed.
This behaviour can be modified by adding the following lines to the Atoll.ini file:
[Validation]
TrimTextFields = 0
When TrimTextFields is set to 0, text field values are not trimmed and may contain leading and trailing space
characters.
TrimTextFields is set to 1 by default.
A macro can be obtained from Forsk support to verify that existing text fields in the database comply with this rule.
10.1.5.5 Displaying Database Tables in the Event Viewer at Open

This option displays the database tables that are read as they are loaded when opening a document from a
database. The table names are displayed in the event viewer. To turn this feature on, add the following lines to the
Atoll.ini file:
[Database]
DisplayTableNamesOnOpenFromDB = 1
10.1.5.6 Allowing Null Entries in Non-nullable Custom Fields

By default, to prevent from archival issues and crashes, Atoll does not support null entries in non-nullable custom
fields of connected documents. Failing to fill a non-nullable custom field when you add a new record via a record
template, a file import, or table edition, will return a message in the form "’NameOfField’ column cannot be null". To
avoid this, you can define the custom field as nullable in the database, use a default value in the field definition, or
create the field and fill it in the relevant template.
As a last resort, you can force the previous behaviour of Atoll by adding the following lines to the Atoll.ini file:
[Database]
AllowNullRecordsForNonNullableCustomFields = 1
AllowNullRecordsForNonNullableCustomFields is set to 0 by default.
10.1.5.7 Automatically Running GSM Subcell Audit at Open or Refresh

The following options automatically perform subcell audit when opening a GSM document from a database or
refreshing data from a database.
To automatically audit the consistency of redundant values in the transmitters, subcells, and TRXs tables without
fixing any problems found, add the following lines to the Atoll.ini file:

[Database]
SubCellAuditConsistency = 1
To automatically audit the consistency of redundant values in the transmitters, subcells, and TRXs tables and fix
any problems found, add the following lines to the Atoll.ini file:
[Database]
SubCellAuditConsistency = 2
To automatically audit the compatibility of the main subcell values without fixing any problems found, add the
[Database]
SubCellAuditMainValues = 1
To automatically audit the compatibility of the main subcell values and fixi any problems found, add the following
[Database]
SubCellAuditMainValues = 2
SubCellAuditConsistency and SubCellAuditMainValues are set to 0 by default.
10.1.5.8 Modifying the Default Database Connection Time-out

The ODBC driver has a default command timeout value which could be too short in some cases, such as slow
networks. You can change this default timeout value and set a higher value if you encounter problems, during
execution of commands on the database, which might be related to timeout. To change the value of the command
timeout parameter of the ODBC driver, add the following lines to the Atoll.ini file:
[Database]
CommandTimeout = X
Where X is the timeout value in an integer number of seconds. After X seconds, the command is considered too long
to execute. If you set CommandTimeout = 0, there will be no time limit for the execution of the command.
10.1.5.9 Changing the Database Export Method

By default, when exporting a database to Microsoft Access, Atoll uses a single transaction to export all the tables
of the database. If the query result exceeds temporary storage space, the whole export operation fails.
An alternative method is to perform one transaction for each table. This method is slower, but requires less
temporary storage space. If one of the query results exceeds storage space, then only that table fails to export.
Other tables will be properly exported, but missing data can cause database consistency problems.
To use the alternative database export method, add the following lines to the Atoll.ini file:
[Database]
ExportTransactionMethod = 1
ExportTransactionMethod is set to 0 by default.
10.1.5.10 Making Atoll Case-Sensitive for Database Import From Planet

The network data import from a Planet database into Atoll is not case sensitive by default. You can set this import
to case sensitive by adding the following lines to the Atoll.ini file:
[PlanetImport]

SensitiveCase = 1
Case sensitive means that "Site0" will be considered different from "site0" during import.
10.1.5.11 Setting the Sign for KClutter When Importing Data From Planet EV
Planet EV uses the opposite sign for the Kclutter parameter with respect to Planet DMS. If you are importing data
from Planet EV, you might have to change the sign of this parameter. You can instruct Atoll to change the sign for
Kclutter when importing data from Planet EV by adding the following lines to the Atoll.ini file:
[PlanetImport]
ChangeKclutterSign = 1
ChangeKclutterSign is set to 0 by default.
10.1.5.12 Setting the Clutter No Data Value for When Importing Data From Planet EV
Atoll automatically detects undefined clutter class data as No Data when importing data from Planet EV. No Data
clutter is considered transparent on the map and in calculations. You can instruct Atoll to use a specific value as
the No Data value when importing data from Planet EV by adding the following lines to the Atoll.ini file:
[PlanetImport]
ClutterNoData = X
Where X is the No Data value for clutter. ClutterNoData is set to -9999 by default.
10.1.5.13 Enabling/Disabling Password Prompt at Archive

You can instruct Atoll to prompt the user for password before archiving data in a database. If you want Atoll to ask
the user to enter the username and password once per Atoll session, add the following lines to the Atoll.ini file:
[Database]
PromptOnArchive = 1
PromptOnArchive = 1 is the default setting used if this option is not provided in the Atoll.ini file. The user will be
prompted for password when he tries to archive data in the database for the first time during anAtoll session.
If you want Atoll to ask the user to enter the username and password for every refresh and archive, set:
PromptOnArchive = 2
If you want to disable the prompt for password, set:
PromptOnArchive = 0
 Username and password are stored in the ATL file in an encrypted form.
This option is only appropriate if the database connection string contains a
password.
10.1.5.14 Archiving Data to Databases Using Transactions

Atoll supports transactions for archiving data to databases. This approach ensures that users always get consistent
data when refreshing their documents with data from the database, even when another user is archiving his
modifications at the same time. By default, Atoll uses transactions for archiving data, however you can disable the
transaction mode for Atoll by adding the following lines to the Atoll.ini file:

[Database]
UseTransaction = 0
UseTransaction is set to 1 by default.
 Before modifying this option, make sure that the database server is correctly
configured for transactions.
10.1.5.15 Keeping Separate Work and Master Path Loss Directories

When synchronising a master project with a work project, the shared path loss directory is also updated. This can
cause the work and master projects to overwrite each other’s shared folder. From an operational standpoint, it is
often preferable to keep two different path loss directories: one for the master project and a second for the work
project.
When the [OverwriteSharedFolderPath] option is set to "0", Atoll does not overwrite the shared path loss directory.
[Database]
OverwriteSharedFolderPath = 0
OverwriteSharedFolderPath is set to 1 by default, meaning that the path loss directory is overwritten.
10.1.5.16 Enabling Partial Refresh from Recently Upgraded Databases

When you open anAtoll 2.8.x document connected to a database that has been upgraded to 3.1.0, Atoll
automatically performs a full refresh, i.e., loads all the data from the database, when upgrading the document to the
new version. If you wish to enable partial refresh of data from the upgraded database (not recommended as it can
cause data integrity problems), add the following lines to the Atoll.ini file:
[MajorVersionChange]
EnablePartialRefreshInMigration = 1
EnablePartialRefreshInMigration is set to 0 by default.
10.1.5.17 Setting the Type of Database Being Used

You can set the type of database being used by adding the following lines to the Atoll.ini file:
[Database]
ExclusiveProvider = providername
Where providername can be "Access", "SQLServer", or "Oracle". When this option is set, Atoll uses the defined
database type and does not display the database selection dialog box that appears when creating a new document
from an existing database or when exporting a document to create a new database.
10.1.5.18 Displaying Only the First Export to Database Error in a Dialog Box
When a document containing several inconsistencies is exported to a database, you can force Atoll to display only
the first error in a dialog box and log all other inconsistencies in the Events viewer by adding the following lines to
the Atoll.ini file:
[Database]
LogExportToDbErrors = 1
LogExportToDbErrors is set to 0 by default.

10.1.5.19 Include AMC Database Fields in Read/Write Operations

In normal usage, database fields that are related to Atoll Management Console (DB_RECORD_ID, O_RECORD_ID,
O_CHANGED) are excluded when a document is created from a database and when a document is exported to a
database. When using migration tools, it might be necessary for these fields to included for database
administrators. To include AMC database fields in read/write operations, add the following lines to the Atoll.ini file:
[Database]
KeepAMCDatabaseFields = 1
KeepAMCDatabaseFields is set to 0 by default.

Only database administrator accounts have access to AMC database fields, therefore standard users cannot open
documents from the database when this option is set.
10.1.6 Common Calculation Options
10.1.6.1 Setting the Antenna Patterns Modelling Method

In order to set the modelling method for antenna patterns, the Atoll.ini file can contain the following information:
[Antenna]
Catalog Vertical Diagram Orientation = 90 or angle value
InterpolatePatternEvenIfOnlyOneDiagram = 0 or 1
InterpolatePatternIndB = 0 or 1
Catalog Vertical Diagram Orientation is a display option. It enables rotating the antenna’s vertical diagram to a user-
defined angle. By default, Catalog Vertical Diagram Orientation is set to 90 meaning that the vertical diagram is
displayed pointing to the right. Setting it to 0, for example, will show the vertical diagram pointing to the top.
InterpolatePatternEvenIfOnlyOneDiagram can be used to change the way Atoll interpolates antenna pattern
attenuation diagrammes for antennas with only one diagramme available, vertical or horizontal. With
InterpolatePatternEvenIfOnlyOneDiagram = 0 (default, new method), Atoll uses the only diagramme available for
both vertical and horizontal planes. With InterpolatePatternEvenIfOnlyOneDiagram = 1 (previous method), Atoll uses
the diagramme available for the plane to which it corresponds, vertical or horizontal, and an isotropic diagramme (a
0 dB circular attenuation pattern) for the plane for which no diagramme is available.
InterpolatePatternIndB sets the unit used by Atoll when it performs linear interpolations on antenna pattern
attenuation. When InterpolatePatternIndB = 0 (default), interpolations are calculated in Watts. When
InterpolatePatternIndB = 1 (or any value other than 0), interpolations are calculated in dB leading to stronger antenna
pattern attenuation.
10.1.6.2 Disabling Automatic Locking of Coverage Predictions

By default, Atoll automatically locks a coverage prediction study once it is calculated. To instruct Atoll not to lock
prediction studies automatically, these lines have to be included in the Atoll.ini file:
[Studies]
AutoLock = 0
AutoLock is to 1 by default.
10.1.6.3 Enabling Shadowing Margin in Calculations

An average value of shadowing margin is calculated by Atoll and applied to the signal level and interference levels
during coverage predictions and other calculations such as point analysis, automatic neighbour allocation,

automatic scrambling code and PN offset allocation, and interference matrices calculation. This average value
depends on the cell edge coverage probability that you define for the calculation and the standard deviations
defined per clutter class.
In the dialog boxes of all the above-mentioned calculations, the Shadowing taken into account check box is not
selected by default. Not selecting this check box implies that the shadowing margin is neither calculated nor used
in the calculations.
If you want to select the Shadowing taken into account check box by default in all the above-mentioned dialog
boxes, you have to enter the following lines to the Atoll.ini file:
[Shadowing]
UseShadowing = 1
UseShadowing is set to 0 by default.
 This option does not affect the shadowing margin calculation during Monte Carlo
simulations. Monte Carlo simulations do not use an average value of the
shadowing margin depending on the cell edge coverage probability. During Monte
Carlo simulations, random shadowing margin values are calculated based only on
the standard deviations defined per clutter class.
In UMTS HSPA and CDMA2000 documents, you can also deactivate the calculation and use of macro-diversity
gains. For more information, see "Disabling Macro-diversity (SHO) Gains Calculation for Ec/Io and Eb/Nt" on
page 202.
10.1.6.4 Setting a Default Value for the Cell Edge Coverage Probability
The default value of the cell edge coverage probability can be configured in the Atoll.ini file. If you enter the following
lines to the Atoll.ini file, Atoll will consider the value of the cell edge coverage probability defined in the Atoll.ini file
as the default value, and will take it into account when performing point analysis, in the shadowing margins
calculator, and will propose it as the default value for coverage prediction studies.
[Shadowing]
Reliability = 60
Reliability = 60 means 60 % cell edge coverage probability.
 The value of cell edge coverage probability used for automatic neighbour allocation
and interference matrices calculation is stored in user configuration files (CFG).
10.1.6.5 Enabling Indoor Coverage in Calculations

Indoor losses are taken into account in calculations when the Indoor Coverage check box is selected. This check
box is not selected by default. If you want to select the check box by default in the properties dialog boxes of all the
calculations, you have to enter the following lines to the Atoll.ini file:
[ClutterParams]
IndoorActivity = 1
IndoorActivity is set to 0 by default.
10.1.6.6 Modifying the Resolution for the LOS Area Calculation Around a Site
The calculation of line of sight area around a given site uses the resolution of the geographic data as the default
calculation resolution. These calculations can be time-consuming if the geographic data is available with a very high
resolution. You can set the calculation resolution to a multiple of the resolution of the geographic data by adding

[LOSArea]
ResolutionMultFactor = X
Where X is an integer. Therefore, setting ResolutionMultFactor to 2 will double the calculation resolution and
decrease the time required for the calculation by half.
10.1.6.7 Embedding Path Losses in New Documents

If you calculate path loss matrices for a new document that has not been saved yet, Atoll asks if you would like to
save the document and externalise the path loss matrices or if you would like to keep the path loss matrices
embedded in the document and save it later. You can suppress this message by adding the following lines to the
Atoll.ini file:
[Pathlosses]
EmbeddedByDefault = 1
EmbeddedByDefault is set to 0 by default.
10.1.6.8 Stopping Calculations on Error

If a problem occurs in calculating one or more path loss matrices while calculating a coverage prediction, Atoll
continues performing the remaining calculations, and provides results even if they are not complete. If you want
Atoll to stop the calculations if there is an error, you can add the following lines to the Atoll.ini file:
[Studies]
ContinueOnError = 0
ContinueOnError = 1 by default. This means that by default Atoll does not stop the calculations on error.
10.1.6.9 Warning About Prediction Validity When Display Options are Modified
Coverage predictions have to be recalculated if you modify their display options. Atoll displays a warning message
when you modify the display options for coverage predictions. To deactivate this warning message, add the
[Studies]
RecomputationWarning = 0
RecomputationWarning is set to 1 by default.
10.1.6.10 Reading Exact Altitudes From the DTM

Atoll uses either the user-defined site altitudes from the Sites table or, if they are not defined, the site altitudes read
from the DTM for the site coordinates defined in the Sites table. However, transmitters can be located at certain
distances from the site coordinates. You can set these distances of transmitters from their sites in the Transmitters
table under DX and DY.
If you want Atoll to consider the exact transmitter coordinates, i.e., including DX and DY, during calculations for
determining the transmitter height, which will be read from the DTM at the exact transmitter coordinates, you must
[Calculations]
UseSiteAltitude = 0

UseSiteAltitude is set to 1 by default, which means that the altitude used in calculations will be the one which is
either read from the Sites table or from the DTM at the site’s coordinates, if the user-defined altitude is not available
in the Sites table.
Setting UseSiteAltitude to 0 means that, during calculations, Atoll will read the altitudes from the DTM at the exact
coordinates of each transmitter considering the values entered for the DX and DY parameters.
The above option is also valid for microwave links. In this case, setting UseSiteAltitude to 0 means that, during
calculations, Atoll will read the altitudes from the DTM at the exact coordinates of each microwave link considering
the values entered for the DX_A, DY_A, DX_B, and DY_B parameters.
 With UseSiteAltitude = 0, if DX and DY are 0, i.e., for transmitters and microwave

links located at the site coordinates, Atoll will still use the altitudes defined per site,
if any, or the altitudes from the DTM otherwise
10.1.6.11 Setting a Common Display Resolution For All Coverage Predictions

You can set a display resolution for each coverage prediction individually as well as a default display resolution for
all coverage predictions that you create, in the Predictions tab of the Predictions folder’s Properties dialog box. If
you create a new coverage prediction, Atoll reads the default resolution from the Predictions folder’s Properties
dialog box and sets that as the display resolution for the new coverage prediction. Then, if you delete this resolution
from the coverage prediction properties, and do not enter any resolution, Atoll resets the resolution to the default
value. In this way, each coverage prediction has a display resolution defined. However, it is possible to manage a
common display resolution for all coverage predictions, new or existing, that do not have a resolution defined for
them. You can switch to this option by adding the following lines to the Atoll.ini file:
[Studies]
SpecifyResolutionAfterComputation = 0
Once SpecifyResolutionAfterComputation is set to 0, Atoll no longer resets the resolution to the default value for
coverage predictions that do not have a resolution defined. Atoll allows you to leave the field empty in the coverage
prediction properties, and directly reads the default resolution defined in the Predictions folder’s Properties dialog
box. In this way, when you create coverage predictions without defining resolutions for them, you can modify the
default resolution in the Predictions Properties dialog box and, therefore, change the display resolution for all the
coverage predictions, new or existing.
To return to the normal working, remove the lines from the Atoll.ini file or set SpecifyResolutionAfterComputation
to 1.
10.1.6.12 Setting the Priorities for GUI and Calculations

You can set the priorities for user interface and calculations through the following option in the Atoll.ini file:
[RemoteCalculation]
Priority = 0, 1, or 2
Priority enables you to set the priority between calculations and user interface.
◼ 0: User interface has the highest priority.
◼ 1 (default): User interface has a higher priority than calculations.
◼ 2: User interface and calculations have the same priority.
10.1.6.13 Setting the Number of Parallel Processors and Threads

You can manage the number of processors and threads through the Atoll.ini file. The file should contain the
following options:
[RemoteCalculation]
NumberOfProcessors = X

NumberOfThreadsPathloss = 1, 2, ..., or 8
NumberOfThreadsSimulation = 1, 2, ..., or 8
NumberOfThreadsStudy = 1, 2, ..., or 8
NumberOfThreadsNeighbour = 1, 2, ..., or 8
NumberOfThreadsMicrowave = 1, 2, ..., or 8
Maximum number of processors:

◼ NumberOfProcessors is the maximum number of processors that can be used for calculations. If you set this
option to 0, Atoll will use the actual number of available processors.
Maximum number of calculation threads:
◼ NumberOfThreadsPathloss is the maximum number of threads that can be used for path loss calculations (4
by default, 8 maximum)
◼ NumberOfThreadsSimulation is the maximum number of threads that can be used for Monte Carlo simulation
calculations (4 by default, 8 maximum)
◼ NumberOfThreadsStudy is the maximum number of threads that can be used for the calculation of coverage
predictions (4 by default, 8 maximum)
◼ NumberOfThreadsStudyTile is the maximum number of threads that can be used per coverage prediction
calculation (0 by default, 8 maximum). If you set this option to 0 or 1 (recommended), Atoll will use one thread
for the calculation.
◼ NumberOfThreadsNeighbour is the maximum number of threads that can be used for automatic neighbour
allocation (4 by default, 8 maximum)
◼ NumberOfThreadsMicrowave is the maximum number of threads that can be used for microwave link
calculations (4 by default, 8 maximum)
All these options are upper limits per computer. Atoll supports a maximum of 64 parallel threads.
10.1.6.14 Parallel Calculation of Monte Carlo Simulations

Parallel calculation of Monte Carlo simulations is available only in the following technologies:
◼ GSM
◼ UMTS HSPA
◼ CDMA2000 (1xRTT and 1xEV-DO)
It is not available in TD-SCDMA, WiMAX, LTE, and Wi-Fi documents.
10.1.6.14.1 Parallel Calculation of Monte Carlo Simulations in GSM

In GSM, Atoll can also perform multi-threaded calculations of Monte Carlo simulations if you add these lines to
Atoll.ini:
[GSM]
ParallelSimulations = 1
ParallelSimulations in GSM documents is set to 0 by default.
 The Generator Initialisation must be set to 0 in order for simulations to be

calculated in parallel.
10.1.6.14.2 Parallel Calculation of Monte Carlo Simulations in UMTS HSPA and CDMA2000
In UMTS HSPA and CDMA2000 (1xRTT and 1xEV-DO) documents, Atoll perform multi-threaded calculations of
Monte Carlo simulations by default. To disable parallel calculations in these two technologies, add the following

[CDMA]
ParallelSimulations = 0
ParallelSimulations in UMTS HSPA and CDMA2000 (1xRTT and 1xEV-DO) documents is set to 1 by default.
10.1.6.15 Performing Calculations in Read-Only Documents
 Parallel calculation of Monte Carlo simulations is not available in TD-SCDMA,

WiMAX, LTE, and Wi-Fi documents.
By default, when you open a read-only Atoll document, it is not possible to run calculations in it. If you want to run
calculations in read-only documents, add the following lines to the Atoll.ini file:
[Studies]
ComputeEvenIfReadOnly = 1
If you open a document that is already open in another Atoll session, Atoll lets you open the document as read-only.
10.1.6.16 Identifying Transmitter, Repeater, and Remote Antenna Coverage Areas

In GSM, UMTS, CDMA2000, LTE, and WiMAX documents, you can create a "Coverage by Aerial" prediction providing
separate coverage areas of transmitters, repeaters, and remote antennas.
In order to make this coverage prediction available in Atoll, add the following lines to the Atoll.ini file:
[Studies]
AerialStudy = 1
10.1.6.17 Disabling Rounding of Antennas’ Updated Half-power Beamwidth Values

By default, when the antennas’ half-power beamwidths are recalculated with the Electrical Azimuth and Beamwidth
Update command, Atoll automatically rounds the new values to the nearest integers. You can disable this default
behaviour and force Atoll to not round new values by adding the following lines to the Atoll.ini file:
[Antenna]
RoundBeamwidth = 0
RoundBeamwidth is set to 1 by default.
10.1.6.18 Changing the Rounding Method Used for Profile Extraction

Before Atoll 2.8.0, real values for altitudes read from the DTM files were rounded down to their integer values.
However, from Atoll 2.8.0 onwards, real values are rounded up or down to their nearest integer values. For example,
98.8 m was rounded to 98 m when the previous method was used, and it is rounded to 99 m with the new method.
To switch back to the previous method, add the following lines to the Atoll.ini file:
[Calculations]
RoundAltitudes = 0
RoundAltitudes is set to 1 by default.

10.1.6.19 Disabling Calculations Over NoData Values for DTM and Clutter Classes
If you don’t want Atoll to calculate path losses on the pixels located over nodata values defined in the DTM and
clutter classes files, add the following lines to the Atoll.ini file:
[FskPropagModels]
OptimOnNoData = 1
By default, OptimOnNoData is set to 0. This option only works with the propagation models available with Atoll by
default.
10.1.6.20 Co-planning: Calculating Predictions in the Current Document Only

Atoll calculates all the unlocked coverage predictions in the Predictions folder of the current document and the
unlocked coverage predictions in the linked Predictions folder from another document when you click the Calculate
button, press F7, or select the command from a context menu in the current document. If you want Atoll to calculate
only the unlocked coverage predictions in the Predictions folder of the current document, and not in the linked
Predictions folder from another document, add the following lines to the Atoll.ini file:
[CoPlanning]
ComputeLinkedPredictions = 0
ComputeLinkedPredictions is set to 1 by default.
10.1.6.21 Co-planning: Calculating Predictions in Serial or in Parallel

If you want Atoll to calculate in parallel the invalid or unavailable path loss matrices and unlocked coverage
predictions in the Predictions folder of the current document and the linked Predictions folder from another
document, add the following lines to the Atoll.ini file:
[CoPlanning]
LinkedPredictionsComputationMode = Parallelized
LinkedPredictionsComputationMode is set to "Serialized" by default, which means the path loss matrices and
unlocked coverage predictions in the current and linked documents are calculated in a serial way. If you set the
option to any other value, the calculations are performed in parallel but without being managed by a task list.
Calculations are carried out starting with the current document in the order of the coverage predictions in the
Predictions folder.
10.1.6.22 Forcing Neighbour Symmetry Only Inside Focus Zone

Atoll carries out automatic neighbour allocation on transmitters located inside the Focus Zone (or the Computation
Zone if the Focus Zone does not exist). When you run an automatic neighbour allocation with the Force Symmetry
option selected, Atoll makes calculated neighbour relations symmetrical even if one of the transmitter in the
neighbour relation is located outside the Focus Zone. If you want Atoll to make only those neighbour relations
symmetrical for which both transmitters in the neighbour relation are located inside the Focus Zone, add the
[Neighbours]
ForceSymmetryInFocusZone = 1
ForceSymmetryInFocusZone is set to 0 by default.
10.1.6.23 Using Poisson Distribution in Monte Carlo Simulations

By default, mobiles are generated in each simulation following a Poisson distribution. This means that there are
small variations in the number of randomly distributed mobiles from one simulation to another. To disable this type

of distribution, i.e., to have the same number of mobiles generated in each simulation of a group, add the following
[Simulation]
RandomTotalUsers = 0
RandomTotalUsers is set to 1 by default.
10.1.6.24 Setting the Precision of Global Scaling Factor in Simulations

You can set the precision of the global scaling factor used in simulation properties (Traffic tab > Global scaling
factor) by setting the following option:
[Simulation]
GlobalScalingFactorDigitsNumber = <value>
where <value> is the number of digits following the decimal point.

GlobalScalingFactorDigitsNumber is set to 6 by default.
10.1.6.25 Calculating EIRP from Max Power in Signal Level Predictions

Atoll calculates the EIRP from the pilot power in UMTS and CDMA2000, and reference signal power in LTE. If you
wish to calculate the EIRP from the Max Power values when calculating signal level-based coverage predictions, add
[Studies]
EIRPfromMaxPower = 1
EIRPfromMaxPower is set to 0 by default. This option applies to "Coverage by Transmitter", "Coverage by Signal
Level", and "Overlapping Zones" predictions in UMTS, CDMA2000, and LTE.
10.1.6.26 Excluding Filtered Transmitters from the List of Neighbours

By default, Atoll includes filtered transmitters in the list of neighbours. If you wish to exclude filtered transmitters
from the list of neighbours, add the following lines to the Atoll.ini file:
[Neighbours]
ExcludeFilteredCellsFromNeighbourLists = 1
ExcludeFilteredCellsFromNeighbourLists is set to 0 by default.
10.1.6.27 Changing the Weighting Factor of the Effective Inter-transmitter Distance

By default, the weighting factor of the effective inter-transmitter distance is set 30. To change this weighting factor,
[Neighbours]
DistanceAzimutWeightingPercent = 30 (default)
 If the value you set is too high (e.g. 70), the resulting inter-transmitter distance can
be negative. In such a case, nothing will be displayed in the corresponding table
cell.

10.1.6.28 Extending the Maximum Inter-site Distance to Repeaters and Remote Antennas
The maximum inter-site distance used in automatic neighbour allocation and neighbour importance evaluation
considers the donor sites only. If you want it to also consider repeaters and remote antennas, then add the following
[Neighbours]
RepeaterInterSiteDistanceInAlloc = 1
RepeaterInterSiteDistanceInAlloc is set to 0 by default.
10.1.6.29 Forcing the Real Inter-site Distance Threshold

By default, the automatic neighbour allocation compares the defined Max inter-site distance with the effective inter-
transmitter distance. As a consequence, there can be cases where the real distance between assigned neighbours
is higher than the Max inter-site distance, because the effective distance is smaller.
To force Atoll to compare the defined Max inter-site distance with the real inter-site distance, add the following lines
[Neighbours]
RealInterSiteDistanceCondition = 1
RealInterSiteDistanceCondition is set to 0 by default.
10.1.6.30 Prioritising Individual Inter-site Distances in Neighbour Importance Calculation

By default, the neighbour importance calculated with respect to distance is based on the global Max inter-site
distance setting for all neighbour candidates. As a consequence, there can be cases where the calculated
importance is different when the global Max inter-site distance is modified.
You can avoid that by forcing Atoll to prioritise individual distances between reference transmitters/cells and their
respective neighbour candidates. To do that, add the following lines to the Atoll.ini file:
[Neighbours]
CandidatesMaxDistanceInImportanceCalculation = 1
CandidatesMaxDistanceInImportanceCalculation is set to 0 by default.
10.1.6.31 Keeping Assigned Neighbours that are not Symmetric with the Reference Transmitter
By default, when the Force Symmetry option is selected and the neighbour list of a transmitter is full, the reference
transmitter is not added as a neighbour and that transmitter is removed from the reference transmitter’s neighbours
list.
To force Atoll to keep that transmitter in the reference transmitter’s neighbours list, add the following lines to the
Atoll.ini file:
[Neighbours]
DoNotDeleteSymmetrics = 1
DoNotDeleteSymmetrics is set to 0 by default.
10.1.6.32 Keeping Neighbours that Relate to Themselves

By default, during a neighbour audit, Atoll automatically deletes neighbour relationships that might exist between a
transmitter and itself. This situation can occur when importing a document from old versions of Atoll or if a
relationship was created manually. If you want to keep these neighbour relationships, add the following lines to the
Atoll.ini file:

[Neighbours]
DeleteOnAuditIfSourceEqualsTarget = false
DeleteOnAuditIfSourceEqualsTarget is set to true by default.
10.1.6.33 Enabling and Disabling Per-site Path Loss Matrix Calculations

Atoll calculates path loss matrices of co-located co-site transmitters in a single step, i.e., per site, instead of
calculating each transmitter’s matrix separately. You can disable per-site calculation of path loss matrices by
[RemoteCalculation]
DisablePathlossPerSiteCalculation = 1
DisablePathlossPerSiteCalculation is set to:

◼ 1 by default in Atoll 32-bit
◼ 0 by default in Atoll 64-bit
10.1.6.34 Defining a Global Maximum Path Loss Calculation Radius

You can set a maximum path loss calculation radius, applicable to both main and extended matrices, by adding the
[Transmitter]
MaximumCalculationRadius = value
Where value is the maximum calculation radius in metres. By default, there is no limit for the path loss calculation
radii. The limit you set here is applied to values entered by the user in the Transmitters table or properties dialog box.
10.1.6.35 Preserving Loss and Noise Figures with no Assigned Equipment

By default, calculating and updating UL/DL loss and noise figures updates the parameters of the transmitter, even
when no equipment is assigned to the transmitter. This can cause problems in some environments.
You can force Atoll to preserve the existing transmitter values when no equipment is assigned by adding the
[Transmitter]
UpdateLossIfNoEquipment = 0
UpdateLossIfNoEquipment is set to 1 by default.
 The above applies if no equipment is defined and if the Miscellaneous losses are
set to 0 dB (in transmission and reception) in the Equipment Specifications dialog
box. If no equipment is defined and one of these values is different from 0 dB, then
the total losses will be updated even if UpdateLossIfNoEquipment is set to 0.
10.1.6.36 Linear Interpolation of Inter-technology IRF

You can force Atoll to interpolate inter-technology IRF values in linear values (instead of dBs) by adding the following
lines to the Atoll.ini file. This will only affect background calculations, i.e., the Reduction Factors graphs remain in
dB.
[Calculations]
InterTechIRFInterpolationMode = 1

InterTechIRFInterpolationMode is set to 0 by default.
10.1.6.37 Changing the Real-Time Profile Drawing Method in Point Analysis

By default, propagation models draw the profile in real-time as the Point Analysis receiver is moved on the map. If
you wish to change this behaviour and make the propagation models draw the profile only once the left mouse has
been released, i.e., the Point Analysis receiver has been placed at its destination on the map, add the following lines
[DisplayProfileRealTime]
Propagation Model Type = False
Here Propagation Model Type is the text string stored under Type in the Propagation Models table. For example, the
Propagation Model Type of the "Standard Propagation Model" is "Atoll.StdPropagModel". This option does not apply
to Aster and CrossWave propagation models. These two models always redraw the profile when the left mouse
button is released.
10.1.6.38 Modelling Non-Selective RF Repeaters

By default, Atoll models selective RF repeaters that only amplify and transmit useful signals from their donor
transmitters. To model non-selective RF repeaters that amplify and transmit useful as well as interfering signals,
[Studies]
RFRepeatersFullInterferences = 1
RFRepeatersFullInterferences is set to 0 by default.

If you want Atoll to display calculation details related to repeated interfering signals in the Event viewer, add the
[Studies]
RFRepeatersDetails = 1
RFRepeatersDetails is set to 0 by default.
10.1.7 GSM GPRS EDGE Options
10.1.7.1 Considering Inter-technology Interference

In GSM "Coverage by C/I Level (DL)" predictions and in point analysis ("Interference" and "Details" views), inter-
technology interference is taken into account by default. By adding the following option in the Atoll.ini file, you can
add an Inter-technology check box to the list of Interference Sources on the Conditions tab of "Coverage by C/I
Level (DL)" predictions’ Properties dialog boxes and in point analyses’ "Interference" and "Details" views, which will
allow to consider or not inter-technology interference.
[GSM]
ExternalIncluded = 0
ExternalIncluded is set to 1 by default, i.e. inter-technology interference is taken into account by default in GSM
"Coverage by C/I Level (DL)" predictions (the Inter-technology check box does not appear in the list of Interference
Sources) and in point analyses’ "Interference" and "Details" views.

10.1.7.2 Considering Overlapping Zones for IM Calculation Based on Traffic

When calculating interference matrices based on traffic, overlapping between coverage areas of different
transmitters is taken into account when the option "Best Server" is selected and a positive margin is defined. For
interference matrices calculation based on "All" the servers (not Best Server), Atoll does not consider the
overlapping to improve performance. However, you can instruct Atoll to consider the overlapping during these
calculations as well by adding the following lines to the Atoll.ini file:
[Features]
IM_TRAFFIC_OVERLAP = 1
10.1.7.3 Setting the Default BSIC Format

You can set the default BSIC format to be used by Atoll by adding these lines to the Atoll.ini file:
[BsicFormat]
DefaultValue = 1 for Octal or 0 for Decimal format
DefaultValue enables you to change the default BSIC format (Octal by default) when you create a new Atoll
document.
10.1.7.4 Checking Database Consistency Automatically

If you want Atoll to automatically perform a basic data consistency check to avoid incompatibility between
redundant fields in GSM GPRS EDGE documents, add the following lines to the Atoll.ini file:
[Refresh]
TRXIntegrity = 1
By default, this option is considered to be set to 0, which improves Atoll’s performance.

If this option is set to 1, Atoll updates the values of the fields "Number of TRXs" and "Channels" in the Table tab of
the Transmitters folder’s Properties dialog box with the values from the TRGs and the TRXs tables respectively,
when a document is opened from a database or refreshed.
10.1.7.5 Disabling the Maximum Range Parameter

The maximum cell range parameter (System frame in the Network Settings folder’s Properties dialog box) in GSM
GPRS EDGE documents is used by default and set to 35 km. You can disable this option by adding the following lines
[Perfos]
MaxRangeApplied = No
If you set this option to anything other than "No", Atoll will use the maximum range parameter and set it to the default
value of 35 km.
10.1.7.6 Increasing the Memory Block Size for Predictions

When calculating predictions, Atoll divides the calculation zone into blocks that are processed successively. The
size of these blocks is determined by the amount of memory that is allocated to the process. A significant
performance gain can therefore be obtained by allocating more memory, which reduces the total number of blocks
for a prediction.
To define the memory block size, add the following lines to the Atoll.ini file:
[Perfos]

StudyMemorySize = <block size>
where <block size> is the amount of memory allocated to block calculation in megabytes (MB). It is important to
take into account the amount of memory (RAM and dynamic memory or "swap") available for calculations on the
machine, after substracting normal operating system and application usage.
By default, StudyMemorySize is set to 2048.
10.1.7.7 Enabling the Support for Multi-band Transmitters

Atoll is capable of modelling transmitters with subcells (TRX groups) belonging to different frequency domains. To
turn on the multi-band modelling feature, add the following lines to the Atoll.ini file:
[Studies]
MultiBandManagement = 1
MultiBandManagement is set to 0 by default. Enabling multi-band management allows the users to access the
multi-band management features through the Frequency Band Propagation button under the Subcells section of
the TRXs tab of a transmitter’s Properties dialog box, and through the Subcells > Multi-Band Propagation
Parameters command in the context menu of the Transmitters folder.
In the Multi-Band Propagation Parameters table and in the database, Atoll uses the "@" character to identify the
multi-band transmitters. Therefore, if you are working on a document with multi-band transmitters, and you have the
"@" character in the names of repeaters, remote antennas, or subcells without a donor/main transmitter, Atoll
deletes these records when opening the document from a database. If you do not want Atoll to automatically delete
such records when opening the document from a database, you have to sett the following option in the Atoll.ini file:
[Studies]
RemoveBadMultiCells = 0
RemoveBadMultiCells is set to 1 by default.

If you are not working with multi-band transmitters, i.e., MultiBandManagement is set to 0, Atoll does not
automatically delete such records. If you want Atoll to automatically delete such records when opening the
document from a database, you have to sett the following option in the Atoll.ini file:
[Studies]
CleanMultiCellManagement = 1
CleanMultiCellManagement is set to 0 by default.
10.1.7.8 Setting the Best Server Calculation Method in Same Priority HCS Layers
Atoll can calculate serving transmitters according to HCS layer priorities in coverage predictions. The signal level
HCS
received from the serving transmitter must be higher than the minimum reception threshold ( T Rec ) for its HSC
layer.
If there are two HCS layers with different priorities:
◼ The serving transmitter is the one that belongs to the HCS layer with the highest priority.
If there are two HCS layers with the same priority:
◼ 1st strategy: The serving transmitter is the one for which the difference between the received signal level and
HCS HCS
T Rec is the highest. Where, T Rec is the minimum reception threshold for the HSC layer of each respective
transmitter.
◼ 2nd strategy: The serving transmitter is the one which has the highest received signal level.
The default strategy is the 1st one. You can use the 2nd strategy by adding the following lines to the Atoll.ini file:
[Studies]

UseThresholdForSameLayerPriorities = 0
UseThresholdForSameLayerPriorities is set to 1 by default.
10.1.7.9 Hiding AFP Advanced Parameters

You can hide advanced parameters in the Atoll AFP Properties dialog box by adding the following lines to the
Atoll.ini file:
[AFP]
SimpleUserGUI = 1
SimpleUserGUI is set to 0 by default. When set to 1, the Interference Matrices, Finalisation, and Advanced tabs are
hidden.
10.1.7.10 Hiding AFP Hopping Parameters

You can hide hopping parameters in the Atoll AFP Properties dialog box by adding the following lines to the Atoll.ini
file:
[AFP]
HideHopping = 1
HideHopping is set to 0 by default. When set to 1, the HSN tab, the MAL tab, and the MAIO frame on the Reuse tab
are hidden.
10.1.7.11 Hiding Violations from Low Importance GSM Neighbours in AFP Results
By default, each neighbour pair has an importance value which defines the quality (and the rank) of the neighbour
link. This importance can be evaluated during the automatic neighbour allocation, a specific calculation process or
manually populated in the neighbour tables. In the Allocation tab of the AFP results dialog box, no difference is
made between high and low importance neighbours in term of violation display. In other words, whatever the
importance value is, any neighbour link in a separation violation is systematically displayed in a specific colour. You
can avoid displaying separation violations between low importance neighbours in a specific colour by adding the
[GSM]
MinNeighbourImportanceInAFPResults = XX
Where XX is the minimum importance for a neighbour pair to be considered as potentially violated.
 The value in the Atoll.ini file has to be between 0 and 100 whereas the importance
value in the neighbours tables is between 0 and 1.
10.1.7.12 Hiding Violations Between Non-synchronised MALs-MAIOs in AFP Results

In SFH, one can call synchronised MALs-MAIOs the case where, assuming the synchronisation site and the HSN can
be identified over the entire duration of a GSM frame. As an example, when the synchronisation site, the HSN and
the MAL length of 2 MALs-MAIOs are identical, it is always possible to identify if these are or not in separation
violation. In case the synchronisation site, the HSN and/or the MAL lengths or 2 MALs-MAIOs are different, a certain
probability of collision (and consequently a separation violation) may occur.
You can avoid displaying separation violations between non-synchronised MALs-MAIOs in a specific colour by
[GSM]

ShowNonSynchSFHViolationsInAFPResults = 0
ShowNonSynchSFHViolationsInAFPResults is set to 1 by default.
10.1.7.13 Modifying the Thresholds for Important Violations in AFP

By default, AFP allocation results are displayed in red when a resource has been modified and there is an important
separation constraint violation. You can modify the thresholds above which the important violations will be
highlighted by adding the following lines to the Atoll.ini file:
[GSM]
CoRedColorThreshPercent = 12
AdjRedColorThreshPercent = 15
CoRedColorThreshPercent (for co-channels) and AdjRedColorThreshPercent (for adjacent channels) are set to 12
and 15 by default. You can modify these thresholds to any value from 0 to 999.
Setting CoRedColorThreshPercent and/or AdjRedColorThreshPercent to 0 will force the behaviour of previous
versions of Atoll where important and less important violations were both highlighted.
10.1.7.14 Selecting the Interference Matrices Used During the AFP

All active interference matrices are taken into account during an AFP session according to the method defined in
the Atoll.ini file:
[AFP]
WorstCaseIM_FskAfp = 0|1
WorstCaseIM_FskAfp is set to 1 by default (corresponding to the Worst Case Method) and is only valid for Forsk’s
AFP.
When set to 0, the First Value Method is used.
◼ Worst Case Method: For each interference matrix relationship, the worst case value in all the active
interference matrices is taken into consideration.
◼ First Value Method: For each interference matrix relationship, the first value found in any active interference
matrix is taken into consideration. The order in which the interference matrices are scanned to find the first
value is the order of the interference matrices in the Interference Matrices folder in the Network tab, i.e. the
first IM is the one on top.
 The First Value Method was the default method in previous versions of Atoll.
That allowed multiple interference matrix imports.
10.1.7.15 Defining the Maximum Number of Transmitters for Reuse Distance

When using the reuse distance with the AFP, you can limit the number of relations based on distance taken into
consideration for each transmitter in order to ensure that performance is not degraded. In this example, the number
is limited to 70:
[AFP]
GlobalDistanceMatrixDegreeUB = 70
10.1.7.16 Defining the Maximum Number of Separation Violations

The maximum number of separation violations in AFP sessions can be raised to 21 by adding these lines to the
Atoll.ini file:

[AFP]
MaxNumberofSeparations = 21
10.1.7.17 Making Redundant Fields in the Transmitters Table Read-only

Some of the fields in the Transmitters table are redundant with other fields in the Subcells table. Modifying values
in one table might cause inconsistencies between the two tables in some cases. You can make these redundant
fields uneditable in the Transmitters table by adding the following lines to the Atoll.ini file:
[GSM]
CanEditTRXInfoAtTXLevel = 0
The redundant fields in the Transmitters table are the BCCH and the Number of TRXs fields.
CanEditTRXInfoAtTXLevel is set to 1 by default, which means that the fields are editable.
10.1.7.18 Setting the Transmission Diversity Gain

If a subcell is using transmission diversity, the air-combining gain of 3 dB is applied to all the received signal levels,
wanted (C) as well as interfering (I), during calculations. You can modify the default value of 3 dB by adding the
[Studies]
2GTxDiversityGain = X
Where X is the value of the air-combining gain in dB.
10.1.7.19 Deactivating Frequency Band Filtering in IM Calculation

When calculating interference matrices, Atoll filters potential interferers based on the frequency bands used by the
interfered and interfering subcells. For example, if the interfered subcell uses the GSM900 band and a potential
interferer uses the GSM1800 band, and the two bands do not overlap, then this potential interferer is ignored. This
filtering helps improve the calculation performance by ignoring the interfered-interferer pairs that would have
eventually resulted in no IM entry after the calculation. Any interferer whose assigned frequency band overlaps with
the frequency band assigned to the interfered subcell is not filtered.
You can deactivate this filtering by adding the following lines to the Atoll.ini file:
[IM]
FilterByFrequencyBands = 0
FilterByFrequencyBands is set to 1 by default.
10.1.7.20 Starting TRX Indexes at 1

By default, TRXs are indexed by Atoll starting at index 0. If you wish to start the indexing at 1, add the following lines
[GSM]
FirstTRXIndex = 1
FirstTRXIndex is set to 0 by default. Setting it to any other value has the same effect as FirstTRXIndex = 1.
10.1.7.21 Hiding the TRX Index

If you wish to hide the TRX index column, add the following lines to the Atoll.ini file:

[GSM]
TRXIndexHidden = 1
TRXIndexHidden is set to 0 by default.
10.1.7.22 Listing TRX Types in Alphabetical Order in Subcells Tables

You can force Atoll to list TRX types in alphabetical order in the subcells table of a transmitter’s properties by adding
the following lines to the Atoll.ini file.
[GSM]
SortSubcellsAlphabetically = 1
SortSubcellsAlphabetically is set to 0 by default.
10.1.7.23 Automatically Correcting Out-of-range Subcell Values

When out-of-range subcell values are found in the GSM network, Atoll fixes them by default as follows:
Subcell Value If it is... ...then it is replaced by:
Number of required TRXs <1 or >62 1

Number of required BCCHs not 1 1
Traffic load <0 or >1 1
Reception threshold < -116 dBm or > -50 dBm -102 dBm
Minimum C/I > 25 dB 12 dB

Half-rate traffic ratio <0% or >100% 40%
Mean power control gain <0 dB or >32 dB 4 dB
DL power reduction <0 dB or >25 dB 0 dB

AFP weight <0 or >100 1
Target rate of traffic overflow <0% or >100% 0%
Maximum percentage of interference <1% or >100% 1%

Maximum MAL size >62 62
If you wish to modify this default behaviour, add the following lines to the Atoll.ini file:
[GSM]
SubcellValueFixMethod = 1
SubcellValueFixMethod is set to 0 by default, which corresponds to the default behaviour described above.
If you set this parameter to 1, the values currently out-of-range are shifted to the closest boundary of the authorised
range. For example if the reception threshold is less than -116 dBm, it will be replaced by -116 dBm instead of -102
dBm as in the default behaviour. Likewise, if it is greater than -50 dBm, it will be replaced by -50 dBm instead of -102
dBm.
10.1.8 UMTS HSPA, CDMA2000, and TD-SCDMA Options
10.1.8.1 Suppressing Cell Name Carrier Suffixes

It is only possible to suppress the carrier suffix in a 3G cell name in the case of a single carrier scenario, i.e., the first
carrier is also the last carrier in the global parameters. To do this, add the following lines to the Atoll.ini file:

[3GCells]
NoSuffixIfUniqueCarrier = 0 or 1
This is set to 0 by default, which means that cell names will follow the normal convention of Atoll, SiteN_X(C). If
there is only one carrier, meaning that C is unique, then this option can be set to 1. This will result in cell names which
will be same as the transmitter names, SiteN_X.
10.1.8.2 Disabling Macro-diversity (SHO) Gains Calculation for Ec/Io and Eb/Nt
In UMTS HSPA and CDMA2000 documents, macro-diversity gains are calculated by default for pilot Ec/Io, DL and
UL Eb/Nt based on their respective standard deviations.
You can deactivate the calculation and use of macro-diversity gains for all of the above by adding this option in the
Atoll.ini file:
[Shadowing]
WithSHOGain = 0
WithSHOGain is set to 1 by default.

If you want, you can deactivate macro-diversity gain calculations for pilot Ec/Io only by adding this option in the
Atoll.ini file:
[CDMA]
AddPilotSHOGain = 0
AddPilotSHOGain is set to 1 by default.
10.1.8.3 Calculating and Displaying Peak or Instantaneous HSDPA Throughput

In UMTS HSPA documents, you can choose to display and work with either peak values or instantaneous values of
the HSDPA throughputs per mobile, cell, and site in simulation results. To do this, you can add the following lines to
the Atoll.ini file:
[CDMA]
HSDPAThroughputPeak = 0 or 1
◼ 0: Instantaneous throughput (Default)

◼ 1: Peak throughput
If you choose to display the instantaneous HSDPA throughputs, Atoll will:
◼ Display the number of simultaneous HSDPA users in the simulation results.
◼ Place a certain part of HSDPA users in a waiting queue during simulations.
◼ Display the instantaneous gross and instantaneous application level throughputs per mobile and per cell in
the simulation results.
◼ Display the instantaneous throughput per site in the Sites tab of the simulation results.
If you choose to display the peak HSDPA throughputs, Atoll will:
◼ Not display the number of simultaneous HSDPA users in the simulation results.
◼ Display the peak gross and peak application level throughputs per mobile and per cell in the simulation results.
◼ Display the MUG table on the MUG tab of the Proportional Fair properties. Inputs from this is used to calculate
the peak gross throughput per cell when the scheduling algorithm is "Proportional Fair".
◼ Display the average HSDPA throughput per user in the Cells tab of the simulation results.
HSDPA resource scheduling will not be carried out. The HSDPA throughput for each user will be calculated by taking
into account the MUG corresponding to the current number of connected HSDPA users.
In Average Simulation results, the average HSDPA throughput per user can be calculated excluding the simulations
where no HSDPA users were served. To do this, add the following lines to the Atoll.ini file:

[CDMA]
HSDPAAvgSimuResults = 1
HSDPAAvgSimuResults = 0 by default.
10.1.8.4 Setting the Power to Use for Intra-cell Interference in HSDPA

In HSDPA prediction studies, you can choose whether to perform intra-cell interference calculations based on total
cell power (Ptot) or maximum cell power (Pmax). By default, Atoll performs this calculation based on the total
power. You can instruct Atoll to use maximum power in stead by adding the following lines to the Atoll.ini file:
[CDMA]
PmaxInIntraItf = 1
◼ 0: Intra-cell interference calculation based on total power (Default)

◼ 1: Intra-cell interference calculation based on maximum power
10.1.8.5 Enabling Coverage Predictions of Connection Probabilities

You can perform coverage prediction studies for connection probabilities in UMTS HSPA documents by adding the
[CDMA]
UseStudyCnxProba = 1
MinUsersPerBin = X
This coverage prediction study is available in the list of prediction studies if UseStudyCnxProba is set to 1.
Otherwise, it will not be available. MinUsersPerBin is the minimum number of users per pixel required for that pixel
to be taken into account in the coverage prediction.
10.1.8.6 Setting the Calculation Method for HS-PDSCH CQI

If you choose the “CQI based on CPICH quality” option in Global Parameters, you can select the formula used for
calculating HS-PDSCH CQI in Atoll by adding the following lines to the file:
[CDMA]
CQIDeltaWithPower = 0 or 1
CQIDeltaWithPower is set to 1 by default. In this case, the HS-PDSCH CQI is calculated using the formula:
 CQI  HS – PDSCH =  CQI  pilot – P pilot + P HS – PDSCH
If you set CQIDeltaWithPower to 0, the HS-PDSCH CQI will be calculated using the formula:
EC EC
 CQI  HS – PDSCH =  CQI  pilot –  ------- +  -------
 N T pilot  N T HS – PDSCH
Note that the default configuration (CQIDeltaWithPower set to 1) is relevant only when N T is calculated using the
"Total Noise" option.
The above equations are in dB. Refer to the Technical Reference Guide for more details.
10.1.8.7 Enabling Orthogonality Factor in Pilot EC/NT Calculation in HSDPA

%Pilot Finger and the Orthogonality Factor model two different effects on the CPICH quality. %Pilot Finger is related
to the CPICH physical channel only and models the loss of energy in the CPICH signal due to multipath. The

Orthogonality Factor is related to the correlation between the CPICH physical channel and other intra-cell physical
channels.
You can instruct Atoll to use the Orthogonality Factor in the calculation of pilot EC/NT in HSDPA instead of %Pilot
Finger by adding the following lines to the Atoll.ini file:
[CDMA]
OrthoInCPICH = 1
10.1.8.8 Setting the Maximum Number of Rejections for Mobiles

You can define a maximum number of rejections for mobiles during simulations by adding the following lines to the
Atoll.ini file:
[CDMA]
MaxRejections = X
If a mobile is rejected X number of times, it will no longer be considered in the next iterations.
10.1.8.9 Setting the Maximum Number of Rejections for HSDPA Mobiles

You can set the number of times an HSDPA mobile should be rejected (or placed in a queue) before it is considered
permanently rejected (or permanently placed in the queue). The default value of this option is 5. To modify the
default value, enter the following lines to the Atoll.ini file:
[CDMA]
HSDPAMaxRejections = X
Where X is the number of times an HSDPA mobile should be rejected to be considered permanently rejected for the
simulation.
10.1.8.10 Defining an Offset With Respect to The Thermal Noise

You can define an offset with respect to the thermal noise by adding the following lines to the Atoll.ini file:
[CDMA]
CutOffSimu = X
Where, X is the offset value in dBs. During Monte Carlo simulations, calculations performed on each mobile only
take into account the cells whose received power, at the mobile location, is greater than the thermal noise minus
this offset. You should set CutOffSimu to 20 dB for optimum performance without losing a lot of interference.
10.1.8.11 Setting Precision of the Rasterisation Process

During Monte Carlo simulations, Atoll internally converts vector traffic maps to raster traffic maps in order to
perform a distribution of users according to the traffic densities and the connection probabilities. The accuracy of
this conversion from vectors to raster is high enough for most, nearly all, cases. However, this accuracy might not
be enough for highly precise vector polygons defining traffic hotspots.
The figure below depicts this effect for a vector polygon which is just slightly larger than 1 raster pixel. The vector
polygon and the raster bin have the same traffic density in the following figure.
Figure 10.1: : Rasterisation Process
The primitive libraries, which perform the conversion from vector to raster, deal in terms of float values for the x and
y coordinates of the vector polygons. Since these are float values, you will have to create vector polygons with the
exact (accurate to all the decimal places) size of a pixel (or multiples of a pixel) in order to get raster pixels with the

exact same surface area as the vector polygons. If the coordinates of the vector polygons are not accurate, it is
possible that the raster pixel found from the vector polygon will be shifted 1 bin to the right or to the left.
Such a rasterisation means that the number of users in the vector remains correct, but the density might be different
since the surface area has changed (Number of users = User Density x Area).
If you want Atoll to increase the precision of the rasterisation process for hotspots in your network. You can add the
[Rasterization]
Improve = 0 or 1
Precision = 1
SurfRatio = 20
MaximumSurf = 2500
The options are:

◼ Improve = 1 (by default) means that Atoll will use the accurate rasterisation method for small polygons.
Improve = 0 means that the normal rasterisation method will be used for all polygons. Setting this option to 1
implies that this algorithm will not be used globally for all polygons, but only for small polygons which are
defined by the options “SurfRatio” or “MaximumSurf”.
◼ Precision = 1 (by default) means that the rasterisation resolution (step) used by the algorithm for small
polygons is 1 metre. You can set it to a higher value if you observe performance degradation. The step of
rasterisation means the size of the bin used to approximate the vector shape with bins.
 If you set Precision = 1, the performance (calculation speed) can be considerably

decreased depending on the size of your network. It is recommended to set a higher
value for the Precision option.
◼ SurfRatio = 20 (by default) means that the accurate algorithm will be used only for polygons whose size is
smaller than 20 times the size of the normal raster bin. The normal raster bin size in anAtoll document is the
finest resolution among the geographic data available in the document.
 If your Atoll document contains two geographic data files, one with a 20 m
resolution and the other with a 5 m resolution, and you remove the 5 m one from
your document, Atoll will still keep 5 m as the normal raster bin size.
◼ MaximumSurf = 2500 (by default) means that a polygon will be considered small only if its surface area is less
than or equal to 2500 sq. m.
So, a polygon will be considered small, and will be rasterised using the accurate algorithm, if either the ratio of its
surface area to the surface area of the normal raster bin is equal to or less than SurfRatio, or if its surface area is
less than MaximumSurf. If you want to use just the MaximumSurf option, you can set the SurfRatio to 0.
10.1.8.12 Defining the Number of Iterations Before Downgrading

You can set the number of iterations that Atoll should carry out before starting the downgrading. The default value
of this option is 30. To modify the default value, enter the following lines to the Atoll.ini file:
[CDMA]
IterBeforeDown = X
Where X is the integer number of iterations.
10.1.8.13 Adjusting the Working of the Proportional Fair Scheduler

In UMTS HSPA documents, you can adjust how the proportional fair scheduler functions by adding the following

[CDMA]
PFSchedulerCQIFactor = X
Where X is a number between 0 and 100, which represents the proportional fair scheduler weight.
PFSchedulerCQIFactor = 50 by default. If you set PFSchedulerCQIFactor = 0, the proportional fair scheduler
functions like the Round Robin scheduler. If you set PFSchedulerCQIFactor = 100, the proportional fair scheduler
functions like the Max C/I scheduler.
10.1.8.14 Displaying the Ec/I0 of Rejected Mobiles in Simulation Results

In UMTS and CDMA simulation results, the Ec/I0 AS1 column in the Mobiles tab can list the Ec/I0 values from the
best server for all the mobiles, connected or rejected. To display the Ec/I0 from the best server for the rejected
mobiles, add the following lines to the Atoll.ini file:
[CDMA]
DisplayEcIoOfRejected = 1
DisplayEcIoOfRejected is set to 0 by default.
10.1.8.15 Switching Back to the Old Best Server Determination Method

Before Atoll 3.3.0, best server determination in UMTS and HSPA predictions (i.e, coverage prediction and AS
Analysis) used to be performed by selecting the cell with the highest Ec/I0 with no layer priority consideration. To
switch back to this best server determination method, add the following lines to the Atoll.ini file:
[UMTS]
BestServer_LayerPriority = 0
BestServer_LayerPriority is set to 1 by default.

Before Atoll 2.8.0, best server determination in simulations of UMTS and CDMA networks used to be performed by
selecting the best carrier within transmitters according to the selected method (site equipment) and then the best
transmitter using the best carrier. To switch back to this best server determination method, add the following lines
[CDMA]
MultiBandSimu = 0
MultiBandSimu is set to 1 by default.
10.1.8.16 Switching Back to the Old Radio Bearer Allocation Algorithm for Multi-carrier EVDO
Rev.B
Before Atoll 3.2.1, radio bearer allocation for multi-carrier EVDO Rev.B used to be performed by equally sharing the
available terminal power between the carriers.
To switch back to this radio bearer allocation method, add the following lines to the Atoll.ini file:
[CDMA]
SharingEquallyPower = 1
UsingPreviousIterationPowerWeight = 1
These two options are set to 0 by default.

10.1.8.17 Displaying Automatic Allocation Cost Values

You can display the cost values calculated by Atoll for different relations when allocating scrambling codes and PN
offsets. To display cost values, add the following lines to the Atoll.ini file:
[PSC]
DisplayCostValues = 1
DisplayCostValues is set to 0 by default.
10.1.8.18 Selecting SC and PN Offset Allocation Strategies Available in the GUI

In the Atoll.ini file, you can select the scrambling code (UMTS and TD-SCDMA) and PN offset (CDMA2000)
allocation strategies that will be available to the user in the automatic allocation dialog box. To select the allocation
strategies, add the following lines to the Atoll.ini file:
[CDMA]
CodeStrategies = 1, 2, 3, 4
The allocation strategies 1, 2, 3, and 4 correspond to the following:

◼ In UMTS:
◼ 1: Clustered
◼ 2: Distributed per Cell
◼ 3: One Cluster per Site
◼ 4: Distributed per Site
◼ In TD-SCDMA:
◼ 1: Clustered
◼ 2: Distributed per Cell
◼ 3: One SYNC_DL Code per Site
◼ 4: Distributed per Site
◼ In CDMA2000:
◼ 1: PN Offset per Cell
◼ 2: Adjacent PN-Clusters per Site
◼ 3: Distributed PN-Clusters per Site
10.1.8.19 Defining a Fixed Interval Between Scrambling Codes

You can define a fixed interval between scrambling codes assigned to cells on a same site when the allocation is
based on a distributed strategy (Distributed per Cell or Distributed per Site). To apply the defined interval, add the
[PSC]
ConstantStep = 1
ConstantStep is set to 0 by default.
10.1.8.20 Compressed Mode: Restricting Inter-carrier and Inter-technology Neighbour Allocation

You can prevent Atoll from allocating inter-carrier and inter-technology neighbours to cells located on sites whose
equipment does not support compressed mode, by adding the following lines to the Atoll.ini file:
[Neighbours]
CompressModeEval = 1

CompressModeEval is set to 0 by default.
10.1.8.21 Setting the Maximum AS Size for SC Interference Prediction

You can set the maximum active set size to a fixed number of transmitters for the scrambling code interference
coverage prediction by adding the following lines to the Atoll.ini file:
[Studies]
SCActivesetMaxSize = X
Where X is the maximum number of transmitters in the active set. If you set SCActivesetMaxSize = 10, you will get
the same results in the coverage prediction as the SC Interference tab in the point analysis.
10.1.8.22 Displaying Uplink Total Losses in Coverage by Signal Level

In UMTS, CDMA, LTE, WiMAX, and Wi-Fi technologies, you can activate the Uplink Total Losses and Minimum Uplink
Total Losses display options in the Coverage by Signal Level (DL) prediction by adding the following lines to the
Atoll.ini file:
[Studies]
UplinkLosses = 1
UplinkLosses is set to 0 by default.

Uplink total losses are calculated from the downlink total losses by replacing the downlink transmitter losses by
uplink transmitter losses. In GSM, the Uplink Total Losses display options is available in the Coverage by Signal
Level (UL) prediction.
In addition to the above, in LTE, this option enables an Uplink Total Losses (dB) display option in the Effective Signal
Analysis (UL) prediction. These losses are calculated using LTE-specific parameters, including MIMO, schedulers,
power control, and uplink bandwidth allocation.
10.1.8.23 Setting the Maximum UL Reuse Factor for HSUPA Users’ Noise Rise Estimation
In UMTS HSPA simulations, Atoll assumes a constant uplink reuse factor for estimating the maximum available
noise rise per HSUPA user. This can cause unnecessary rejection of some HSUPA users in very low traffic cases.
You can set an upper limit for the uplink reuse factor by adding the following lines to the Atoll.ini file:
[UMTSSimus]
MaxReuseFactor = value
Where value is 5 by default.
10.1.8.24 Configuring HSUPA Resource Allocation for Active Set Analysis

In HSUPA calculations of the Active Set Analysis, HSUPA resources (the remaining load of the cell after allocating
capacity to all R99 users) are considered as equally shared between HSUPA users. The number of HSUPA bearer
users is taken either from the cell properties or from the simulation.
Atoll can calculate HSUPA-results for a single user by adding the following lines to the Atoll.ini file:
[UMTS]
HSUPA_users_sharing_resource = 0
In this case, the entire remaining load of the cell is allocated to a single HSUPA bearer user.
HSUPA_users_sharing_resource is set to 1 by default.

10.1.9 LTE, NB-IoT, WiMAX, Wi-Fi, and LPWA Options
10.1.9.1 Blocking Access to IEEE Parameters in WiMAX

You can disallow modification of the parameters that come from the IEEE specifications, and are not supposed to
be changed, by adding the following lines to the Atoll.ini file:
[WiMAX]
ModifiableIEEEParams = 0
By default, ModifiableIEEEParams is set to 1, which means that all the parameters are modifiable. When you set
ModifiableIEEEParams to 0, it means that the following parameters will be unmodifiable in the GUI:
◼ In the Permutation Zones table: Number of Used Subcarriers, Number of Data Subcarriers, and Number of
Subchannels per Channel.
◼ In the Permutation Zones table: Subchannel Groups (Segment 0), Subchannel Groups (Segment 1), and
Subchannel Groups (Segment 2) for FFT sizes < 1000.
 In the Permutation Zones table, the first DL PUSC permutation zone cannot be
deactivated.
◼ In the Frame Configurations table and in the General tab of the frame configurations Properties dialog box:
Number of Preamble Subcarriers.
 In the Frames Configurations table, the cells under Total Number of Subcarriers
change into combo boxes with the following five values: 128, 256, 512, 1024, 2048.
10.1.9.2 Ensuring Compatibility of UL and DL Bearers between Reception Equipment

If you want Atoll to perform an intersection over the bearers supported by the cell equipment and by the terminal
equipment, add the following lines to the Atoll.ini file:
[OFDM]
UseCommonBearersOnly = 1
When UseCommonBearersOnly is set to 1, Atoll only uses the bearers for which selection thresholds are defined in
both the terminal and the cell equipment for both downlink and uplink bearer selection.
◼ For DL calculations, Atoll compares the DL bearer selection threshold curves of the terminal and the cell
equipment.
◼ For UL calculations, Atoll compares the UL bearer selection threshold curves of the terminal and the cell
equipment.
UseCommonBearersOnly is set to 0 by default.
10.1.9.3 Enabling Display of Signals per Subcarrier Point Analysis in LTE and NB-IoT
By default a point analysis in LTE and NB-IoT displays carrier-wide signal levels. You can also use a point analysis
to display per-subcarrier signal levels by adding the following lines to the Atoll.ini file:
[LTE]
DisplaySignalsPerSCInPtA = 1
DisplaySignalsPerSCInPtA is set to 0 by default.

10.1.9.4 Including Cyclic Prefix Energy in LTE and NB-IoT Signal Level Calculation
The useful signal level calculation takes into account the useful symbol energy (Es), i.e., excluding the energy
corresponding to the cyclic prefix part of the total symbol duration. However, you can include the cyclic prefix energy
in the useful signal level calculation by adding the following lines to the Atoll.ini file:
[LTE]
ExcludeCPFromUsefulPower = 0
ExcludeCPFromUsefulPower is set to 1 by default.

Independent of the option, interference levels are calculated for the total symbol durations, including the energy
useful symbol duration and the cyclic prefix energy.
10.1.9.5 Excluding Cyclic Prefix Energy in WiMAX and Wi-Fi Signal Level Calculation
The useful signal level calculation can exclude the energy corresponding to the cyclic prefix part of the total symbol
duration, hence taking into account only the energy belonging to the useful symbol duration. In order to do so, you
must add the following lines to the Atoll.ini file:
[WiMAX]
ExcludeCPFromUsefulPower = 1
ExcludeCPFromUsefulPower is set to 0 by default.

Independent of the option, interference levels are calculated for the total symbol durations, including the energy
useful symbol duration and the cyclic prefix energy.
10.1.9.6 Ignoring Inter-Neighbour Preamble Index Collision in WiMAX

The automatic preamble index allocation algorithm in Atoll takes into account the possible collision of preamble
indexes assigned to neighbours of a cell. This means that Atoll tries to not allocate the same preamble index to two
neighbours of a cell. If you want to disable this constraint, i.e., allow Atoll to allocate the same preamble index to
two neighbours of a cell, add the following lines to the Atoll.ini file:
[WiMAX]
InterNeighbourPICollisions = 0
InterNeighbourPICollisions is set to 1 by default.

The preamble index audit based on neighbours also takes this option into account. With InterNeighbourPICollisions
= 1, the audit lists the cell pairs that are neighbours of a cell and are allocated the same preamble index. When
InterNeighbourPICollisions = 0, the preamble index collision is not verified between neighbours of a cell.
10.1.9.7 Ignoring Inter-Neighbour Physical Cell ID Collision in LTE

The automatic physical cell ID allocation algorithm in Atoll takes into account the possible collision of physical cell
IDs assigned to neighbours of a cell. This means that Atoll tries to not allocate the same physical cell ID to two
neighbours of a cell. If you want to disable this constraint, i.e., allow Atoll to allocate the same physical cell ID to two
neighbours of a cell, add the following lines to the Atoll.ini file:
[LTE]
InterNeighbourIDCollisions = 0
InterNeighbourIDCollisions is set to 1 by default.

The physical cell ID audit based on neighbours also takes this option into account. With InterNeighbourIDCollisions
= 1, the audit lists the cell pairs that are neighbours of a cell and are allocated the same physical cell ID. When
InterNeighbourIDCollisions = 0, the physical cell ID collision is not verified between neighbours of a cell.

10.1.9.8 Renaming OPUSC Zone to PUSC UL in WiMAX

If you wish to work with two PUSC UL permutation zones, you can rename the OPUSC permutation zone to PUSC UL
by adding the following lines to the Atoll.ini file:
[WiMAX]
ReplaceOPUSCwithPUSCUL = 1
ReplaceOPUSCwithPUSCUL is set to 0 by default.
10.1.9.9 Deactivating Uniform Distribution of Resources

By default, the basic automatic allocation of physical cell IDs and preamble indexes distributes the allocated
resources uniformly. If you wish to deactivate the uniform distribution of resources, add the following lines to the
Atoll.ini file:
[OFDM]
UniformIDDistribution = 0
UniformIDDistribution is set to 1 by default.
10.1.9.10 Taking Second Order Neighbours into Account in the AFP

The LTE AFP takes first order neighbours into account when allocating physical cell IDs. The WiMAX AFP takes first
order neighbours into account when allocating preamble indexes and downlink and uplink zone permbases. If you
want the AFP to take both first and second order neighbours into account, add the following lines to the Atoll.ini file:
[OFDM]
SecondNeighbours = 1
SecondNeighbours is set to 0 by default.
10.1.9.11 Excluding the Adjacent Channel Overlap from the AFP Cost Functions
The LTE, WiMAX, and Wi-Fi AFPs take the adjacent channel overlap into account for allocation frequencies, physical
cell IDs, preamble indexes, and other resources. If you wish to take only the co-channel overlap into account and
exclude the effect of adjacent channel overlap in resource allocation, add the following lines to the Atoll.ini file:
[OFDM_AFP]
AdjacentProtection = 0
AdjacentProtection is set to 1 by default.
10.1.9.12 Synchronised/Unsynchronised Interference Calculation in LTE and NB-IoT

There are two downlink interference calculation methods in Atoll. For more information, see the Technical Reference
Guide.
Method 1: Synchronised transmission/reception (default).
Atoll calculates the interference between two cells using this method when:
◼ The frequency channels assigned to the interfered and interfering cells have the same centre frequency,
and
◼ The interfered and interfering cells both have an even number of frequency blocks or both have an odd
number of frequency blocks, and
◼ The following option is set in the Atoll.ini file (default value):

[LTE]
SameItf_PDSCH_RS_PDCCH = 0
Synchronised transmission and reception means that OFDM symbols of the interfered and interfering frames
overlap and match each other in time.
Method 2: Unsynchronised transmission/reception
Atoll calculates the interference between two cells using this method when:
◼ The frequency channels assigned to the interfered and interfering cells do not have the same centre
frequency, or
◼ The interfered and interfering cells do not both have an even number of frequency blocks or do not both
have an odd number of frequency blocks, or
◼ The following option is set in the Atoll.ini file:
[LTE]
This method is also used to calculate interference received from LTE and NB-IoT cells of an external network
in co-planning and multi-RAT modes, i.e. inter-technology interference received from LTE and NB-IoT cells
calculated using inter-technology IRFs.
10.1.9.13 Setting PDCCH to 100% Loaded in LTE Interference Calculations

By default, the downlink interference from PDCCH is weighted by the downlink traffic load of the interfering cell. If
you wish to calculate the interference coming from the PDCCH using a fixed load of 100%, add the following lines
[LTE]
ApplyDLLoadOnPDCCHInterf = 0
ApplyDLLoadOnPDCCHInterf is set to 1 by default. Using SameItf_PDSCH_RS_PDCCH = 1, Atoll calculates a single

total noise (I+N) value for the RS, PDCCH, and PDSCH containing interference from the RS, PDCCH, and PDSCH.
Within this combined total noise (I+N) value, the ApplyDLLoadOnPDCCHInterf option only impacts the interference
component from the PDCCH. The RS and PDSCH interference components are calculated as usual.
For more information on SameItf_PDSCH_RS_PDCCH, see "Synchronised/Unsynchronised Interference Calculation
in LTE and NB-IoT" on page 211 and the Technical Reference Guide.
10.1.9.14 Calculating EIRP from RS/NRS EPRE in LTE/NB-IoT Signal Level Predictions
Atoll calculates the EIRP from the RS and NRS power in LTE and NB-IoT. In signal level-based coverage predictions,
if you wish to calculate the EIRP from the RS and NRS EPRE instead, add the following lines to the Atoll.ini file:
[LTE]
EIRPfromRSEPRE = 1
EIRPfromRSEPRE is set to 0 by default. This option applies to Coverage by Transmitter, Coverage by Signal Level,
and Overlapping Zones predictions in LTE and NB-IoT.
10.1.9.15 Extending the List of Server Selection Methods in Coverage Predictions

Extended best server selection methods can be made available for in-depth analyses by adding following lines in
the Atoll.ini file:
[LTE]

ExtendedServerMethodsInPredictions = 1
ExtendedServerMethodsInPredictions is set to 0 by default. Setting ExtendedServerMethodsInPredictions to 1

enables you to base the best server selection on the uplink total losses in the Effective Signal Analysis (UL) coverage
prediction, and on RSRQ, RS C/(I+N), or PDSCH C/(I+N) in the Coverage by C/(I+N) Level (DL) coverage prediction.
These best server selection methods are computationally intensive and may require more time to calculate than the
ones based on RSRP available by default.
10.1.9.16 Averaging the Uplink Noise Rise in dB

The average simulation results provide the linear average of uplink noise rise values displayed in dB. If you want
Atoll to calculate the average by directly using the noise rise values in dB, add the following lines to the Atoll.ini file:
[OFDM_SIMU]
MeanNRInDB = 1
MeanNRInDB is set to 0 by default.
10.1.9.17 Deactivating Service Max Throughput Demand Downgrading in LTE

Service maximum throughput demand downgrading is active by default in LTE Monte Carlo simulations. If you wish
to deactivate this downgrading, add the following lines to the Atoll.ini file:
[LTE]
ServiceMBRDowngrading = 0
ServiceMBRDowngrading is set to 1 by default. The above does not apply to LTE-A mobiles performing carrier
aggregation or downlink non-coherent joint transmission CoMP.
10.1.9.18 Displaying Pixels with Zero Throughput in Coverage Predictions

In throughput coverage predictions, pixels are coloured according to the defined throughput threshold colours if
there are bearers available on those pixels. If you wish to have other pixels, i.e., those with no available bearer hence
zero throughput, to be coloured as well, add the following lines to the Atoll.ini file:
[OFDM]
DisplayThroughputZero = 1
DisplayThroughputZero is set to 0 by default.
10.1.9.19 Setting Uplink Noise Rise Control Parameters in LTE

The default method of uplink noise rise control is the best effort method. This means that uplink noise rise control
is not part of the simulation convergence criteria. For best effort noise rise control, you can modify the noise rise
control margin through Atoll.ini file by adding the following lines:
[LTE]
NR_CONTROL_MARGIN_MIN = X
Positive values of NR_CONTROL_MARGIN_MIN are considered as negative margins. For example, X is interpreted
by Atoll as -X dB. NR_CONTROL_MARGIN_MIN is set to 1 by default, interpreted as -1 dB.
If you wish to include the uplink noise rise control in the simulation convergence criteria, you can change the uplink
noise rise control method from best effort to strict by setting the following option in the Atoll.ini file:
[LTE]

ULNRControlMethod = 1
ULNRControlMethod is set to 0 by default.

For the strict noise rise control method, you can modify the noise rise control precision level through the Atoll.ini file
by adding the following lines:
[LTE]
ULNRControlPrecision = X
Integer values of ULNRControlPrecision are considered as tenths of dB. For example, X is interpreted by Atoll as
0.X dB. ULNRControlPrecision is set to 5 by default, interpreted as 0.5 dB.
10.1.9.20 Using the LTE ABS Patterns on Cell-edge Only

By default, ABS patterns are used throughout the cell, irrespective of the cell-edge area and the cell-edge traffic ratio.
If you wish to apply ABS patterns only on the cell-edges, you can do so by adding the following lines to the Atoll.ini
file:
[LTE]
UseABSonCellEdgeOnly = 1
By default, UseABSonCellEdgeOnly is set to 0. Applying the ABS patterns only on the cell-edge means that all
subframes are considered non-ABS subframes in the cell centre. This method enables you to include the cell-edge
traffic ratio in the calculation of interference.
10.1.9.21 Switching Between Carrier Aggregation/Multicarrier Operation Modes

Atoll supports different modes of LTE carrier aggregation and NB-IoT multicarrier operation: group-based, intra-
eNode-B, and multi-eNode-B. You can switch between these carrier aggregation/multicarrier operation modes by
[LTE]
CAWithinENB = 0|1|2
where:
◼ 0 corresponds to the multi-eNode-B mode. This means that cells belonging to any site can perform carrier
aggregation/multicarrier operation with each other.
◼ 1 corresponds to intra-eNode-B mode. This means that only cells belonging to the same site can perform
carrier agrregation/multicarrier operation with each other. Atoll only selects secondary/slave serving cells
from within the same eNode-B (belonging to the same site) as the selected primary/anchor serving cell.
◼ 2 corresponds to the group-based mode. This means that cells belonging to the same group can perform
carrier aggregation/multicarrier operation with each other.
CAWithinENB is set to 2 by default. For more information on managing carrier aggregation/multicarrier operation
groups, see the User Manual.
10.1.9.22 Switching Between LTE Multi-Server Scheduling Methods

For their maximum throughput demands, LTE-A users are scheduled separately on each of their serving cells
(primary and secondary cells for carrier aggregation, and coordinated servers for downlink non-coherent joint
transmission CoMP). Each user’s remaining throughput demand (maximum – minimum) is distributed over each of
its serving cells proportionally to the resources available on each serving cell and to the user’s downlink effective
RLC channel throughput or uplink effective RLC allocated bandwidth throughput on each of its serving cell. Within
each serving cell, resource allocation for the maximum throughput demands is carried out according to the
scheduler used by that cell.

If you wish to have each user’s remaining throughput demand (maximum – minimum) distributed over each of its
serving cells proportionally only to the resources available on each serving cell, add the following lines to the Atoll.ini
file:
[LTE]
CASchedulingMethod = 1
CASchedulingMethod is set to 0 by default. The CASchedulingMethod option is only used when the option
CAWithinENB is either set to 0 or 1.
10.1.9.23 Switching Between PCell/Anchor Cell Selection Methods

By default, cells of type LTE-A PCell/Multicarrier anchor and of type LTE/Standard are processed in the same
manner during cell selection. If you wish to change this method, add the following lines to the Atoll.ini file:
[LTE]
OldBestServerMethodForCA = 1
OldBestServerMethodForCA is set to 0 by default. Setting OldBestServerMethodForCA to 1 assigns an implicit

priority to cells of type LTE-A PCell/Multicarrier Anchor over cells of type LTE/Standard. UEs are then connected to
cells of type LTE-A PCell/Multicarrier Anchor irrespective of the layer priorities and the received RSRP/NRSRP.
10.1.9.24 Displaying Grid-of-Beam Patterns in Logarithmic Scale

By default, Atoll displays the horizontal patterns of antennas selected as beams in the LTE grid-of-beams smart
antenna model properties using a linear scale. If you wish to display these patterns using the logarithmic scale, add
[GOB_MODEL]
DisplayLinearDiagram = 0
DisplayLinearDiagram is set to 1 by default.
10.1.9.25 Allowing Multi-Cell Transmitters Using Different Frequencies

By default, Atoll allows you to create transmitters with more than one cell as long as the downlink start frequency
of the frequency bands used by all the cells is the same. This implies that the path losses calculated for a transmitter
are considered valid for all the cells of the transmitter. If you wish to remove this restriction, add the following lines
[OFDM]
ForceSameFrequencyForCoTXCells = 0
ForceSameFrequencyForCoTXCells is set to 1 by default.
10.1.9.26 Changing the LTE Cell-Edge Determination Method

By default, Atoll compares the difference between the total losses at the mobile/pixel from its best server and the
second best server with the delta path loss threshold defined for the best server to determine whether the mobile/
pixel is located at cell-edge or not. Instead, if you want Atoll to use the difference between the RSRPs from the best
and second best server, add the following lines to the Atoll.ini file:
[LTE]
CellEdgeMethod = 1

CellEdgeMethod is set to 0 by default. For calculating the cell-edge regions for CoMP, if CellEdgeMethod is set to 1,
Atoll compares the difference between the RSRP from the best server and the second best server belonging to the
same CoMP set with the cell edge margin defined for the best server.
10.1.9.27 Filtering LTE and NB-IoT Cell Groups Loaded From a Database
In multi-user environments, cell groups, such as carrier aggregation/multicarrier operation groups and CoMP sets,
can be stored in the database. When you open a document from a database, Atoll loads all the cell groups by default.
If you want Atoll to only load cell groups relevant to the cells being loaded, you must set the following option in the
Atoll.ini file:
[LTE]
FilterUsedGroups = 1
FilterUsedGroups is set to 0 by default.
10.1.9.28 Allocating PRACH RSIs from Non-Overlapping Lists

By default, Atoll allocates PRACH RSIs from lists of overlapping possible values. For example, if a cell requires 10
PRACH RSIs, depending on the cell’s defined PRACH RSI domain, Atoll may allocate 10 PRACH RSIs from
overlapping lists with consecutive starting values: 0-9, 1-10, 2-11, 3-12, etc. If you want to allocate PRACH RSIs from
non-overlapping lists, such as 0-9, 10-19, 20-29, etc., add the following lines to the Atoll.ini file:
[OFDM_AFP]
CandidatePrachRsiListsWithOverlap = 0
CandidatePrachRsiListsWithOverlap is set to 1 by default. This option is also taken into account by the audit.
Note that setting this option to 0 reduces the number of available resources for allocation, reduces the AFP search
space, and may result in an allocation plan with many full collisions between PRACH RSI lists.
CandidatePrachRsiListsWithOverlap set to 0 may provide better allocation results when the number of cells to
allocate is less than the number of available resources.
10.1.9.29 Excluding DMRS Overhead from Cell Resources

DMRS are transmitted on antenna ports 7 and 8, or on 7 through 14. To take into account the DMRS overhead, add
[LTE]
ApplyDMRSOverhead = 1
ApplyDMRSOverhead is set to 0 by default.
10.1.9.30 Changing the Display Mode of the Number of Aggregated Servers

By default, the throughput coverage predictions display the effective numbers of aggregated servers per pixel using
the Discrete values display type. Using this display type, the resulting prediction plot only has one value available
per pixel. You can change the display mode to Value intervals, hence obtaining all possible numbers of aggregated
servers available per pixel, by adding the following lines to the Atoll.ini file:
[LTE]
NumberOfServerDisplay = 1
NumberOfServerDisplay is set to 0 by default.

10.1.9.31 Aggregating SCell Throughputs Even When No Service From PCell

If you want Atoll to aggregate throughputs from SCells, from which the radio signal quality is above the defined SCell
activation threshold, even when the radio signal quality from the PCell is below the minimum required for accessing
any bearer, add the following lines to the Atoll.ini file:
[LTE]
ThresholdForCAWithNoThroughputOnPcell = X
ThresholdForCAWithNoThroughputOnPcell is the threshold in dB above which the PCell is assumed to provide

service even when it is below the required threshold for any bearer. The default value of this threshold is very high,
which means that this calculation is not active by default. To activate this calculation mode, you must set X to a low
value.
10.1.9.32 Displaying the Statistics Tab of the AFP

If you want to view the allocation plan statistics in the AFP, add the following lines to the Atoll.ini file:
[OFDM_AFP]
DisplayStatisticsTab = 1
DisplayStatisticsTab is set to 0 by default, implying that the Statistics tab of the AFP is hidden by default.
10.1.9.33 Defining the Ratio of NPDCCH to NPDSCH

In NB-IoT interference calculations, the NPDCCH is considered to be transmitted on some subframes while
NPDSCH on other subframes. The default ratio of presence of the NPDCCH is set to 20 %, and hence that of the
NPDSCH to 80 %. You can change this ratio by adding the following lines to the Atoll.ini file:
[NB-IoT]
NPDCCHtoNPDSCHRatio = X
Where X can be a value from 0 to 100.
10.1.9.34 Blanking LTE PRBs for Inband NB-IoT

By default, for LTE cells located on the same site as their inband NB-IoT cells, the LTE PRBs other than the centre
six PRBs that overlap the NB-IoT channel are blanked in downlink and uplink to decrease interference from co-
located cells. You can disable LTE PRB blanking by adding the following lines to the Atoll.ini file:
[NB-IoT]
InbandMethod = 1
InbandMethod is set to 0 by default.
10.1.9.35 Limiting the Number of Co-Scheduled MU-MIMO Users

By default, any user-defined value can be entered for the numbers of co-scheduled MU-MIMO users per cell in the
downlink or uplink. This value is used as a cell capacity gain, or in other words, a multiplicative coefficient for the
peak RLC channel throughput. If you want to use the numbers of antennas defined for the transmitter as the limit of
this MU-MIMO gain, add the following lines to the Atoll.ini file:
[LTE]
LimitMuMimoGain = 1
LimitMuMimoGain, is set to 0 by default.

10.1.9.36 Defining the Table Row Height for the Display of the Angular Distribution of Interference
Diagrams
By default, Atoll draws the diagrams stored in the Angular Distributions of Interference (AAS) field of the Cells table
only if the row height is greater than 120 pixels. You can change this threshold by adding the following lines to the
Atoll.ini file:
[OFDM]
MinimumAASResultsCellSize = X
MinimumAASResultsCellSize is set to 120 by default.
10.1.10 3GPP Multi-RAT Options
10.1.10.1 BSIC, SC, and PCI Allocation with Inter-technology Neighbour Constraints
The automatic allocations of BSIC (using the GSM AFP), scrambling codes (in UMTS), and physical cell IDs (using
the LTE AFP) take inter-technology neighbour constraints into account. For example, different physical cell IDs are
assigned to two LTE cells that are neighbours of the same GSM transmitter or UMTS cell. If you wish to disable the
inter-technology neighbour constraints in the automatic allocations of BSIC, SC, and PCI, add the following lines to
the Atoll.ini file:
[MultiRAT]
AllCodesAllocWithInterRATNeighbours = 0
AllCodesAllocWithInterRATNeighbours is set to 1 by default.
10.1.10.2 Multi-RAT Technology Selection Default Behaviour

When users open a Multi-RAT Atoll document, the radio technology selection dialog box appears with all
technologies selected by default. In some cases, you might want to force users to explicitly select the technologies
on which they want to work by making the technologies appear as unselected by default.
If you want the radio technology selection dialog box to appear with no technologies selected by default, add the
[MultiRAT]
UncheckTechnoChoices = 1
UncheckTechnoChoices is set to 0 by default.
10.1.11 Microwave Radio Link Options
10.1.11.1 Modifying the Default Format of Link Names

By default, Atoll automatically generates link names by using the format "Site A name-Site B name". In some cases,
the site names might contain characters that are undesirable for a link name (for example, spaces or underscores).
To specify characters that are forbidden when generating the link name, add the following lines to the Atoll.ini file:
[MWLinks]
AutoNameForbiddenChars = list of forbidden characters surrounded by quotes

For example, if AutoNameForbiddenChars is set to "_ ", any new link will be named "SiteName123-SiteName345"
instead of "Site_Name 123-Site_Name 345".
AutoNameForbiddenChars is set to "" by default, meaning that no characters are forbidden.
10.1.11.2 Updating A>>B and B>>A Profiles in Real-time

In the MW Analysis window’s Profile view, when a change is made on the A>>B link, it is not automatically taken into
account in the B>>A direction in real time. This produces inconsistent results in the 2 directions. If you want to make
the profile update real-time in both directions, i.e., changes in one direction automatically updated in the other
direction, add the following lines to the Atoll.ini file:
[MWCalculations]
UpdateOppositeHop = 1
UpdateOppositeHop is set to 1 by default.
10.1.11.3 Disabling Shielding Factor on Wanted Signal at Receiver

If you want to disable the use of the shielding factor on the wanted signal at the receiver during interference
calculations, add the following lines to the Atoll.ini file:
[MWCalculations]
ShieldingFactorOnWantedSignal = 0
ShieldingFactorOnWantedSignal is set to 1 by default, which means that the shielding factor is taken into account
at the receiver when calculating interference. On the transmitter side, the shielding factor is always taken into
account when calculating interference.
10.1.11.4 Considering XPIF value in Interference for Dual-Polar Links

If you have dual-polar links (i.e., a link with 2+0 XPIC configuration and a co-channel allocation), you can consider
XPIF in interference calculation by adding the following lines to the Atoll.ini file:
[MWCalculations]
CCDP_XPIF = 1
CCDP_XPIF is set to 0 by default, which means that XPIF is considered in the decoupling calculation only. When the
option is set to 1, the XPIF value is considered in the decoupling and it is deducted from the interference level.
10.1.11.5 Making the ITU-R P.530-5 Method Available

The Rec. ITU-R P.530-5 method is hidden by default on the Models tab of the Microwave Radio Links Properties
dialog box. You can make this method available for availability and quality calculations by adding the following lines
[MWCalculations]
HIDE_REC530_5 = 0
HIDE_REC-5 is set to 1 by default. If the method was selected in a document saved in a previous Atoll version, it will
be available even if HIDE_REC-5 is set to 1 in the Atoll.ini file.

10.1.11.6 Applying Cross-Polar Discrimination Outage

The formulas that apply cross-polar discrimination (XPD) outage from section 4 of the IUT-R P.530 method only
apply to dual polarization (2+0) links. By default, cross-polar discrimination outage is applied only if, on the same
link, at least two cross-polarised channels are present, where the second channel is either co-channel or adjacent
to the first.
In previous versions of Atoll, XPD outage was applied to single polarization (1+0) and dual polarization (2+0) links.
If you need to ensure compatibility with results from previous versions of Atoll, add the following lines to the Atoll.ini
file:
[MWCalculations]
PXPBDOnDualOnly = 0
PXPBDOnDualOnly is set to 1 by default.
10.1.11.7 Using Old Min C/I Values

If you wish to use Min C/I values defined or calculated in old versions of Atoll, add the following lines to the Atoll.ini
file:
[Compatibility]
MWEquipment_CIMIN = 1
MWEquipment_CIMIN is set to 0 by default.
10.1.11.8 Solving Alignment Issue in Generated Reports

If you encounter an alignment issue in the Microwave report or in the Reflection Analysis report, you can solve it by
increasing the tab value. To do that, add the following lines to the Atoll.ini file:
[MWReport]
tab = 2000
tab is set to 500 by default.
10.1.11.9 Setting the Maximum Number of Modulations in Generated Reports

Microwave reports limit the number of displayed modulations for an equipment to 8 by default.
You can change this number by specifying a value between 1 and 15 in the Atoll.ini file:
[MWReport]
MaxNumberOfModulations = value
MaxNumberOfModulations is set to 8 by default.
10.1.11.10 Sorting Modulations by Rx Threshold

By default, modulations are listed by the number of modulation states. It is possible configure Atoll to sort
modulations by Rx Threshold in the power settings, design summary report, analysis report, custom reports, and
interference calculation parameters. To specify this behaviour, add the following lines to the Atoll.ini file:
[MWReport]
SortModulationByRxThreshold = 1

10.1.11.11 Defining Default Configuration Files for Link Budgets Reports

You can define a default configuration file for each link budget report by specifying an absolute or UNC path in the
Atoll.ini file:
[MWReport]
DesignSummaryCfg = path to the report’s default configuration file
LinkAnalysisCfg = path to the report’s default configuration file
LinkInterferenceCfg = path to the report’s default configuration file
RequiredMarginCfg = path to the report’s default configuration file
LinksBudgetCfg = path to the report’s default configuration file
LinksInterferenceCfg = path to the report’s default configuration file
MultihopAnalysisCfg = path to the report’s default configuration file
ReflectionAnalysisCfg = path to the report’s default configuration file
Where each of the above options corresponds to a specific Report Configuration dialog box:
◼ DesignSummaryCfg: corresponds to the Report Configuration dialog box displayed after clicking the
Configure Report button ( ) from the Design Summary view (MW Analysis window).
◼ LinkAnalysisCfg: corresponds to the Report Configuration dialog box displayed after clicking the Configure
Report button from the Analysis Report view (MW Analysis window).
◼ LinkInterferenceCfg: corresponds to the Report Configuration dialog box displayed after clicking the
Configure Report button from the Interference Report view (MW Analysis window).
◼ RequiredMarginCfg: corresponds to the Report Configuration dialog box displayed after clicking the
Configure Report button from the Required Margin view (MW Analysis window).
◼ LinksBudgetCfg: corresponds to the Report Configuration dialog box displayed after selecting Microwave
Radio Links > Links > Link Budgets > Configuration Report from the Network explorer.
◼ LinksInterferenceCfg: corresponds to the Report Configuration dialog box displayed after selecting
Microwave Radio Links > Links > Interference > Configuration Report from the Network explorer.
◼ MultihopAnalysisCfg: corresponds to the Report Configuration dialog box displayed after selecting
Microwave Radio Links > Multi-Hops > [Multi-Hop X] > Analysis from the Network explorer.
◼ ReflectionAnalysisCfg: corresponds to the Report Configuration dialog box displayed after:
◼ right-clicking in the Profile Analysis view (MW Analysis window) and selecting Reflection and Diversity
Analysis,
◼ then clicking the Configure Report button from the Analysis Report view (MW Reflection/Diversity
window).
10.1.11.12 Defining a Default Configuration File for the Channel Arrangement Display
You can define a default configuration file for the channel arrangement display by specifying an absolute or UNC
path in the Atoll.ini file:
[MWChannelArrangement]
DefaultConfiguration = path to the channel arrangement default configuration file
Where the above option corresponds to the Channel Arrangement dialog box displayed after selecting Microwave
Radio Links > Interference > Channel Arrangement > Display on Map from the Network explorer.
10.1.11.13 Defining a Default Template for Microwave Links Custom Reports

You can define a default template for microwave links custom reports by specifying an absolute or UNC path in the
Atoll.ini file:
[MWReport]

DefaultTemplate = path to the default template for microwave links custom reports
10.1.11.14 Considering ATPC for ANSI and ETSI Modes Similarly

ATPC is considered for all selected modulations with ANSI mode while it is only used for the highest modulation
with ETSI. To consider ATPC in ANSI mode as it is done for ETSI (i.e., to use ATPC for the highest modulation only),
[MWCalculations]
AtpcOnlyOnHighest = 1
AtpcOnlyOnHighest is set to 0 by default.
10.1.11.15 Hiding Clutter from the Profile Analysis View

Atoll displays the terrain height in the Profile view as well as clutter classes and clutter heights.
You can choose to display the clutter along the profile only if the visibility check box of the Clutter Classes and
Clutter Heights folders on the Geo tab is selected,
You can also choose to display the clutter in grey when the clutter is not taken into account in calculations.
To change the way clutter is displayed in the Profile view, you can enable the following option in the Atoll.ini file.
[MWProfile]
AlwaysDrawClutters = <setting>
where <setting> can be:

◼ 0: Clutter is drawn on the profile if the visibility check box is selected in the Geo explorer.
◼ 1: Clutter is always drawn on the profile, regardless of the visibility checkbox.
◼ 2: Clutter is always drawn on the profile, regardless of the visibility checkbox, but is displayed in grey (and
ignored in the calculations) if the Clutter taken into account option is disabled in the propagation model.
By default, AlwaysDrawClutters is set to 1.
10.1.11.16 Changing the Decoupling Calculation Method for Co-site Interference

Before Atoll 3.3.1, decoupling calculation in case of co-site interference was based on antenna patterns.
To switch back to this calculation method, add the following lines to the Atoll.ini file:
[MWCalculations]
NewDecouplingCoSite = 0
This option is set to 1 by default.
10.1.11.17 Calculating the Receiver Thermal Noise for the Radio Effective Bandwidth
The thermal noise is calculated for the channel bandwidth and the temperature defined in the Geoclimatic
parameters of the link. To consider the radio effective bandwidth instead of the channel bandwidth, add the
[MWCalculations]
UseFktb332 = 0

10.1.11.18 Confirming a Delete Action

You can configure Atoll to display a confirmation dialog box when you delete a microwave or non-microwave link.
To add the confirmation dialog box, add the following lines to the Atoll.ini file:
[MWLink]
AskConfirmDeleteLinkOrOTLink = 1
10.1.12 Measurement Options
10.1.12.1 Displaying Additional Information in Drive Test Data

It is possible to display the following additional information in the columns of serving and neighbour cells:
◼ BCCH - BSIC pair (GSM GPRS EDGE documents)
◼ Scrambling Code - Scrambling Code Group pair (UMTS HSPA documents)
◼ PN Offset - PN Offset Group pair (CDMA2000 1xRTT 1xEV-DO documents)
You have to add the following lines to the Atoll.ini file to display this information:
[TestMobileData]
ShowCoupleInfo = 1
Setting ShowCoupleInfo to 0 hides this information.
10.1.12.2 Setting the Number of Transmitters per Drive Test Data Path
By default, Atoll can import information about one serving transmitter (or cell in CDMA documents) and six
neighbour transmitters (or cells in CDMA documents) for drive test data paths. You can change the number of
transmitters per drive test data path by adding the following lines to the Atoll.ini file:
[TestMobileData]
NumberOfTestMobileTransmitters = X
Where X is the number of transmitters per drive test data path. The default value of
NumberOfTestMobileTransmitters is 7.
10.1.12.3 Recalculating Distances of Points From There Serving Cells at Import

If you want Atoll to calculate the distance of each measurement point from its nearest serving cell, you can add the
[TestMobileData]
RecalcDist = 1 or 0
The default value of RecalcDist is 1, which means that Atoll will calculate the distance for each measurement point.
The nearest serving cell is the one closest to the measurement point which has the same (Scrambling Code, SC
Group), (BSIC, BCCH), or (PN Offset, PN Offset Group) pair as the point.

10.1.12.4 Defining the BCCH and BSIC Columns for FMT Import
The .fmt files generated by the TEMS Investigation GSM tool contain a number of columns. To define which of these
columns should be imported as the BCCH column and which one as the BSIC column in Atoll, you can add the
[TestMobileDataImportFmt]
BCCHColumn = Column1
BSICColumn = Column2
Where, Column1 and Column2 are the titles of the two columns in the .fmt file corresponding to the BCCH and the
BSIC columns respectively.
10.1.12.5 Importing Drive Test Data with Scrambling Codes as Integers

You can force the conversion of scrambling codes to integer values when importing drive test data by adding the
following option in the Atoll.ini file:
[TestMobileData]
FloatingPointScramblingCodeSupport = 1
FloatingPointScramblingCodeSupport is set to 0 by default, and the scrambling codes are imported according to the
numeric data type selected for the scrambling code column in the import dialog box.
10.1.12.6 Importing Drive Test Data for Active and Filtered Transmitters Only
When you import drive test data in Atoll, it assigns servers and neighbours to each measurement point based on the
cell identification method defined for the import. By default, Atoll takes all the transmitters and cells of the
document into account, whether they are active or inactive and filtered or not. If you want Atoll to take only active
and filtered transmitters and cells into account for drive test data import, add the following option in the Atoll.ini file:
[TestMobileData]
ImportForFilteredTransmittersOnly = 1
ImportForFilteredTransmittersOnly is set to 0 by default.
10.1.12.7 Specifying the Location of the ACP.ini File

For the most part, you can configure the ACP with its own initialisation file: the ACP.ini. However, there are a few
options that you can set in the Atoll.ini to configure the ACP.
By default, Atoll ACP uses the global ACP.ini file, located in the installation directory of Atoll. You can set an option
in the Atoll.ini file to define a different location for the ACP.ini file. This option is useful for assigning a different ACP
initialisation for a different group of users.
To use another location, add the following line to the Atoll.ini file:
[ACP]
iniFile = path_to_ACP.ini
10.2 ACP Initialisation File

The ACP initialisation file is used to inform Atoll of the preferred settings when the ACP is used for automatic cell
planning during Atoll sessions. It can be used to adjust the behaviour of the ACP.

You can comment out any option in the ACP.ini by preceding the line with a semi-colon (";") or a hashtag ("#").
 The ACP initialisation file is a powerful tool. You should not modify any option in the
ACP.ini file until and unless you are absolutely sure of what you are doing.
In order for the ACP initialisation file to be used by Atoll, you should place the ACP.ini file in the Atoll installation
directory.
You can define a different location for the ACP.ini file as shown in "Specifying the Location of the ACP.ini File" on
page 224.
10.2.1 Managing ACP Preferences
Some of the settings provided in the ACP.ini file can be modified directly using the ACP - Automatic Cell Planning
Properties dialog box, under ACP Automatic Cell Planning on the Setup Template tab. ACP either embeds these
settings directly in the ATL document or in a user-defined ACP.ini file. These settings are referred as "local settings".
Local settings are the settings found in sections using the "Tpl" keyword, such as [ACPTplGeneralPage].
The local settings, defined using the ACP - Automatic Cell Planning

◼
Properties dialog box, take precedence over the same settings defined in the
global ACP.ini file. The settings in the ACP.ini file are read when you start a
new project to initialise the settings of the ACP.
◼ When using the ACP.ini file to define options, instead of using the ACP -
Automatic Cell Planning Properties dialog box, you can also define any other
settings even if they can not be set using the ACP - Automatic Cell Planning
Properties dialog box. These settings redefined locally have precedence over
the global settings.
10.2.2 ACP GUI Options
In this section are the settings defining default values and certain aspects of the GUI configuration. These settings
are local and are usually defined using Setup Template tab of the ACP - Automatic Cell Planning Properties dialog
box, and stored either in the Atoll project or a local ACP.ini file.
10.2.2.1 Default Settings of the Optimisation Tab

The following options can be used to set default settings for the number of iterations and the resolution:
[ACPTplGeneralPage]
nbIteration = 100
resolution = 50
10.2.2.2 Default Settings of the Optimisation > Cost Control Tab

The following options can be used to define the default settings for the calculation of costs:
[ACPTplGeneralPage]
cost.type = 0|1|2
# 0=off, 1=limt to max, 2=apply cost to change plan
cost.unit = unit
# unit = $, yen, etc. (less than 4 characters recommended)

cost.tradeoffLevel = 0|1|2
# 0=low, 1 = normal, 2=strong
cost.maxCost = 50
cost.azimuth.cost = 1
cost.azimuth.isSiteVisit=true
cost.tilt.cost = 1
cost.tilt.isSiteVisit=true
cost.antenna.cost = 1
cost.antenna.isSiteVisit=true
cost.etilt.cost = 0.1
cost.etilt.isSiteVisit=false
cost.height.cost = 1
cost.height.isSiteVisit=true
cost.power.cost = 0.1
cost.power.isSiteVisit=false
cost.siteVisitCost = 2
cost.upgradeSiteCost = 5
cost.newSiteCost = 10
cost.removeSiteCost = -5
10.2.2.3 Default Settings of the Optimisation > Advanced Cost Control Tab
The following options can be used to define the default settings for advanced cost control. Advanced cost control
options allow you to define the maximum number of changes to be made (either as a value or a ratio) and to change
the ranking of the order of cost in the final implementation plan.
The option below allows you to display the Advanced label under Cost Control in the left-hand pane of the
Optimisation tab. It is set to 0 by default.
[ACPGeneralPage]
enableAdvancedCost = 1
The following option enables you to define the importance of cost in the implementation plan. It is set to 1 by
default.
[ACPTplGeneralPage]
cost.planCostWeighting = 0|1|2
#0=low, 1=medium (default), 2=high
The following option enables you to specify the number of changes in the implementation plan. It is set to 0 by
default.
[ACPTplGeneralPage]
cost.planLimitType = 0|1|2
#0=unlimited, 1=max as absolute value, 2=max as ratio
◼ 0: the number of changes is unlimited.

◼ 1: use cost.planChangeMax to define the max. number of changes in the implementation plan as an absolute
value:
cost.planChangeMax = 10
◼ 2: use cost.planChangePercent to define the max. number of changes in the implementation plan as a ratio of
the number of antennas currently available in the computation zone:
cost.planChangePercent = 20

When cost.planLimitType is set to 2, you can also set cost.planChangeRefZone to 1 in the [ACPGeneralPage]
section to define the focus zone as the reference zone instead of the computation zone:
cost.planChangeRefZone = 0|1
#0=computation zone (default), 1=focus zone
10.2.2.4 Automatically Creating Custom Zones on the Optimisation Tab

In the [ACPTplGeneralPage] section, you can find the options used to automatically create custom zones that will
appear on the Optimisation tab when you create a new ACP setup.
The following option can be used to automatically create ACP custom zones from the hotspots in the Atoll project:
[ACPGeneralPage]
zone.autobuildHotspot = 1
# Automatically build hotspot from Atoll hotspot (default)
The following options can be used to automatically create ACP custom zones from one or more clutter classes or
from a SHP file:
[ACPGeneralPage]
zone.count = 2
# Number of zones to be created.
zone.0.name = MyClutterZone1
# Name of the zone (in this case from clutter)
zone.0.clutters = 10,11,12
# Clutter classes that will constitute this zone
zone.1.name = MyVectorZone2
# Name of the zone (in this case from SHP)
zone.1.file=c:\path\to\file.shp
# Absolute path to the SHP file.
10.2.2.5 Default Settings of the Objectives Tab

In the [ACPTplObjectivePage] section are the settings defining default settings of the Objectives tab.
The following option can be used to specify the location of the traffic file which will be used as a weighting map for
each objective:
[ACPTplObjectivePage]
traffic.global.file = "C:\tmp\traffic.bil"
The following option can be used to define the default extraction resolution of the traffic map (in metres). It is set
to 50 by default.
traffic.global.resolution = value
The following options can be used to define the default values for the technology quality indicators (UMTS Ec/Io,
UMTS RSCP, UMTS overlap, GSM signal level, GSM overlap, WiMAX CINR, WiMAX C/N, LTE C/N, etc.):
param.gsm.overlap.autoPrediction = yes
param.gsm.overlap.margin = 5
param.gsm.overlap.minRxLevel = 0
# 0=use defined TRG threshold, other=defined value
param.gsm.bcch.autoPrediction = yes
param.gsm.bcch.isShadowing = no
param.gsm.bcch.cellEdgeCov = 0.75

param.umts.overlap.autoPrediction = yes
param.umts.overlap.margin = 10
param.umts.overlap.minRxLevel = -120
param.umts.rscp.autoPrediction = yes
param.umts.rscp.isShadowing = no
param.umts.rscp.cellEdgeCov = 0.75
param.umts.ecio.autoPrediction = yes
param.umts.ecio.isShadowing = no
param.umts.ecio.cellEdgeCov = 0.75
param.cdma.overlap.autoPrediction = yes
param.cdma.overlap.margin = 10
param.cdma.overlap.minRxLevel = -120
param.cdma.coverage.autoPrediction = yes
param.cdma.coverage.isShadowing = no
param.cdma.coverage.cellEdgeCov = 0.75
param.cdma.ecio.autoPrediction = yes
param.cdma.ecio.isShadowing = no
param.cdma.ecio.cellEdgeCov = 0.75
param.lte.overlap.autoPrediction = yes
param.lte.overlap.margin = 5
param.lte.overlap.minRxLevel = -105
param.lte.coverage.autoPrediction = yes
param.lte.coverage.isShadowing = no
param.lte.coverage.cellEdgeCov = 0.75
param.lte.cinr.autoPrediction = yes
param.lte.cinr.isShadowing = no
param.lte.cinr.cellEdgeCov = 0.75
param.lte.cinr.useICIC = 1
param.wimax.overlap.autoPrediction = yes
param.wimax.overlap.margin = 5
param.wimax.overlap.minRxLevel = -105
param.wimax.coverage.autoPrediction = yes
param.wimax.coverage.isShadowing = no
param.wimax.coverage.cellEdgeCov = 0.75
param.wimax.cinr.autoPrediction = yes
param.wimax.cinr.isShadowing = no
param.wimax.cinr.cellEdgeCov = 0.75
param.wimax.cinr.useSegmentation = 1
param.wifi.overlap.autoPrediction = yes
param.wifi.overlap.margin = 5
param.wifi.overlap.minRxLevel = -105
param.wifi.coverage.autoPrediction = yes
param.wifi.coverage.isShadowing = no
param.wifi.coverage.cellEdgeCov = 0.75
param.wifi.cinr.autoPrediction = yes
param.wifi.cinr.isShadowing = no
param.wifi.cinr.cellEdgeCov = 0.75
The following options can be used to define the default threshold for each objective rule:
quality.gsm.bcch.threshold = -85
quality.gsm.overlap.threshold = 4
quality.gsm.distance.threshold = 5000
quality.umts.rscp.threshold = -85
quality.umts.ecio.threshold = -13
quality.umts.overlap.threshold = 4
quality.umts.distance.threshold = 5000
quality.cdma.rscp.threshold = -85
quality.cdma.ecio.threshold = -13
quality.cdma.overlap.threshold = 4
quality.cdma.distance.threshold = 5000

quality.lte.coverage.threshold = -85
quality.lte.c.threshold = -85
quality.lte.cn.threshold = 20
quality.lte.rsrp.threshold = -105
quality.lte.cinr.threshold = 10
quality.lte.rsrq.threshold = -12
quality.lte.rssi.threshold = -80
quality.lte.overlap.threshold = 5
quality.lte.distance.threshold = 5000
quality.wimax.coverage.threshold = -85
quality.wimax.c.threshold = -85
quality.wimax.cn.threshold = 20
quality.wimax.cinr.threshold = 10
quality.wimax.overlap.threshold = 5
quality.wimax.distance.threshold = 5000
quality.wifi.coverage.threshold = -85
quality.wifi.c.threshold = -85
quality.wifi.cn.threshold = 20
quality.wifi.cinr.threshold = 10
quality.wifi.overlap.threshold = 5
quality.wifi.distance.threshold = 5000
quality.lpwa.coverage.threshold = -130
quality.lpwa.redserver.threshold = 3
The following option can be used to define a default number of servers for the 1st-Nth objective. It is set to 4 by
default.
NbServers1stNth = value
The following option can be used to remove the Capacity and Load Balancing features from the Objectives tab.
[ACPCapacityPage]
enable = 0
The following option can be used to clear the Scale Traffic according to Zone Weighting check box on the Capacity
page:
[ACPCapacityPage]
useZoneWeight = 0
The following options can be used to define a capacity traffic map, either by a BIL file or by a comma-separated list
of traffic map names:
[ACPTplCapacityPage]
traffic.file = c:\tmp\traffic.bil
traffic.maps = user_density_traffic_map; environment_map
traffic.resolution = 50
The following option can be used to avoid recalculating capacity traffic maps after each new run:
calculationcapacitytrafficmap = 1
The following option can be used to force ACP to show load balancing and traffic capture results when either feature
is enabled:
show.loadbalancingandthroughput = 1

The following options can be used to define the default threshold for each quality (Objectives tab > Capacity page
> Services Definition frame):
The following options can be used to define the default quality used by each technology for traffic capture condition:
quality.gsm.bcch.threshold = -85
quality.umts.rscp.threshold = -85
quality.umts.ecio.threshold = -13
quality.cdma.rscp.threshold = -85
quality.cdma.ecio.threshold = -13
quality.wimax.coverage.threshold = -85
quality.wimax.c.threshold = -85
quality.wimax.cn.threshold = 20
quality.wimax.cinr.threshold=10
quality.lte.coverage.threshold = -85
quality.lte.c.threshold = -85
quality.lte.cn.threshold = 20
quality.lte.rsrp.threshold = -105
quality.lte.cinr.threshold=10
quality.lte.rsrq.threshold = -12
quality.lte.rssi.threshold = -80
service.gsm.condition.quality=bcch
service.umts.condition.quality=rscp
service.cdma.condition.quality=coverage
service.wimax.condition.quality=coverage
service.lte.condition.quality=coverage
service.factor=1.0
service.density = 30
The following option can be used to enable the load balancing feature by default:
loadBalancing.enable = 1
Note that the Load Balancing feature is not available on the Objectives tab if CDMA2000 transmitters are detected.
The following options can be used to specify the load balancing default target coverage (%) and the load balancing
weight:
loadBalancing.target = 80
loadBalancing.weight = 1
10.2.2.6 Default Settings of the Reconfiguration Tab

In the [ACPTplReconfPage] section are the settings defining the default values of the Reconfiguration tab.
 The options in this section do not select the default reconfiguration options when
set to "1", instead they disable those reconfiguration options.
By default, all the zones listed under Zone Parameters on the Optimisation > Zones tab appear in the drop-down list
next to Display on on the Reconfiguration tab (except the KPI zones and lines). You can force ACP to list only the
main zones ("Computation", "Focus", "All") in both drop-down lists by adding the following lines to the ACP.ini file:
[ACPReconfPage]

filter.onlyMainZones = 1
filter.onlyMainZones is set to 0 by default.

The following options can be used to define the default settings for the reconfiguration of power on the Cells vertical
tab:
[ACPTplReconfPage]
umts.disablePilotPowerOptimisation = 1
umts.disableMaxPowerOptimisation = 1
umts.SyncMultiCellPower = 1
umts.SyncSiteMultiCellPower = 1
# lock UMTS cell power optimisation for co-site cells
umts.defaultPowerAutoMinMax = 3
# automatically set min/max power at an offset of 3dBm around actual value.
# If 0, use fixed value 37-46
cdma.1xrtt.SyncMultiCellPower = 1
cdma.1xrtt.SyncSiteMultiCellPower = 0
cdma.1xrtt.disablePilotPowerOptimisation = 1
cdma.1xrtt.disableMaxPowerOptimisation = 1
cdma.1xevdo.SyncMultiCellPower = 1
cdma.1xevdo.SyncSiteMultiCellPower = 0
cdma.1xevdo.disableMaxPowerOptimisation = 1
cdma.defaultPowerAutoMinMax = 3
gsm.disablePowerOptimisation = 1
gsm.defaultPowerAutoMinMax = 3
wimax.disablePreamblePowerOptimisation=1
wimax.SyncMultiCellPower = 1
wimax.SyncSiteMultiCellPower = 1
# lock WiMAX cell power optimisation for co-site cells
wimax.defaultPowerAutoMinMax = 3
lte.disablePowerOptimisation = 1
lte.SyncMultiCellPower = 1
lte.SyncSiteMultiCellPower = 1
# lock LTE cell power optimisation for co-site cells
lte.defaultPowerAutoMinMax = 3
nbiot.disablePowerOptimisation=1
nbiot.SyncMultiCellPower=1
nbiot.SyncSiteMultiCellPower=0
# lock NB-IoT cell power optimisation for co-site cells
nbiot.defaultPowerAutoMinMax=3
The following options can be used to define the default settings for the reconfiguration of transmitters and sites:
[ACPTplReconfPage]
disableAntennaOptimisation = 1
disableAzimuthOptimisation = 1
disableHeightOptimisation = 1
disableETiltOptimisation = 1
disableMechTiltOptimisation = 1
disableSiteSelection = 1
disableRepGainOptimisation = 1

disableCandidateSelection = 1
The following options can be used to define default settings for reconfiguration ranges:
[ACPTplReconfPage]
defaultTxAzimuthVariation = 20
defaultTxAzimuthStep = 5
defaultTxAzimuthMinInterSector = 0
defaultTxTiltMin = 0
defaultTxTiltMax = 5
defaultTxTiltStep = 1
defaultTxETiltMin = 0
defaultTxETiltMax = 10
defaultTxHeightMin = 0
defaultTxHeightMax = 10
defaultTxHeightStep = 5
defaultTxHeightMin.feet = 0
defaultTxHeightMax.feet = 30
defaultTxHeightStep.feet = 15
umts.disablePilotPowerOptimisation = 0
umts.disableMaxPowerOptimisation = 0
The following options can be used to define a default range for the optimisation of repeater gains:
[ACPTplReconfPage]
defaultRepGainMin = -1
# if -1, the default equipment min value is used
defaultRepGainMax = -1
# if -1, the default equipment max value is used
defaultRepGainStep = 3
# default = 3
The following option can be used to hide the No. Remotes column on the Reconfiguration > Transmitters vertical
tab:
[ACPReconfPage]
showNbRemotes = 0
#default = 1 to display the No. Remotes column
The following option can be used to display on the Reconfiguration > Transmitters vertical tab the additional
constraint applied to electrical tilt changes.
[ACPReconfPage]
tx.etilt.deltaLimitConstraint.show = 1
#default = 0
When tx.etilt.deltaLimitConstraint.show = 1, the Variation + column appears under Electrical Tilt (deg). You can
enter a value next to the Variation + header or add the following lines to ACP.ini to define a default value:
[ACPTplReconfPage]
etilt.deltaLimitConstraint = 1,2,...
#default = 0
◼ If etilt.deltaLimitConstraint = 0, the variation constraint is disabled and the Variation + column is greyed.
◼ If etilt.deltaLimitConstraint = 1,2,..., the constraint is enabled and the following appears under Variation +:
◼ A check box which must be selected in order for the constraint to be considered.

◼ A range determined by the value under Current and the value indicated next to the Variation + header.
The Variation + constraint determines one range and the specified Min. and Max. limits determine another
range. The final electrical tilt will fall within the intersection of the two ranges.
You can use the following option to disable proposals for electrical tilt changes below a defined relative
variation.
E.g. to disable electrical tilt change proposals for relative variations of 1 degree, you should set this option to 2.
[ACPTplReconfPage]
etilt.relative.min.variation = 2
#default = 1
constraint applied to mechanical tilt changes.
[ACPReconfPage]
tx.tilt.deltaLimitConstraint.show = 1
#default = 0
When tx.tilt.deltaLimitConstraint.show = 1, the Variation + column appears under Mechanical Tilt (deg).
You can enter a value next to the Variation + header or add the following lines to ACP.ini to define a default value:
[ACPTplReconfPage]
tilt.deltaLimitConstraint = 1,2,...
#default = 0
◼ If tilt.deltaLimitConstraint = 0, the variation constraint is disabled and the Variation + column is greyed.
◼ If tilt.deltaLimitConstraint = 1,2,..., the constraint is enabled and the following appears under Variation +:
◼ A range determined by the value under Current and the value indicated next to the Variation + header.
range. The final mechanical tilt will fall within the intersection of the two ranges.
You can use the following option to disable proposals for mechanical tilt changes below a defined relative
variation. E.g. to disable mechanical tilt change proposals for relative variations of 1 degree, you should set
this option to 2.
[ACPTplReconfPage]
tilt.relative.min.variation = 2
#default = 1
constraint applied to global tilt changes (electrical + mechanical).
[ACPReconfPage]
tx.etilt.tilt.sum.deltaLimitConstraint.show = 1
#(Default = 0)
When tx.etilt.tilt.sum.deltaLimitConstraint.show=1, ETilt + MTilt (deg) appears with Current and Variation +
columns.
You can enter a value next to the Variation + header or add the following lines to ACP.ini to define a default value:
[ACPTplReconfPage]
etilt.tilt.sum.deltaLimitConstraint = 1|2|...
#(Default = 0)
◼ If etilt.tilt.sum.deltaLimitConstraint = 0, the variation constraint is disabled and the Variation + column is

greyed.
◼ If etilt.tilt.sum.deltaLimitConstraint = 1,2,etc., the constraint is enabled and this appears under Variation +:

◼ A range determined by the value under Current (sum of the values under Current for electrical and
mechanical tilts) and the value indicated next to the Variation + header.
range. The final gloabl tilt will fall within the intersection of the two ranges.
The final mechanical tilt will fall within the intersection of the two ranges.
The following option allows you to reconfigure inter-sector electrical tilts as asymetrics, i.e. it allows you to obtain
different tilts for sectors belonging to the same site. The value you specify (in degree) is a "minimum difference"
constraint if tilts are reconfigured. If they are not reconfigured, the constraint will not apply.
[ACPTplReconfPage]
etilt.asymetric = 1
#(No default)
The following option can be used to automatically disable reconfiguration of all donors (possibly in cascade) of a
repeater:
[ACPTplReconfPage]
autoLockDonor = 0
#(Default = 0)
Possible settings:
Value Description
0 No auto lock (default).
1 The Use check boxes for transmitter reconfiguration parameters are cleared (antenna, tilt, azimuth, and
height). Only the last repeater in a series of cascading repeaters is optimised; the rest are cleared by
default (but can be selected manually).
2 The Use check boxes for all reconfiguration parameters are cleared (antenna, tilt, azimuth, height, and
power). Only the last repeater in a series of cascading repeaters is optimised; the rest are cleared by
default (but can be selected manually).
5 Same as 1, except that the Use check boxes can not be selected in the user interface.
6 Same as 2, except that the Use check boxes can not be selected in the user interface.
10.2.2.7 Default Settings of the Reconfiguration > Sites vertical tab

In the [ACPTplReconfPage] section are the settings defining the default settings of the Reconfiguration> Sites
vertical tab.
The following options enable you to define the reconfiguration options that are selected by default: site removeable,
sector removeable, antenna azimuth, and/or height. The settings of defaultSiteCellsRemoveable,
defaultSiteRemoveable, and defaultSiteHeightLocked also define the default settings in the Station Template
Reconfiguration dialog box.
When these options are set to 1, the corresponding reconfiguration options in the user interface are selected by
default.
[ACPTplReconfPage]
defaultSiteCellsRemoveable = 1
defaultSiteRemoveable = 1
defaultSiteAzimuthLocked = 1
#Lock Sector/Azimuth
defaultSiteHeightLocked = 1
#Lock Sector/Height
defaultSiteReconfigurationLocked = 1
 The defaultSiteHeightLocked option is forced to 0 for sites that have antennas at

different heights.

10.2.2.8 Defining the Inter-site Distance in Co-located Site Detection

The following option can be used to define the inter-site distance within which sites will be retained in co-located
site detection.
[ACPTplReconfPage]
site.min.distance.colocated = 2
#default setting in metres
10.2.2.9 Defining the Inter-antenna Distance in Co-located Transmitter Detection

The following option can be used to define the inter-antenna distance within which transmitters will be retained in
co-located transmitter detection.
[ACPTplReconfPage]
tx.min.distance.colocated = 1
#default setting in metres
10.2.2.10 Custom Columns on Reconfiguration > Sites Vertical Tab

The following options can be used to define the number of custom columns to display on the Reconfiguration >
Sites vertical tab:
[ACPReconfPage]
site.custom.count=x
site.custom.0.type=tabularDataColumn
site.custom.0.column=FOO
Where ’tabularDataColumn’ displays data issued from Atoll’s SITES table and identified by site.custom.0.column
(column name). Atoll column names are case sensitive.
The option below defines an optional label for a given column. If unset, the Atoll column name is used (e.g. FOO):
[ACPReconfPage]
site.custom.0.label=The Foo Label
10.2.2.11 Default Settings of the Reconfiguration > Transmitters Vertical Tab

In the [ACPReconfPage] section are the settings defining default settings for the display of mechanical and
electrical tilts, and for the display of linked transmitters.
The following options can be used to display the mechanical and electrical tilts as relative values instead of absolute
values. As a result, the Min. and Max. columns will be renamed to Min. Offset. and Max. Offset.
[ACPReconfPage]
tx.tilt.asRelative = 1 (default = 0)
tx.etilt.asRelative = 1 (default = 0)
The following option can be used to display the minimum and maximum electrical tilts only once for each group of
linked transmitters, when the Advanced mode is selected for display.
[ACPReconfPage]
tx.etilt.groupMinMax = 1 (default = 1)
When tx.etilt.groupMinMax is set to 0, the min/max electrical tilts are displayed for each transmitter.

10.2.2.12 Custom Columns on the Reconfiguration > Transmitters/Remotes Vertical Tabs

You can use this option to define the number of custom columns to display on the Reconfiguration > Transmitters
vertical tab and the Reconfiguration > Remotes vertical tab:
[ACPReconfPage]
tx.custom.count = 2
You can then set the following options to specify the data you want to show under each custom column.
tx.custom.0.type=tabularDataColumn
tx.custom.0.column=FOO
tx.custom.0.label=The FOO label
tx.custom.1.type=elevation
#site altitude + transmitter height
tx.custom.1.type=bandwidth
#cell bandwidth (only for LTE, WiMAX, and Wi-Fi)
 tabularDataColumn shows data issued from Atoll TRANSMITTERS table, identified

by the required tx.custom.x.column setting.
Atoll column names are case sensitive.
10.2.2.13 Default Settings of the Optimisation > EMF Exposure Tab

In the [ACPTplEMFPage] section are the settings defining default settings of the Optimisation > EMF Exposure tab.
The following option can be used to enable the EMF exposure module:
[ACPTplEMFPage]
enable = 1
The following option enables you to define the level of importance accorded to the optimisation of EMF exposure.
[ACPTplEMFPage]
weightLevel = 1
#(normal, default)
Possible values:
Value Description
0 Low: EMF exposure is optimised only if does not worsen coverage quality.
1 Normal: There is a trade-off between EMF exposure and coverage quality (default).
2 Critical: EMF exposure is optimised independently from the effect it may have on coverage quality.
The following options enable you to define the default resolution in metres in the X, Y, and Z planes:
[ACPTplEMFPage]
resolutionXY = 5
resolutionZ = 3
The following options define how EMF exposure will be measured in buildings: only on the facade or inside the
building as well:
[ACPTplEMFPage]
onlyFacade=1
#only on facade in building propagation classes. Default = 1 (yes)

buildingDeeping=10
#if onlyFacade is set to 0, the depth in the building measured.
The following option defines whether clutter classes and clutter heights are used to create a 3D representation of
the terrain or whether just vectors are to be used. The default is 1 (yes), but, given that vectors are always given
priority where they exist, this option can be disabled if vectors are available for the entire area of interest.
[ACPTplEMFPage]
useDhmFromClutter=1
# Default is 1 (yes)
The following option defines whether the 3D propagation model is using diffraction. When it is not, only positions
with a direct LOS to transmitters will register EMF exposure.
[ACPTplEMFPage]
useDiffraction = 0
The following option defines whether the EMF module should use transparent mode. When transparent mode is
used, no obstacle or indoor loss is accounted for.
[ACPTplEMFPage]
isWorstCase = 0
# Default is 0 (no)
The following option defines the calculation radius (in metres) around transmitters when calculating EMF exposure:
[ACPTplEMFPage]
calculationRadius = 300
The following options define the default threshold and weight for the EMF exposure objective:
[ACPTplEMFPage]
defaultObjThreshold = 0.6
defaultObjWeight = 1
The following options enable you to define up to 16 propagation classes for EMF exposure. Each class is defined
by a name, an indoor loss, and whether it can be edited by the user.
[ACPTplEMFPage]
eclass.count = 2
# Total number of propagation classes defined.
eclass.0.name=Open
eclass.0.position = 0
# Distribution of measurement points:
# 0 = 3D, i.e., distribution at all heights over area, 1 = 2D on top, 2 = 2D on bottom
eclass.0.buildingLos = 0
eclass.0.linearBuildingLos = 0
eclass.0.linearBuildingStart = 0
eclass.0.editionFlag = 0
# 0 can not be edited by user
The following options enable you to map clutter classes to propagation classes. Each mapping is defined on two
lines: the first line defines the clutter class (by its code from the Description tab of the Clutter Classes Properties
dialog box); the second line defines the propagation class (by its ID under Propagation on the Optimisation tab of
the ACP Setup dialog box). The default propagation classes in the ACP are "Open" (ID "0"), "Vegetation" (ID "1"), and
"Building" (ID "2"). Any additional propagation classes will have an ID assigned when they are created.
[ACPTplEMFPage]
clutterMapping.count = 3

clutterMapping.0.clutterCode = 10
clutterMapping.0.classCode = 0
In the [ACPEMFPage] section, you can specify whether or not users can define new propagation classes:
[ACPEMFPage]
isPropClassesExtendable = 1
# 1 enables user to create propagation classes.
10.2.2.14 Default Settings of the Optimisation > Multi-Storey Tab

In the [ACPTplMultistoreyPage] section are the settings defining default settings of the Optimisation > Multi-Storey
tab.
The following option can be used to enable the Multi-Storey module:
[ACPTplMultistoreyPage]
enable = 1
#default = 0
The following option can be used to define the minimum number of storeys for a building to be considered by the
Multi-Storey module. This is the value displayed next to Ignore buldings smaller than (storeys) on the Optimisation
> Multi-Storey tab.
minHeight = value
#default = 3
The following option can be used to define the vertical calculation step in the number of storeys. This is the value
displayed next to Calculation step (storeys) on the Optimisation > Multi-Storey tab.
resStorey = value
#default = 3
The following options can be used to define the default storey height in metres (or in feet when Atoll is configured
to use feet) displayed next to Storey height on the Optimisation > Multi-Storey tab.
storeyHeight = value
#default = 3
storeyHeight.feet = value
#default=10
The following option can be used to define the traffic weighting method for pixels in storeys, i.e. weight inside
buildings Vs. weight outside buildings (when value = 1, the total weight for all indoor pixels is equal to the weight of
an outdoor pixel). The defined weighting method will only be considered when the Vertical weight sharing check
box is selected.
weightShareMode = value
#default=1

The following option can be used to specify the maximum number of storeys for a building to be considered by the
Multi-storey calculation. This is the value displayed next to Maximum number of storeys on the Optimisation >
Multi-Storey tab.
MaxStoreyNb = value
#default=10
10.2.2.15 Controlling Antenna Pattern Smoothing

Crosswave version 4.0.4 has introduced the AntennaLossesThreshold option to control the smoothing performed
on antenna patterns in gain calculations. A similar option has been introduced in ACP for compliance with
Crosswave results. When AntennaLossesThreshold is specified in the Crosswave.ini file, the following lines must
be included in ACP.ini:
[ACPGenericPM]
cw.antennaLossesThreshold = X
where X is a value between 0 and 500 specified by AntennaLossesThreshold in Crosswave.ini to increase the
specific threshold applied by Crosswave.
10.2.2.16 Default Settings of the Antenna Tab
10.2.2.16.1 Global Antenna Tab

The following options enable you to define default regex patterns that will be used to automatically create physical
antennas (from antenna patterns), merge physical antennas, and create antenna groups (from physical antennas).
[ACPAntennaPage]
autoGroupPattern=(.*)
#for example (.*18deg) or (.+18deg)
autoGroupPattern_ant=(.*)
autoGroupPattern_group=(.*)
When the following option is set to 1 (default), ACP applies the default antenna configuration automatically (i.e. the
last configuration backed up as default) each time a new setup is created:
[ACPTplAntennaPage]
autoRestoreDefaultConfig = 1
10.2.2.16.2 Patterns Vertical Tab

Electrical Tilt Constraints
You can add the following lines to the ACP.ini file to enable the management of electrical tilt constraints on antenna
patterns; additional columns appear under Electrical Tilt Constraint (°). When the Use check box is selected, an
electrical constraint will be applied to the corresponding antenna pattern.
[ACPAntennaPage]
enableETilt = 1
# (default = 0)
You can also use the option below to enable management of AEDT (additional electrical downtilt); an additional Use
AEDT column appears. When a check box is selected under this column, an AEDT constraint will be applied to the
corresponding antenna pattern.

[ACPAntennaPage]
enableAedt = 1
When enableETilt and/or enableAEDT is set to 1, you can modify the Min and Max values that appear under
Electrical Tilt Constraint (°).
[ACPTplAntennaPage]
defaultETiltMin = 0
#default = 0
defaultETiltMax = 10
#default = 10
You can use the following option if you want to use a regular expression to define a set of antenna patterns on which
electrical tilt constraints will be used automatically. As a result, the Use check box will be selected under Electrical
Tilt Constraint (°) and the defined electrical tilt constraints will appear under Min and Max.
[ACPTplAntennaPage]
autoUseEtiltFromRegex=(.*)
Conversely, you can use the autoDisableEtiltFromRegex option if you want to use a regular expression to define a
set of antenna patterns on which electrical tilt constraints will be disabled automatically. As a result, the Use check
box is cleared under Electrical Tilt Constraint (°) and a dash appears under Min and Max..
[ACPTplAntennaPage]
autoDisableEtiltFromRegex=(.*)
Mechanical Tilt Constraints

You can add the following lines to the ACP.ini file to enable the management of mechanical tilt constraints on
antenna patterns; additional columns appear under Mechanical Tilt Constraint (°). When the Use check box is
selected, a mechanical constraint will be applied to the corresponding antenna pattern.
[ACPAntennaPage]
enableMTilt = 1
#default = 0
When enableMTilt is set to 1, you can modify the Min and Max values that appear under Mechanical Tilt Constraint
(°).
[ACPTplAntennaPage]
defaultTiltMin = 0
#default = 0
defaultTiltMax = 5
#default = 5
You can use the following option if you want to use a regular expression to define a set of antenna patterns on which
mechanical tilt constraints will be used automatically. As a result, the Use check box will be selected under
Mechanical Tilt Constraint (°) and the defined mechanical tilt constraints appear under Min and Max.
[ACPTplAntennaPage]
autoUseTiltFromRegex=(.*)
Conversely, you can use the autoDisableTiltFromRegex option if you want to use a regular expression to define a
set of antenna patterns on which mechanical tilt constraints will be disabled automatically. As a result, the Use
check box is cleared under Mechanical Tilt Constraint (°) and a dash appears under Min and Max.
[ACPTplAntennaPage]
autoDisableTiltFromRegex=(.*)

For physical antennas containing several antenna patterns with different electrical tilts, if you set the following
option the Use check box will be selected under Mechanical Tilt Constraint (deg) and a dash appears under Min and
Max.
[ACPTplAntennaPage]
autoDisableTiltOnMultiPattern = 1
#default = 0
10.2.2.16.3 Physical Antenna Vertical Tab

By setting the following option, you can control the internal logic that ACP uses to assign different antenna patterns
to different frequency bands. ACP considers that an antenna pattern is allowed for a given frequency band if its base
frequency is within the allowed range.
[ACPAntennaPage]
freqBandRange = 49
#default = 49 (MHz)
You can also add the following lines to the ACP.ini file if you want to activate electrical tilt sharing between merged
physical antennas when the frequency difference lies within a defined limit.
[ACPAntennaPage]
etiltShareFrequencyRange = 100
#default = 100 (MHz)
10.2.2.17 Defining the Antenna Masking Model

In the [ACPAntMaskModelPage] section, you can find the options used to set the choices available under Antenna
Masking Method on the Setup Template tab of the ACP - Automatic Cell Planning Properties dialog box.
You can use the advancedUI option to display a column called Delegate Calculation to Model. Using the Delegate
Calculation to Model column, you can define whether the ACP calculates the path loss matrices or angles of
incidence used in antenna masking or whether it delegates calculation to the propagation model (providing the
propagation model implements the appropriate methods of Atoll’s API). Delegating calculation to the propagation
model provides more accurate results but might take longer. Additionally, it will use disk space to store the
calculation results.
[ACPAntMaskModelPage]
advancedUI = 1
#Default = 0 ("Delegate Calculation to Model" feature disabled)
The following option can be used to allow "Optimised" propagation models (i.e., propagation models that use the
"Optimised" mode) to use "Full Path Loss" mode:
nativeAllowFullPathLoss = 1
#default = 0 (disabled)
For external propagation models other than Aster that correctly implement the relevant API, the following option can
be used to force the default setting of "Antenna Masking Method" to "Antenna Correction":
DefaultAntennaCorrection = 0
#default = 0
 The relevant API interface must be implemented in order for the above option to
work.

10.2.2.18 Defining Reconfiguration Values Using Custom Fields

In the [ACPCustomFieldExtraction] section, you can set options that will enable ACP to extract data from custom
fields in the relevant tables of the Atoll database. ACP will extract the values entered in the custom fields and use
them as default reconfiguration values when a new optimisation setup is created. The values extracted can be
updated in the ACP setup, but ACP will not update the Atoll tables with the new values.
By default, ACP does not extract custom fields.


◼
◼ If a value is undefined in a custom field, ACP will use the default value for that
parameter.
10.2.2.18.1 Defining Reconfiguration Values for Transmitters, Repeaters, and Secondary Antennas Using
Custom Fields
fields in the Transmitters, Repeaters, and Secondary Antennas tables of the Atoll database. This data will be used
to initialise the reconfiguration parameters of transmitters, repeaters, remote antennas, and secondary antennas in
the corresponding technology.
The custom columns in the Transmitters, Repeaters, Remotes, and Secondary Antennas tables of the Atoll platform
must match the column names defined in the ACP.ini file.
 Some reconfiguration parameters such as height and azimuth can be defined either
as relative values (i.e., by defining the reconfiguration range starting from the
current value) or as absolute values. You therefore only need to define the settings
relevant to the value type (i.e., relative or absolute).
[ACPCustomFieldExtraction]
tx.antenna.optimize=acp_ant_use
#Best to define this column as a Boolean
tx.antenna.group=acp_ant_group
tx.etilt.optimize=acp_etilt_use
tx.etilt.min=acp_etilt_min
tx.etilt.max=acp_etilt_max
tx.etilt.deltamin=acp_etilt_deltamin
tx.etilt.deltamax=acp_etilt_deltamax
tx.tilt.optimize=acp_tilt_use
tx.tilt.min=acp_tilt_min
tx.tilt.max=acp_tilt_max
tx.tilt.deltamin=acp_tilt_deltamin
tx.tilt.deltamax=acp_tilt_deltamax
tx.tilt.step=acp_tilt_step
tx.tilt.sum.optimize=acp_tilt_sum_use
tx.tilt.sum.delta=acp_tilt_sum_delta
tx.azimuth.optimize=acp_azim_use
#Relative values from current azimuth
tx.azimuth.deltamin=acp_azim_deltamin
tx.azimuth.deltamax=acp_azim_deltamax
tx.azimuth.min=acp_azim_min
#Absolute value for azimuth angle
tx.azimuth.max=acp_azim_max
tx.azimuth.step=acp_azim_step
tx.azimuth.minInterSector=acp_azim_inter

The following options are NOT valid for the SecondaryAntennas table.
tx.height.optimize=acp_height_use
tx.height.deltamin=acp_height_deltamin
#Relative values from current height
tx.height.deltamax=acp_height_deltamax
tx.height.min=acp_height_min
#Absolute value for height values
tx.height.max=acp_height_max
tx.height.step=acp_height_step
The following options are ONLY valid for the GSM Transmitters table.
 In GSM, ACP extracts data from custom fields in the GSM Transmitters tables of
the Atoll database and displays it in ACP on the Reconfiguration > GSM Cells
vertical tab.
tx.gsm.power.optimize=acp_gsmpower_use
tx.gsm.power.min=acp_gsmpower_min
tx.gsm.power.max=acp_gsmpower_max
tx.gsm.power.step=acp_gsmpower_step
The following options are ONLY valid for the Repeaters table.
repeater.gain.optimize=acp_gain_use
repeater.gain.min=acp_gain_min
repeater.gain.max=acp_gain_max
repeater.gain.step=acp_gain_step
10.2.2.18.2 Defining Reconfiguration Values for Cells Using Custom Fields

fields in a technology-specific "Cells" table of the database. This data will be used to initialise the reconfiguration
parameters for cells in the corresponding technology.

In GSM, ACP extracts data from custom fields of the Transmitters table (not Cells
table) in the Atoll database and displays it in ACP on the Reconfiguration > GSM
Cells vertical tab. The relevant options are described in "Defining Reconfiguration
Values for Transmitters, Repeaters, and Secondary Antennas Using Custom Fields"
on page 242.
The following options can be used to extract data from custom fields in the "CDMA2000 cells" table of the database.
The custom columns in the CDMA2000 Cells table of the Atoll platform must match the column names defined in
the ACP.ini file.
ccell.pilotPower.optimize=acp_pilotpower_use
ccell.pilotPower.min=acp_pilotpower_min
ccell.pilotPower.max=acp_pilotpower_max
ccell.pilotPower.step=acp_pilotpower_step
ccell.maxPower.optimize=acp_maxpower_use
ccell.maxPower.min=acp_maxpower_min

ccell.maxPower.max=acp_maxpower_max
ccell.maxPower.step=acp_maxpower_step
The following options can be used to extract data from custom fields in the "UMTS cells" table of the database. The
custom columns in the UMTS Cells table of the Atoll platform must match the column names defined in the ACP.ini
file.
wcell.power.optimize=acp_power_use
wcell.power.min=acp_power_min
wcell.power.max=acp_power_max
wcell.power.step=acp_power_step
The following options can be used to extract data from custom fields in the "LTE cells" table of the database. The
custom columns in the LTE Cells table of the Atoll platform must match the column names defined in the ACP.ini
file.
lcell.power.optimize=acp_power_use
lcell.power.min=acp_power_min
lcell.power.max=acp_power_max
lcell.power.step=acp_power_step
10.2.2.18.3 Defining Reconfiguration Values for Sites Using Custom Fields

fields in the "Sites" table of the database. The custom columns in the Sites table of the Atoll platform must match
the column name defined by the settings in the ACP.ini file:
By using the site.status option to define the name of the custom status column in the Sites table, you can extract
the status (candidate or existing) of sites for site selection.
◼ All sites in the Sites table with the label set to the one defined by the site.status.candidate option will be
automatically set as candidate sites.
◼ Any site in the Sites table with a label other than the one defined by the site.status.candidate option will be
considered as an existing site.
◼ By default, all active sites are considered as existing sites.
site.status=acp_site_status
# Name of the custom column in Sites table.
# Default value is 'ACP_STATUS'.
site.gsm.status=acp_site_gsm_status
site.umts.status=acp_site_umts_status
site.lte.status=acp_site_lte_status
site.status.candidate=candidate
# Name used to define a candidate site.
The following options can be used to define custom columns in the Sites table of the Atoll platform. These will be
used for default reconfiguration options for each site.
site.disableSelection=acp_site_disableSelection
site.gsm.disableSelection=acp_site_gsm_disableSelection
site.umts.disableSelection=acp_site_umts_disableSelection
site.lte.disableSelection=acp_site_lte_disableSelection

site.removeable=acp_site_removeable
site.gsm.removeable=acp_site_gsm_removeable
site.umts.removeable=acp_site_umts_removeable
site.lte.removeable=acp_site_lte_removeable
site.sectorsRemoveable=acp_site_sectorsRemoveable
site.gsm.sectorsRemoveable=acp_gsm_site_sectorsRemoveable
site.umts.sectorsRemoveable=acp_umts_site_sectorsRemoveable
site.lte.sectorsRemoveable=acp_lte_site_sectorsRemoveable
The following option can be used to manage the Inter Sector Lock check boxes (Height and Azimuth) in the
Reconfiguration column of the Reconfiguration > Sites vertical tab.
The following option can be used to manage the Disable check box in the Reconfiguration column of the
Reconfiguration > Sites vertical tab.
10.2.2.18.4 Defining Reconfiguration Values for Antennas Using Custom Fields

fields in the Antennas table of the Atoll database. ACP can use the information in the custom fields to group
antennas and to set default reconfiguration values when a new optimisation setup is created . The custom column
in the Antennas table must match the column names defined in the ACP.ini file.
The following option can be used to name the custom column in the Antennas table to group antenna patterns into
groups of physical antennas (i.e., all patterns related to the same physical antenna) and group the physical antennas
at different frequencies into radomes by using the antenna.model option. Using the antenna.model enables you to
automatically form a multi-band antenna. The antenna model is by default set to the PHYSICAL_ANTENNA column
of the Antennas table. Hence by default the auto antenna grouping is always enabled if antenna patterns are
correctly assigned to physical antennas.
antenna.model=PHYSICAL_ANTENNA
If the physical antenna has been defined using the antenna.model option, the following option can be used to name
the custom column in the Antennas table that is used to define antenna groups. In the custom column in the
Antennas table, all antenna patterns corresponding to physical antenna belonging to the same group are identified
with a unique string. The ACP automatically groups all physical antenna into a new group with the name given by
the string used in the column.
antenna.group.model=acp_group_model
The following options can be used to name the custom columns in the Antennas table to automatically define the
mechanical tilt options.
◼ The name of the custom column in ANTENNA table of type 'bool', defining which antenna pattern is associated
with a mechanical tilt constraint:
antenna.tilt.use=ACP_TILT_USE
◼ The name of the custom columns in ANTENNA table of type 'string' or numeric, defining the mechanical tilt
allowed range. Non-valid values are treated as "forbidden":
antenna.tilt.min=ACP_TILT_MIN
antenna.tilt.max=ACP_TILT_MAX
The following options can be used to name the custom columns in the Antennas table to automatically define the
electrical tilt options.

 In order to optimise the electrical tilt, you must first activate the following option:
[ACPReconfPage]
enableETilt = 1
Optionally, if you want to activate AEDT support, you must also set the following
option:
[ACPAntennaPage]
enableAedt = 1
◼ The name of the custom column in the ANTENNA table of type 'bool', defining which antenna pattern is
associated with an 'electrical tilt constraint':
antenna.etilt.use=ACP_ETILT_USE
ACP supports additional electrical downtilt (AEDT) processing. AEDT is used when antenna patterns are not
available for changes in electrical tilts. The patterns are derived by ACP using geometric downtilts of the
original antenna pattern. When you have activated AEDT support, new columns appear in the Antenna Pattern
table on the Antenna > Patterns vertical tab allowing you to configure which antenna uses AEDT and the range
of allowed electrical tilt.
antenna.aedt.use=ACP_AEDT_USE
◼ The name of the custom columns in the ANTENNA table of type 'string' or numeric, defining the allowed range
for AEDT and electrical tilt. Non-valid values are treated as "forbidden":
antenna.etilt.min=ACP_ETILT_MIN
antenna.etilt.max=ACP_ETILT_MAX
The following option can be used to name the custom column in the Antennas table to automatically link antenna
elements of a multi-band physical antenna which have the same electrical tilt. In the ACP Setup dialog box, this is
accomplished by selecting the check box in the Same Elec. Tilt column. The antenna.etilt.share option should
contain a list of the space-separated frequencies for which the corresponding physical antenna must be linked (i.e.,
physical antenna that always uses same electrical tilt):
antenna.etilt.share=ACP_ETILT_SHARE
10.2.2.19 Defining Site Class Options

You can set options in the ACP.ini file to define site classes in the ACP. You can both define site classes that
automatically appear in the ACP Setup dialog box and set options in the ACP.ini so that the ACP applies site classes
based on optional data in the Atoll database.
10.2.2.19.1 Defining Automatic Site Classes

The following option can be used to show or hide the site class feature and set the number of site classes defined:
[ACPGeneralPage]
cost.classes.showUI = 1
# Default = 1 (site class feature is enabled).
The following option can be used to define the default settings when the site class option is available. These
settings are local.
[ACPTplGeneralPage]

cost.classes.count = 1
# Number of defined classes
You can then define the site classes that will appear each time a new ACP optimisation is created along with pre-
defined costs. The name of each class as it appears in the ACP is defined by an option called cost.classes.X.name
where X is a sequential number. The corresponding settings for the class defined in cost.classes.X.name are
defined using the following options:
◼ cost.classes.X.azimuth.cost: This key is used to define the cost of changing the antenna azimuth.
◼ cost.classes.X.azimuth.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.
◼ cost.classes.X.tilt.cost: This key is used to define the cost of changing the mechanical tilt of the antenna.
◼ cost.classes.X.tilt.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.
◼ cost.classes.X.antenna.cost: This key is used to define the cost of changing the type of the antenna.
◼ cost.classes.X.antenna.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.
◼ cost.classes.X.etilt.cost: This key is used to define the cost of changing the electrical tilt of the antenna.
◼ cost.classes.X.etilt.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.
◼ cost.classes.X.height.cost: This key is used to define the cost of changing the antenna height.
◼ cost.classes.X.height.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.
◼ cost.classes.X.power.cost: This key is used to define the cost of changing the power.
◼ cost.classes.X.power.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.
◼ cost.classes.X.siteVisitCost: This key is used to define the cost of a site visit.
◼ cost.classes.X.upgradeSiteCost: This key is used to define the cost of upgrading an existing site.
◼ cost.classes.X.newSiteCost: This key is used to define the cost of creating a new site.
◼ cost.classes.X.removeSiteCost: This key is used to define the cost of removing an existing site.
The following is an example of the keys for the first site class (numbered 0) called "Planned" in this example.
[ACPTplGeneralPage]
cost.classes.0.name=Planned
cost.classes.0.azimuth.cost = 1
cost.classes.0.azimuth.isSiteVisit=true
cost.classes.0.tilt.cost = 1
cost.classes.0.tilt.isSiteVisit=true
cost.classes.0.antenna.cost = 1
cost.classes.0.antenna.isSiteVisit=true
cost.classes.0.etilt.cost = 0.1
cost.classes.0.etilt.isSiteVisit=false
cost.classes.0.height.cost = 1
cost.classes.0.height.isSiteVisit=true
cost.classes.0.power.cost = 0.1
cost.classes.0.power.isSiteVisit=false
cost.classes.0.siteVisitCost = 2
cost.classes.0.upgradeSiteCost = 5
cost.classes.0.newSiteCost = 10
cost.classes.0.removeSiteCost = -5
10.2.2.19.2 Automatic Assignment of Site Classes in the ACP

In the [ACPCustomFieldExtraction] section, you can define the custom field in the Sites table of the Atoll database
that identifies the site class of each site.

 You must first create the corresponding custom column in the Sites table of the
Atoll database and assign a site class to each site in this column for this option to
have effect.
site.costClass=[name of custom field in Site table]
The site class defined in the Sites table will be assigned automatically when an ACP optimisation is defined. For
new candidate sites which are located on an existing site, the site class is the same as the site on which the new
candidate is located. For new candidate sites which are not co-located on an existing site, the site class is set to
"Default" and can be changed manually.
By defining the costs of each site class as explained in "Defining Automatic Site Classes" on page 246, the cost
structure is automatically defined as well.
10.2.2.20 Defining the Appearance of a Running Optimisation Dialog Box

In the [ACPMapDefault] and [ACPMapPage] sections are the settings you can use to define the appearance of the
Optimisation dialog box during a run. Some options refer to the Quality tab and others to the Graphs tab.
10.2.2.20.1 Defining the Colours in the Analysis Maps on the Quality Tab
The following settings can be used to define the colours in the analysis maps on the Quality tab.
 None of the options described in this section are available by default in the ACP.ini
file. If you want to use any of them, you must specify it manually in the ACP.ini file.
There are two possible formats for defining the range of colours on maps:
1. Detailed format: The detailed format enables you to set a non-uniform range. The number of ranges is defined
and, for each range, the minimum and maximum value of the range followed by its RGB color representation.
[ACPMapDefault]
colormap.techno.quality.nbRange = 8
# Number of ranges to be defined
colormap.techno.quality.range.0=[-99999.000000 -15.000000] RGB(0 0 255)
colormap.techno.quality.range.7=[-3.000000 99999.000000] RGB(255 0 0)
◼ Uniform format description: A uniform format description using a range and step, in one of the following
intervals: [firstBreak startcolor] [lastBreak endColor]
◼ -INF [firstBreak startcolor] [lastBreak endColor]
where interval starts from minus infinite to englobe all lower values and avoid transparent pixels for lower
values.
[ACPMapDefault]
colormap.techno.quality.rangeDefinition=[-5 RGB(255 0 0)] [-20 RGB(0 0 255)] -5
colormap.techno.quality.rangeDefinition = -INF[-5 RGB(255 0 0)] [-20 RGB(0 0 255)]
-5

These descriptions are used for default colormap and can easily be changed by the user. The settings are the same
for the various quality indicator in various technologies, where you replace:
◼ techno by "umts", "gsm", "lte", "wimax", "cdma"
◼ quality by "sl", "slgain" (in GSM), "ecio", "ec", "ecgain", "eciogain", "ecnt", "ecntgain" (in UMTS), "sl", "slC", "slCN",
"rsrp", "cinr", "rsrq", "slgain", "cinrgain", "rssi" (in LTE), "sl", "slC", "slCN", "cinr", "slgain", "cinrgain" (in WiMAX)
[ACPMapDefault]
colormap.gsm.sl
colormap.gsm.slgain
colormap.umts.ec
colormap.umts.ecgain
colormap.umts.ecio
colormap.umts.eciogain
colormap.umts.ecnt
colormap.umts.ecntgain
colormap.lte.cinr
colormap.lte.cinrgain
colormap.lte.rsrp
colormap.lte.rsrq
colormap.lte.rssi
colormap.lte.sl
colormap.lte.slC
colormap.lte.slCN
colormap.lte.slgain
colormap.wimax.cinr
colormap.wimax.cinrgain
colormap.wimax.sl
colormap.wimax.slC
colormap.wimax.slCN
colormap.wimax.slgain
In addition, a number of other colormaps can be defined for other types of maps, e.g: overlap maps, objective status
maps, electrical tilt maps, mechanical tilt maps, combined electrical/mechanical tilt maps, change maps, emf maps,
etc.

[ACPMapDefault]
colormap.bestcell.etilt
colormap.bestcell.objective
colormap.bestcell.sector
colormap.bestcell.tilt
colormap.bestcell.ttilt
colormap.bestcellHeight
colormap.capacity
colormap.capacitygain
colormap.change.azimuth
colormap.change.cost
colormap.change.etilt
colormap.change.impr
colormap.change.power.cdma
colormap.change.power.gsm
colormap.change.power.lte
colormap.change.power.umts
colormap.change.power.wimax
colormap.change.power2.cdma
colormap.change.power2.umts
colormap.change.selectionType
colormap.change.tilt
colormap.change.ttilt
colormap.change.type
colormap.changeHeight
colormap.diff
colormap.emf
colormap.emf.badSector
colormap.emf.gain
colormap.gain
colormap.imprCoverage
colormap.objective
colormap.objective.gain
colormap.objective.weighting
colormap.overlap
colormap.overlapgain
10.2.2.20.2 Other Components of the Optimisation Dialog Box

The following options can be used to define other components of the Optimisation dialog boxduring a run. Below
are the default colour codes for the foreground and background on the Quality tab, with the RGB code as an integer:
[ACPMapPage]
config.foreground = 0
#default foreground colour setting (black)
config.background = 16777215
#default background colour code (white)
8 16
The RGB code for white is calculated as follows: 255 + 255  2 + 255  2 = 16777215 .
The following options define the size of the map title on the Quality tab:
[ACPMapPage]
config.titleHeight = 16
# Title height in pixels
config.titleFontSize = 16
# Size of title font in points
The following option defines the width of the margin on the Quality tab:
[ACPMapPage]

config.margin = 2
# Margin width in pixels
The following options define the appearance of the map legend on the Quality tab:
[ACPMapPage]
config.showLegend = 1
# Defines whether the legend is displayed.
config.legendWidth = 40
# Defines the width of the legend in pixels.
config.legendFontSize = 11
# Defines the font used in points.
config.legendForeground = 0
# RGB code as integer: here black
The following option defines whether or not the axis will be displayed on the Quality tab:
[ACPMapPage]
config.showAxis = 1
The following options define the appearance of the histogram on the Quality tab:
[ACPMapPage]
config.showHistogram = 1
# Defines whether the histogram is displayed.
config.histogramHeight = 60
# Defines the width of the histogram in pixels.
The following options define the appearance of the selected zone on the Quality tab:
[ACPMapPage]
config.showZoneSelection = 1
# Defines whether the selected zone is displayed.
config.zoneLighterPercent = 70
# Defines how much lighter selected zone is displayed.
10.2.2.21 Defining the Appearance of ACP Predictions

The following option defines the transparency of ACP predictions:
[ACPMapDefault]
transparency = 50
The following option automatically selects the Add to legend check box in the properties of new ACP predictions:
[ACPMapDefault]
isAddToLegend = 1
The following option forces any new ACP prediction to not reuse the shading settings (if any) of the Atoll prediction
defined next to Base prediction settings in the Objectives page of the corresponding quality parameter.
[ACPMapDefault]
isUsePredictionColormap = 1
#default = 1 (shading settings of ACP prediction prevail)

10.2.2.22 Defining New Predictions

In the [ACPNewPredictionDlg] section are options for displaying additional predictions that can be created from
setups and from the optimisation results.
Setting the following option allows you to create a prediction that displays the initial and final coverage by antenna.
[ACPNewPredictionDlg]
showBestServerAerialPrediction = 1
#default = 0
Setting the following option allows you to create a prediction that displays the coverage by layer.
showBestServerLayerPrediction = 1
#default = 0
Setting the following option allows you to create a prediction that displays the weight used for the traffic and for
each zone.
showObjectiveWeightPrediction = 1
#default = 0
Setting the following option allows you to create a prediction that displays the improvement in coverage.
showchangeImprovementPrediction = 1
#default = 0
10.2.2.23 Defining the Functionality of the Commit Tab

In the [ACPCommitPage] section is the option for defining whether the user can only edit the set of changes to be
committed on the Change Details tab (default). Setting allowUserChangeForCommit to "true" allows the user to edit
the set of changes on the Commit tab; this setting is not recommended.
[ACPCommitPage]
allowUserChangeForCommit=false
You can use the addCandidateComment option to create a comment in any site, transmitter, and cells automatically
created by ACP in Atoll as part of the candidate site selection. No comment is added if this option is left blank.
10.2.2.24 Defining the Appearance of the Overlay Window

[ACPCommitPage]
addCandidateComment=Created from ACP candidate list
In the [ACPOverlayDialog] section is the option for defining the opacity of the overlay window when it loses focus.
A value of 100 disables it.
[ACPOverlayDialog]
opacity = 100
10.2.2.25 Defining the Appearance of the Graph Tab

In the [ACPGraphPage] section is the option for enabling the display of time markers on the Graph tab of the
Optimisation Properties dialog box. A value of 100 disables it.

[ACPGraphPage]
showTimeMarkers = 1
# To add time markers on the X axis. Default is 0
10.2.2.26 Defining the Default Font

In the [ACPUI] section is the option for defining the default font to be used by the grid, graph component, and map
component. In the example below, the "MS UI Gothic" font used in Japanese systems is set as the default font.
[ACPUI]
DefaultFont = MS UI Gothic
#Font used by grid, graph component, and map component
DefaultGridFontSize = 0
#Font size for grid only. 0 mean default size
10.2.2.27 Exporting Optimisation Results in XML

You can use the following options to define the contents and appearance of an XML report generated from the
Statistics tab of an optimisation’s Properties dialog box.
[ACPXmlReport]
enableXmlExport = 1
# Enable the XML report from the ResultStatPage
generateXmlSection = -1
# Bit combination of the following: 1=metadata, 2=setup, 4=resultSummary,
# 8=resultSectors, 16=resultIterations, 32=resulstChangeset, 64=resultMaps, -1=all
encoding=UTF-8
saveDefaultStylesheet = 1
#save a default stylesheet if none exist
defaultStylesheetName=.acpReport.xslt
# Name of default stylesheet file.
# Set it empty to disable stylesheet processing instruction
10.2.3 ACP Core Engine Options
The settings in the [ACPCore] section are used to define how the ACP engine functions.
10.2.3.1 Log File Settings

ACP enables you to set up a log file as well as create a crash report in case of an application crash.
The following option defines whether ACP generates a log file (with the name ATL_NAME_optim.log):
[ACPCore]
generateLogFile = 0
# default = 0; no log file.
10.2.3.2 Calculation Thread Pool Settings

The following options define how the calculation thread pool will be managed. If useComputationThreadPool is set
to "false," ACP uses only one thread. If useComputationThreadPool is set to "true," ACP uses the number of threads
specified by the computationThreadPoolSize option.

[ACPCore]
useComputationThreadPool=true
computationThreadPoolSize = 4
The default setting for computationThreadPoolSize is 4 and the maximum value that can be specified is 8.
10.2.3.3 Number of Threads Used for Propagation Model Calculations

With the following option, you can define the number of threads that the propagation model can use when
calculations are delegated to the propagation model (e.g. calculations of heights or angles of incidence). This can
be useful, for example, to control the number of licences taken by the ACP, without reducing the number of threads
used by regular ACP calculations.
[ACPCore]
pathlossThreadPoolSize = -2
# Default = -2
Possible settings:
Value Description
-2 The default value means that the propagation model will use the same number of threads as the number
of threads defined by computationThreadPoolSize.
-1 Auto configuration; the propagation model will use one thread for each CPU core.
Other The defined numerical value indicates the number of threads that the propagation model can use.
10.2.3.4 Memory Management Settings

The following options define how the ACP manages memory during calculations.
The ACP tries to estimate the worst-case scenario in memory use, and indicates to the user when memory use
seems too high. Using one of the following options, you can define the method ACP uses to indicate excessive
memory use:
◼ memLimitNumPos: Memory use is determined to be excessive when the maximum number of pixels (as
defined by memLimitNumPos) is reached during a calculation. Setting memLimitNumPos to -1 deactivates
this option.
◼ memLimitMemory: Memory use is determined to be excessive when the estimated memory use in Mb (as
defined by memLimitMemory) is reached during a calculation. Setting memLimitMemory to -1 deactivates this
option.
◼ memLimitUseableMemory: Memory use is determined to be excessive when the estimated memory use
exceeds the percentage of the total memory available for Atoll, as defined in memLimitUseableMemory.
Setting memLimitUseableMemory to -1 deactivates this option.
If all three options are deactivated, ACP does not check excessive memory usage.
The abortIfMemLimitReach option defines how ACP reacts if the defined maximum memory use is reached. By
default (with abortIfMemLimitReach set to 0), ACP will attempt to allocate memory. If unable to successfully
allocate memory, ACP displays a message and the calculation is stopped. When using the option
abortIfMemLimitReach, then ACP will not start if the message indicating excessive memory use is displayed.
By default, excessive memory use is considered an estimate of 80% of the memory available to the process; ACP is
not prevented running even when 80% is exceeded.
 When ACP estimates actual memory use (i.e., using either memLimitMemory or
memLimitUseableMemory), the memory estimate is only a rough estimate.
Depending on the project, actual memory usage can be quite different.
[ACPCore]

memLimitNumPos = -1
# -1 deactivates this option.
memLimitMemory = -1
memLimitUseableMemory = 80
abortIfMemLimitReach = 0
10.2.3.5 Automatic Stops of the Search Phase

Prior to the Tuning phase, the Search phase is automatically stopped when no more improvements can be made
(indicated on the graphs by a light blue vertical line). If you want, you can disable automatic stops and let the Search
phase reach its maximum duration, i.e. 2/3 of the defined number of iterations (indicated on the graphs by a dark
blue vertical line) by setting the following option in the ACP.ini file.
[ACPCore]
AutomaticStopSearchPhase = 0
#Default = 1
10.2.3.6 Considering Progressive Thresholds for Some Quality Objectives

By default, a Progressive threshold check box appears in the Thresholds Definition dialog box for the following
objectives:
◼ GSM: BCCH Signal Level, CINR Co-Channel
◼ UMTS: RSCP, EcIo
◼ LTE: RSRP, RSCINR, RSRQ, PDSCH CINR
◼ WiMAX: Signal Level
◼ WiFi: Signal Level
◼ LPWA: Signal Level
When the Progressive threshold check box is selected in the Thresholds Definition dialog box of a given objective,
ACP evaluates the amount of improvement or degradation of the that objective, leading to more intelligent decisions
on improvements that may cause degradations elsewhere in the network.
All other objectives (and the above objectives when the Progressive threshold check box is cleared) are evaluated
by ACP on a "fixed-threshold basis" on each pixel and in a logical manner, whether the objective is met or not.
If you want, you can remove the Progressive threshold check box from the Thresholds Definition dialog box by
setting the following option in the ACP.ini file:
[ACPCore]
useProgressiveThreshold = 0
#default = 1
The following options define the values used by ACP to control the curve shapes. Although you can modify these
settings, they are the recommended factory values:
[ACPCore]
gsm.signallevel.th.min = -120
gsm.signallevel.th.max = -50
gsmcnircocanal.th.min = 0
gsm.cinrcocanal.th.max = 20
umts.rscp.th.min = -120
umts.rscp.th.max = -60
umts.ecio.th.min = -20
umts.ecio.th.max = -6

lte.rsrp.th.min = -130
lte.rsrp.th.max = -70
lte.rscinr.th.min = -10
lte.rscinr.th.max = 30
lte.rsrq.th.min = -20
lte.rsrq.th.max = -8
lte.pdschcinr.th.min = -10
lte.pdschcinr.th.max = 40
wimax.signallevel.th.min = -120
wimax.signallevel.th.max = -50
wifi.signallevel.th.min = -120
wifi.signallevel.th.max = -50
lpwa.signallevel.th.min = -140
lpwa.signallevel.th.max = -50
10.2.3.7 Macro Diversity Gains Calculation

The following option indicates how ACP handles macro diversity gains.
[ACPCore]
addPilotSHOGain = 1
#Default = 1
For details on disabling macro-diversity gains calculation, see "Disabling Macro-diversity (SHO) Gains Calculation
for Ec/Io and Eb/Nt" on page 202.
Possible settings:
Value Description
0 ACP does not take macro diversity gains into account.

For consistency with the Atoll platform, the following option must be set in the Atoll.ini file:
[CDMA]
AddPilotSHOGain = 0
1 Default. ACP takes macro diversity gains into account.
2 ACP uses the same value as the one defined for the AddPilotSHOGain option in the Atoll.ini file:
[CDMA]
AddPilotSHOGain = value
10.2.3.8 Transmitter Altitude Calculation

The following option determines how ACP calculates the transmitter altitude from the DTM when no site altitude is
defined in Atoll.
[ACPCore]
useSiteAltitude = 1
#Default = 1
For details on reading altitudes from the DTM in Atoll, see "Reading Exact Altitudes From the DTM" on
page 187.Possible settings:

Value Description
0 During calculations, ACP will read the altitudes from the DTM at the exact coordinates of each transmitter
considering the values entered for the DX and DY parameters.
1 Default. This is the value used by the Atoll platform (which uses either the user-defined site altitudes from
the Sites table or, if they are not defined, the site altitudes read from the DTM for the site coordinates
defined in the Sites table).
2 ACP uses the same value as the one defined for the useSiteAltitude option in the Atoll.ini file:
[Calculations]
useSiteAltitude = value
10.2.3.9 Automatic Candidate Positioning Options

ACP will not crete a candidate site if it falls too close to an existing site or to a predefined candidate site. By default,
the minimum distance is 25% of the inter-candidate distance defined in the Automatic Candidate Positioning dialog
box.
The following option defines the inter-candidate distance for the sites proposed by ACP (in metres):
[ACPAutoCandPosDlg]
interSiteDist = 500
#default = 500
For areas (polygon zones only, not polylines), you can set the following option to modify the default minimum ratio
of inter-site distance below which candidate sites will not be proposed:
[ACPAutoCandPosDlg]
minInterSiteDistRatio = 25
#default = 25
ACP normally places candidate sites in a strict hexagonal pattern. However, the ACP can search for a more
appropriate site within a search radius ratio according to the defined rules. The following option defines the default
search radius ratio as a percentage of the defined inter-candidate site distance.
[ACPAutoCandPosDlg]
searchRadiusRatio = 30
The following option defines the default minimum increase in altitude (in metres) that the ACP must find when
placing a new automatic candidate site.
[ACPAutoCandPosDlg]
hpHeightThres = 10
10.2.3.10 Setting a Minimum Inter-site Distance for Site Activation

The following option can be used to constrain the site activation during an ACP optimisation by setting a minimum
inter-site distance between candidates (in metres):
[ACPCore]
minInterSiteDistanceCandidates=500
The default value is 500. This constraint is disabled if minInterSiteDistanceCandidates is set to 0.
10.2.3.11 Balancing Speed, Memory Use, and Accuracy in Calculations

The Preferences tab of the ACP - Automatic Cell Planning Properties dialog box enables you to select a mode of
operation that balances speed, memory use, and accuracy. By defining the settings of the options in the ACP.ini file
that each mode uses, you can fine-tune how ACP will operate in the selected mode:

◼ High Speed: Using the highest speed also uses the least memory although the final results might be slightly
less accurate.
◼ Default: When no changes are made to the ACP.ini file, ACP uses the default settings. The default settings can
be overridden by changing the settings in this section.
◼ High Precision: When the settings in this section are defined to give the results of the highest precision,
calculating the results will take the longest time and will use more memory.
The options described below are those used for the default operation mode.
The ACP.ini options that define how the selected mode works are described below:
◼ maxMonitorCell: defines the maximum number of cells monitored. This option affects memory use and
accuracy. The analogous options for the high speed mode and the high precision mode are
maxMonitorCellSpeed and maxMonitorCellPrec, respectively.
◼ threshLevelMonitorCell: defines the best server signal threshold (dB) in order to be monitored. This option
affects memory and accuracy.
◼ The analogous options for the high speed mode and the high precision mode are
threshLevelMonitorCellSpeed and threshLevelMonitorCellPrec, respectively.
The following options define the values ACP uses for default mode:
[ACPCore]
maxMonitorCell = 32
threshLevelMonitorCell = 35
The following options define the values ACP uses for high speed mode:
[ACPCore]
maxMonitorCellSpeed = 30
threshLevelMonitorCellSpeed = 30
The following options define the values ACP uses for high precision mode:
[ACPCore]
maxMonitorCellPrec = 35
threshLevelMonitorCellPrec = 40
Other options in the ACP.ini file can be used to define additional offsets that will be used by the specific technology
that ACP is optimising:
[ACPCore]
threshLevelOffGsm = 0
maxMonitorOffGsm = 0
threshLevelOffUmts = 0
maxMonitorOffUmts = 0
threshLevelOffCdma = 0
maxMonitorOffCdma = 0
threshLevelOffLte = 10
maxMonitorOffLte = 10
threshLevelOff5gnr = 10
maxMonitorOff5gnr = 10
threshLevelOffWimax = 5
maxMonitorOffWimax = 5
threshLevelOffWifi = 5
maxMonitorOffWifi = 5
threshLevelOffLpwa = 20
maxMonitorOffLpwa = 20

10.2.3.12 Accessing Raster Data

When working in co-planning mode, you have several Atoll documents open and you are working with the ACP from
the main document. ACP needs to access raster data and by default it accesses only the raster data specified in the
main document. If for some reason different raster data is used in the secondary document, you must set the ACP
to access raster data for each document separately using the following option:
[ACPCore]
gisDataTechnoShared = 0
ACP loads raster data with block-based processing to reduce memory usage. The maximum memory (in Mb)
allowed for this block processing in Mb is controlled with the following setting (you can reduce the value if you
experience issues with ACP failure due to memory allocation):
[ACPCore]
gisDataCacheMemMax = 256
For lower memory usage, you can use the following option to specify an optimized block-based raster data loading
strategy:
[ACPCore]
gisDataCacheStrategy = 1
# default = 1
When you set the following option, ACP will consider a mix or raster data and polygons for the DLU file (should be
set to 1 when clutter classes are edited with the clutter editor):
[ACPCore]
gisDataClutterUsePoly = 0
# default = 0
When you set the following option, ACP creates multistorey points for areas where the DLU file is present (with
default heights) without the presence of DHM raster (clutter height). The default setting (TRUE) makes the ACP
distribute vertical points only where DHM is available:
[ACPCore]
multistorey.onlyDHM = TRUE|FALSE
# default = TRUE
10.2.3.13 Filtering Clutter Class Layers

When using several layers of raster clutter classes, each with a different resolution, you can define which resolution
(usually the lower resolution) ACP should use when defining zones by clutter class. Setting the
gisDataClutterOnlyRes option to 0 (the default) means that clutter class layers will not be filtered out by resolution.
Setting this option to any other value (e.g. 20) means that ACP will only use clutter classes with that resolution (in
this case 20).
[ACPCore]
gisDataClutterOnlyRes = 20
# ACP will only use clutter classes with this resolution
If you set the gisDataClutterOnlyRes option to filter out all clutter classes but those with the defined option, you
should also list the clutter classes that are not to be used in the zone.clutter.hiddenCodes in the [ACPGeneralPage]
section to ensure that the user will not create zones based on clutter classes that are not used. When you define the
clutter classes that are not used, they will not be displayed in the Zone Definition dialog box.
[ACPGeneralPage]
zone.clutter.hiddenCodes = 0,1,2,12,13
# These clutter classes are not displayed

10.2.3.14 Fixed Ratio Between Pilot Power and Max Power (UMTS)
When optimising the maximum cell power in UMTS, the ACP forces the ratio between pilot power and maximum
power to stay constant. You can remove this constraint using the following option:
[ACPCore]
umtsPilotPowerRatioFixed = 0
10.2.3.15 Showing Initial/Final Total Poweror DL Load on Sectors Tab (UMTS)

When optimising the pilot power in UMTS, you can display an additional Total Power (dBm) or DL Load (%) column
on the Sectors and Commit tabs of the Optimisation Properties dialog box, according to the DL load setting
(Absolute or % Pmax, resp.) in the Network Settings Properties dialog box.
Before you run an optimisation, make sure that Pilot Power is selected on the Reconfiguration > UMTS Cells vertical
tab of the Setup Properties dialog box and set the following option in ACP.ini:
[ACPResultSectorPage]
showDlLoad = 1
#default = 0
10.2.3.16 Custom Columns on the Sectors tab of the Optimisation Results

You can use the following options to display Atoll’s transmitter columns on the Sectors tab of the optimisation
results.
[ACPResultSectorPage]
custom.count = 2
#default = 2
You can then set the following options to specify the data you want to show under each custom column.
custom.0.type=tabularDataColumn
custom.0.column=FOO
custom.0.label=FOO label of custom.0.column
custom.1.type=tabularDataColumn
custom.1.column=BAR
 tabularDataColumn shows data issued from Atoll TRANSMITTERS table, identified

by the required custom.x.column setting.
Atoll column names are case sensitive.
10.2.3.17 Enabling Multi-technology Optimisation Including WiMAX

In order to use the ACP to optimise your WiMAX network with any other technology network (GSM, UMTS,
CDMA2000, LTE), set the following option in ACP.ini:
[ACPImportProject]
importWimax = 1
# default = 0
 This option is valid for co-planning support between WiMAX and:

◼ Single-RAN GSM, UMTS, CDMA2000, and LTE
◼ Multi-RAT 3GPP and 3GPP2

10.2.4 EMF Exposure Core Options
In the [ACPEMFCore] section there are several options controlling the EMF exposure calculation engine.
One set of options allows for the detection and auto correction of transmitter heights which are found to be indoors,
just below the roof. This is usually caused by inconsistencies between the vectors imported to create the 3D
representation of the terrain and Atoll database.
The other option controls the resolution used internally to rasterise input vectors, the default being 2 metres.
When the height of a transmitter is within the Digital Height Model (i.e., the combination of clutter heights and
imported vectors used to create the 3D representation of the terrain) and DHM-offset, then it is considered to be
indoors, just below the roof. The ACP automatically detects these transmitters and displays warnings in the Event
Viewer. The default distancebeneath the roof is 5 metres.
[ACPEMFCore]
detectTxIndoorOffset = 5
The ACP can automatically adjust the height of transmitters that are below roof so that they are on top of the clutter
height using the defined offset (in metres).
[ACPEMFCore]
resetTxHeightWhenIndoor = 0
#default = 0; height is not reset.
The following option defines the internal resolution in metres (2 by default) for terrain 3D representations when the
ACP rasterises input vectors:
[ACPEMFCore]
vectorRasterizationResolution = 2
The following option allows you decrease the displayed EMF exposure level when penetration loss is increased for
buildings.
[ACPEMFCore]
flagPixelFacadeDist = distance
flagPixelFacadeDist defines (in metres) the indoor distance from facade for a pixel to be considered as "indoor".
When the distance is 0, the outdoor pixels will be applied the indoor penetration loss specified in the Propagation
Class Definition table (Propagation page on the Optimisation tab).
10.2.5 Other Options
10.2.5.1 EMF and Multi-Storey Extensions

You can add the following lines to the ACP.ini file to show the Optimisation > EMF Exposure tab in ACP setups
(equivalent to manually selecting the EMF Exposure check box under Extensions on the Preferences tab):
[ACPExtension]
emf = 1
Likewise, you can add the following lines to show the Optimisation > Multi-Storey tab in ACP setups (equivalent to
manually selecting the Multi-Storey check box under Extensions on the Preferences tab):
[ACPExtension]
multistorey = 1

10.2.5.2 Validity of Path Loss Matrices

You can use the following option to enable or disable the automatic verification of the validity of path loss matrices
before running an optimisation setup.
[ACPMisc]
autoCheckPathlossValidity = 0|1
autoCheckPathlossValidity is set to 1 by default, which means that the validity of path loss matrices is automatically
checked before running an optimisation setup.
In addition, the following options can be used:
◼ To enable ("1") or disable ("0") the automatic check of the path loss matrix files (file location and file size)
before a run:
autoCheckPathlossFileValidity = 0|1
autoCheckPathlossFileValidity is set to 1 by default.

◼ To enable ("1") or disable ("0") the automatic recalculation of invalid path loss matrices before running an
optimisation setup:
autoPathlossRecomputation = 0|1
autoPathlossRecomputation is set to 1 by default.

◼ To enable ("1") or disable ("0") the automatic check of active transmitter number:
autoCheckTxNumber = 0|1
autoCheckTxNumber is set to 1 by default.

◼ To consider locked path loss matrices as always valid:
manageLockedPathlossAsvalid = 0|1
manageLockedPathlossAsvalid is set to 1 by default.
10.2.5.3 Considering Zero-degree Electrical Tilts

By default, the ACP algorithm calculates an estimated electrical tilt value when the Pattern Electrical Tilt (°) field of
the Antennas table is null, that is to say when the field is empty or the value is equal to zero.
You can force ACP to consider a pattern electrical tilt equal to zero degrees (0°) by setting the following option in
the ACP.ini file:
[ACPMisc]
CalculateEtiltWhenZero = 0
CalculateEtiltWhenZero is set to 1 by default.
10.2.5.4 Linking Transmitters Operating on the Same Frequency Band

By default, transmitters that have the same site location but belong to different frequency bands can be linked to
ensure that the same reconfiguration is applied to each shared antennas.
You can link transmitters operating on the same frequency band by setting the following option in the ACP.ini file:
[ACPMisc]
canLinkOnSameBand = 1
canLinkOnSameBand is set to 0 by default.

AT340_AM_E3 Index of Initialisation Options
Index of Initialisation Options
acp.ini main options

Calculation Thread Pool Settings defaultTxHeightStep.feet 232
computationThreadPoolSize 254 defaultTxTiltMax 232
useComputationThreadPool 254 defaultTxTiltMin 232
Custom columns on Transmitters and Remote tabs of defaultTxTiltStep 232
Reconfiguration page etilt.relative.min.variation 233
236 showNbRemotes 232
tx.custom.x.column 236 tx.etilt.deltaLimitConstraint.show 232
tx.custom.x.label 236 tx.tilt.deltaLimitConstraint.show 233, 234
tx.custom.x.type 236 Default Values on the Transmitters Tab of the Reconfig-
Default Values on the Antennas Tab uration Tab
enableAedt 240 tx.tilt.asRelative 235
Default Values on the Optimisation Tab Defining Automatic Site Classes
cost.antenna.cost 226 cost.classes.0.antenna.cost 247
cost.antenna.isSiteVisit 226 cost.classes.0.antenna.isSiteVisit 247
cost.azimuth.cost 226 cost.classes.0.azimuth.cost 247
cost.azimuth.isSiteVisit 226 cost.classes.0.azimuth.isSiteVisit 247
cost.etilt.cost 226 cost.classes.0.etilt.cost 247
cost.etilt.isSiteVisit 226 cost.classes.0.etilt.isSiteVisit 247
cost.height.cost 226 cost.classes.0.height.cost 247
cost.height.isSiteVisit 226 cost.classes.0.height.isSiteVisit 247
cost.newSiteCost 226 cost.classes.0.name 247
cost.power.cost 226 cost.classes.0.newSiteCost 247
cost.power.isSiteVisit 226 cost.classes.0.power.cost 247
cost.removeSiteCost 226 cost.classes.0.power.isSiteVisit 247
cost.siteVisitCost 226 cost.classes.0.removeSiteCost 247
cost.tilt.cost 226 cost.classes.0.siteVisitCost 247
cost.tilt.isSiteVisit 226 cost.classes.0.tilt.cost 247
cost.upgradeSiteCost 226 cost.classes.0.tilt.isSiteVisit 247
cost.classes.0.upgradeSiteCost 247
Default Values on the Patterns tab of the Antenna Tab
cost.classes.count 247
enableMTilt 239, 240
Defining Reconfiguration Values for Sites Using Custom
Default Values on the Reconfiguration Tab
Atoll Fields
232
site.gsm.status 244
defaultRepGainMax 232
site.lte.status 244
defaultRepGainMin 232
site.status 244
defaultRepGainStep 232
site.status.candidate 244
defaultTxAzimuthMinInterSector 232
site.umts.status 244
defaultTxAzimuthStep 232
Defining the Appearance of the Graph Tab
defaultTxAzimuthVariation 232
defaultTxETiltMax 232 showTimeMarkers 253
defaultTxETiltMin 232 Defining the Functionality of the Commit Tab
defaultTxHeightMax 232 allowUserChangeForCommit 252
defaultTxHeightMax.feet 232 Number of Threads Used for Propagation Model Calcula-
defaultTxHeightMin 232 tions
defaultTxHeightMin.feet 232 pathlossThreadPoolSize 254
defaultTxHeightStep 232
atoll.ini options listed by INI section

3GCells, NoSuffixIfUniqueCarrier 202 ACP, iniFile 224

Add-ins, ’Add-in Name’ 165 DefaultFolders, CustomReportExportFolder 168

AFP, GlobalDistanceMatrixDegreeUB 199 DefaultFolders, DataExchangeExportFolder 168
AFP, HideHopping 198 DefaultFolders, DataExchangeImportFolder 168
AFP, MaxNumberOfSeparations 200 DefaultFolders, GeoExportFolder 168
AFP, SimpleUserGUI 198 DefaultFolders, ImportFolder 168
AFP, WorstCaseIM_FskAfp 199 DefaultFolders, PredictionExportFolder 168
Antenna, AntennaPatternConsistencyDifference 156 DefaultFolders, UserConfigurationFilesFolder 168
Antenna, CatalogVerticalDiagramOrientation 185 Display, CaseInsensitiveGroups 176
Antenna, CheckOrFixElecAzAndTilt 169 Display, CellIDNbDigits 174
Antenna, HighResolutionAntennaPattern 156 Display, DiscreteValueColoring 175
Antenna, InterpolatePatternEvenIfOnlyOneDiagram 185 Display, MaxColorNeighbours 175
Antenna, InterpolatePatternIndB 185 Display, PaletteColor0 175
Antenna, PrecisionTimes10 156 Display, ShowCellularSchemaFolder 177
Antenna, REDTDisplay 174 Display,RepeaterDefaultType 176
Antenna, RoundBeamwidth 190 DocTitle, UseTechnoName 174
AutoRename, 3GCells 150 EventsObserver, LogPath 151
AutoRename, Repeaters 150 EventsObserver, milliseconds 172
AutoRename, Transmitters 150 EventsObserver, ShowAddinAccessDeniedMsg 151
BsicFormat, DefaultValue 196 EventsObserver,date 172
Calculations, InterTechIRFInterpolationMode 194 Export, AdvancedXML 156
Calculations, RoundAltitudes 190 Export, AlwaysUseListSeparatorInCSV 157
Calculations, UseSiteAltitude 187 Export, AutoOpenWithExcel 157
CDMA, AddPilotSHOGain 202 Export, NewLineEscapeSequence 167
CDMA, CodeStrategies 207 FavouriteViews, DefaultStorage 169
CDMA, CQIDeltaWithPower 203 FavouriteViews, UpdateFocusAndComputationZone 169
CDMA, CutOffSimu 204 Features, IM_TRAFFIC_OVERLAP 196
CDMA, DisplayEcIoOfRejected 206 FskPropagModels, OptimOnNoData 191
CDMA, HSDPAAvgSimuResults 203 Geo, FindGeoButtonAlwaysActive 159
CDMA, HSDPAMaxRejections 204 Geo, ReportObeysVisibility 159
CDMA, HSDPAThroughputPeak 202 Geo, VectorDisplayConfigurationCompanionFile 159
CDMA, IterBeforeDown 205 GeoProfileDisplay, Beamwidth 175
CDMA, MaxRejections 204 GeoProfileDisplay, BeamwidthColor 176
CDMA, MinUsersPerBin 203 GeoProfileDisplay, Lower3dbColor 176
CDMA, MultiBandSimu 206 GeoProfileDisplay, Upper3dbColor 176
CDMA, OrthoInCPICH 204 GOB_MODEL, DisplayLinearDiagram 215
CDMA, ParallelSimulations 189, 190 Grids, NbDecimals 158
CDMA, PFSchedulerCQIFactor 206 GSM, 199
CDMA, PmaxInIntraItf 203 GSM, CanEditTRXInfoAtTXLevel 200
CDMA, SharingEquallyPower 206 GSM, ExternalIncluded 195
CDMA, UseStudyCnxProba 203 GSM, FirstTRXIndex 200
CDMA, UsingPreviousIterationPowerWeight 206 GSM, MinNeighbourImportanceInAFPResults 198, 199
Clutter, OnlyVisibleClassesInInterferenceReport 161 GSM, ShowNonSynchSFHViolationsInAFPResults 199
Clutter, PerClassPercentagesRelativeToCoverageInRe- GSM, SortSubcellsAlphabetically 201
port 162 GSM, SubcellValueFixMethod 201
ClutterParams, IndoorActivity 186 GSM, TRXIndexHidden 201
Compatibility, MWEquipment_CIMIN 220 GsmLive, GsmLiveGui 171
Compression, StartSizeInMB 165 GUIUserRights, AllowSharedParameterModification 158
CoPlanning, ComputeLinkedPredictions 191 GUIUserRights, EnableMacrosAddins 157
CoPlanning, LinkedPredictionsComputationMode 191 GUIUserRights, EnableNewDocFromTemplate 157
CoPlanning, LinkSites 160 GUIUserRights, EnableZip 157
Database, AllowNullRecordsForNotNullableCustom- GUIUserRights, HidePropagationModelsFolder 158
Fields 181 IM, FilterByFrequencyBands 200
Database, CommandTimeout 182 Import, LoadKMLVectors 155
Database, DisplayTableNamesOnOpenFromDB 181 Import, WarningSameValues 155
Database, ExclusiveProvider 184 Import,ShowOptionMergeZone 155
Database, ExportTransactionMethod 182 License, 5GNR 179
Database, IntegrityChecker 180 License, 5GNR_AFP 179
Database, KeepAMCDatabaseFields 185 License, ACP_5GNR 179
Database, LogExportToDbErrors 184 License, ACP_CDMA 179
Database, OverwriteSharedFolderPath 184 License, ACP_GSM 179
Database, PromptOnArchive 183 License, ACP_LPWA 179
Database, SubCellAuditConsistency 182 License, ACP_LTE 179
Database, SubCellAuditMainValues 182 License, ACP_UMTS 179
Database, UseTransaction 184 License, ACP_WiMAX 179
DefaultFolders License, BH 179
DefaultFolders, RootFolder 168 License, CDMA 179
DefaultFolders, ATLFilesFolder 168 License, GSM 179

License, GSM_AFP 179 Neighbours, DoNotDeleteSymmetrics 193

License, IdleTime 180 Neighbours, ExcludeFilteredCellsFromNeighbourLists
License, LPWA 179 192
License, LTE 179 Neighbours, ForceSymmetryInFocusZone 191
License, LTE_AFP 179 Neighbours, RealInterSiteDistanceCondition 193
License, Measures 179 Neighbours, RepeaterInterSiteDistanceInAlloc 193
License, MW 179 OFDM_AFP, AdjacentProtection 211
License, NB-IoT 179 OFDM_SIMU, MeanNRInDB 213
License, TD-SCDMA 179 OFDM, DisplayThroughputZero 213
License, TimeBombNotice 178 OFDM, ForceSameFrequencyForCoTXCells 215
License, UMTS 179 OFDM, SecondNeighbours 211
License, WiMAX 179 OFDM, UniformIDDistribution 211
License, WiMAX_AFP 179 OFDM, UseCommonBearersOnly 209
Licenses, Live 170 OnlineMaps, BingCulture"X" 167
LOSArea, ResolutionMultFactor 187 OnlineMaps, BingKey 166
LTE, ApplyDLLoadOnPDCCHInterf 212 OnlineMaps, BingLanguage"X" 167
LTE, CASchedulingMethod 215 OnlineMaps, Name 166
LTE, CAWithinENB 214 OnlineMaps, Proxy 166
LTE, CellEdgeMethod 215 OnlineMaps, TilesCachePath 166
LTE, DisplaySignalsPerSCInPtA 209 OnlineMaps, URL 166
LTE, EIRPfromRSEPRE 212 OnlineSearch, BingKey 167
LTE, ExcludeCPFromUsefulPower 210 Pathlosses, EmbeddedByDefault 187
LTE, ExtendedServerMethodsInPredictions 213 Pathlosses, FullResyncPrivShared 162
LTE, InterNeighbourIDCollisions 210 Pathlosses,DisplayIndividualSuccessOrFailure 153
LTE, NR_CONTROL_MARGIN_MIN 213 Pathlosses,DisplayInvalidityCause 153
LTE, OldBestServerMethodForCA 215 Pathlosses,DisplayOverallSuccessOrFailure 153
LTE, SameItf_PDSCH_RS_PDCCH 212 Perfos, MaxRangeApplied 196
LTE, ServiceMBRDowngrading 213 Perfos, PtAnalysisMargin 155
LTE, ULNRControlMethod 214 Perfos, PtAnalysisNbServersDisplayed 155
LTE, ULNRControlPrecision 214 Perfos, PtAnalysisNbServersMax 154
LTE, UseABSonCellEdgeOnly 214 PlanetImport, ChangeKclutterSign 183
MajorVersionChange, EnablePartialRefreshInMigration PlanetImport, ClutterNoData 183
184 PlanetImport, SensitiveCase 183
Memory, DisplayMaximumWorkingSetSize 149 Population, ReportResolution 163
Memory, MaximumWorkingSetSize 148 Print, LogoFooterChecked 163
MITAB, ’Coordinate system definition in the header file’ Print, MaxDPI 151
153 PSC, ConstantStep 207
MITAB, DisableNormalization 160 PSC, DisplayCostValues 207
MITAB, EnableMessages 163 RasterExport, ExportBILAsESRI 87, 159
MITAB, OptimizedTABExport 160 RasterExport, GeorefWithTAB 159
MultiRAT, AllCodesAllocWithInterRATNeighbours 218 Rasterization, Improve 205
MultiRAT, UncheckTechnoChoices 218 Rasterization, MaximumSurf 205
MWCalculations, CCDP_XPIF 219 Rasterization, Precision 205
MWCalculations, HIDE_REC530_5 219 Rasterization, SurfRatio 205
MWCalculations, NewDecouplingCoSite 222 Refresh, ControlIntegrity 180
MWCalculations, PXPBDOnDualOnly 220 Refresh, TRXIntegrity 196
MWCalculations, ShieldingFactorOnWantedSignal 219 RemoteAntennas, FrozenSymbol 171
MWCalculations, UpdateOppositeHop 219 RemoteCalculation, AtollSvrPriority 177
MWChannelArrangement, DefaultConfiguration 221 RemoteCalculation, DetectTimeOut 178
MWProfile, AlwaysDrawClutters 222 RemoteCalculation, DisablePathlossPerSiteCalculation
MWReport, DefaultTemplate 222 194
MWReport, DesignSummaryCfg 221 RemoteCalculation, MultiUserDCS 178
MWReport, LinkAnalysisCfg 221 RemoteCalculation, NumberedServers 177
MWReport, LinkInterferenceCfg 221 RemoteCalculation, NumberOfProcessors 188
MWReport, LinksBudgetCfg 221 RemoteCalculation, NumberOfThreadsMicrowave 189
MWReport, LinksInterferenceCfg 221 RemoteCalculation, NumberOfThreadsNeighbour 189
MWReport, MaxNumberOfModulations 220 RemoteCalculation, NumberOfThreadsPathloss 189
MWReport, MultihopAnalysisCfg 221 RemoteCalculation, NumberOfThreadsSimulation 189
MWReport, ReflectionAnalysisCfg 221 RemoteCalculation, NumberOfThreadsStudy 189
MWReport, RequiredMarginCfg 221 RemoteCalculation, Priority 188
MWReport, SortModulationByThreshold 220 Repeaters, FrozenSymbol 171
MWReport, tab 220 SAMModel, DrawSingleElementPattern 173
Neighbours, CandidatesMaxDistanceInImportanceCal- Settings, CopyExternalResultsDialog 151
culation 193 Settings, EnableDataExchangeCommands 168
Neighbours, CompressModeEval 207 Settings, KeepFilterZoneOnRemoveFilter 168
Neighbours, DeleteOnAuditIfSourceEqualsTarget 194 Shadowing, Reliability 186
Neighbours, DistanceAzimutWeightingPercent 192 Shadowing, UseShadowing 186

Shadowing, WithSHOGain 202 Studies, SCActivesetMaxSize 208

Simulation, GlobalScalingFactorDigitsNumber 192 Studies, ShowIntervalsWithNoCoverageInReport 164
Simulation, RandomTotalUsers 192 Studies, SpecifyResolutionAfterComputation 188
Site, AddToSiteListOnDuplicate 160 Studies, UplinkLosses 208
Site, AskConfirmDeleteSite 177 Studies, UseFullHotSpotSurfaceOnReport 164
Site, Prefix 149, 218 Studies, UseThresholdForSameLayerPriorities 198
Site, ResetAltitude 161 Studies,SelectNullMarginOnly 153
SitesSymbol, Color 171 System, RestartOnImproperExit 168
SitesSymbol, FontName 171 TestMobileData, FloatingPointScramblingCodeSupport
SitesSymbol, Size 171 224
SitesSymbol, Symbol 171 TestMobileData, ImportForFilteredTransmittersOnly 224
StatusBar, ClutterPaneWidth 174 TestMobileData, NumberOfTestMobileTransmitters 223
StatusBar, DisplayClutterClass 172 TestMobileData, RecalcDist 223
StatusBar, DisplayClutterHeight 172 TestMobileData, ShowCoupleInfo 223
StatusBar, DisplayZ 172 TestMobileDataImportFmt, BCCHColumn 224
Studies, 152 TestMobileDataImportFmt, BSICColumn 224
Studies, 2GTxDiversityGain 200 TiffExport, PaletteConvention 150
Studies, AerialStudy 190 Traffic, PerClassPercentagesRelativeToCoverageInRe-
Studies, AutoLock 185 port 162
Studies, CleanMultiCellManagement 197 Transmitter, AutoSynchronizeDisplay 172
Studies, CommentsInLegend 174 Transmitter, ChangeSymbolOnSearch 172
Studies, ComputeEvenIfReadOnly 190 Transmitter, CheckImpactOnRepeaters 158
Studies, ContinueOnError 187 Transmitter, EmptySymbolWhenInactive 172
Studies, CoordSystemForTextExportIsProjection 152 Transmitter, FirstCharSuffix 150
Studies, CustomStudiesFilteredByTechno 163 Transmitter, MaximumCalculationRadius 194
Studies, EIRPfromMaxPower 192 Transmitter, Prefix 149
Studies, EnableStudyCompanionFileExport 152 Transmitter, SuffixIsNum 150
Studies, ExportOnlyVisibleLevels 164 Transmitter, Underscore 150
Studies, ExposureStudy 173 Transmitter, UpdateLossIfNoEquipment 194
Studies, MultiBandManagement 197 UMTSSimus, MaxReuseFactor 208
Studies, MultiplePlotsTipTextLines 173 Units, MeterToFeetFactor 149
Studies, NoOverlapOnBestServer 165 Units, MileToMeterFactor 149
Studies, RecomputationWarning 187 WiMAX, ExcludeCPFromUsefulPower 210
Studies, RemoveBadMultiCells 197 WiMAX, InterNeighbourPICollisions 210
Studies, ReportDecimalPlacesAbsolute 164 WiMAX, ModifiableIEEEParams 209
Studies, ReportDecimalPlacesPercent 164 WiMAX, ReplaceOPUSCwithPUSCUL 211
Studies, ReportMethod 165


Head Office US Office China Office
7 rue des Briquetiers 200 South Wacker Drive – Suite 3100 Suite 302, 3/F, West Tower, Jiadu Commercial Building,
31700 Blagnac, France Chicago, IL 60606, USA No. 66 Jianzhong Road, Tianhe Hi-Tech Industrial Zone,
Tel: +33 562 747 210 Tel: +1 312 674 4800 Guangzhou, 510665, P. R. of China
Fax: +33 562 747 211 Fax: +1 312 674 4847 Tel: +86 20 8553 8938 Fax: +86 20 8553 8285
AT340_AM_E3 www.forsk.com April 2019

Atoll

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Atoll

Hochgeladen von

Copyright:

Verfügbare Formate

Atoll

Wireless Network Engineering Software

2 Atoll and Component Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3 Distributed Calculation Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

© 2019 Forsk. All Rights Reserved. 3

4.6.1 Creating Project Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

6 Coordinate Systems and Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

7 Atoll File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

4 © 2019 Forsk. All Rights Reserved.

7.2.3 LOS File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

8 Administration and Usage Recommendations . . . . . . . . . . . . . . . . . . . . .103

9 Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

© 2019 Forsk. All Rights Reserved. 5

9.4 Content of the "Value Intervals" Predictions Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

10 Initialisation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

6 © 2019 Forsk. All Rights Reserved.

10.1.1.68 Defining MapQuest for Online Searches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167

© 2019 Forsk. All Rights Reserved. 7

10.1.6.1 Setting the Antenna Patterns Modelling Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

8 © 2019 Forsk. All Rights Reserved.

10.1.8.11 Setting Precision of the Rasterisation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204

© 2019 Forsk. All Rights Reserved. 9

10.1.11.18 Confirming a Delete Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Index of Initialisation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

10 © 2019 Forsk. All Rights Reserved.

© 2019 Forsk. All Rights Reserved. 11

Printing Help Topics

About Atoll Documentation

Contacting Technical Support

12 © 2019 Forsk. All Rights Reserved.

Forsk Head Office

© 2019 Forsk. All Rights Reserved. 13

14 © 2019 Forsk. All Rights Reserved.

1.1 Supported Technologies

1.2 Supported Operating Systems

Supported Operating Systems for Atoll 64-bit

© 2019 Forsk. All Rights Reserved. 15

◼ Microsoft Windows Server 2012

Supported Operating Systems for Atoll 32-bit

1.3 Supported Database Management Systems

Database Client Component

Microsoft Access Not needed

Oracle Oracle Client 64-bit

1.4 Recommended Hardware and Software

16 © 2019 Forsk. All Rights Reserved.

◼ "Single-user Standalone Configuration" on page 17

1.4.1 Single-user Standalone Configuration

In a single-user standalone configuration, the Atoll installation is local, i.e.:

Figure 1.1: : Single-user Standalone Configuration

Processor Core i7 at 2.5+ GHz

Storage 512 GB1 (SSD recommended)

Operating System Microsoft Windows2

1. Depends on size of locally stored data.

1.4.2 Multi-user Thick Client Configuration

In a multi-user thick client configuration, the Atoll installation is local, i.e.:

© 2019 Forsk. All Rights Reserved. 17

Figure 1.2: : Multi-user Thick Client Configuration

Atoll Workstation Atoll Database

Processor Core i7 at 2.5+ GHz Xeon E3/E5 family or equivalent

RAM 8 GB or more 8 GB or more

1. Depends on size of locally stored data.

1.4.3 Multi-user Thin Client Configuration

18 © 2019 Forsk. All Rights Reserved.

Figure 1.3: : Multi-user Thin Client Configuration