Part One - Integration Measurement

New Site Integration SOW

Introduction

1. The main target of this document is to show the process to integrate successfully the new sites in the Network. Drive test team will insure that the site is running on air on a proper mode.

New 2G sites Integration SOW

The SOW will consist of the following:

1. New Site data check

a. Site Template verification

With the kickoff for the integration service, Supplier will propose the integration template to assurethe verification of all parameters and will not harm any KPIs in the surrounding area. Upon the mutual agreement with Mobinil on this template, it will be regularly used as integration reportalong the duration of this service. Any amendment or addition to this template should be mutually agreed between Mobinil & Supplier prior to applying it.b. Site Database creation check.Mobinil will ensure that the DB of the site is created with all the neighbors defined and FP with all RTFs is created before dispatching the integration teams to the field. DB creation will be Mobinil responsibility.

2. D4B verificationa. Mobinil to deliver site D4B associated with site integration request.b. INTEGRATION team will verify Height, tilt & Azimuth of the Antenna equipped in the site against the D4B of the site as delivered from Mobinil.c. In case the variance between the actual on site and the received D4B is limited to antenna azimuth or tilt, INTEGRATION team in the field will solve it given that the adjustment will be on the same side arm without the need of any additional hardware such as side arm, jumpersetc, then Integration team willcommunicate the action as part of the integration report.d. Otherwise Integration team will communicate the variance to Mobinil integration team to take the necessary action for solution.e. INTEGRATION TEAM will double check the feeders labels for the new sites.

3. Site Integration

a. Site Objective Integration Team will insure that each sector is serving according the requested site objective with good level and not responsible for the overshooting of these sectors outside this objective coverage area.Integration Team will report back to Mobinil for solution.The site objective should be provided with the related work order in terms of coverage (limits & targets),densification and quality reasons.

b. Inverted sectors & cross feeders detection & Solution Integration Team will perform a drive test to insure that every sector is located in the right direction. Integration Team will submit Cell Identification Plots (CID) showing the boundaries for each site. The team will detect Inverted sectors / cross feeders on the site taking all necessary actions to solve these problems given that no additional hardware or accessories is needed.

c. HW problem detection & solution Integration Team will report all the BSS hardware problem that might appear during the integration such as the below to Mobinil Team TRX/DRI problems SURF problems Bad connectors Combiner problems SUMA problems Any other BTS problem.

d. Missing NeighborsIntegration team will detect all the missing Neighbors in the objective coverage area and will report it to Mobinil Integration operation teamto add it on the time of integration

e. Frequency clashesIntegration team will detect most of the clashes that can cause downlink quality problems in the objective coverage area and report it to Mobinil Integration Team to send W.O to change it on time of integration.

f. Down Link Rx-Level Integration Team will perform 2 minutes call on each TRX on cell to insure that all the TRXs in a certain cell have the same Rx-Level in a stationery location with no Downlink power control. All RX-Level details will be submitted in a separated report for acceptance.

g. Successful Handover Integration team will insure that all expected handovers are defined1. Between cells (Intra BTS ) 1. Between the serving cell and 1st neighbors (Inter Site)

4. Report Delivery

Integration report for Successfully integrated sites will include RXLEVEL PLOT: The rxlevel plot will present the coverage map of the major and secondary roads around the site. RXQUALITY PLOT: The rxqual plot will show the quality distribution in the downlink direction. CELL IDENTIFICATION PLOT: The CID plot shows the boundaries of the cell between each other. This plot serves as a process to identify the overshooting cells, cells that have tilting, and cells shooting in wrong directions. Path balance values : the average path balance values will be reported for all DRIs of the site to be delivered

5. SLA

Supplier will be committed to the below SLA

New Sites integration report will be delivered within 1 working week from production request & D4B verification Supplier will carry the integration of new sites and committing not to affect the KPIs of the surrounding sites

Under the following conditions: No access problems: - to be able to fix the VSWR, Swapped or cross feeders, etc. Permission for outage if needed is not delayed.

