Version 3.3.

OSS Importable File Formats

Technical Note

TN046
Atoll 3.3.2 OSS Importable File Formats © Forsk 2017

2
TN046 Atoll 3.3.2 OSS Importable File Formats

1 OSS Importable File Formats

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.
The Atoll Live module for GSM can import the following OSS measurement data:
• OSS interference matrix (IM) data, to be integrated into the AFP process along with the IM scope.
• OSS traffic count data, which improves AFP quality and allows traffic-based channel and TRX number optimisations.
• OSS handover data, for updating neighbour relations, neighbour importance, exceptional pair information and defines
the work area for the AFP.
Only text file formats can be imported into the Atoll Live module. Binary formats cannot be read. This document describes
the file format requirements that are expected by the Atoll Live module.

The specifications of data that is exported by OSS systems is subject to change by the
vendors of those systems. For detailed information about OSS system data formats, refer
to the documentation provided by the vendor of your OSS system.

2 File Import Requirements

There are a several requirements for the add-in to properly import interference measurement files:
• In the Atoll document, the BCCH frequency plan as well as the BSIC plan in the ATL must be up-to-date. This is because
the add-in uses BSIC-BCCH identifier to identify interferers.
• All active transmitters must be active in Atoll and all inactive transmitters must be inactive in Atoll.
• All the audits in Atoll must be run and should return a good result.
The add-in includes support for the following OSS measurement files:
• Huawei MR interference files.
• Ericsson ICDM interference and traffic files.
• NSN interference and traffic files.
• ZTE interference and traffic files.
The add-in analyses headers of imported files to automatically determine the file type.

2.1 Huawei MR Files

The OSS Importable File Formats add-in can import Huawei MR interference files exported with a tab or comma separator.
Each file is expected to contain multiple one-hour time sessions. The neighbour list being different in each session, the add-
in can explore extra-neighbour interferences.
For Huawei MR files, the LABEL field contains the identifiers of the transmitters in Atoll.
• If the identifiers are identical to the transmitter names in Atoll, including upper-case and lower-case characters, then
the correspondence is performed automatically.
• If the identifiers differ from the transmitter names in Atoll, then you must create a custom field in the Transmitter
table of the Atoll document named OMC_CELLID that contains the name of the transmitter as it appears in the LABEL
field of the Huawei MR file.
Each Huawei MR file generates a new interference matrix in Atoll.

2.1.1 Huawei MR File Format Details

Huawei MR files are tabulated text files that use a tab or a comma separator. There may be several variants of the file format.
The information in this section is provided as an example.
Files start with a header line, which contains the field names in the following columns:
• Column 1: Start time
• Column 2: Period
• Column 3: NE Name
• Column 4: GCELL_NCELL. The value of this field must start with “LABEL=V(i), CellIndex=…”. V(i) is used to identify the
victim for which the information is given in the i’th line
• Column 5: BCCH
• Column 6: BCC,NCC
• Column 7: NCC
• Column 8: AS360:Mean Strength of Signals in Neighbor Cells(dBm)

3
Atoll 3.3.2 OSS Importable File Formats © Forsk 2017

