Plan Checker7v3

Plan_Checker7v3
By Dayanti Pratiwi
Was developed under:

Windows XP
MapInfo/MapBasic 7
Necessary header/column for bts table:

BTS_NAME
CI
X: Longitude
Y: Latitude
CELL_TYPE: Macro, Micro, Indoor
CELL_SYST: DCS, GSM
NUM_SECT:
#of sector 1 for single cell,
> 1 for quasi antennas
AZM1 to AZM4 (azimuth)

-2 for indoor (small square)
-1 for omni antenna (circle)
If single cell just use AZM1 and
others put 0
NCC
BCC
BCCH
TCH1 to TCH7: put 0 if not use
SIZE (optional): in meter
Necessary header/column for adjacency table (using BTS_NAME format):

SOURCE
TARGET
Company Confidential
1
2005 Nokia
Plan_Checker7v2.ppt / 2005-10-25 / DP
Plan_Checker7v3
By Dayanti Pratiwi
No need to create specific directory nor specific table name

Flexibility format data txt/xls/mdb for input table
Capable for Frequency Checker; Handover Checker; BSIC Checker; KPI Checker
Additional menu for neighbor audit
Delete/Create HO, the list of deleted/created relation will be recorded in
tabnameAudit.TAB
Mapping the KPI from different table and create the thematic on the map
Three different style of drawing the btstable for your presentation purposes
Connect the measurement data with related cell using Line Connection
Note: Please exit the tools and run again if you found problem cannot draw the
btstable, this is bugs from MapInfo7, I cannot fix it
2
2005 Nokia
3
2005 Nokia
Clover2 style
The DCS and GSM data
will be split into two
different table
Arrow style
Micro
Indoor
Clover1 style using user defined

from column SIZE value
Clover1 style
The DCS and GSM data
keep maintain in one table
SIZE = 100
Macro GSM
4
2005 Nokia
Macro DCS
Size = 300
Select the coordinate column with XY; and the projection that you use
Default projection is Longitude/Latitude in decimal degree
Follow the instruction on the dialog
Flexible for any data type (txt/xls/mdb)

The simplest one is txt format, minimize your mistakes if
you forgot to put 0 value when no data
5
2005 Nokia
Quasi omni with 4 antennas direction
indoor
6
2005 Nokia
Put 0 value if you have no data
Necessary columns are

SOURCE & TARGET, the other
columns are your own
additional data
7
2005 Nokia
You need to open the btstable first before continue

with the checker menus
8
2005 Nokia
Frequency Checker Menus:

Open window frequency checker and then select the
freq that you want to check
9
2005 Nokia
New freq will be checked
Red = co = ch55
Blue = co + 1 = ch56
Green = co 1 = ch54
10
2005 Nokia
Handover Checker Menus:

Open window HO checker; Open HO table; and then
select the relation that you want to check
11
2005 Nokia
New HO will be checked
Red = selected bts / SOURCE

Blue = adjacencies bts / TARGET
12
2005 Nokia
Select the bts that you want to add

in your neighbor list; and then
choose menu Create HO
13
2005 Nokia
After Ctr+j you will see that

the new neighbors were
added
14
2005 Nokia
Select the bts that you want to

delete in your neighbor list; and
then choose menu Delete HO
15
2005 Nokia
After Ctr+j you will see that

the old neighbors were
deleted
16
2005 Nokia
Your delete/create list result will be

saved in the new tableAudit.TAB in the
same directory with your other data
17
2005 Nokia
When you delete the adjacency

from the HO list there will be
blank rows in the adce table,
you can Packing the HO Table
to clean up the blank rows after
you finished the neighbor audit
BSIC Checker Menus:

Open window BSIC checker and then select the BSIC or
co BCCH_BSIC that you want to check
18
2005 Nokia
Check BSIC only, if you want

to check co BCCH_BSIC choose
menu
19
2005 Nokia
KPI Checker Menus:

Open window KPI checker; Open KPI table; and then
select the column kpi that you want to display
20
2005 Nokia
Column from KPI table that you

want to display will be inserted
temporarily into BTS table
If you want to modify the

previous threshold and
redraw the result
Open KPI table
You can use any data and
no need to create specific
table/columns name
21
2005 Nokia
Line Connection Menus:

Open window Line Connection; Open measurement
table (TAB format); and then draw the line connection
between bts vs measurement point using CI as
reference
22
2005 Nokia
You can use any measurement data (TOM ; TEMS ; etc)

as long as you have CI column with integer type in your
TAB table
The result will be saved in measnameLine.TAB in the

same directory
23
2005 Nokia
Note: we are using dummy data for the sample
Have a nice day
24
2005 Nokia

Plan Checker7v3

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Plan Checker7v3

Uploaded by

Copyright:

Available Formats

Plan_Checker7v3

Was developed under:

Necessary header/column for bts table:

AZM1 to AZM4 (azimuth)

Necessary header/column for adjacency table (using BTS_NAME format):

No need to create specific directory nor specific table name

Clover1 style using user defined

Follow the instruction on the dialog

Flexible for any data type (txt/xls/mdb)

Quasi omni with 4 antennas direction

Put 0 value if you have no data

Necessary columns are

You need to open the btstable first before continue

Frequency Checker Menus:

New freq will be checked

Handover Checker Menus:

New HO will be checked

Red = selected bts / SOURCE

Select the bts that you want to add

After Ctr+j you will see that

Select the bts that you want to

After Ctr+j you will see that

Your delete/create list result will be

When you delete the adjacency

BSIC Checker Menus:

Check BSIC only, if you want

KPI Checker Menus:

Column from KPI table that you

If you want to modify the

Line Connection Menus:

You can use any measurement data (TOM ; TEMS ; etc)

The result will be saved in measnameLine.TAB in the

Note: we are using dummy data for the sample

Have a nice day

You might also like