Notes for scft

Document No : Samsung/WCC2/SCFT Quality Assurance/Guidelines/2015/07

Prepared By

Arjun Anand ( WCC2 & SCFT QA Engineer)

Reviewed by

Dhruvrajsinh Rana (WCC2 In charge / Central SCFT QA Manager)

Vikrant Tawade (National SCFT Manager)

Approved by

Satyendra Kumar Singh (Head- Deployment)

Distribution List:

• RRMs

• Circles RF leads & Circle Heads.

• HQ SCFT Team.

• SCFT Quality Assurance Team and NEO Team

Guidelines and Recommendations for SCFT

Version 1.0

1

INDEX:

1. Purpose and Objectives.

1.1. Purpose.

1.2. Reasons for SCFT Quality Implementation.

1.3. Objectives.

2. Guidelines.

2.1. Guidelines for Circles.

2.2. Guidelines for Central SCFT Optimizers.

2.3. Guidelines for Accepting Avg. UL/DL Throughputs Circles &

Central SCFT Team.

2.4. Guidelines for WCC2 Quality Assurance Team.

3. SCFT WCC2 Process Matrix.

4. SCFT Quality Escalation Matrix.

4.1. For Backhaul Issue/GTP Losses support.

4.2. For Actix One Issues support.

4.3. For FTP related Issues support.

4.4. For SCFT On field issues support.

2

1. Purpose and Objectives.

1.1. Introduction & Purpose.

Objectives and quality guidelines for SCFT is mandatory to be considered and to

be implemented at all levels of operations. Quality assurance is the key role in

execution of WCC for SCFT completion.

Purpose to release this guideline is to ensure the minimum errors in validation of

SCFT Reports. It will ensure the precautions and implementations of effective

methods to improve the quality of SCFT completion at the Circle/Zonal level as

well as the National level, so as to accelerate and increase the percentile of WCC

Approval. This is possible only when errors, lack of co-ordination, etc. will be

overcome and updated guidelines will be shared uniformly to all the Solpars,

Circle Head, RF Optimizers, RRMs, WCC Quality Assurance Team.

1.2. Reasons for SCFT Quality Implementation.

DL/UL throughput issues.

Main KPI failure issues ( Coverage objective ,Single Sector Swap, VoLTE call

Test, UE attach, Handover)

Re-drives.

Excessive or less drive issues.

Non-referral BSP & drive routes before conducting SCFT drive.

No pre-check to Backhaul Issue, GTP Losses, Alarm status, neighbor site

status (ON/OFF).

Azimuth and Tilt issues impacting main KPIs and Throughputs.

Lack of coordination with Field Engineers.

3

Mechanical Tilt must be 0o for all the eNBs before accepting the SCFT

Reports.

1.3. Objectives.

Avg. DL-UL throughput should be considered as main KPI effective from

16-June-2015.

For 2.3G:

Avg. DL throughput greater than/equal to 15MBPS, and

Avg. UL throughput greater than/equal to 1 MBPS

is only acceptable otherwise reject.

For 1.8G:

Avg. DL throughput greater than/equal to 5MBPS, and

Avg. UL throughput greater than/equal to 2.5 MBPS

is only acceptable otherwise reject.

Main KPI failures like

PROBLEM:

Coverage objective failure(COF) due to less than 80% samples

collected in main BSP of respective sectors.

CAUSE:

a.) Due to wrong PCI samples or poor RSRP collected within main BSP.

b.) Inaccessible/non-drivable roads for collecting samples.

RESOLUTION/HANDLING:

a.) BSP should be referred before conducting the SCFT drive.

b.) Drive route should be studied before conducting the SCFT drive.

4

c.) Samples should be collected within main BSP for respective eNB.

d.) Important roads should not be missed.

PROBLEM:

Sector swap KPI failure due samples more than 50% collected in

other sector BSPs.

CAUSE:

a.) Excessive drive done on the periphery of main BSP.

b.) Excessive drive in null zone b/w the sectors.

c.) Less separation b/w sectors.

d.) More samples collected out of BSP.


a.) BSP should be referred before conducting the SCFT drive.

b.) Drive route should be studied before conducting the SCFT drive.

c.) Samples should be collected within main BSP for respective eNB.

PROBLEM:

Handover KPI failure b/w the sectors.

CAUSE:

a.) Sectors not covered properly.

b.) Alarm ON if any.

c.) HO not defined on enB.


a.) Drive clockwise & anticlockwise to meet HO.

b.) Pre-check the alarm from LSMR.

c.) Ensure the HO defined within PCIs.

5

PROBLEM:

VoLTE calls KPI failure & UE attach KPI failure.

CAUSE:

a.) UE functioning issue.

b.) Improper PCI latching, etc.

c.) IMS/Core registration failure.

d.) HW/SW/Link Issues.


a.) Ensure proper PCI latch.

b.) Need to ensure UE is working proper before SCFT.

PROBLEM:

Low Avg. UL and Avg. DL throughputs.

CAUSE:

a.) FTP space not available.

e.) Backhaul and Packet Losses.

f.) Alarm running on site.

g.) Excessive drive at the periphery of main BSP.

h.) Excess drive done in null zone.


a.) Pre check Alarm status, Backhaul Issue, Packet Losses and FTP space

status before SCFT.

b.) Refer hard copy of BSP, and study the drive route map before SCFT.

Plan SCFT drive to be executed in first time right (FTR), just to avoid re-

drives.

6

Ensuring these objectives implementation on the front will improve the

Quality of SCFT. These objectives will ensure the acceleration in WCC2 process

to the end point. Issues will be minimum; SCFT validation ratio will be

improved. Main objective to implement SCFT QUALITY GUIDELINES is to bring

the rejections to null point.

2. Guidelines.

Implementation of quality guidelines is to be processed and to be distributed

uniformly and at all the levels of Operations, so as to extract the best result.

2.1 Guidelines for Circles.

ISSUE ACTION TO BE TAKEN

BY CIRCLE ACCEPTANCE

CRITERIA/EXCLUSIONS LOCAL RJIL APPROVAL

1. Coverage Objective fail

1.)Drive in complete BSP area. 2.)Don’t do excessive drive in periphery of BSP. 3.)Important roads should not be missed. 4.)Circle Head/SCFT Lead/SCFT Coordinators ensure that Solpars carry BSPs hard copy & drive routes before conducting SCFT drive.

No exclusion if fails.

For cases like road blockages,

inaccessible roads, Circle team

ensures instructing the DT

Engineers to collect the proper

snapshot with GPS Lat./Long.,

BSP plot, Google snapshots,

proofing the scenario and for

same mail approval from RJIL

CTO with SAP ID can be given.

2. Handover failure.

1.)Do walk test below site. 2.)Drive clockwise & anticlockwise to meet HO. 3.)Do neighbor check from LSMR before SCFT.

No exclusion if fails. No RJIL Approval if fails.

7

3. Sector Swap failure.

1.)Drive more roads in main lobe to improve coverage samples. 2.)Do not drive excessively in null zone and periphery of the main BSP. 3.)Pre-check the site plan, and accordingly cover the roads to avoid azimuth mismatch issues.

Exclusion available if sector swap fails in only

1 sector (excluding azimuth mismatch

issues).Need to give reasonable justification

along with BSP plots and Google snapshots.

No exclusion if fails in more than 1 sector.

No RJIL Approval if fails in more than 1 sector.

4. VoLTE MtoM Call failure

1.)Need to ensure UE is working proper before SCFT.

2.)Should stand below the enB within 5m radius, ensure the proper PCI latch, and then carry out the test.


5. UE attach failure.

1.)Need to ensure UE is working proper before SCFT. 2.)Should stand below the enB within 5m radius, ensure the proper PCI latch, and then carry out the test.


6. Cell Overshooting and Undesired lobes failure.

1.)Avoid excessive drive in periphery of main BSP. 2.)Pre-check the neighbor site is turned OFF. 3.)Ensure the M/E Tilts according to ATP11A.

Exclusion available for COS and USL. Can be

justified providing the failure sectors details

with reasonable remarks.

No RJIL Approval required.

8

7. Low UL/DL throughputs

1.)Ensure pre-checks for any Backhaul Issue, GTP Losses, Neighbor site status (ON/OFF), Alarm ON if any before SCFT. 2.)Avg. DL and Avg. UL throughput for both 2.3G & 1.8G must meet the threshold. (For throughputs target details: Refer section 2.3) 3.) Ensure pre-check for FTP space availability before SCFT.


Circle Team need to ensure to execute the SCFT Drive first time right(FTR)

just to minimize requirement of re-drive.

If any Lat/Long of eNB is mismatching the actual plan of Site Forge, should

be escalated at the same time to the responsible team.


Reports.

2.2 Guidelines for SCFT Field Engineer.

Field Engineer needs to ensure to carry safety equipment before SCFT.

Ensure pre-check to UE and Tools performance before SCFT.

Carry hard copies of BSP and refer drive routes before SCFT.

Collect Alarm status for eNB before SCFT.

Ensure to cover main BSP to collect good samples.