New site / sector integration shall be done in 24 Hrs inside Cairo & Alexandria while 48 Hrs for Delta, Red Sea, Sinai & Upper Egypt given that the total number of work-orders per day is ten and theneeded time to access or solve problems of antenna system will be excluded from the SLA. All tools needed from TEMS tools; SIM cards & Cars are totally the supplier responsibility and should be provided by the supplier.

6. Acceptance

If the site is integrated successfully in the objective coverage area, Supplier will deliver the acceptance reports every week for the accepted sites in the previous week.

Supplier will deliver the accepted reports in (1 hard copy of each report + 1 CD contains all reports soft copy, and drive test log files)

Supplier will receive the acceptance of the delivered reports within one week after the delivery date.

Mobinil team will review the delivered reports and discuss any problem in its contents (if any) within the same week and have the right to refuse the report in case of any missing element as per the mutually agreed contents.

7. Quantity: Estimated number of sites based on the 2016 target to be integrated is 350 sites.

8. Responsibility Matrix

ItemActivity / Task Description

Responsibility of

1D4B Verification

1.1

D4B Data deliveryA new site notification will be received by Supplier via mail for integration including the following. Sites Address Antenna (Azimuth) Antenna (Type, Tilting, elevation) (D4B) Coverage objective

Mobinil

1.2D4B Verification Supplier

2New Site data check

2.1Site Database creationMobinil

2.2Site operation verification (links / HW)Mobinil

2.3Neighbor Relations verification Supplier

2.4Site Frequencies Plan verification Supplier

2.5OMC account for Normal Operation to support the Integration team at any time in the fieldMobinil

3Site Integration

3.1Inverted sectors & cross feeders detection & Solution Supplier

3.2Objective coverage areaSupplier

3.3HW problem detection Supplier

3.4Missing NeighborsSupplier

3.5Frequency clashesSupplier

3.6Antenna Replacement Mobinil

3.7Spare Parts Mobinil

5 Post Integration Optimization Mobinil

5Permissions

5.1 Permissions for any site cannot be accessed without permission Site Outage permissions in case of needsMobinil

New 3G sites Integration SOW


1. New Site data check


I. With the kickoff for the integration service, Supplier will propose the integration template to assure the verification of all parameters and will not harm any KPIs in the surrounding area.II. Upon the mutual agreement with Mobinil on this template, it will be regularly used as integration report along the duration of this service.III. Any amendment or addition to this template should be mutually agreed between Mobinil & Supplier prior to applying it.b. Site Database creation check.Mobinil will ensure that the DB of the site is created with all the neighbors defined and FP with all RTFs is created before dispatching the integration teams to the field. DB creation will be Mobinil responsibility.

2. D4C verificationa. Mobinil to deliver site D4B associated with site integration request.b. INTEGRATION team will verify Height, tilt & Azimuth of the Antenna equipped in the site against the D4B of the site as delivered from Mobinil.c. In case the variance between the actual on site and the received D4B is limited to antenna azimuth or tilt, INTEGRATION team in the field will solve it given that the adjustment will be on the same side arm without the need of any additional hardware such as side arm, jumpersetc, then Integration team willcommunicate the action as part of the integration report.d. Otherwise Integration team will communicate the variance to Mobinil integration team to take the necessary action for solution.e. INTEGRATION TEAM will double check the feeders labels for the new sites.

3. Site Integration

a. Call Tests:I. SC Check:Checking Srambling code to be on site as planned.II. 3G Voice Test Calls: 30 sec Dedicated; 20 sec idle time. III. UE LOCKED 3G:Set UE to 3G as only band and testcall voice by taking a duration of 20 sec idle time and for 30 sec dedicated modeIV. 3G Voice Terminating Test Calls: 30 sec Dedicated;20 sec idle time. UE LOCKED 3G,Set UE to 3G as only band and making voice calls duration for 20 sec in idle mode and 30 sec in dedicated mode.V. 3G SMS Check UE LOCKED 3G:Set UE to 3G as only band and making sms sessions on all sectors