• Column 9: AS362:Mean Signal Strength Difference Between Serving Cell and Neighbor Cell(dBm)
• Column 10: S360:Strength of Signals in Neighbor Cells(dBm)
• Column 11: S361:MRs of Neighbor Cells(none)
• Column 12: S362:Strength of Signals in Serving Cells(dBm)
• Column 13: S363:Number of MRs in Which the Signal Strength Difference Between the Serving Cell and the Neighbor
Cell Is Smaller Than the Neighbor Cell Interference Level Threshold 1(none)
• Column 14: S364:Number of MRs in Which the Signal Strength Difference Between the Serving Cell and the Neighbor
Cell Is Greater Than the Neighbor Cell Interference Level Threshold 1(none)
• Column 15: S365:Number of MRs in Which the Signal Strength Difference Between the Serving Cell and the Neighbor
Cell Is Greater Than the Neighbor Cell Interference Level Threshold 2(none)
• Column 16: S366:Number of MRs in Which the Signal Strength Difference Between the Serving Cell and the Neighbor
Cell Is Greater Than the Neighbor Cell Interference Level Threshold 3(none)
• Column 17: S367:Number of MRs in Which the Signal Strength Difference Between the Serving Cell and the Neighbor
Cell Is Greater Than the Neighbor Cell Interference Level Threshold 4(none)
• Column 18: S368:Number of MRs in Which the Signal Strength Difference Between the Serving Cell and the Neighbor
Cell Is Greater Than the Neighbor Cell Interference Level Threshold 5(none)
• Column 19: S369:Number of MRs in Which the Signal Strength Difference Between the Serving Cell and the Neighbor
Cell Is Greater Than the Neighbor Cell Interference Level Threshold 6(none)
• Column 20: S370:Number of MRs in Which the Signal Strength Difference Between the Serving Cell and the Neighbor
Cell Is Greater Than the Neighbor Cell Interference Level Threshold 7(none)
• Column 21: S371:Measurement Reports with Signal Strength Difference Between Neighbor Cell and Serving Cell
Greater Than Relative Level Threshold(none) (optional)
• Column 22: S372:Measurement Reports with Signal Strength of Neighbor Cell Greater Than Absolute Level
Threshold(none) (optional)
• Column 23: S386:Number of MRs on Competitive Cell (Receive Level Rank 0)(none) (optional)
• Column 24: S387:Number of MRs on Competitive Cell (Receive Level Rank 1)(none) (optional)
• Column 25: S388:Number of MRs on Competitive Cell (Receive Level Rank 2)(none) (optional)
• Column 26: S389:Number of MRs on Competitive Cell (Receive Level Rank 3)(none) (optional)
• Column 27: S390:Number of MRs on Competitive Cell (Receive Level Rank 4)(none) (optional)
• Column 28: S391:Number of MRs on Competitive Cell (Receive Level Rank 5)(none) (optional)
• Column 29: S392:Number of MRs on Competitive Cell (Receive Level Rank 6)(none) (optional)
• Column 30: S393:Number of MRs on Competitive Cell (Receive Level Rank 7)(none) (optional)
• Column 31: S394:Number of MRs in Which the Signal Strength Difference Between the Serving Cell and the Neighbor
Cell Is Smaller Than the Neighbor Cell Interference Level Threshold 0(none) (optional)

There may be multiple variants of Huawei MR with slightly different file formats. The
format described in this section is provided as an indication only.

In this variant of the Huawei file format, columns 1 to 20 are mandatory and must be in the specified order. The other fields
are optional. The fields BCCH, BCC,NCC and NCC are used to identify the cells.
Lines before the header are not ignored.

2.1.2 Huawei TCHF/TCHH Traffic Files

Huawei traffic files are tabulated text files that use a tab or a comma separator. There may be several variants of the file
format. The information in this section is provided as an example.
Files start with a header line, which contains the field names in the following columns:
• Column 1: Start Time
• Column 2: Period
• Column 3: NE Name
• Column 4: Cell
• Column 5: TRX
• Column 6: S4100B:Number of MRs on Downlink TCHF (Receive Level Rank 0 and Receive Quality Rank 0) (None)
• Column 7: S4101B:Number of MRs on Downlink TCHF (Receive Level Rank 0 and Receive Quality Rank 1) (None)
• Column 8: S4102B:Number of MRs on Downlink TCHF (Receive Level Rank 0 and Receive Quality Rank 2) (None)
• Column 9: S4103B:Number of MRs on Downlink TCHF (Receive Level Rank 0 and Receive Quality Rank 3) (None)
• Column 10: S4104B:Number of MRs on Downlink TCHF (Receive Level Rank 0 and Receive Quality Rank 4) (None)
• Column 11: S4105B:Number of MRs on Downlink TCHF (Receive Level Rank 0 and Receive Quality Rank 5) (None)
• Column 12: S4106B:Number of MRs on Downlink TCHF (Receive Level Rank 0 and Receive Quality Rank 6) (None)
• Column 13: S4107B:Number of MRs on Downlink TCHF (Receive Level Rank 0 and Receive Quality Rank 7) (None)
• Column 14: S4110B:Number of MRs on Downlink TCHF (Receive Level Rank 1 and Receive Quality Rank 0) (None)
• Column 15: S4111B:Number of MRs on Downlink TCHF (Receive Level Rank 1 and Receive Quality Rank 1) (None)

4
TN046 Atoll 3.3.2 OSS Importable File Formats