Excessive drive at the periphery of main BSP should not be carried out.

Do walk test wherever necessary if drivable roads is inaccessible/missing.

9

Capture the snaps with GPS Lat/Long for road blockages & in accessible

roads for demonstration and intimate the same immediately to Circle

Head/RF Lead/SCFT Coordinator.

Need to ensure to upload all the log files (if auto upload not functioning)

properly. Nomenclature for log files should be actual and proper.


Reports.

Handling of Log files

After completion of SCFT Drive, FE needs to upload all log files immediately

and turn OFF the UE and only then should leave the site.

*Note:

SCFT Reports will not trigger on Site Forge/Actix if

Incomplete log files available.

Nomenclature for files is improper. So, Naming the log files should be

correct.

FE will ensure that all log files

(.drx format) are uploaded

through XCAL to FMS

Actix One will generate SCFT

report from log files will be

uploaded on Site Forge.

FMS will convert all log files from .drx

to .drm format and will upload the files

to Actix One server

10

2.3 Guidelines for Central SCFT Optimizers.

SCFT Optimizers have to effectively validate the SCFT Reports. They are

responsible for providing proper analysis remarks for each case where

justification is required. Below the main parameters are provided where SCFT

Optimizers’ attention is required.

Optimizers can accept the reports without any remarks only when :

a.) All the Main and Info KPIs meet the threshold, and

b.) All the plots are available for further analysis at WCC2 final validation

level.

Targets for accepting Avg. Throughputs:

Category Avg. DL Throughput Avg. UL Throughput

1.8G >=5MBPS >=2.5MBPS

2.3G >=15MBPS >=1MBPS

**GTP/I-perf snapshots are not under consideration temporarily as NEO &

RANCORE is performing test on Backhaul & GTP Losses. Once any update

releases, will be circulated to all immediately.

**GTP/Iperf is to demonstrate Low Avg. DL TPT due to packet loss. It cannot

justify Low Avg. UL TPT.

Any value less than the provided targets are not acceptable for Low avg.

UL/DL throughputs.


Reports.

11

For Low Avg. DL TPT cases, acceptable attachment scenario:

Attachment type1: Only Original GTP Losses screenshot is

considerable reflecting SAP ID and date (Should be exactly same as of

SCFT drive done date) and packet loss should be greater than 0.02 in

the attached file.

Attachment type2: Only Original Iperf screenshot is considerable

reflecting IP Address of eNB and packet loss %age in the screenshot

along with eNB IP details screenshot from Site Forge (Path provided

below for eNB IP details screenshot from Site Forge).

Path for Site Forge to extract eNB IP Details:

Samsung Viewer Site Forge Login>Sites>Filter SAP ID>RAN>eNodeB

IP Details>Capture Screenshot.

SCFT Optimizer need to attach RJIL CTO approval mail for cases like

inaccessible roads, roads blockages, where KPIs impacted due to fewer

1.SAP ID

2

3 4.eNB IP Details

12

samples collected. In addition, Google snapshots for available roads, BSPs

with drive plots should be attached in the report.

** Approval mail must have the SAP ID in the mail body, else it will be

treated invalid and site will be rejected.

For cases like Cell overshooting and Undesired side lobes failure, Optimizers

have to give justification remarks with particular sectors in analysis tracker.

For E.g. a) Cell overshooting failure in Alpha/Beta/Gamma/All sectors.

b) Undesired side lobes failure in Alpha/Beta/Gamma/All sectors.

Single sector swap failure case can be accepted under exclusion criteria,

but analyzer must provide the reason behind swap occurred (like less

drivable area, small BSP, excessive drive, less separation between sectors

only where applicable).

Single sector swap due to azimuth issues, samples collected completely

outside BSP are not acceptable at all.

Optimizers do not have to accept any Main KPI failure. Though exceptions

can be considered if mail approval from RJIL CTO with respective SAP ID is

attached.

Central SCFT Team need to take care of the rejected sites from WCC2 ,and

have to resolve the rejection cause. Once the case is resolved, priorly need

to update to WCC2 QA Team within the TAT provided.

For any pending cases, regular follow up is to be taken, same status to be

shared to WCC2 QA Team within TAT.

If plots in the report are missing, Optimizer needs to provide Unique

remarks in analysis sheet for the missing plots with reference attachments.

13

Turn Around Time to revert on the Issue Tracker.

Responsible Tasks Responsibility TAT

Internal & External rejection of site

list is to be shared with Central SCFT

Lead

WCC2 QA Team. 1 DAY.

SCFT Rejection site resolution/To

Justify or provide required input to

pass rejected sites.