b. Data Tests:I. 3G PS Internet browsing: 1 min session; 20 sec idle time. UE LOCKED 3G:Set UE to 3G as only band and test PS setup duration and web surffing by taking a duration of 20 sec idle mode and 1 min browsing session to check continuty of data packet transfer based on transmission allowed.II. HSDPA Session: 2 min Session. UE LOCKED 3G:Set UE to 3G as only band and making hsdpa sessions on all sectors for duration 2 minsIII. 3G Video Test Calls: 30 sec Dedicated; 20 sec idle time. UE LOCKED 3G:Set UE to 3G as only band and making video sessions on all sectors for duration 30 sec on dedicated mode and 20 sec on idle mode.

c. Site Objective Integration Team will insure that each sector is serving according the requested site objective with good level and not responsible for the overshooting of these sectors outside this objective coverage area.Integration Team will report back to Mobinil for solution.The site objective should be provided with the related work order in terms of coverage (limits & targets),densification and quality reasons.

d. Inverted sectors & cross feeders detection & Solution Integration Team will perform a drive test to insure that every sector is located in the right direction. Integration Team will submit Cell Identification Plots (CID) showing the boundaries for each site. The team will detect Inverted sectors / cross feeders on the site taking all necessary actions to solve these problems given that no additional hardware or accessories is needed.

e. HW problem detection & solution Integration Team will report the entire BSS hardware problem that might appear during the integration to Mobinil Team

f. Pilot Pollution: Integration team will detect any pilot pollution that might cause the bad EC/No leading to a bad quality problem and they report it to Mobinil integration team in order to solve it and repeat the measurements again.

i. Checking 2G Missing Neighbors

Integration team will detect all the missing Neighbors in the objective coverage area and will report it to Mobinil Integration operation team to add it on the time of integration


Mobility Soft HANDOVER TestChecking handover between 3G sectors ONLY.I. ISHO 3G->2G:Checking handover between 3G TO 2G SAME SECTORS(3G SEC1 = 2G SEC1 )II. Re-selection 2G->3G:Checking handover between 2G TO 3GIII. Re-selection 3G->2G:Checking handover between 3G TO 2GIV. Transmission Capability:Checking no.of E1s to be on site as planned.

h. Mobility Data tests

PS IRAT: checking Handover between 3G to 2G during any data session on all sectors3G Mobility data test: checking Data download while movement around the site.

4. SLA

Supplier will be committed to the below SLA New Sites integration report will be delivered within 1 working day fromFinishing the Drive test in the field. Supplier will carry the integration of new sites and committing not to affect the KPIs of the surrounding sitesUnder the following conditions: No access problems: - to be able to fix the VSWR, Swapped or cross feeders, etc. Permission for outage if needed is not delayed. New site integration shall be done in 24 Hrs inside Cairo & Alexandria while 48 Hrs for Delta, Red Sea, Sinai & Upper Egypt given that the total number of work-orders per day is TEN and the needed time to access or solve problems of antenna system will be excluded from the SLA. All tools needed as TEMS tools; SIM cards & Cars are totally the supplier responsibility and should be provided by the supplier.

5. Acceptance

After receiving FCR (Function Check Report), Mobinil integration team will check it, if not accepted then FCR will be resubmit to the supplier to amend it and send it again to Mobinil. If the FCR is accepted from Mobinil Team, Site will be opened for KPIs check in case any comments appeared from the KPIs integration team will be send again to Integration team in the field to solve it. Supplier will deliver the Hard copy for all accepted sites in (1 CD contains all reports soft copy, and drive test log files) Supplier will receive the acceptance of the delivered reports within one week after the delivery date. Mobinil team will review the delivered reports and discuss any problem in its contents (if any) within the same week and have the right to refuse the report in case of any missing element as per the mutually agreed contents.




Responsibility of

1D4C Verification

1.1

D4C Data deliveryA new site notification will be received by Supplier via mail for integration including the following. Sites Address Antenna (Azimuth) Antenna (Type, Tilting, elevation) (D4B) Coverage objective

Mobinil

1.2D4C Verification Supplier







3Site Integration





3.5Pilot PollutionSupplier




5Permissions


New Sector Integration SOW

Introduction

1. The main target of this document is to show the process to integrate successfully the new Sector in the Network. Drive test team will insure that the site is running on air on a proper mode.

New 2G Sector Integration SOW


1. New Sector data check


