Scrambling Code Planning Process

Technology

Date Printed: 17 January 2012

SCRAMBLING CODE PLANNING PROCESS

Document Version: V1.0 Date: 10/04/08

Author: Niall O’Brien Process / Guidelines Owner: Jason Chandler

CONFIDENTIALITY This document has been issued in strictest confidence and contains proprietary information of O2. It should not be reproduced, transmitted or disclosed to others, copied to other documents or used for any other purpose other than that for which it was intended without the prior written consent of O2.

Confidential to O2

Template Version 9.0

1 of 9

............................9 Confidential to O2 Template Version 9.......................3 DISTRIBUTION TO THIRD PARTIES ...........................................................4 2.............................................................................0 2 of 9 ........................................... PROCESS SCOPE..............5........................................................................ DOCUMENT HISTORY.............4 2............................................................................................................4.......................................................................................................................................4................................................................4 2................. ROLES AND RESPONSIBILITIES ........... BSS Operations Role.. ABOUT THIS PROCESS / THESE GUIDELINES.......................8 APPENDIX.........5 2............. ABBREVIATIONS .......................................Scrambling Code Planning Process Technology Date Printed: 17 January 2012 1............................................................................................................3 REVISION HISTORY.............3...5 2...............................................................3 1............... DOCUMENT LOCATION .....................................2........................................................................................ ACRONYMS AND EXPLANATIONS ............. 1.......................................................................................1................................................................................. 1....................................... PROCESS / GUIDELINES .......6 2............................................................5................................... PROCESS FLOW DIAGRAM.................3 2......2........3 APPROVALS .......................................... PROCESS GOALS...............................................................1.................................3.........4 2........4 2.................................... PROCESS METRICS............................................................................................................................. 1....5.........................6............................6 3. Network Performance Role.......1..............................................2............................................................

Scrambling Code Planning Process Technology Date Printed: 17 January 2012 1.0 Date of Current Revision: Revision Date Version Number Summary of Changes Change Marked Y/N 1. DOCUMENT HISTORY 1. Document Location This document is only valid on the day it was printed.0 3 of 9 .3.1. Revision History V1.2.0 10/04/08 This document requires the following approvals: Name Jason Chandler 1. Distribution to Third Parties Date of Issue Version This document has been distributed to: Company and Contact Name and Title Confidential to O2 Template Version 9.4. Approvals Title Network Performance Line Manager Date of Issue Version 1. The source of this document can be found in the following directory location: For completion by Technology Quality and Effectiveness Team 1.

Acronyms and Explanations Meaning 2.1. Abbreviations. An optimised Scrambling Code plan will result in an increase in network quality and an improvement in the customer experience. Process Scope This document outlines the process for planning and implementing a new Scrambling Code plan on the 3G network. 2. 2. ABOUT THIS PROCESS / THESE GUIDELINES 2. Process Goals The purpose of this process is to ensure a proactive and clear approach to Scrambling Code planning and implementation.2.4.Scrambling Code Planning Process Technology Date Printed: 17 January 2012 2.3. Process Flow Diagram Confidential to O2 Template Version 9. Interfering cells should be assigned different scrambling codes. Acronyms and Explanations BO CR OSS PM RT SC WO Business Objects Change Request in REMEDY Operation Support Sub-system Performance Monitoring Resource Task in REMEDY Scrambling Code Work Order in REMEDY Table 1: 2.3. The process outlined below assumes all Change Requests for implementing new Scrambling Code plans have been approved by Change Management. Abbreviations. Acronyms and Explanations Abbreviations. Scrambling Code planning is required to ensure that code reuse is as efficient as possible.0 4 of 9 .