Central SCFT Team 3 DAYS.

2.3 Guidelines for Accepting UL/DL Throughputs for

Circles/Central SCFT Team.

These guidelines should be treated as valid and should be uniformly circulated

among all the Circles, Central SCFT Optimizers. This is mandatory to bring this in

immediate effect.

Targets for accepting Avg. Throughputs:

Category Avg. DL Throughput Avg. UL Throughput

1.8G >=5MBPS >=2.5MBPS

2.3G >=15MBPS >=1MBPS

**GTP/I-perf snapshots are not under consideration temporarily as NEO &

RANCORE is performing test on Backhaul & GTP Losses. Once any update

releases, will be circulated to all immediately.

**GTP/Iperf is to demonstrate Low Avg. DL TPT due to packet loss. It cannot

justify Low Avg. UL TPT.

14

2.4 Guidelines for WCC2 Quality Assurance Team.

WCC2 Quality Assurance Team is responsible for checking the quality of

validated sites and eligible for Accept and Reject the sites which are approved

from RJIL CTO, before final submission for WCC2.

WCC2 QA Team has to accept the Avg. DL/UL throughput according to

the threshold decided (Refer section 2.3).

Single sector swap can be justified where justification is been provided

by SCFT Optimizers.

Any main KPI failure is not acceptable unless mail approval for the

reason caused from RJIL CTO with respective SAP ID is attached to the

report.

KPI Info like DL Throughput and UL Throughput, where threshold is not

meeting, and Related snapshots like GTP Losses snapshot and RSSI

snapshot with proper SAP ID, Loss percentage, and Date are not

attached, should not be accepted at any cases.

WCC2 QA Team must analyze the drive plots before rejection of failure

cases.


Reports.

15

3. SCFT WCC2 Process Matrix.

SCFT Drive completed by FE

SCFT Optimizers Accept/Reject

the SCFT Reports

RJIL CTO Accept/Reject the SCFT

Reports

WCC2 QA Team pre validates the SCFT Reports and

Accept/Reject the Reports before WCC2 final submission.

RANCORE Approves the submitted BATCH for WCC2. If

needed rejection is done by RANCORE.

RANCORE Approved sites are submitted as hard copy to

Billing Dept. for processing billing.

Uploading log files (C1,C2,C3….)

If accepted

If accepted

If accepted

If accepted

If rejected, SCFT

Coordinator will

follow up with

Solpar to

overcome the

rejection.

If rejected,

Optimizers will follow

up with circle/ Other

project team to

overcome the

rejection.

If rejected

If rejected

If rejected

If rejected, Issue

tracker will be

acknowledged to

Central SCFT Team.

SCFT Team needs to

revert on issue

tracker within TAT.

If rejected

If rejected, It will be

added in issue

tracker and will be

circulated to the

respective Circles to

revert back on same

within TAT.

16

4. SCFT Quality Escalation Matrix.

4.1 For Backhaul Issue/GTP Losses support.

I&C Contact details and Escalation Matrix

ZONE

LEVEL1 REPORTI

NG

CIRCLE

CONTACT DETAILS

LEVEL 2

REPORTING

CONTACT DETAILS LEVEL 3 REPORTING (I&C

Managers)

NZ Prasun

Chakravorty

DL 9990110899 [email protected]

Samir Ranjan Mahar

ana

9953497869 samir.ranjan@sa

msung.com

Vivek Kamboj [email protected];8527389988;0124-6625005

NZ Ajay

Singh Rawat

UP-E

7838593247 [email protected]

Surendra

Singh Baghel

e

9582997731 s.baghele@samsu

ng.com

NZ Amit Jain UP-W


Sanjay Warath

e 9582307415

[email protected]

NZ Abhishek Jaiswal

PJ 7838380790 [email protected]

Nikunj Pandey

8800417690 nikunj.p@partner

.samsung.com

NZ Abhishek Pandey

HR


Manoj Sharma

7838652773 manoj.mishra@s

amsung.com

NZ Naveen Kumar Sharma

HP


Shyam Naraya

n Gupta

9560899052 sn.gupta@samsu

ng.com

NZ Puneet

Khanduja J&K


Bhaskar

Sharma 9891117507

[email protected]

If not resolved

For any Backhaul

Issue/GTP Issues

SCFT Engineer / Circle RF Lead

will escalate the issue to

respective LSMR Engineer

(Circle wise)

LSMR Engineer will raise the Ticket to CISCO

to get the issue resolved in 24 hours (1 day)

and once issue is resolved need to revert to

Circle RF Lead for same.

LEVEL 1