• Column 16: S4112B:Number of MRs on Downlink TCHF (Receive Level Rank 1 and Receive Quality Rank 2) (None)
• Column 17: S4113B:Number of MRs on Downlink TCHF (Receive Level Rank 1 and Receive Quality Rank 3) (None)
...
• Column 69: S4177B:Number of MRs on Downlink TCHF (Receive Level Rank 7 and Receive Quality Rank 7) (None)

There may be multiple variants of Huawei MR with slightly different file formats. The
format described in this section is provided as an indication only.

In this variant of the Huawei file format, columns 1 to 20 are mandatory and must be in the specified order. The other fields
are optional. The fields BCCH, BCC,NCC and NCC are used to identify the cells.
Lines before the header are not ignored.

2.1.3 Huawei HO Handover Files

Huawei handover files are tabulated text files that use a tab or a comma separator. There may be several variants of the file
format. The information in this section is provided as an example.
Files start with a header line, which contains the field names in the following columns:
• Column 1: Result Time
• Column 2: Object Name
• Column 3: H370c:Outgoing Inter-Cell Handover Requests (None)
• Column 4: H371A:Outgoing Inter-Cell Handover Commands (Uplink Quality) (None)
• Column 5: H371B:Outgoing Inter-Cell Handover Commands (Downlink Quality) (None)
• Column 6: H371C:Outgoing Inter-Cell Handover Commands (Uplink Strength) (None)
• Column 7: H371D:Outgoing Inter-Cell Handover Commands (Downlink Strength) (None)
• Column 8: H371E:Outgoing Inter-Cell Handover Commands (Timing Advance) (None)
• Column 9: H371F:Outgoing Inter-Cell Handover Commands (Better Cell) (None)
• Column 10: H371G:Outgoing Inter-Cell Handover Commands (Load) (None)
• Column 11: H371H:Outgoing Inter-Cell Handover Commands (Rapid Level Drop) (None)
• Column 12: H371I:Outgoing Inter-Cell Handover Commands (MSC Intervention) (None)
• Column 13: H371J:Outgoing Inter-Cell Handover Commands (OM Intervention) (None)
• Column 14: H371K:Outgoing Inter-Cell Handover Commands (Directed Retry) (None)
• Column 15: H371L:Outgoing Inter-Cell Handover Commands (Other Causes) (None)
• Column 16: H371:Outgoing Inter-Cell Handover Commands (None)
• Column 17: H372A:Failed Outgoing Inter-Cell Handovers (Uplink Quality) (None)
• Column 18: H372B:Failed Outgoing Inter-Cell Handovers (Downlink Quality) (None)
• Column 19: H372C:Failed Outgoing Inter-Cell Handovers (Uplink Strength) (None)
• Column 20: H372D:Failed Outgoing Inter-Cell Handovers (Downlink Strength) (None)
• Column 21: H372E:Failed Outgoing Inter-Cell Handovers (Timing Advance) (None)
• Column 22: H372F:Failed Outgoing Inter-Cell Handovers (Better Cell) (None)
• Column 23: H372G:Failed Outgoing Inter-Cell Handovers (Load) (None)
• Column 24: H372H:Failed Outgoing Inter-Cell Handovers (Rapid Level Drop) (None)
• Column 25: H372I:Failed Outgoing Inter-Cell Handovers (MSC Intervention) (None)
• Column 26: H372J:Failed Outgoing Inter-Cell Handovers (OM Intervention) (None)
• Column 27: H372L:Failed Outgoing Inter-Cell Handovers (Other Causes) (None)
• Column 28: H372P:Failed Outgoing Inter-Cell Handovers (Directed Retry) (None)
• Column 29: H372:Failed Outgoing Inter-Cell Handovers (None)
• Column 30: H373A:Successful Outgoing Inter-Cell Handovers (Uplink Quality) (None)
• Column 31: H373B:Successful Outgoing Inter-Cell Handovers (Downlink Quality) (None)
• Column 32: H373C:Successful Outgoing Inter-Cell Handovers (Uplink Strength) (None)
• Column 33: H373D:Successful Outgoing Inter-Cell Handovers (Downlink Strength) (None)
• Column 34: H373E:Successful Outgoing Inter-Cell Handovers (Timing Advance) (None)
• Column 35: H373F:Successful Outgoing Inter-Cell Handovers (Load) (None)
• Column 36: H373G:Successful Outgoing Inter-Cell Handovers (MSC Intervention) (None)
• Column 37: H373H:Successful Outgoing Inter-Cell Handovers (OM Intervention) (None)
• Column 38: H373I:Successful Outgoing Inter-Cell Handovers (Better Cell) (None)
• Column 39: H373J:Successful Outgoing Inter-Cell Handovers (Rapid Level Drop) (None)
• Column 40: H373K:Successful Outgoing Inter-Cell Handovers (Directed Retry) (None)
• Column 41: H373L:Successful Outgoing Inter-Cell Handovers (Other Causes) (None)
• Column 42: H373:Successful Outgoing Inter-Cell Handovers (None)
• Column 43: H374A:Outgoing Inter-Cell Handover Requests (Uplink Quality) (None)
• Column 44: H374B:Outgoing Inter-Cell Handover Requests (Downlink Quality) (None)