With the kickoff for the integration service, Supplier will propose the integration template to assurethe verification of all parameters and will not harm any KPIs in the surrounding area. Upon the mutual agreement with Mobinil on this template, it will be regularly used as integration reportalong the duration of this service. Any amendment or addition to this template should be mutually agreed between Mobinil & Supplier prior to applying it.b. Site Database creation check.Mobinil will ensure that the DB of the site is created with all the neighbors defined and FP with all RTFs is created before dispatching the integration teams to the field. DB creation will be Mobinil responsibility.


3. New Sector Integration

a. Inverted sectors & cross feeders detection & Solution

Integration Team will perform a drive test to insure that the sector is located in the right direction. Integration Team will submit Cell Identification Plots (CID) showing the boundaries for the sector. The team will detect Inverted sectors / cross feeders on the site taking all necessary actions to solve these problems given that no additional hardware or accessories is needed.

b. Sector Objective

Integration Team will insure that the sector is serving according the requested objective with good level and not responsible for the overshooting of the sector outside this objective coverage area.Integration Team will report back to Mobinil for solution.The sector objective should be provided with the related work order in terms of coverage (limits & targets),densification and quality reasons.

c. HW problem detection & solution

Integration Team will report all the BSS hardware problem that might appear during the integration such as the below to Mobinil Team TRX/DRI problems SURF problems Bad connectors Combiner problems SUMA problems Any other BTS problem.

d. Missing NeighborsIntegration team will detect all the missing Neighbors in the objective coverage area and will report it to Mobinil Integration operation team to add it on the time of integration

e. Frequency clashesIntegration team will detect most of the clashes that can cause downlink quality problems in the objective coverage area and report it to the responsible team to send W.O to Integration operation team to change it on time of integration.

f. Down Link Rx-Level

Integration Team will perform 2 minutes call on each TRX on cell to insure that all the TRXs in a certain cell have the same Rx-Level in a stationery location with no Downlink power control. All RX-Level details will be submitted in a separated report for acceptance.

g. Successful Handover

Integration team will insure that all expected handovers 1. Between cells (Intra BTS ) 1. Between the serving cell and 1st neighbors (Inter Site)

4. Report Delivery

Integration report for Successfully integrated sites will include RXLEVEL PLOT: The rxlevel plot will present the coverage map of the major and secondary roads around the sector. RXQUALITY PLOT: The rxqual plot will show the quality distribution in the downlink direction. CELL IDENTIFICATION PLOT: The CID plot shows the boundaries of the cell between each other. This plot serves as a process to identify the overshooting cells, cells that have tilting, and cells shooting in wrong directions. Path balance values : the average path balance values will be reported for all DRIs of the site to be delivered

5. SLA


New Sector integration report will be delivered within 1 working week from production request & D4B verification Supplier will carry the integration of new sectors and committing not to affect the KPIs of the surrounding sites


New sector integration shall be done in 24 Hrs inside Cairo & Alexandria while 48 Hrs for Delta, Red Sea, Sinai & Upper Egypt given that the total number of work-orders per day is ten and theneeded time to access or solve problems of antenna system will be excluded from the SLA. All tools needed from TEMS tools, SIM cards & Cars are totally the supplier responsibility and should be provided by the supplier

6. Acceptance

If the Sector is integrated successfully in the objective coverage area, Supplier will deliver the acceptance reports every week for the accepted sites in the previous week.



Mobinil team will review the delivered reports and discuss any problem in its contents (if any) within the same week and have the right to refuse the report in case of any missing element as per themutually agreed contents.

7. Quantity: Estimated number of Sectors based on the 2016 target to be integrated is 300 Sectors.



Responsibility of

1D4C Verification

1.1


Mobinil



2.1Sector Database creationMobinil

2.2Sector operation verification (links / HW)Mobinil


2.4Sector Frequencies Plan verification Supplier


3Sector Integration





3.5Frequency clashesSupplier




5Permissions


New 3G Sector Integration SOW

1. New Sector data check

a. Sector Template verification

With the kickoff for the integration service, Supplier will propose the integration template to assure the verification of all parameters and will not harm any KPIs in the surrounding area. Upon the mutual agreement with Mobinil on this template, it will be regularly used as integration report along the duration of this service. Any amendment or addition to this template should be mutually agreed between Mobinil & Supplier prior to applying it.b. Sector Database creation check.Mobinil will ensure that the DB of the site is created with all the neighbors defined and FP with all RTFs is created before dispatching the integration teams to the field. DB creation will be Mobinil responsibility.