Compare PM stats in Business Objects pre and post SC replan and retune aspects of plan as required End 2. Roles and Responsibilities The following section outlines the roles and responsibilities of the different teams within the process. Run consistency checks following implementation by BSS Ops and clean up any inconsistencies NO Accept plan YES 7.5. Analyse new plan and check for inconsistencies 6.1. Generate new Scrambling Code plan in Asset 3G 5. 2.0 5 of 9 . Run SC and Neighbour consistency checks between Asset 3G and the OSS 2. Export plan to 3G Consistency Database and generate xml files for BSS Ops 4.Scrambling Code Planning Process Technology Date Printed: 17 January 2012 1. the Network Performance Team is responsible for: Confidential to O2 Template Version 9. Confirm Asset 3G predictions are up-todate and re-predict if necessary 3.5. • • • • • Network Performance Role Triggering the need for a Scrambling Code re-plan Using Excel to perform data consistency checks between the Asset 3G database and the OSS before initiating SC plan in Asset 3G Running the SC planning tool in Asset 3G Using the 3G Consistency Database to generate the xml files for BSS Operations to implement new SC plan Raising the CRs in REMEDY In this process.

5.0 6 of 9 .2. Compare and update Asset 3G with any inconsistencies Stage 2: Confirm Asset 3G predictions are up-to-date and re-predict if necessary Inputs: Coverage predictions Outputs: Up-to-date predictions in Assert 3G Role: Network Performance Activity: 1. Stage 1: Run SC and Neighbour consistency checks between Asset 3G and the OSS Inputs: Database dump from Asset 3G and the OSS Outputs: Consistent info between Asset 3G and the OSS Role: Network Performance Activity: 1. Re-predict 3G sites (if required) at the correct resolution Stage 3: Generate new Scrambling Code plan in Asset 3G Inputs: Site and neighbour database in Asset 3G Outputs: Scrambling Code plan Role: Network Performance Activity: 1.Scrambling Code Planning Process Technology Date Printed: 17 January 2012 • • Using Excel to perform parameter consistency checks between the planned and implemented SC plans Using Business Objects to benchmark the improvement (or degradation) in quality due to the SC re-plan 2. Run the Scrambling Code planning tool in Asset 3G Stage 4: Analyse new plan and check for inconsistencies Inputs: New SC plan from Asset 3G Outputs: Acceptable plan Confidential to O2 Template Version 9. Perform dump of SC and neighbour info from OSS (using Neomad database) 3.6. Process / Guidelines Each numbered stage in the process flow diagram in section 2. • BSS Operations Role Implementing the new SC plan using xml files supplied by Network Performance In this process.4 is explained further in the section below. the BSS Operations Team is responsible for: 2. Perform dump of SC and neighbour info from Asset 3G database 2.

Check new plan for SC re-use distance and neighbour SC conflicts Stage 5: Export plan to 3G Consistency Database and generate xml files for BSS Ops Inputs: New SC plan in Excel Outputs: Xml files for BSS Operations Role: Network Performance Activity: 1. Compare new SC plan from Asset with the implemented plan and clean up any inconsistencies in SCs or neighbour definitions Stage 7: Compare PM stats in Business Objects pre and post SC re-plan and retune aspects of plan as required Inputs: BO reports benchmarking PM stats before and after new SC plan Outputs: List of areas for re-tuning Role: Network Performance Activity: 1. Compare PM stats before and after re-plan to highlight areas that need further re-tune Confidential to O2 Template Version 9.0 7 of 9 . Send files to BSS Ops Stage 6: Run consistency checks following implementation by BSS Ops and clean up any inconsistencies Inputs: New SC plan and SC and neighbour dump from OSS Outputs: Consistent SC and neighbour plan Role: Network Performance Activity: 1. Export new SC plan from Asset 3G in Excel format 2.Scrambling Code Planning Process Technology Date Printed: 17 January 2012 Role: Network Performance Activity: 1. Import into 3G Consistency Database and generate xml files for SC changes and neighbour definition changes (3G-3G and 2G-3G) 3.

PROCESS METRICS Specify the metrics used to measure the success of the process. for example.Scrambling Code Planning Process Technology Date Printed: 17 January 2012 3. Confidential to O2 Template Version 9.0 8 of 9 . number of bugs fixed first time and time to fix.

Scrambling Code Planning Process Technology Date Printed: 17 January 2012 APPENDIX Confidential to O2 Template Version 9.0 9 of 9 .

Sign up to vote on this title
UsefulNot useful