5
Atoll 3.3.2 OSS Importable File Formats © Forsk 2017

• Column 45: H374C:Outgoing Inter-Cell Handover Requests (Uplink Strength) (None)

• Column 46: H374D:Outgoing Inter-Cell Handover Requests (Downlink Strength) (None)
• Column 47: H374E:Outgoing Inter-Cell Handover Requests (Timing Advance) (None)
• Column 48: H374F:Outgoing Inter-Cell Handover Requests (Load) (None)
• Column 49: H374G:Outgoing Inter-Cell Handover Requests (MSC Intervention) (None)
• Column 50: H374H:Outgoing Inter-Cell Handover Requests (OM Intervention) (None)
• Column 51: H374I:Outgoing Inter-Cell Handover Requests (Better Cell) (None)
• Column 52: H374J:Outgoing Inter-Cell Handover Requests (Rapid Level Drop) (None)
• Column 53: H374K:Outgoing Inter-Cell Handover Requests (Directed Retry) (None)
• Column 54: H374L:Outgoing Inter-Cell Handover Requests (Other Causes) (None)
• Column 55: H375A:Outgoing Inter-Cell Handover Fail Reconn Success (None)
• Column 56: H375B:Outgoing Inter-Cell Handover Fail Reconn Fail (None)
• Column 57: H375C:Number of Outgoing Inter-Cell Handover Requests (Frequency Offset Handover) (None)
• Column 58: H375D:Number of Outgoing Inter-cell Handover Command Send Times (Frequency offset handover)
(None)
• Column 59: H375E:Number of Successful Outgoing Inter-Cell Handovers (Frequency Offset Handover) (None)
• Column 60: H375F:Number of Failed Outgoing Inter-cell Handovers (Frequency Offset Handover) (None)
• Column 61: H375G:Number of Outgoing Inter-cell Handover Requests (Quick PBGT Handover) (None)
• Column 62: H375H:Number of Outgoing Inter-cell Handover Command Send Times (Quick PBGT Handover) (None)
• Column 63: H375I:Number of Successful Outgoing Inter-cell Handovers (Quick PBGT Handover) (None)
• Column 64: H375J:Number of Failed Outgoing Inter-cell Handovers (Quick PBGT Handover) (None)
• Column 65: RH373:Outgoing Inter-Cell Handover Success Rate (%)
In this variant of the Huawei file format, columns 1 to 29 are mandatory and must be in the specified order. The other fields
are optional.
Lines before the header are not ignored.

2.2 Ericsson ICDM Files

The OSS Importable File Formats add-in can import ICDM (Inter Cell Dependency Matrix) files from the Ericsson FAS
application, which contain the percentage of co-channel interfered traffic and the percentage of adjacent channel interfered
traffic, for each victim-interferer pair. These files can be exported for one BSC or several BSCs, and for a period of time
between two dates.
Ericsson ICDM files are exported in a folder, which contains an .msmt file and various other files. During the import, the
Ericsson ICDM files must all be located in the same directory. At least one .msmt file must be imported. The add-in includes
the accompanying files automatically.
For Ericsson ICDM files , the second half of the text field of each victim and interferer contains the identifier of the transmitter
in Atoll.
• If the identifiers are identical to the transmitter names in Atoll, including upper-case and lower-case characters, then
the correspondence is performed automatically.
• If the identifiers differ from the transmitter names in Atoll, then you must create a custom field in the Transmitter
table of the Atoll document named OMC_CELLID that contains the name of the transmitter as it appears in the second
half of the text field of each victim and interferer in the Ericsson ICDM file.
For Ericsson ICDM files, the interference is provided in traffic units. The add-in automatically incorporates the additional traffic
information from the files that accompany the .msmt file.
Each Ericsson ICDM file generates a new interference matrix in Atoll.

