kpi doc for upe

5 dJuneJuly.0629MAY JulyMay JulyJune July“External 3rd Party Products” shall mean products (software and/or hardware that i) constitute the relevant existing technical environment of Hutchison and/or ii) Hutchison obtains from 3rd parties. On a case-by-case basis the Parties can agree in a Service Description Appendix or an Addendum to this Agreement that Nokia shall obtain identified External 3rd Party Products on behalf of Hutchison. In such a case, Hutchison shall agree to the terms and conditions for such External 3 rd

Party Products provided by the relevant supplier and passed through by Nokia to Hutchison. If the Service is being performed at a fixed price, the Parties shall agree upon the pricing of the additional Services that Nokia provides as a result of such change.thirteen 13 Hutchison may order specialized or optional Services from time to time under this Agreement not later than thirteen (13) weeks [in other words, one quarter in advance before the commencement of such Services. Nokia will confirm the order with one calendar week following the date of issuance of the order.

Optional Services shall be paid as agreed with respect to each such project. If no payment milestones have been agreed for an optional service Nokia shall invoice such service on a monthly basis and Products upon delivery. Hutchison agrees to pay interest on the amount delayed at the rate of the lower of (a) SBI+ 2% per annum for each day elapsed from the due date to the date of actual payment, calculated on the basis of a 360-day year or (b) the maximum rate allowed by applicable law. Any partial payments received will first be applied to cover accrued interest, if any, and thereafter credited to cover the principal amount outstanding.Nokia reserves a right to require reasonable credit assurances and reasonable credit limits for purchases made by Hutchison under this Agreement.reserves a right to suspend furtherand/or if the credit limit established is exceeded and/or in the event of material adverse effect on Hutchison's overall creditworthiness.

If Hutchison is late in two or more payments owed under this Agreement, Nokia reserves a right to require a letter of credit as additional security for all future payments under this Agreement, such letter of credit being in an amount equal to the next two quarters estimated fees.

Nokia warrants that it will perform Services in a workmanlike manner and with professional diligence and skill and care and that at the time of acceptance the Deliverables will conform to the specifications in this Agreement in all material respects. Nokia does not warrant that any of the Services or Product(s) will meet Hutchison’s particular purpose or requirements unless expressly stated otherwise, or that the operation of any software will be uninterrupted and/or error-free.

Notwithstanding the aforesaid Hutchison shall pay to Nokia all External 3rd Party Products delivered to Hutchison unless Nokia has the right to, without any additional cost, return such Deliverables to the original vendor. Regardless of the aforesaid, Hutchison shall compensate to Nokia all costs accrued due to the return. Hutchison is responsible for the acquisition and maintenance of third party software and hardware as set out in this Agreement or as agreed separately during the provision of the Services.trained up to a standard level (ie formal training by attending a required course(s)) and their knowledge is

1 /21 © Nokia 2005 Strictly Nokia Confidential

kept up to date during the project.shown belowIn case of significant changes to number and timing of sites, the service price will have to be adjusted.

This process complements the drive-test based optimization works done by other teams during the network rollout.a will nominate a dedicated personnominated contact person

Additional Service Modules

The following optional services are also available under this Agreement, on an as quoted basis: These Services are optimisation related services. The services listed are examples and not included in the service prices offered in Appendix 3.

Our Service Portfolio covers 2G, 2.5G and 3G networks and mainly includes the following three categories:

Performance Optimization Assessment and Benchmarking Solution Architecture and Design

A list of typical service modules is shown in following figure. Service modules are not limited to this list, as most of our services are developed specifically for individual operator’s requirements.

Nokia Performance Services – portfolio example

The Performance Optimization Services are available for all technologies including GSM, GPRS, EDGE, and UMTS and includes radio, transmission and core networks. The Assessment and Benchmarking Services provide operators with an understanding of its competitive position in terms of network operations efficiency 2 /21 © Nokia 2005 Strictly Nokia Confidential

and network quality. The service also includes financial aspects to show the impact of network quality as a business success factor.The Solution Architecture and Design Services evaluates network capacity and performance and recommends a cost effective network evolution path to implement the operator’s business strategy for new services and traffic growth. This includes capacity growth plans and technology options.Other services available in this category of optional services include:

Performance audits Feature trials Performance Benchmarking License Bid Support

These services can be delivered on a short-term project basis according to Hutchison’s business needs. These services offer a high degree of flexibility and therefore are subject to separate definition of scope and schedules for a best fit to Hutchison strategic intentions. These services will be priced on a case-by-case basis.


Appendix 2KPI Measurements

This Appendix 2 describes the Key Performance Indicators with respect to each of the Services to be provided by Nokia under this Agreement. See also service credits, Appendix 3.

KPI Formula for cell wise measurements

SDCCH Completion Rate

=100-100 x sum (sdcch_radio_fail + sdcch_rf_old_ho + sdcch_user_act + sdcch_bcsu_reset + sdcch_netw_act + sdcch_bts_fail + sdcch_lapd_fail) / sum (sdcch_assign + sdcch_ho_seiz) - sum(sdcch_abis_fail_call + sdcch_abis_fail_old) -sum (sdcch_a_if_fail_call + sdcch_a_if_fail_old)

In the above-mentioned formula failure due to A_if, is removed as this contributed by IMSI detach, which are not perceived by subscriber. This KPI formula will be reviewed after three months from the date of start of the service. And will be changed if required as per the statistics.

TCH Completion Rate

Drops after TCH assignment considering re-establishments =100- 100 * -------------------------------------------------------- % = TCH assignments for new calls+ max(0,(sum(HOin)-sum(HOout)) sum(spare057044 - tch_re_est_release) =100-100 * ------------------------------------- % (sum(tch_new_call_assign)+ max(0,(sum(HOin)-sum(HOout))

Details of Spare 057044 and tch_new_call_assign

Spare057044New dropped call counter implemented as spare counter 57044 in S10.5. The

counter is updated only for voice- and data calls (not SMS, IMSI detach, etc). i.e. count the drops between TCH assignment complete and TCH release. Every call dropping TCH failure that happens between assignment complete and disconnect triggers this counter.


6

Counters from table(s): p_nbsc_service

SDCCH Assignment Success

sum(SDCCH_busy_att - tch_seiz_due_sdcch_con)100-100 * ------------------------------------------- % sum(SDCCH_seiz_att) Counters from table(s):p_nbsc_traffic

TCH Assignment Success

sum(a.tch_call_req - a.tch_norm_seiz) - sum(b.msc_o_sdcch_tch + b.bsc_o_sdcch_tch +


MS

BTS

BSC

MSC

Assignment Complete Assignment

Complete Assignment Complete

Call is setup in normal way

Call release continues

Connection Failure

Clear RequestClear CommandClear CompleteChannel

release

All DX Causes >=300trigger counter 57044/1202

b.cell_sdcch_tch) + sum(a.tch_succ_seiz_for_dir_acc) - sum(c.SPARE057046) 100-100 * -----------------------------------------------------------% sum(a.tch_call_req) - sum(c.SPARE057046)

Call Success Rate

=(100-SD Blck)*(100-SD drop)*(100-TCH Blck)*TCH Ass Succ Rate)/1000000

Handover Success Rate

Sum(msc_o_call_clear+bsc_o_call_clear+cell_call_clear)100-100 * ------------------------------------------------------% /* all HO attempts */ sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at +bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch_at...... +cell_tch_tch_at+cell_sdcch_tch_at+cell_sdcch_at) Counters from table(s): p_nbsc_ho


KEY PERFORMANCE INDICATOR FOR DATA SERVICES

STATISTICSNetwork statistics are gathered through Cell Doctor Report in Nokia OSS. Drive test statistics are derived from post processing of drive test logs. Below mentioned KPIs are highly dependent on Subscriber behaviour, MS capability and actual Data usage in the Network.

NETWORK KPIKPI proposed for network level performance.

TBF Retainability (tbf_34): This KPI is used to measure the quality of the radio interface for TBF sessions. The KPI measures purely the retainability of TBFs and is not dependent on interfaces and NEs outside BSS. Nokia propose a target value of >=95%.

Below is the formula100-TBF failure % =

TBF establishments -Normal TBF releases - releases due to flush – releases due to suspend100 - 100 * -------------------------------------------------------- % = TBF establishments - releases due to flush – releases due to suspend

sum(NBR_OF_UL_TBF+ NBR_OF_DL_TBF ;TBF establishments -decode(AVE_DUR_UL_TBF_SUM,0,0,AVE_DUR_UL_TBF_DEN) -decode(AVE_DUR_DL_TBF_SUM,0,0,AVE_DUR_DL_TBF_DEN) -UL_TBF_REL_DUE_TO_FLUSH-DL_TBF_REL_DUE_TO_FLUSH -UL_TBF_REL_DUE_TO_SUSPEND-DL_TBF_REL_DUE_TO_SUSPEND) 100 - 100 * ------------------------------------------------------- % sum(NBR_OF_UL_TBF+NBR_OF_DL_TBF -UL_TBF_REL_DUE_TO_FLUSH-DL_TBF_REL_DUE_TO_FLUSH -UL_TBF_REL_DUE_TO_SUSPEND-DL_TBF_REL_DUE_TO_SUSPEND)

UL Multislot Blocking (tbf_15)This KPI indicates the failure to establish UL TBF due to resources issue. Highly critical KPI due to service impact to subscriber.


Nokia propose a target value of <=1% Below is the formula.

sum(NO_RADIO_RES_AVA_UL_TBF)100 * -------------------------------------------------------------------------------------------------% sum(req_1_TSL_UL+req_2_TSL_UL+req_3_TSL_UL +req_4_TSL_UL+ req_5_8_TSL_UL)

Territory upgrade rejection (blck_22)Indicates the lack of resources to upgrade the data territory.Nokia proposed a target value of <=5%

Below is the formula sum(gprs_ter_ug_rej_due_csw_tr + gprs_ter_ug_rej_due_lack_psw + gprs_ter_ug_rej_due_lack_pcu)100 * ------------------------------------------------------------- % sum(gprs_ter_upgrd_req)

Bearer Load DL, BH (frl_8)Indicates the load % of the frame relay bearer for incoming data from SGSN.Nokia proposed a target value of

Gb bandwidth [kbps]

Link utilization [%]

128 25256 61384 68512 68

Below is the formula

max per bearer_id (8*(dlci_1_bytes_rec + dlci_2_bytes_rec + dlci_3_bytes_rec + dlci_4_bytes_rec + dlci_5_bytes_rec)/(period_duration*60))8 /21 © Nokia 2005 Strictly Nokia Confidential

100 * --------------------------------------------- % sum per frbc over all unlocked child nsvc (c_nsvc.committed_info_rate*16);

Average bearer unavailability (uav_12)Indicates the average unavailability for a Bearer (Gb)Nokia proposed a target value of 98%

100*sum(time_bear_oper_unoper)/sum(period_duration*60)

FIELD TESTS for EGPRS

ObjectiveThe purpose of the field tests is to verify the EDGE functionality and performance in Hutch’s network. Two different test cases will be carried out. The mentioned stationary test will be performed on two cells (one on good RF conditions >-60dBm and second on bad RF conditions <-80dBm) in each BSC. And the same test will be repeated every two months.

1. Stationary Tests

2. Drive Tests

Test Equipment The following test equipments are required to carry out the tests

NEMO Technologies Ltd., TOM EDGE Outdoor Drive Test Tool (with Nokia 6220 terminal) One EDGE NOKIA handset [N6220 (2+1 for EDGE) with Net monitor software] One DKU cable (supplied with TOM) One Laptop PC (with IR port) to use with EDGE NOKIA handset Dedicated FTP server (for thruput tests) in Hutch’s Network OR TEMs drivetest tool

Stationary Tests The purpose of the stationary tests (or spot checks) is to measure the performance of the EDGE network in the ideal environment to check that its performance (Thruput) matches the set criteria. The stationary tests also measure the performance of selected end-user applications.The tests will be done for following conditions9 /21 © Nokia 2005 Strictly Nokia Confidential

· 2 EDGE TS (dedicated) + 1 EDGE TS (Dymanic)

The number of cells where the tests are conducted shall be two cells per BSC every two months. One cell for Good RF condition (>-60 dBm Rxlev) and the second in the Poor RF conditions (<-80 dBm Rxlev). The value mentioned for the tests refer to good RF condition only.The following must be done before starting the test case in case TOM EDGE Outdoor tool used for the test.

Check if the test cell is EDGE enabled. Go to menu->net monitor->group display 0612. If EGPRSASUP is 1, EDGE is enabled in the cell. If EGPRSASUP is 0, EDGE is not enabled in the cell. Before starting the test case, the frequency has to be locked to the tested cell. Go to menu->net monitor->group display 0112-> test input (enter the test channel).

The following procedures will be followed for the stationary tests

Test cases will be conducted during “off-peak hours” at night or early morning. One stationary test point per cell. The test point must be close to the site (or antenna in case of indoor site) If during the testing one of the test cases fail, check for possible problems. After troubleshooting, conduct again all the test cases. Conduct all the test cases three times. Calculate the average values from the three tests. Dedicated FTP server will be used for the FTP download


GPRS Attach, PDP context activation and FTP download

Test id S1System EGPRSDescription

The success rate of GPRS session set-up can be described by attach and PDP activation procedures. The data is collected from the drive test tool TOM

Test execution

Make a script in TOM to do the following: GPRS attach PDP activation Start Downloading 100KB file from

TEST server using FTP PDP Context Release GPRS Detach 10 s delay

This script may be run at least 100 times for statistical reliability.

Test criteria

Record the GPRS Attach success rate and average Attach time

Record the PDP Context activation success rate and average PDP Activation response time

EGPRS data download complete. FTP download reference is 50.0 kbps for 1 timeslot. (in good RF condition)

Note that the thruput figures mentioned above are those of the FTP application. They are therefore lower than the theoretical thruput of the RLC layer.

PING Tests

Test id S2System EGPRS


Description To measure the round trip delay and to verify that packet loss is acceptable

Test execution

Ping the FTP test server by sending 500 ping packets of different sizes (32 bytes, 128 bytes, 256 bytes, 512 bytes and 1024 bytes) using the TOM tool.

Activate PDP context from MS Start Sending ping packets to test-server Send 32 byte-packet 500 times with a limit of 3

seconds for timeout Send 128 byte-packet 500 times with a limit of 3




seconds for timeoutTest criteria Record the round trip delays, the amount of sent ping

packets and loss packets Reference values for Round trip delay (average,

seconds) (In good RF condition) PING 32 bytes: 0.8 sec PING 128 bytes: 1.1 sec PING 256 bytes: 1.2 sec PING 512 bytes: 1.6 sec PING 1024 bytes: 2.8 sec

Drive Tests The purpose of the drive tests is to measure the performance of the EDGE network as experienced by the end user in a mobile environment, and to identify potential problems.


Test cases will be conducted on specific routes which would be mutually agreed at the beginning of the project

Tests will be done using a drive test tool (TOM Outdoor/TEMs Drive Test TOOL) with EDGE terminal

Dedicated FTP server will be used for the FTP download

EGPRS Drive TestTest id D1System EGPRS or GPRSDescription

Drive test with FTP download

Test execution

Start downloading a 1MB file from the test server using FTP application

Drive on the specified routes When download finishes, start another download

Test criteria

FTP throughput and time slot allocation are recorded from the tool or its post-processing software

Note that the thruput in the drive test depends on the extent of EDGE coverage, on CS traffic, on PS traffic and the core network interfaces.

Proposed KPIThe KPI will be based on report generated by the analysis tools.GPRS Attach Success: proposed target 90%TBF drop: proposed target 5%Timeslot Allocated: proposed target 90% For FTP, web download only 2 TSL are requested. Usually for GPRS 3 DL TSL+1 UL TSL & EDGE 2 DL TSL+1 UL TSLRLC data throughput: 90 kbps, For GPRS: 28 kbps


Network Year 1 (INR) Year 2 (INR) Year 3 (INR)ChennaiGujaratAndhra PradeshKarnatakaUP (East)RajasthanHaryanaUP (West)West Bengal

Table 1

A2. KPIs & Penalty/Bonus Mechanism

Key Performance Indicator

The Key Performance Indicators targets will be reviewed based on mutual agreementperformance afterof 6 months period. The below table shows the present KPIs targets.

Penalty/Bonus Formula

The Bonus criteria will be defined based on mutual agreement after 9 months, based on the performance of the network.

The following price adjustment mechanism for applicability of penalty/bonus will be followed. The penalty/bonus will be based on an NQI (Network Quality Index), which will be computed on the basis of weighted average of the critical Key Performance Indicators

Penalty/Bonus payments will be calculated on a quarterly basis and will be limited to a maximum of 5% of the quarterly charges for that particular quarter.

Network optimisation shall be delivered as a performance-based service, where Nokia commits to achieve a measurable performance improvement to the network as a joint effort with Hutchsion’s Staff. Target values are defined as a relative quantity with respect to the current network performance, rather than an absolute value.

Following steps outline the principles:


Sr. No KPI Period of meas Threshold Weightage Max value Min Value Measured value Quality Index1 SDCCH Completion Rate % Cell BH >98.5% 20% 100% 98.00% 98.50% 5.002 TCH Completion Rate % Cell BH >98.5% 20% 100% 98.00% 98.50% 5.003 SDCCH Assignment Success % Cell BH >99.5% 10% 100% 99.50% 99.50% 0.004 TCH Assignment Success % Cell BH >98% 10% 100% 98.00% 98.00% 0.005 Call Success Rate % Cell BH >94% 20% 100% 93.65% 94.61% 3.026 Rx Quality (0-5) DL cumulative Cell BH >95% 10% 100% 95.00% 95.00% 0.007 Handover Success % Cell BH >96% 10% 100% 96.00% 96.00% 0.00

100% 13.02

Assign specific weightings to individual KPI’s, reflecting their relative importance

Establish a formula, aggregating all weighted KPI’s into a single number. This Network Quality index (NQI) shall serve as the trend indicator and will be measured.

Calculate the NQI-value for a “perfect” network, using the formula. (max. NQI)

Assess the current network performance level by applying the weightings, exclusion criteria and formula to the KPI history of the last e.g. 100 days. The averaged value shall be defined as the current NQI.

Perform optimisation activities as planned Regular NQI reporting, using the agreed KPI’s, criteria and aggregation

formula


Following are the KPI’s for Network Acceptance Criteria

Network is divided in to two sub categoriesCategory-A: Cities greater than or equal to 5 sites

Acceptance Method

Quality Index will be calculated daily for each cell of Network during the cell busy hour based on above methodology

Averaging of individual quality index will be done over 1 month (excluding sundays & holidays) for all cells.

At the end of every month, based on averaged Quality Index values, following will be considered a good network

For the first 6 3 months (Gujarat, AP, Karnataka and Chennai) & for first 9 months (in UPE, UPW, Rajasthan, WB and Haryana) at least 85% of cells will have 0<Quality Index < 13. (Please note the above said duration is subject to the mutual agreement and after the actual assessment of network performance).

After the above said periodFor the next 3 months (4-6 months), (or any other mutually agreed period agreed later), at least 9095% of the cells will have 0 < Quality Index < 13

After 6 months, 100% of the cells will have 0 < Quality Index < 13

Bonus and Penalty

For Penalty and Bonus mechanism, averaging of individual quality index will be done over a quarter.

Cell is considered acceptable if Quality Index is between 13 & 0. No Penalty/Bonus will be applicable for 1st 3 months. Penalty will be applicable for next 3 months (4-6 months)in case less than

85% of the cells are not below the Quality Index of 13.02 Penalty will be applicable for beyond 6 months next 3 months (6-9 months) in

case less than 95% of the cells are below the Quality Index of 13.02 Penalty will be applicable for next 3 months onwards (9-12 months) in case

100% of the cells are below the Quality Index of 13.02. However, Hutchison will consider giving a 3 months grace period for bringing 100% cells to the Quality Index value before applying Penalty on Nokia.

Following table gives the penalty and Bonus methodology


Sr. No KPI Period of meas Threshold Weightage Max value Min Value Measured value Quality Index1 SDCCH Completion Rate % Cell BH >98.5% 20% 100% 98.00% 98.50% 5.002 TCH Completion Rate % Cell BH >98.5% 20% 100% 98.00% 98.50% 5.003 SDCCH Assignment Success % Cell BH >99.5% 10% 100% 99.50% 99.50% 0.004 TCH Assignment Success % Cell BH >98% 10% 100% 98.00% 98.00% 0.005 Call Success Rate % Cell BH >94% 20% 100% 93.65% 94.61% 3.026 Rx Quality (0-5) DL cumulative Cell BH >95% 10% 100% 95.00% 95.00% 0.007 Handover Success % Cell BH >96% 10% 100% 96.00% 96.00% 0.00

100% 13.02

No penalty/bonus will be applicable if category-A is in bonus criteria and category-B is in penalty criteria, or vice-versa.

For Penalty, worst of both categories will be taken For Bonus, best of both categories will be taken No Bonus / Penalty is applicable for first 3 months

A. for initial 4 to 6 months phase Quality Index achieved Penalty for initial 4-6 months1 0 < Quality Index < 13 for 85% of Cells Not applicable, fixed cost payable to vendor2 Quality Index >= 0 for 84% of cells 1% Penalty3 Quality Index >= 0 for 83% of cells 2% Penalty4 Quality Index >= 0 for 82% of cells 3% Penalty5 Quality Index >= 0 for 81% of cells 4% Penalty6 Quality Index >= 0 for 80% or less cells 5% Penalty

B. After 6 months phase

Quality Index achieved Penalty after months1 0 < Quality Index < 13 for 95% of Cells Not applicable, fixed cost payable to vendor2 Quality Index >= 0 for 94% of cells 1% Penalty3 Quality Index >= 0 for 93% of cells 2% Penalty4 Quality Index >= 0 for 92% of cells 3% Penalty5 Quality Index >= 0 for 91% of cells 4% Penalty6 Quality Index >= 0 for 90% or less cells 5% Penalty

KPI for Data Services:

The KPI will be based on report generated by the analysis tools. GPRS Attach Success : Target 90% TBF drop : Target 5% Timeslot Allocated (4) : Target 90% For FTP, web download only 2 TSL are

requested. Usually for GPRS 3 DL TSL+1 UL TSL & EDGE 2 DL TSL+1 UL TSL RLC data throughput : 90 kbps, For GPRS: 28 kbps

However in case these KPIs do not meet the committed KPI levels, a detailed cause analysis will be performed together with your team and suitable recommendations will be given. These will be followed up on regular basis jointly till the time the committed levels are achieved.


Category-B: Cities less then or equal to 4 sites

Acceptance Method

Quality Index will be calculated for daily each cell of Network during the cell busy hour based on above methodology

Averaging of individual quality index will be done over 1 month (excluding Sundays & holidays) for all cells.

At the end of every month, based on averaged Quality Index values, following will be considered a good network

For the first 6 3 months (Gujarat, AP, Karnataka and Chennai) & for first 9 months (in UPE, UPW, Rajasthan, WB and Haryana) at least 75% of cells will have 0<Quality Index < 10.5. (Please note the above said duration is subject to the mutual agreement and after the actual assessment of network performance).

For the next 3 months (4-6 months), , at least 85% of the cells will have 0 < Quality Index < 10.5

After 6 months, 90% of the cells will have 0 < Quality Index < 10.5 After the 6 months period, at least 80% of the cells will have 0 < Quality

Index < 10.5

Bonus and Penalty

For Penalty and Bonus mechanism, averaging of individual quality index will be done over a quarter.

Cell is considered acceptable if Quality Index is between 10.5 & 0. No Penalty/Bonus will be applicable for 1st 3 months. Penalty will be applicable for next 3 months (4-6 months)in case 85% of the

cells are below the Quality Index of 10.5 Penalty will be applicable for next 3 months (6-9 months) in case 95% of the

cells are below the Quality Index of 10.5 Penalty will be applicable for next 3 months onwards (9-12 months) in case

100% of the cells are below the Quality Index of 10.5. However, Hutchison will consider giving a 3 months grace period for bringing 100% cells to the Quality Index value before applying Penalty on Nokia.

Following table gives the penalty and Bonus methodology

No penalty/bonus will be applicable if category-A is in bonus criteria and category-B is in penalty criteria, or vice-versa.

For Penalty, worst of both categories will be taken18 /21 © Nokia 2005 Strictly Nokia Confidential

Sr. No KPI Period of meas Threshold Weightage Max value Min Value Measured value Quality Index1 SDCCH Completion Rate % Cell BH >98% 20% 100% 97.50% 98.00% 4.002 TCH Completion Rate % Cell BH >98% 20% 100% 97.50% 98.00% 4.003 SDCCH Assignment Success % Cell BH >99% 10% 100% 99.00% 99.00% 0.004 TCH Assignment Success % Cell BH >98% 10% 100% 98.00% 98.00% 0.005 Call Success Rate % Cell BH >93% 20% 100% 92.23% 93.18% 2.446 Rx Quality (0-5)* DL cumulative Cell BH >93% 10% 100% 93.00% 93.00% 0.007 Handover Success % Cell BH >93% 10% 100% 93.00% 93.00% 0.00

* for SFH towns only. For all others, it will be RxQual 0-4 100% 10.44

For Bonus, best of both categories will be takenNo Bonus / Penalty for first 3 months

Table 3.


/bonusesand Hutchison providing us KPI history for last 100 days cellwise for all 9 circles before the start of service.10and post processingXSupport in definition of synchronization principlesX Rectify faults in NetworkXXfor office use StationaryvendorIt is expected that Hutchison personnel working with Nokia personnel on these projects will be competent, skilled, and trained to a standard level recommended by Nokia (i.e formal training by attending a required course(s)) and that each will keep their knowledge and training up to date during the entirety of the applicable projects. at Nokia recommended configurationshe prices quoted herein assume that Hutchison will purchase all planning, competence transfer and optimising services quoted under the fixed price and performance-based pricing models in Appendix 3, for all nine (9) Hutchison-owned circles in India, for the entirety of the term of this Agreement, without interruption. Any deviations will require re-pricing and a new quotation, pursuant to the change order procedure. Major ramp downs or scope reductions in service will also require advance notice to Nokia as specified in Section 2.5 of the Agreement.While committing to and fully supporting the performance obligations under this Agreement, Nokia nonetheless reserves the right to allocate and assign its people and resources as it best sees fit. No dedicated or guaranteed persons or resources are promised. Nokia reserves the right to optimize its resources and performance, in a cost effective manner. Fulltracked and available for last 100

Nokia CorporationProprietary and Confidential

1

kpi doc for upe

Documents