Routine Tasks

Take Hourly stats for last two days of the BSC & check for any down/fluctuating cells.
Cells which are having down time or fluctuating issues escalate to FOPs immediately.
Check BSC BH KPIs & compare it with assigned targets.
Make WCL based on cell BH which are consistently degraded or above threshold targets avoid
spikes.

Down Time/Fluctuation cases:

Down Time:

Cells which are down till last hour must be sent immediately to FOPs & also
communicated to concern FOPs person on phone for immediate resolution.
Cells which were down but currently up & its not following trend can be kept in
observation & must be check in evening.
Cells which were down between 1800 to 2200 hrs must be escalated to FOPs regardless
they are currently up or not.
Cases escalated to FOPs must be kept in a tracker FOPs Tracker, can be access @

Fluctuation Cases:

Cells having severe fluctuation especially between 1800 to 2200 hrs must be sent to
FOPs.
Seldom spikes in availability must be kept under observation if they occur outside (1800-
2200) window.
Cases escalated to FOPs must be kept in a tracker FOPs Tracker, can be access

Down TRXs:

A list of down TRXs must be shared to FOPs twice per week and should be included in
FOPs tracker.
Cases escalated to FOPs must be kept in a tracker FOPs Tracker, can be access
WCL cases:

Identify worst cells in the BSC with respect to CSSR, CDR & HSR by checking BH trend of cell BH
for last 5 days.

CSSR:

Sort out worst CSSR cases & try to find out the reason for degradation. Following are some points
to troubleshoot.
o Check CSSR is degraded due to SD blocking.
a) If yes find out in hourly trend if there is any abnormal traffic increase in that specific hour or for
some hours.
b) Check for any down sites/ fluctuating sites in that area.
c) Check if there is any occasion/protest/gathering/event in that area.
d) In case that SD blocking is consistent check for LU( location updates).
e) If LU are very high check CRO settings in order to cater it.
f) Perform SD redimension for those cells where SD blocking is high & persistent.
o Check CSSR is degraded due to TCH blocking.
a) If yes find out in hourly trend if there is any abnormal traffic increase in that specific hour or for
some hours.
b) Check for any down sites/ fluctuating sites in that area.
c) Check if there is any occasion/protest/gathering/event in that area.
d) In case that TCH blocking is consistent make sure there is no TRX down/locked in that specific
cell.
e) For persistent TCH blocking kindly check if it can be catered by Traffic sharing or by expansion.
f) If cell is at its Max Config(8 TRXs) check if band addition is possible or a new site is required.
g) Recommendation for such cases must be sent to planning team once per month so they can
check that if it is already included in their plan or not.
o Check CSSR is degraded due to Faulty TRX.
g) Check if the CSSR is degraded due to faulty TRX.
h) Check for alarms appearing on the TRX.
i) Give reset to TRX & check in next interval. If its not resolved share it with FOPs team & get it
locked.
j) Cases escalated to FOPs must be kept in a tracker FOPs Tracker, can be access
CDR:

Sort out worst CDR cases & try to find out the reason for degradation. Following are some points
to troubleshoot.
1) Check if CDR is degraded on a certain day or for some hours.
2) If yes it may be due to outages at neighboring site, compare the degraded CDR time with
outages time in the neighboring area.
3) If this is the case escalate it to FOPs to resolve the outage/fluctuation issue & mentioning
them that its causing degradation in the specific cell.
4) CDR may be increased due to a faulty radio.
5) Check for alarms appearing on the cell/radio, lock the TRX & inform FOPs to replace.
6) If CDR is high & there is no hard ware issue at the cell, then check for following some points
to improve DCR.
a) Neighbor Audit of the cell to check any missing immediate neighbor.
b) Cell is serving more than its legitimate area, can be find through TA analysis.
c) Frequency audit if majority of drops are based on quality.
d) Check for HO settings whether if HO criteria is so tight that cell cannot find a good
neighbor to HO.
e) Make Drive Test of that cell to find out on field scenario, It will help to find out
overshooting of cell, which frequencies is being interfered.
f) Discuss with any senior member in the team for any other possibilities & parameter trial
to improve DCR.

HSR:

Sort out worst HSR cases & try to find out the reason for degradation. Following are some points
to troubleshoot.
1) Check HSR is degraded due to interference on EGSM cells.
2) Check HSR is degraded due to any hard ware case (faulty TRX issue).
3) Take per neighbor relation stats & check with which relation HSR is degraded.
4) If HSR is degraded with all relation check for VSWR issue, cross sector issue, SUMA Synch
Issue(ALU Case), Check inter clock Synch (Huawei Case).
5) Check for BCCH BSIC clash in the area if found any change BSIC of the cell.
6) If HSR is degraded with any one relation perform point 4, if no CO BCCH BSIC found then
perform frequency audit, perform DT & make HO in both directions to find out actual
scenario.
7) Neighbor audit to done for check any missing relation.
8) Check if any of its first tier site is down & HO relation is degraded to tier-2 relation in such
case send case to FOPs to make this site is up.
9) Discuss with any senior member in the team for any other possibilities & parameter trial to
improve HSR.
 Alrams & History of Cases:

BSC owner is responsible for keeping a track record of the cases & history of every cells in a
sheet so that in case of his absence or BSC shuffle any other engineer can track the issues
smartly. This sheet should be placed at the server & can be accessible by RAN south tea.
Sheet name should be with the name of BSC e.g KHIBSC24.

Sheet must contain three TABs.

TAB1: (History)

TAB1 should be named with Case history.

This sheet must contain following columns.

Date Close
Site Cell Alarms Issue
Open date

TAB2: (WAP)
Any parameter change in the BSC must be done through WAP.
Approval is necessary to be taken from the Manager & in his absence from team
leads.
Following columns must be included in this TAB.

Reason
Parameter Short Impact On Pre Post
Date Cell/BSC for Result
Name Description (CDR/CSSR/HSR) Value Value
change

TAB3:(FOPs Tracker)
FOPs tracker is shared with FOPs team every Monday& their feedback is received
on Thursday.
Weekly meeting is held on Friday to discuss all open cases. Therefore this tracker
must be updated on regular basis.
Following columns must be included in this TAB.

Week Site BSC KPI Escalated Escalated FOPs

Num ID BSC Owner Traffic Drops Affected Issue On To Feedback Status Priority
System Folders:

Go to following link.

172.22.11.161\RAN South\

In RAN South there will be a folder namedBSCs where you can put your tracker of your BSC mentioned
above .( 172.22.11.161\RAN South\BSCs\KHIBSC24.xls)

There are some other folders in RAN South which are mentioned below.