3. Sector Integration

a. Call Tests:I. SC Check:Checking Srambling code to be on site as planned.II. 3G Voice Test Calls: 30 sec Dedicated; 20 sec idle time. III. UE LOCKED 3G:Set UE to 3G as only band and testcall voice by taking a duration of 20 sec idle time and for 30 sec dedicated modeIV. 3G Voice Terminating Test Calls: 30 sec Dedicated;20 sec idle time. UE LOCKED 3G,Set UE to 3G as only band and making voice calls duration for 20 sec in idle mode and 30 sec in dedicated mode.V. 3G SMS Check UE LOCKED 3G:Set UE to 3G as only band and making sms sessions on all sectors

b. Data Tests:I. 3G PS Internet browsing: 1 min session; 20 sec idle time. UE LOCKED 3G:Set UE to 3G as only band and test PS setup duration and web surffing by taking a duration of 20 sec idle mode and 1 min browsing session to check continuty of data packet transfer based on transmission allowed.II. HSDPA Session: 2 min Session. UE LOCKED 3G:Set UE to 3G as only band and making hsdpa sessions on all sectors for duration 2 minsIII. 3G Video Test Calls: 30 sec Dedicated; 20 sec idle time. UE LOCKED 3G:Set UE to 3G as only band and making video sessions on all sectors for duration 30 sec on dedicated mode and 20 sec on idle mode.

c. Site Objective Integration Team will insure that each sector is serving according the requested site objective with good level and not responsible for the overshooting of these sectors outside this objective coverage area.Integration Team will report back to Mobinil for solution.The site objective should be provided with the related work order in terms of coverage (limits & targets),densification and quality reasons.

d. Inverted sectors & cross feeders detection & Solution Integration Team will perform a drive test to insure that every sector is located in the right direction. Integration Team will submit Cell Identification Plots (CID) showing the boundaries for each site. The team will detect Inverted sectors / cross feeders on the site taking all necessary actions to solve these problems given that no additional hardware or accessories is needed.

e. HW problem detection & solution Integration Team will report the entire BSS hardware problem that might appear during the integration to Mobinil Team

f. Pilot Pollution: Integration team will detect any pilot pollution that might cause the bad EC/No leading to a bad quality problem and they report it to Mobinil integration team in order to solve it and repeat the measurements again.

j. Checking 2G Missing Neighbors



Mobility Soft HANDOVER TestChecking handover between 3G sectors ONLY.I. ISHO 3G->2G:Checking handover between 3G TO 2G SAME SECTORS(3G SEC1 = 2G SEC1 )II. Re-selection 2G->3G:Checking handover between 2G TO 3GIII. Re-selection 3G->2G:Checking handover between 3G TO 2GIV. Transmission Capability:Checking no.of E1s to be on site as planned.

h. Mobility Data tests

PS IRAT: checking Handover between 3G to 2G during any data session on all sectors3G Mobility data test: checking Data download while movement around the site.

4. SLA

Supplier will be committed to the below SLA New Sites integration report will be delivered within 1 working day fromFinishing the Drive test in the field. Supplier will carry the integration of new sites and committing not to affect the KPIs of the surrounding sitesUnder the following conditions: No access problems: - to be able to fix the VSWR, Swapped or cross feeders, etc. Permission for outage if needed is not delayed. New site integration shall be done in 24 Hrs inside Cairo & Alexandria while 48 Hrs for Delta, Red Sea, Sinai & Upper Egypt given that the total number of work-orders per day is TEN and the needed time to access or solve problems of antenna system will be excluded from the SLA. All tools needed as TEMS tools; SIM cards & Cars are totally the supplier responsibility and should be provided by the supplier.

5. Acceptance

