Professional Documents
Culture Documents
Technology
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
1 of 9
Technology
1. DOCUMENT HISTORY..............................................................................................................................3 1.1. 1.2. 1.3. 1.4. DOCUMENT LOCATION ..........................................................................................................................3 REVISION HISTORY.............................................................................................................................3 APPROVALS ......................................................................................................................................3 DISTRIBUTION TO THIRD PARTIES ...........................................................................................................3
2. ABOUT THIS PROCESS / THESE GUIDELINES.....................................................................................4 2.1. PROCESS SCOPE...............................................................................................................................4 2.2. PROCESS GOALS...............................................................................................................................4 2.3. ABBREVIATIONS , ACRONYMS AND EXPLANATIONS ........................................................................................4 2.4. PROCESS FLOW DIAGRAM....................................................................................................................4 2.5. ROLES AND RESPONSIBILITIES ..............................................................................................................5 2.5.1. Network Performance Role...........................................................................................................5 2.5.2. BSS Operations Role...................................................................................................................6 2.6. PROCESS / GUIDELINES .......................................................................................................................6 3. PROCESS METRICS.................................................................................................................................8 APPENDIX....................................................................................................................................................9
Confidential to O2
2 of 9
Technology
This document is only valid on the day it was printed. The source of this document can be found in the following directory location: For completion by Technology Quality and Effectiveness Team
1.2.
Revision History
V1.0
Summary of Changes
1.3.
Approvals
Title Network Performance Line Manager Date of Issue Version 1.0 10/04/08
1.4.
Confidential to O2
3 of 9
Technology
This document outlines the process for planning and implementing a new Scrambling Code plan on the 3G network. The process outlined below assumes all Change Requests for implementing new Scrambling Code plans have been approved by Change Management.
2.2.
Process Goals
The purpose of this process is to ensure a proactive and clear approach to Scrambling Code planning and implementation. Scrambling Code planning is required to ensure that code reuse is as efficient as possible. Interfering cells should be assigned different scrambling codes. An optimised Scrambling Code plan will result in an increase in network quality and an improvement in the customer experience.
2.3.
Meaning
2.4.
Confidential to O2
4 of 9
Technology
1. Run SC and Neighbour consistency checks between Asset 3G and the OSS
5. Export plan to 3G Consistency Database and generate xml files for BSS Ops
6. Run consistency checks following implementation by BSS Ops and clean up any inconsistencies
NO
Accept plan
YES
7. Compare PM stats in Business Objects pre and post SC replan and retune aspects of plan as required
End
2.5.
The following section outlines the roles and responsibilities of the different teams within the process.
2.5.1.
Confidential to O2
5 of 9
Technology
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.5.2.
2.6.
Process / Guidelines
Each numbered stage in the process flow diagram in section 2.4 is explained further in the section below. 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. Perform dump of SC and neighbour info from Asset 3G database 2. Perform dump of SC and neighbour info from OSS (using Neomad database) 3. 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. 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. 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.0 6 of 9
Technology
Role: Network Performance Activity: 1. 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. Export new SC plan from Asset 3G in Excel format 2. Import into 3G Consistency Database and generate xml files for SC changes and neighbour definition changes (3G-3G and 2G-3G) 3. 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. 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
7 of 9
Technology
3. PROCESS METRICS
Specify the metrics used to measure the success of the process; for example, number of bugs fixed first time and time to fix.
Confidential to O2
8 of 9
Technology
APPENDIX
Confidential to O2
9 of 9