Only if issue is not resolved within 24 hours

by LSMR Team, Level 2 Escalation can be

processed to the respective LEVEL 2

Reporting Team.

LEVEL 2

17

EZ Yogesh Chorage

Kol


Nilanjan Das

Chowdhury

9830911774 n.chowdhury@sa

msung.com

Pravin Kokate [email protected]

9324285806;022-44759617

EZ Krishnendu Das

WB


Yogesh Chorag

e 9821591720

[email protected]

EZ Swayam Sambit

Das

OR


Vipin Singh

Sisodiya

9560599513 v.sisodiya@sams

ung.com

EZ Chandan

Das JHK


Navneet

kumar pandey

7033807895 navneet.pandey

@ril.com

EZ Modassir Mukhtar

BH


Gajanan dipak

Patil 7710048424

[email protected]

EZ Manoj Patil

A&NE


Jayant kanubhai Patel

7715037962 jk.patel@samsun

g.com

WZ Jatin

Harioudh MU


Ahtesham

Ahmed 7489448110

[email protected]

Kunal Gandhi [email protected] 9920922019;022-44788045

WZ Madan Mohan Singh

RJ 7718032285 [email protected]

Prakash

Somidi 9819052235

[email protected]

WZ Manoj Patidar

GJ 7738150335 [email protected]

Irfan Ahmed Siddiqu

i

7498480407 ia.siddiqui@sams

ung.com

WZ Rahul Bansal

MP


Rahul Goyal


om

WZ Yogesh Ugale

MHnG


Mohit Pandya

8860661930 mohit.pandya@s

amsung.com

WZ Uday Patil

CHG


Mukesh

Pandey 8452882850

[email protected]

SZ Manish Kumar

KL 9561094870 [email protected]

Madhav

Vyawhare

7498480569 m.vyawhare@sa

msung.com

Abhijit Lokhande [email protected]

9867698548; 022-44759635

SZ Pravin

Sharma AP


Prafull Kumar


om

SZ Satish C

Jain TN


Manoj Tiwari

9323460952 manoj.rp@partne

r.samsung.com

SZ Ganesh Mankar

KTK


Shivaraj Seena

9916149655 shivaraj.s@samsu

ng.com

18

4.2 For Actix One Issues support.

Level Reporting Contact Details

1st Level

1. Nasheer Mohammad.

2. Tabrez Khan

3. Subhash Yadav.

4.Suresh Thakur-(Also provides XCAL & FTP support)

1. [email protected].(08454888008)


3. [email protected](08898514550)


2nd Level Madhuraj Y. [email protected](07718881698)

If not

resolved

For Actix related

Issues

SCFT Analyzer will escalate the

issue to respective LEVEL 1

Dedicated Helpdesk.

1. Nasheer Mohammad. 2. Tabrez Khan

3. Subhash Yadav. 4.Suresh Thakur

LEVEL 1

[email protected]

LEVEL 2

19

4.3 For FTP related Issues support (Specifically for FTP Health

issue impacting Avg. DL/UL throughputs).

Level Reporting Contact Details

1st Level Suresh Thakur ([email protected].(09004599988)

2nd Level

1. East – Purna Chandra Biswas.

2. West – Srinivas Ghule.

3. North – Amit Kundra.

4. South – Satish Shenoy.

1. 09830080867

2. 09004663178

3. 09971522749

4. 09620921362

If not

resolved

For FTP server related

Issues.

Circle RF Lead will escalate the

issue to Suresh Thakur

([email protected].(090045

99988)

East – Purna Chandra Biswas.

West – Srinivas Ghule.

North – Amit Kundra.

South – Satish Shenoy.

LEVEL 1

Regional EPC RRMs will take follow up with

RJIL EPC Circle Leads to get the resolution

and to revert back to Circle SCFT Team.

Regional EPC RRMs will take follow up with

RJIL EPC Circle Leads to get the resolution

and to revert back to Circle SCFT Team.

LEVEL 2

20

4.4 For SCFT On-field issues support.

For any on field support during SCFT drive like UE issue/

Tools issue (XCAL, Net Velocity, etc.)/ eNodeB/ VoLTE/FTP

Issues –

War-room Helpdesk is available for online support from

Mon-Sat between 9AM-11PM. Engineers are available on

Helpline numbers provided below for supporting any type

On field queries/issues along with Cisco and Cerragon Team

(10AM-7PM) related to SCFT.

Helpline Numbers (9AM-11PM):

022-44787680;

022-44787742.

In addition, For XCAL and FTP support:-

Suresh Thakur

([email protected].(09004599988)

………

Documents

Notes for scft