After receiving FCR (Function Check Report), Mobinil integration team will check it, if not accepted then FCR will be resubmit to the supplier to amend it and send it again to Mobinil. If the FCR is accepted from Mobinil Team, Site will be opened for KPIs check in case any comments appeared from the KPIs integration team will be send again to Integration team in the field to solve it. Supplier will deliver the Hard copy for all accepted sites in (1 CD contains all reports soft copy, and drive test log files) Supplier will receive the acceptance of the delivered reports within one week after the delivery date. Mobinil team will review the delivered reports and discuss any problem in its contents (if any) within the same week and have the right to refuse the report in case of any missing element as per the mutually agreed contents.

6. Quantity: Estimated number of Sectors based on the 2016 target to be integrated is 500Sectors.



Responsibility of

1D4C Verification

1.1


Mobinil








3Site Integration





3.5Pilot PollutionSupplier




5Permissions


2nd carrier OR UMTS 900 implementation

Introduction

The main target of this document is to show the process to integrate successfully the 2nd Carrier or UMTS 900 in the Network. Drive test team will insure that the 2nd Carrier or UMTS 900 is implemented and running on a proper mode.

1. Neighbors additionOptimization team starts to create a neighbor script to add the new site neighbors with the back office team.

2. Site functional check test (site integration)We start to test the following 2nd Carrier or UMTS 900 functionalities to be sure that the 2nd Carrier or UMTS 900 is working properlyA. SC checkB. 3G CS VOICE Test Calls: 30sec Dedicated; 20 sec idle time. UE LOCKED 3GC. 3G PS Internet browsing: 1 min session; 20sec idle time. UE LOCKED 3GD. Site configuration and powerE. Service:I. Accessibility: Mobile in Idle Mode is Camping on F1

II. Single RAB: Mobile Initiates HSDPA on F2 and returned back to F1 after disconnection or during inactivity mode. Mobile Initiates R99 (PS) On F1 ( HSDPA non Capable mobile) voice call termination and origination (on F1) SMS on F1

III. Multi RAB: User initiates or terminates voice call while HSDPA PS session is Active (on F2) User initiates or terminates video call while HSDPA PS session is Active (on F2) User Initiates PS session while voice call is active (on F1)

IV. Mobility: Intra-NB HSDPA serving cell change (based on event 1D) (on F2) Inter-NB HSDPA serving cell change (on F2) Inter-NB HSDPA movement from dual carrier site (on F2) to single carrier site Inter-NB HSDPA movement from single carrier site to dual carrier site IRAT HSDPA PS out HO (on F2) IRAT PS in (Reselection from 2G>>F1)

V. Customer Perception:

Throughput test over F2 (static UE) Throughput test during movement from single carrier site to dual carrier site Throughput test during movement from dual carrier site to single carrier site Max. HSDPA throughput test for each sector

VI. SMS: SMS on F2 (MOC, MTC)

VII. Coverage Check: Snapshot EC/Io, RSCP, SC footprint and HSDPA footprint (on F2)

3. SLA


New 2nd carrier or UMTS 900 integration report will be delivered within 1 working day from production request Supplier will carry the integration of 2nd carrier or UMTS 900 and committing not to affect the KPIs of the surrounding sites


New 2nd Carrier or UMTS 900 integration shall be done in 24 Hrs inside Cairo & Alexandria while 48 Hrs for Delta, Red Sea, Sinai & Upper Egypt given that the total number of work-orders per day is ten and the needed time to access or solve problems of antenna system will be excluded from the SLA. All tools needed from TEMS tools; SIM cards & Cars are totally the supplier responsibility and should be provided by the supplier.

4. Acceptance

After receiving FCR (Function Check Report), Mobinil integration team will check it, if not accepted then FCR will be resubmit to the supplier to amend it and send it again to Mobinil. If the FCR is accepted from Mobinil Team, Site will perform KPIs check in case any comments appeared from the KPIs integration team will be send again to Integration team in the field to solve it. Supplier will deliver the Hard copy for all accepted sites in (1 CD contains all reports soft copy, and drive test log files) Supplier will receive the acceptance of the delivered reports within one week after the delivery date. Mobinil team will review the delivered reports and discuss any problem in its contents (if any) within the same week and have the right to refuse the report in case of any missing element as per the mutually agreed contents.




Responsibility of


3Neighbor AdditionMobinil

3Site Integration

3.1SC checkSupplier