2.2.1 Ericsson ICDM File Format Details

Ericsson ICDM files are tabulated text files that use a tab or a comma separator. Each file must contain a header line, which
contains the field names in the following columns:
• Column 1: Cell
• Column 2: Interferer
• Column 3: CoChannelInterferedTraffic(%)
• Column 4: AdjChannelInterferedTraffic(%)
• Column 5: NoSamples (optional)
• Column 6: OtherBandFactor (optional)
• Column 7: CellType (optional)
• Column 8: Distance(km) (optional)
• Column 9: Notes (optional)
• Column 10: NeighbourOrder (optional)
• Column 11: RecTime(minutes) (optional)

6
TN046 Atoll 3.3.2 OSS Importable File Formats

Columns 1 to 4 are mandatory and must be in specified order. The other fields are optional. If available, the fields
"RecTime(minutes)" and "NoSamples" are used to improve the reliability of the import and the field "CellType" is used to
ignore the “overlayed” records.
Lines before the header are ignored.

Figure 1: Ericsson ICDM file example

2.3 NSN Files

The OSS Importable File Formats add-in can import multiple NSN interference and traffic files, which includes DAC, CF, and RX
files. The files must all be located in the same directory and must all be selected at once. At least one DAC file must be
imported.
• If only a DAC file is imported, then the add-in generates an IM of type "RXLEV OMC Statistics (between neighbors
only)". The IM scope will not be complete CF files are not imported with the DAC file.
• If DAC and CF files are imported, then the add-in generates an IM of type "RXLEV OMC Statistics (+ neighbor
extension)".
• RX files are not mandatory but will increase the quality of the generated interference matrix.
For NSN files, the BTS_NAME field of the DAC file contains the identifiers of the transmitters in Atoll..
• If the identifiers are identical to the transmitter names in Atoll, including upper-case and lower-case characters, then
the correspondence is performed automatically.
• If the identifiers differ from the transmitter names in Atoll, then you must create a custom field in the Transmitter
table of the Atoll document named OMC_CELLID that contains the name of the transmitter as it appears in the
BTS_NAME field of the DAC file.
Multiple DAC files generate a single IM, and therefore NSN files cannot be imported with Huawei, Ericsson, or ZTE files in the
same operation.
When the required number of TRXs is different from actual number of TRXs the traffic load is adapted according to the number
of required TRXs.

2.3.1 NSN File Format Details

NSN DAC files are tabulated text files that use a tab or a comma separator. At least one DAC file is mandatory in a set of NSN
files. Each file must contain a header line, which contains the field names in the following columns:
• Column 1: DATE
• Column 2: PERIOD_START_TIME
• Column 3: DURATION
• Column 4: BTS_INT_ID
• Column 5: BSC_NAME
• Column 6: BTS_NAME
• Column 7: BTS_ID
• Column 8: NCC
• Column 9: BCC
• Column 10: BCCH
• Column 11: DB_VALUE_LOW
• Column 12: DB_VALUE_HIGH
• Column 13: AVE_DL_SIG_STR_SERV_CELL_SUM (not used)
• Column 14: AVE_DL_SIG_STR_SERV_CELL_DEN (not used)
• Column 15: STD_DEV_OF_SERV_CELL (not used)
• Column 16: AVE_DL_SIG_STR_ADJ_CELL
• Column 17: STD_DEV_OF_ADJ_CELL
• Column 18: NBR_OF_SAMPLES_IN_CLASS_1
• Column 19: NBR_OF_SAMPLES_IN_CLASS_2
• Column 20: S370:NBR_OF_SAMPLES_IN_CLASS_3

7
Atoll 3.3.2 OSS Importable File Formats © Forsk 2017

Figure 2: NSN DAC file example