3.23G CS VOICE Test CallsSupplier

3.33G PS Internet browsingSupplier

3.4Site configuration and powerSupplier

3.5Services TestSupplier


4Post Integration Optimization Mobinil

5Permissions


Antenna Swap Integration SOW

Introduction

The main target of this document is to show the process to integrate successfully 3G Antenna Swap in the Network. Drive test team will insure that the site is running on air on same as before antenna swap was done.

Antenna swap SOW


1. D4C verification

a. Mobinil to deliver site D4C associated with site integration request.b. INTEGRATION team will verify Height, tilt & Azimuth of the Antenna equipped in the site against the D4B of the site as delivered from Mobinil.c. In case the variance between the actual on site and the received D4B is limited to antenna azimuth or tilt, INTEGRATION team in the field will solve it given that the adjustment will be on the same side arm without the need of any additional hardware such as side arm, jumpersetc, then Integration team willcommunicate the action as part of the integration report.d. Otherwise Integration team will communicate the variance to Mobinil integration team to take the necessary action for solution.e. INTEGRATION TEAM will double check the feeders labels for the new sites.

2. Site Integration

a. Inverted sectors & cross feeders detection & Solution

Integration Team will perform a drive test to insure that every sector is located in the right direction. Integration Team will submit Cell Identification Plots (CID) showing the boundaries for each site. The team will detect Inverted sectors / cross feeders on the site taking all necessary actions to solve these problems given that no additional hardware or accessories is needed.

b. Site Objective

Integration Team will insure that each sector is serving according the requested site objective with good level and not responsible for the overshooting of these sectors outside this objective coverage area.Integration Team will report back to Mobinil for solution.The site objective should be provided with the related work order in terms of coverage (limits & targets),densification and quality reasons.

c. Missing Neighbors


d. Frequency clashes

Integration team will detect most of the clashes that can cause downlink quality problems in the objective coverage area and report it to the responsible team to send W.O to Integration operation team to change it on time of integration.

3. Report Delivery

Integration report for Successfully integrated sites will include RXLEVEL PLOT: The rxlevel plot will present the coverage map of the major and secondary roads around the site. RXQUALITY PLOT: The rxqual plot will show the quality distribution in the downlink direction. CELL IDENTIFICATION PLOT: The CID plot shows the boundaries of the cell between each other. This plot serves as a process to identify the overshooting cells, cells that have tilting, and cells shooting in wrong directions. Path balance values : the average path balance values will be reported for all DRIs of the site to be delivered

4. SLA


Site integration report will be delivered within 1 working week from production request & D4B verification Supplier will carry the integration of 3G antenna swap and committing not to affect the KPIs of the surrounding sites


3G antenna swap integration shall be done in 24 Hrs inside Cairo & Alexandria while 48 Hrs for Delta, Red Sea, Sinai & Upper Egypt given that the total number of work-orders per day is ten and theneeded time to access or solve problems of antenna system will be excluded from the SLA. All tools needed from TEMS tools, SIM cards & Cars are totally the supplier responsibility and should be provided by the supplier

5. Acceptance

If the site is integrated successfully in the objective coverage area, Supplier will deliver the acceptance reports every week for the accepted sites in the previous week.



Mobinil team will review the delivered reports and discuss any problem in its contents (if any) within the same week and have the right to refuse the report in case of any missing element as per themutually agreed contents.

6. Quantity: Estimated number of Sites based on the 2016 target to be integrated is 600 sites.



Responsibility of

1D4B Verification

1.1

D4C Data deliveryA new site notification will be received by Supplier via mail for integration including the following. Sites Address Antenna (Azimuth) Antenna (Type, Tilting, elevation) (D4C) Coverage objecti

Mobinil


2Site Integration






3Permissions


BSC Migration SOW

Introduction

The main target of this document is to show the process to measure and confirm the proper performance of BSCs in the network after the migration actions takes place immediately. Drive test team will insure that the BSC is running on air on a proper mode.

BSCs Migration SOW


1. Global check