NSN CF files are tabulated text files that use a tab or a comma separator. A CF file is not mandatory in a set of NSN files, but
the imported results will be poor if it is missing. Each file must contain a header line, which contains the field names in the
following columns:
• Column 1: DATE
• Column 2: PERIOD_START_TIME
• Column 3: DURATION
• Column 4: BTS_INT_ID
• Column 5: BSC_NAME
• Column 6: BTS_NAME
• Column 7: BTS_ID
• Column 8: NCC
• Column 9: BCC
• Column 10: BCCH
• Column 11: DB_VALUE_LOW
• Column 12: DB_VALUE_HIGH
• Column 13: AVE_DL_SIG_STRENGTH
• Column 14: STANDARD_DEVIATION
• Column 18: NBR_OF_SAMPLES_IN_CLASS_1
• Column 19: NBR_OF_SAMPLES_IN_CLASS_2
• Column 20: NBR_OF_SAMPLES_IN_CLASS_3

Figure 3: NSN CF file example

NSN RX files are tabulated text files that use a tab or a comma separator. An RX file is not mandatory in a set of NSN files. Each
file must contain a header line, which contains the field names in the following columns:
• Column 1: BSC_NAME
• Column 2: BTS_NAME
• Column 3: START
• Column 4: STOP
• Column 5: PERIOD_DURATION
• Column 6: BTS_ID
• Column 7: TRX_ID
• Column 8: BSC_INT_ID
• Column 9: BTS_INT_ID
• Column 10: TRX_INT_ID
• Column 11: CLASS _UPPER _RANGE
• Columns 12 to 19: FREQ_UL_QUAL0 to FREQ_UL_QUAL7
• Column 20 to 27: REQ_DL_QUAL0 to FREQ_DL_QUAL7

8
TN046 Atoll 3.3.2 OSS Importable File Formats

Figure 4: NSN RX file example

All columns except those specified "not used" are mandatory and must be in the specified order. Lines before the header are
ignored.

2.4 ZTE Files

The OSS Importable File Formats add-in can import multiple ZTE interference and traffic files, which includes ZTE_CI and
optionally ZTE_RX files. The files must all be located in the same directory and must all be selected at once. At least one ZTE_CI
file must be imported.
• When ZTE_CI files are imported, the add-in generates an IM of type “RXLEV OMC Statistics (+ neighbor extension)”.
• If ZTE_RX files are imported, the add-in updates the traffic load figures, the half rate ratio, and checks that the layer
configuration is correct.
For ZTE files, the transmitter name in Atoll should be composed of 4 numbers, separated by an underscore. For example, if
the OSS identifies the transmitter with omcrid=1, bscid=2, siteid=3, and cellid=4, then the transmitter name in Atoll should be
"1_2_3_4".
• If the identifiers are identical to the transmitter names in Atoll, then the correspondence is performed automatically.
• If the identifiers differ from the transmitter names in Atoll, then you must create a custom field in the Transmitter
table of the Atoll document named OMC_CELLID that contains the name of the transmitter under the form "1_2_3_4".
Multiple ZTE files generate a single IM, and therefore ZTE files cannot be imported with Huawei, NSN, or Ericsson files in the
same operation.

The add-in can only import ZTE traffic files if the entire frequency plan is up to date. This
means that the TRX table must contain a TRX record, including TCH and BCCH for each
TRX in the network.

When the required number of TRXs is different from actual number of TRXs the traffic load is adapted according to the number
of required TRXs.

2.4.1 ZTE File Format Details

ZTE_CI files are tabulated text files that use a comma or a semicolon separator. At least one ZTE_CI file is mandatory in a set
of ZTE files. Each file must contain a header line, which contains the field names in the following columns:
• Column 1: omcrid
• Column 2: bscid
• Column 3: siteid
• Column 4: cellid
• Column 5: mmr
• Column 6: bcch
• Column 7: bsic
• Column 8: time
• Column 9: sn
• Column 10 to 41: c0 to c31
ZTE_RX files are tabulated text files that use a comma or a semicolon separator. Each file must contain a header line, which
contains the field names in the following columns:
• Column 1: omcrid
• Column 2: bscid

9
Atoll 3.3.2 OSS Importable File Formats © Forsk 2017

• Column 3: siteid
• Column 4: cellid
• Column 5: Link
• Column 6: Layer
• Column 7 to 15: RXQ0 to RXQ7
• Column 16 to 80: RxLev0 to RxLev 63

10
TN046 Atoll 3.3.2 OSS Importable File Formats

11
 • 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

TN046 www.forsk.com July 2017