a. DT team will follow the methodology of (Redial Terminated Calls), while call duration will be 120 second to check call setup, cell reselection, LAC update, .etc is OK.b. DT team will check the HO relation between the migrated BSC and the surrounding neighbors, especially on the BSC\LAC borders and verify all neighboring relations are OK.c. DT team will verify all LAC updates are successful and will follow up any LAC update failure problem with the support team until the problem is solved.d. DT team will check switching problems (Silent calls, no audio, cross talk, Echo calls, etc) on all migrated cells and report them to the NSS team on the spot.

2. Report Delivery

Migration report for migrated BSC will include RXLEVEL PLOT: The rxlevel plot will present the coverage map of the major and secondary roads in the migrated site\BSC area. RXQUALITY PLOT: The rxqual plot will show the quality distribution in the downlink direction. LAC IDENTIFICATION PLOT: The LAC plot shows the boundaries of the LAC borders between site\BSC and each other. Events distribution plot for the following events:1. Call events distribution (Call setup, blocked call, and dropped calls)2. HO events (successful HO and HO failures)3. Ideal mode events (cell reselections and routing area update)4. LAC events (successful LAC update and LAC update failures) DT team will confirm that all measured cell were having GPRS enabled, or else a list of cells that have no GPRS enabled.

3. SLA

DT team will be committed to the below SLA

Any BSC migration to be handled on time by online supervision of support\operation teams. Any minor\major problems to be reported on the spot and double-check after the confirmation of support\operation teams those problems are solved. Supplier to deliver a migration report to Mobinil biweekly. All tools needed from TEMS tools, SIM cards & Cars are totally the supplier responsibility and should be provided by the supplier

4. Acceptance Support\supervision team will announce the action successful completion via email after the confirmation of DT team that no minor\major problem exists, next day to the action. The announcement mail to be considered as acceptance confirmation from Mobinil side.

5. Quantity: Estimated number of BSC migrations based on the 2016 target to be integrated is 150 BSC.



Responsibility of

1Migration announcement

1.1 Migration action announcement via EmailMobinil

1.2DT contact personSupplier

2Supervision\Operation Support

2.1BSC migration action from OMCMobinil

2.2Migration drive test and problems reportingSupplier

3Action handlingSupplier

3.1Minor\Major problems detection and reportingSupplier

3.2Minor\Major problems clearance Mobinil

3.3Action completion announcementMobinil\Supplier

4Report Delivery and acceptance

4.1Migration report delivery on biweekly basisSupplier

4.2Migration reports reviewing and acceptance on weekly basis Mobinil

Dials Tests Measurements (SOW)IntroductionThe target is testing the new dial ranges ,SS upgrade and all other feature may be added or modified on the switch level at all 2G/3G networks and also all the VAS tests to check the new services, By this tests we can enhance the network performance and make sure that all features designed correctly and working as the planned rules.

Dials Tests Measurements (SOW)


1. Global Measurements:

The below are some of the main required field tests done on the RCP level:a. Originating call to others networks (Vodafone, Etisalat, PSTN)b. Terminating call from others networks (Vodafone, Etisalat, PSTN)c. Send and receive SMS from others networks (Vodafone, Etisalat, PSTN)d. Checking locations update & Handover between two different LACs.e. Check the credit after each call to ensure the billing procedure

2. Report DeliveryI. Test report contains the test results per location. II. A report should be submitted to Mobinil to check the results and take the necessary actions if needed.

3. SLAI. New Features measurements shall be done in 24 Hrs inside Cairo & Alexandria while 48 Hrs for Delta, Red Sea, Sinai & Upper Egypt.II. Supplier to deliver a report to Mobinil weekly.III. All tools needed from TEMS tools, SIM cards & Cars are totally the supplier responsibility and should be provided by the supplier.

4. Acceptance

Report should be submitted to Mobinil a week after measurements done. Mobinil should accept report within 1 week if all the requirements are fulfilled otherwise Mobinil has the right to reject the report. The submitted report should include all the tests done in the field.5. Quantity: Estimated number of Tests based on the 2016 to be integrated is 1500 sites.

Penalties

0. 0.5 % of the annual Purchase Order price of the delayed PI per Day of delay.0. The accumulated liquidated damages payable shall not exceed 20 (twenty) % of the annual PO value.

Part One - Integration Measurement

Documents

Transcript of Part One - Integration Measurement