PTT BRS Performance Manager v1.0

TeNOSS-Flexi
Commercial in Confidence
10th February 2009
Business Requirement Specification for Performance Management
For Project:
TeNOSS for DFWN
Release No:
Business Requirement Specification
Business Requirements Specification
Version 1.0
Page 1 of 43
TeNOSS-Flexi
10th February 2009
Document Location
The master copy of this document will be found on the Clarity intranet
Author (s)
Name Sanjukta Ray Organization Clarity Designation Business Analyst Document Section Performance Manager
Revision History
Date of this revision: 10th Feb, 2008 Date of Next revision: (date)
Revision Number v0.1 v0.2 v0.3
Revision Date
Summary of Changes
Author
Changes marked N N N
10-11-2008 18-11-2008 27-11-2008
Initial Draft Flexi current business processes details included Functional Requirements section updated based on discussions held with Flexi users Final BRS Updates to Sections 1.4, 4.2.3. Add sections 4.3.16, 4.3.17, 4.3.18 and 4.3.19 and 5.5.1 Final updates after additional discussions with DFWN Users.
Sanjukta Ray Sanjukta Ray Sanjukta Ray
V1.0 V1.4
12-01-2009 13-02-2009
Sanjukta Ray Stewart Humphreys Stewart Humphreys
N N
V2.0
04-03-2009
Approvals
This document requires the following approvals. Name M. Arif Wibowo Desrul Forti Fitrayana Jestar SHS Stewart Humphreys Eric Corneles Title Telkom Telkom Telkom Telkom Clarity Sansaine Exindo Signature Date
Version 1.0
Page 2 of 43
TeNOSS-Flexi
10th February 2009
Distribution
This document has been distributed to Organisation M. Arif Wibowo Desrul Jestar Forti Eric Corneles Stewart Humphreys Heinz Adrian Victor H Makalew Representative Telkom Telkom Telkom Telkom Sansaine Clarity Clarity Clarity Project Manager Project Manager Country Manager MDD - Lead Position Project Manager Business Analyst Department Telkom - DFWN Telkom DFWN Telkom DFWN Telkom - DFWN Sansaine OSS OSS OSS
Version 1.0
Page 3 of 43
TeNOSS-Flexi
10th February 2009
Table of Contents
1 INTRODUCTION........................................................................................................................................................5 2 CURRENT BUSINESS PROCESSES.......................................................................................................................7 3 PROPOSED BUSINESS PROCESSES...................................................................................................................10 4 BUSINESS REQUIREMENTS................................................................................................................................12 APPENDICES...............................................................................................................................................................39 5 STANDARD PERFORMANCE GRAPHS AND KPIS PROPOSED...................................................................39 6 REFERENCES...........................................................................................................................................................42 7 GLOSSARY................................................................................................................................................................43
Version 1.0
Page 4 of 43
TeNOSS-Flexi
10th February 2009
1 Introduction
The Business Requirement Specification document captures the Performance Management Business requirements of Telkom-Flexi and presents the compliance of these requirements with respect to the relevant module of the Clarity OSS suite.
1.1 Document Purpose

This document is designed to serve the following purpose: 1. To capture and document the Telkom-Flexi business processes for the Performance Management of the network; 2. To derive the Business Requirements regarding the Performance Management process in scope; 3. To analyze the business requirements and provide the input for solution design to address the business requirements.
1.2 Document Scope

The document captures the business requirements regarding: 1. Performance Manager including a. Performance Graphs b. 2. Performance KPIs
Please refer to the SOW document for the list of NEs that are being captured in the present phase
3.
Clarity database will be accessible to Telkom-Flexi for generating the required Performance graphs or reports
NOTE: This BRS document will supersede all the previous documents where any requirements related to Performance Manager have been listed NOTE: This document does not describe the technical solution required to meet the customer requirements nor does it incorporate any commercial aspects such as the project schedule, training schedule or resource requirements.
1.3 Business Requirements Change Control
Version 1.0
Page 5 of 43
TeNOSS-Flexi
10th February 2009
A baseline of this Business Requirements document will be signed off by the project stakeholders. Any changes required after the baseline will be required to follow the standard Change Management procedure. Where changes are approved and incorporated into the release, the details will be annexed to this document and a new version issued. Each new version will be subsequently authorized.
Items raised during the workshop by the users request will be subject to commercial and schedule implication of these deliverables (if any). It will be separately managed outside of the scope and delivery time table of the project.
1.4 Document Exclusions

1. Clarity is not responsible for development of any reports other than the ones which are
listed in this document. Clarity will assist Telkom-Flexi to understand the Clarity database accessing which Telkom-Flexi can use Clarity GUI tools to generate the required reports. In caseTelkom chose other 3rd party reporting tools ,Clarity will support data extract. 2. 3. 4. Any service other than CDMA Any inventory other than Location, Equipment, Cards & Ports for CDMA network Clarity installation, Configuration & training.
Version 1.0
Page 6 of 43
TeNOSS-Flexi
10th February 2009
2 Current Business Processes

This section describes the Current Performance Business Processes followed by Telkom-Flexi to monitor the performance parameters of the network.
2.1 Existing Performance Monitoring Process

a) Existing network performance data for NOC is retrieved from the EMS/NMS (where available) or from the NE directly and graphs/reports are generated on the basis of this data; b) Performance Graphs and Reports are monitored by the NOC Performance teams for their respective domains. Presently no thresholds are being set on these reports and graphs;
Below is the Data flow procedure for collection and representation of the Performance data and the escalation flow in case of anomalies/breaches for Performance: Telkom-Flexi has two types of systems for monitoring performance of the network. 1. NOC (Network Operation Center) Real Time Management System Telkom-Flexi core network consists of equipments from Huawei, Motorola, Samsung and ZTE NOC team monitors the NMSes for Huawei, Samsung, Motorola and ZTE to capture the network wide performance. In case of a performance anomaly, the NOC team handles it through the Fault Management team.
2.
Dashboard System Higher level management Dashboard system is used for generating reports for higher level management. Dashboard is used to display area wise integrated performance data. Telkom-Flexi network is divided into 5 different areas namely Jakarta, Bandung, Medan, Makassar, Surabaya. Each area consists of NMSes of different vendors. A polling server in each area polls the data from the different NMSes. Polling servers aggregate the performance data to IS center through FTP for total integration. The integrated network wide data is shown on the dashboard.
Version 1.0
Page 7 of 43
TeNOSS-Flexi
10th February 2009
2.1.1 Below is the flow diagram for collection and representation of the Performance data:
SERVER A: 1. Receives / Takes data from NE (parsing) 2. Converts the data into a uniformed data (unified) 3. Does the ETL process to server B SERVER B: 1. Applies Oracle database 2. Performance data of NE VAS 3. Transfer the data needs by executive dashboard
SERVER C: 1. Applies Dashboard VAS and Web Service
Version 1.0
Page 8 of 43
TeNOSS-Flexi
10th February 2009
2.2 NOC Performance Escalation Matrix

Following is the escalation chart followed presently:Level 0: Staff/Officers Level 1: Managers in different areas Level 2: All Managers Level 3: GM/OSM (Operations Senior Manager) Level 4: Deputy EGM Level 5: EGM
Version 1.0
Page 9 of 43
TeNOSS-Flexi
10th February 2009
3 Proposed Business Processes
3.1 Performance Manager

The diagram below shows the proposed flow and functionality of the Clarity Performance Manager,
Note: SLA block shown in the above diagram is a part of the Clarity SLA Manager and will be covered in the relevant BRS
Version 1.0
Page 10 of 43
TeNOSS-Flexi
10th February 2009
Step
1 2 3
Description
Based on the Performance MDD configuration, the Performance MDD will collect the performance parameters from the EMS/NMS Performance MDD will calculate the KPIs from the performance parameters collected from EMS/NMS. The formulae are user configurable. Upon any threshold breach, an alarm will be generated or email or sms notification will be sent. The alarm will be displayed on the AMS. In case of email, the email will be sent to the configured recipient of the notification. The email message is configurable. The performance parameters stored in Clarity database can be monitored from the Clarity Performance GUI or reports can be developed to show this performance data. From the alarm in the AMS a Fault Ticket can be created The first level of trouble-shooting will take place in NOC itself with the engineers logging onto the equipments remotely to resolve the fault The Network element on which the alarm occurs will be added manually in the Fault links section The fault can be resolved by the Fault Management workgroup by logging into the network element remotely from the EMS/NMS, and the fault ticket is updated with the actions taken to rectify the problem The Fault ticket will be CLEARED upon satisfactory resolution of the problem after verifying the alarm cleared time from the EMS / NMS In case of a SLA breach, the same can be reflected to the SLA manager The Supervisor will CONFIRM the fault after verifying whether all the necessary information has been captured and verifying the alarm clearing time. In case where the threshold breach clears before any action is taken by the workgroup handling the fault ticket (if created), then no action will be taken by the respective workgroup
4 5 6 7 8 9 10 11 12
3.2 Proposed NOC Performance Escalation Matrix

Level 0: Staffs/Officers (hourly) Level 1: R.O Managers in each area (hourly) Level 2: All Operation & Maintenance Managers in each area (daily) Level 3: Deputy EGM,GM/OSM (Operations Senior Manager) (Weekly) Refer to section 5.3 for the escalation matrix.
Version 1.0
Page 11 of 43
TeNOSS-Flexi
10th February 2009
4 Business Requirements
This section describes the Business Requirements (in relation to Performance Monitoring) specified by Telkom-Flexi and provides the responses to these requirements on the basis of the Clarity Performance Manager System capability.
4.1 Interface Requirements

There is No External System Interface Requirement at this stage
4.2 Functional Requirements

This section enlists the requirements from Telkom-Flexi for the Performance Manager.
4.2.1 NETWORK MAP

Performance parameters must be displayed on a network map which should have the following features,
4.2.1.1 The system should provide the user the ability to search through a geographical hierarchy to identify a specifc Area, e.g. (Country (Indonesia), AROP (Jakarta, Bandung, Medan, Makassar, Surabaya), Region, City, Area, etc) 4.2.1.2 All of the locations in an Area should be displayed on the Map View and associated with performance indicators that provide a summary view of any Threshold Breeches linked to the equipment in a Location 4.2.1.3 The Locations on the map must reflect its performance status with colour indicators when a KPI has breached a configured threshold (Multiple threshold levels will be configurable). 4.2.1.4 The thresholds will be configured at the level the raw data is collected at (Carrier for DCR, TCH Blocking Rate, CSSR, HOSR, Occupancy and MSC for Trafficability and PDSN for Data Connection)
Screen shot of the present system is shown below. This picture is for information only and the Clarity System will not match this view
Version 1.0
Page 12 of 43
TeNOSS-Flexi
10th February 2009
4.2.2 PERFORMANCE ALARM

From operational point of view threshold must be set on the lowest level of network hierarchy and correspondingly alarm and faults will be raised. So it would be easy to track the network problem for the user. For the escalation matrix please refer to section 5.3
4.2.3 DATA AGGREGATION

From the managerial point of view users want to see the KPIs from the national, regional,city,MSC,BSC,BTS and sector level.The system should be able to aggregate data at lowest level for each KPI and then it should be aggregated city wise further region wise and finally national wide. This data should be aggregated hourly.
Version 1.0
Page 13 of 43
TeNOSS-Flexi
10th February 2009
The Application should be able to display in a single screen or view, the national daily aggregate for the KPIs Drop call, Call Set Up Success Rate, Hand Over Success Rate, Tch Blocking Rate, Occupancy, Data Connection and Traffic Ability in the form of Dials/Speedometers and the regional daily aggregate for the same KPIs in the form of a bar graph. Both forms of display should identify when a threshold has breached. Both of these displays should be dynamically updated as each hours aggregation is completed. The aggregation of data will take time to process, and should show results, ideally, for data received 1 hour in the past but no more than 2 hours in the past. Eg, An Ideal example would be a display update at 10am would show the aggregation results for the data received at 9am. The Application should be able to generate REGIONAL, MSC, BSC and BTS Aggregated reports filtering the output as follows; 1. 2. From a list of values select one or more AROP Areas; or From a list of values select one or more REGIONS (The list of values will show only Regions for the previously selected AROPs); or 3. From a list of values select one or more CITY (The list of values will show only Cities for the previously selected Regions); or 4. From a list of values select one or more MSC (The list of values will show only MSCs for the previously selected Cities); or 5. From a list of values select one or more BSCs (The list of values will show only BSCs that are connected to the previously selected MSCs ); or 6. From a list of values select one or more BTSs (The list of values will show only the BTSs connected to the previously selected BSCs); or 7. Date Range. (One or more Days of data aggregated to a Day level, one or more weeks of the year of data aggregated to a Week level and one or more months of the year for data aggregated to a Month level) 8. AREA CODE (For BTS Aggregate Report Only) This requirement to be discussed to clarify detailed requirement and as a potential delivery for stage-2. At each level there should be a select ALL option. Each BTS is assigned an AREA CODE ie 021 BTSs is Jakarta, 031 BTSs in Surabya. This is the first 3 digits of the phone numbers. NOTE: The data used for points 1 3, will use the existing agreed AREAS hierarchy as defined in the existing TeNOSS System. These aggregate reports will be generated daily to show daily aggregated data for the previous day or some other day in the past, Weekly to show weekly aggregated data for the previous week or some other week in the past and Monthly to show monthly aggregated data for the previous month.
Version 1.0
Page 14 of 43
TeNOSS-Flexi
10th February 2009
The application should allow the user to select multiple days (adhoc requirement), multiple weeks and multiple months (at the appropriate time aggregation level) and generate the Aggregated reports for the selected dates. NOTE: All Reports detailed below are dependent on Formula and Counter Confirmation. For all reports detailed below, A row will be added the bottom of each report containing the total of all values for each column. This will be delivered stage-2.
4.2.1.5 Regional Aggregate Reports

4.2.1.5.1 Drop Call Ratio REGIO N DIVRE 1 DIVRE 2 DIVRE 3 DIVRE 4 DIVRE 5 DIVRE 6 DIVRE 7 ANSWERED Term. 5000000 2000000 00 1500000 0 2000000 0 2300000 0 2300000 0 2300000 0 DROPP ED 100000 100000 0 150000 200000 350000 350000 350000 DROPPED (%) 1.00% 0.33% 0.56% 0.44% 0.97% 0.97% 0.97%
Orig. 5000000 1000000 00 1200000 0 2500000 0 1300000 0 1300000 0 1300000 0
Total 1000000 0 3000000 00 2700000 0 4500000 0 3600000 0 3600000 0 3600000 0
REGION DIVRE1 DIVRE2 DIVRE3 DIVRE4 DIVRE5 DIVRE6 DIVRE7
BLOCK 89146 9884500 112257 7993 13044 13044 13044
TOTAL ATTEMPTS 27390025 72585300 39214500 26647700 13376111 13376111 13376111
BLOCK CALL(%) 0.33% 13.62% 0.29% 0.03% 0.10% 0.10% 0.10%
4.2.1.5.2
TCH BLOCKING RATE
4.2.1.5.3 CSSR
Version 1.0
Page 15 of 43
TeNOSS-Flexi
10th February 2009
REGION DIVRE1 DIVRE2 DIVRE3 DIVRE4 DIVRE5 DIVRE6 DIVRE7
SUCCESS CALL 2664444 71050404 38399000 25636000 12438000 12438000 12438000
ATTEMPT ORIGIN 27390025 72585300 39214500 26647700 13376111 13376111 13376111
CSSR(%) 98.04% 97.89% 97.92% 96.21% 92.98% 92.98% 92.98%
4.2.1.5.4 HOSR
REGIO N DIVRE1 DIVRE2 DIVRE3 DIVRE4 DIVRE5 DIVRE6 DIVRE7
HO SUCCESS 2664444 71050404 38399000 25636000 12438000 12438000 12438000
HO ATTEMPT 27390025 72585300 39214500 26647700 13376111 13376111 13376111
HOSR(%) 98.04% 97.89% 97.92% 96.21% 92.98% 92.98% 92.98%
4.2.1.5.5 OCCUPANCY
REGIO N DIVRE1 DIVRE2 DIVRE3 DIVRE4 DIVRE5 DIVRE6 DIVRE7 CARRIED ERLANG 1049092 7954193 1302972 2303331 1400282 1400282 1400282 DESIGN ERLANG 8055982 41854999 15269121 6891033 11411332 11411332 11411332
OCCUPANCY(%) 13.02% 19.00% 8.53% 33.47% 13.12% 13.12% 13.12%
4.2.1.6 MSC Aggregate Reports
4.2.1.6.1 Drop Call Ratio Locati on

JKT JKT BDG
TYPE
MSC
Index
MSC1
Orig. 5000000 1000000 00 1200000
ANSWERED Term. 5000000 2000000 00 1500000
MSC MSC MSC2 MSC_BD
Total 1000000 0 3000000 00 2700000
DROPPE D 100000 1000000 150000
DROPPED (%) 1.00% 0.33% 0.56%
Version 1.0
Page 16 of 43
TeNOSS-Flexi
10th February 2009
BDG MDN
MSC MSC2 MSC MSC_BD
0 2500000 0 1300000 0
0 2000000 0 2300000 0
0 4500000 0 3600000 0
200000 350000
0.44% 0.97%
4.2.1.6.2 CSSR
TYPE Location BD BD BD CBN CBN MSC MSC MSC MSC MSC Index MSC1 MSC2 MSC_BD MSC2 MSC_BD
SUCCESS CALL 2664444 71050404 38399000 25636000 12438000
ATTEMPT ORIGIN 27390025 72585300 39214500 26647700 13376111
CSSR(%) 98.04% 97.89% 97.92% 96.21% 92.98%
4.2.1.6.3 HOSR
TYPE Location BD BD BD CBN CBN MSC MSC MSC MSC MSC Index MSC1 MSC2 MSC_BD MSC2 MSC_BD HO SUCCESS 2664444 71050404 38399000 25636000 12438000 HO ATTEMPT 27390025 72585300 39214500 26647700 13376111
HOSR(%) 98.04% 97.89% 97.92% 96.21% 92.98%
4.2.1.6.4 TCH BLOCKING RATE

TYPE Location BD BD BD CBN CBN MSC MSC MSC MSC MSC Index MSC1 MSC2 MSC_BD MSC2 MSC_BD BLOCK 89146 9884500 112257 7993 13044 ATTEMPT ORIGIN 27390025 72585300 39214500 26647700 13376111 BLOCK CALL(%) 0.33% 13.62% 0.29% 0.03% 0.10%
4.2.1.6.5 OCCUPANCY
Version 1.0
Page 17 of 43
TeNOSS-Flexi
Commercial in Confidence TYPE CARRIED ERLANG 1049092 7954193 1302972 2303331 1400282 DESIGN ERLANG 8055982 41854999 15269121 6891033 11411332
10th February 2009
Location BD BD BD CBN CBN
MSC MSC MSC MSC MSC
Index MSC1 MSC2 MSC_BD MSC2 MSC_BD
OCCUPANCY(%) 13.02% 19.00% 8.53% 33.47% 13.12%
4.2.1.7 BSC Aggregate Reports
4.2.1.7.1 Dropped Call Ratio Locatio TYPE n Index

BSC MLG BSC MLG BSC MLG BSC SBY BSC SBY KBL_1 KBL_0 MLG_0 JR_1 JR_0
Orig. 5000000 1000000 00 1200000 0 2500000 0 1300000 0
ANSWERED Term. 5000000 2000000 00 1500000 0 2000000 0 2300000 0
Total 1000000 0 3000000 00 2700000 0 4500000 0 3600000 0
DROPPE D 100000 1000000 150000 200000 350000
DROPPED (%) 1.00% 0.33% 0.56% 0.44% 0.97%

TYPE Location MLG MLG MLG SBY SBY BSC BSC BSC BSC BSC Index JR_0 JR_1 MLG_0 KBL_0 KBL_1 BLOCK 89146 9884500 112257 7993 13044 ATTEMPT ORIGIN 27390025 72585300 39214500 26647700 13376111 BLOCK CALL(%) 0.33% 13.62% 0.29% 0.03% 0.10%
4.2.1.7.3 OCCUPANCY
TYPE Location MLG BSC Index JR_0 CARRIE D ERLANG 1049092
DESIGN ERLANG 8055982
OCCUPANCY(%) 13.02%
Version 1.0
Page 18 of 43
TeNOSS-Flexi
Commercial in Confidence BSC BSC BSC BSC JR_1 MLG_0 KBL_0 KBL_1 7954193 1302972 2303331 1400282
10th February 2009 41854999 15269121 6891033 11411332 19.00% 8.53% 33.47% 13.12%
MLG MLG SBY SBY
4.2.1.7.4 HOSR
TYPE Location MLG MLG MLG SBY SBY BSC BSC BSC BSC BSC Index JR_0 JR_1 MLG_0 KBL_0 KBL_1 HO SUCCESS 2664444 71050404 38399000 25636000 12438000 HO ATTEMPT 27390025 72585300 39214500 26647700 13376111
HOSR(%) 98.04% 97.89% 97.92% 96.21% 92.98%
4.2.1.7.5 CSSR
TYPE Location MLG MLG MLG SBY SBY BSC BSC BSC BSC BSC BSC JR_0 JR_1 MLG_ 0 KBL_0 KBL_1 SUCCESS CALL 2664444 71050404 38399000 25636000 12438000 ATTEMPT ORIGIN 27390025 72585300 39214500 26647700 13376111
CSSR(%) 98.04% 97.89% 97.92% 96.21% 92.98%
4.2.1.8 BTS Aggregate Reports

4.2.1.8.1 Drop Call Ratio Location TYP E
MLG BTS BTS0010
ANSWERED Index Orig. 5000000 Term. 5000000 Total 1000000 0 DROPPE D 100000 DROPPED (%) 1.00%
Version 1.0
Page 19 of 43
TeNOSS-Flexi
Commercial in Confidence BTS BTS BTS BTS BTS0011 BTS0012 BTS0013 BTS0014
10th February 2009
JKT MLG BDG MDN
1000000 00 1200000 0 2500000 0 1300000 0
2000000 00 1500000 0 2000000 0 2300000 0
3000000 00 2700000 0 4500000 0 3600000 0
1000000 150000 200000 350000
0.33% 0.56% 0.44% 0.97%
4.2.1.8.2 HOSR
Location MLG MLG MLG MLG MLG MLG SBY SBY TYPE BTS BTS BTS BTS BTS BTS BTS BTS Index JR_0_BTS1 JR_0_BTS2 JR_0_BTS3 JR_1_BTS1 JR_1_BTS2 MLG_0_BTS1 KBL_0_BTS1 KBL_1_BTS1 HO SUCCESS 2664444 2664444 2664444 71050404 71050404 38399000 25636000 12438000 HO ATTEMPT 27390025 27390025 27390025 72585300 72585300 39214500 26647700 13376111 HOSR(%) 98.04% 98.04% 98.04% 97.89% 97.89% 97.92% 96.21% 92.98%
4.2.1.8.3 CSSR
SUCCESS CALL 2664444 71050404 38399000 25636000 12438000 38399000 25636000 71050404 ATTEMPT ORIGIN 27390025 72585300 39214500 26647700 13376111 39214500 26647700 72585300
Location MLG MLG MLG MLG MLG MLG SBY SBY
TYPE BTS BTS BTS BTS BTS BTS BTS BTS
Index JR_0_BTS1 JR_0_BTS2 JR_0_BTS3 JR_1_BTS1 JR_1_BTS2 MLG_0_BTS 1 KBL_0_BTS1 KBL_1_BTS1
CSSR(%) 98.04% 97.89% 97.92% 96.21% 92.98% 97.92% 96.21% 97.89%
Location MLG MLG MLG MLG MLG
TYPE BTS BTS BTS BTS BTS BTS MLG Business Requirements Specification BTS SBY BTS SBY
Index BLOCK JR_0_BTS1 89146 JR_0_BTS2 9884500 JR_0_BTS3 112257 JR_1_BTS1 7993 JR_1_BTS2 13044 MLG_0_BTS 1 112257 Version 1.0 KBL_0_BTS1 7993 KBL_1_BTS1 89146
ATTEMPT ORIGIN 27390025 72585300 39214500 26647700 13376111
BLOCK CALL(%) 0.33% 13.62% 0.29% 0.03% 0.10% 0.29% 0.03% 0.33%
39214500 20 of 43 Page 26647700 27390025
TeNOSS-Flexi
10th February 2009
4.2.1.8.5 OCCUPANCY
DESIGN ERLANG 8055982 41854999 15269121 6891033 11411332 15269121 8055982 6891033
Index JR_0_BTS1 JR_0_BTS2 JR_0_BTS3 JR_1_BTS1 JR_1_BTS2 MLG_0_BTS1 KBL_0_BTS1 KBL_1_BTS1
CARRIED ERLANG 1049092 7954193 1302972 2303331 1400282 1302972 1049092 2303331
OCCUPANCY(%) 13.02% 19.00% 8.53% 33.47% 13.12% 8.53% 13.02% 33.47%
4.2.1.9 Sector Aggregate Reports

4.2.1.9.1 Drop Call Ratio Location TYP E
MLG MLG BDG BDG MDN MDN BTS BTS BTS BTS BTS BTS BTS0010 BTS0010 BTS0012 BTS0012 BTS0014 BTS0014
ANSWERED Sector Index Sector 1 Sector 2 Sector 1 Sector 2 Sector 1 Sector 2 Orig. 5000000 1000000 00 1200000 0 2500000 0 1300000 0 1300000 0 Term. 5000000 2000000 00 1500000 0 2000000 0 2300000 0 2300000 0 Total 1000000 0 3000000 00 2700000 0 4500000 0 3600000 0 3600000 0 DROPPE D 100000 1000000 150000 200000 350000 350000
DROPPE (%)
1.0
0.3
0.5
0.4
0.9
0.9
4.2.1.9.2 HOSR
Version 1.0
Page 21 of 43
TeNOSS-Flexi
10th February 2009
SECTOR Sector 1 Sector 2 Sector 1 Sector 1 Sector 2 Sector 1 Sector 1 Sector2
HO SUCCESS 2664444 2664444 2664444 71050404 71050404 38399000 25636000 12438000
HO ATTEMP T 27390025 27390025 27390025 72585300 72585300 39214500 26647700 13376111
HOSR(%) 98.04% 98.04% 98.04% 97.89% 97.89% 97.92% 96.21% 92.98%
4.2.1.9.3 CSSR
SUCCESS CALL 2664444 71050404 38399000 25636000 12438000 38399000 25636000 71050404
Index JR_0_BTS1 JR_0_BTS1 JR_0_BTS3 JR_1_BTS1 JR_1_BTS1 MLG_0_BTS1 KBL_0_BTS1 KBL_0_BTS1
SECTOR Sector 1 Sector 2 Sector 1 Sector 1 Sector 2 Sector 1 Sector 1 Sector2
ATTEMPT ORIGIN 27390025 72585300 39214500 26647700 13376111 39214500 26647700 72585300
CSSR(%) 98.04% 97.89% 97.92% 96.21% 92.98% 97.92% 96.21% 97.89%
Version 1.0
Page 22 of 43
TeNOSS-Flexi
10th February 2009
SECTO R Sector 1 Sector 2 Sector 1 Sector 1 Sector 2 Sector 1 Sector 1 Sector2
BLOCK 89146 9884500 112257 7993 13044 112257 7993 89146
ATTEMPT ORIGIN 27390025 72585300 39214500 26647700 13376111 39214500 26647700 27390025
BLOCK CALL(%) 0.33% 13.62% 0.29% 0.03% 0.10% 0.29% 0.03% 0.33%
4.2.1.9.5 OCCUPANCY
CARRIE D ERLANG 1049092 7954193 1302972 2303331 1400282 1302972 1049092 2303331
SECTO R Sector 1 Sector 2 Sector 1 Sector 1 Sector 2 Sector 1 Sector 1 Sector2
DESIGN ERLANG 8055982 41854999 15269121 6891033 11411332 15269121 8055982 6891033
OCCUPANCY(%) 13.02% 19.00% 8.53% 33.47% 13.12% 8.53% 13.02% 33.47%
NOTE: All the above data shown in section 4.2.3.* is for example purpose only and does not reflect actual figures or information. The above tables do not reflect the exact format of the actual Performance Manager displays they indicate the type of data that will be presented.
Version 1.0
Page 23 of 43
TeNOSS-Flexi
10th February 2009
Step 4: Below is the table containing the aggregation formula at each level for each KPI:
NAME KPI
OF
Formula at the Sector level Call drop for all Carriers on the sector / Answered Call for all Carriers on the sector Origination Call Setup Success for all Carriers on the sector / Origination Call Setup Attempt for all Carriers on the sector
Formula at the BTS level Call drop for all sectors per BTS / Answered Call for all sectors per BTS Origination Call Setup Success for all sectors per BTS / Origination Call Setup Attempt for all sectors per BTS
Formula at the BSC level Call drop for all BTS for each BSC /Answered call for all BTS for each BSC Origination Call Setup Success for all BTS for each BSC / Origination Call Setup Attempt for all BTS for each BSC
MSC
Formula at the region level
AROP
Formula at the national level Call drop for all BTSs nation wide/Answered call for all BTSs nation wide
DROP CALL
Call drop for all BTS for each MSC /Answered call for all BTS for each MSC Origination Call Setup Success for all BTS for each MSC / Origination Call Setup Attempt for all BTS for each MSC
Call drop for all BTSs in the region/Answered call for all BTSs in the region
Call drop for all BTSs in the arop/Answered call for all BTSs in the arop
CALL SETUP SUCCESS RATE (CSSR)
Origination Call Setup Success for all BTSs in the region / Origination Call Setup Attempt for all BTSs in the region
Origination Call Setup Success for all BTSs in the arop / Origination Call Setup Attempt for all BTSs in the arop
Origination Call Setup Success for all BTSs nation wide / Origination Call Setup Attempt for all BTSs nation wide
HAND OVER SUCCESS RATE (HOSR)
Successful Handover for all Carriers on the sector / Handover Request for all Carriers on the sector
Successful Handover for all sectors per BTS / Handover Request for all sectors per BTS
Successful Handover for all BTS for each BSC / Handover Request for all BTS for each BSC
Successful Handover for all BTSs in each MSC / Handover Request for all BTSs in each MSC
Successful Handover for all BTSs in the region / Handover Request for all BTSs in the region
Successful Handover for all BTSs in the arop / Handover Request for all BTSs in the arop
Successful Handover for all BTSs nation wide / Handover Request for all BTSs nation wide
Version 1.0
Page 24 of 43
TeNOSS-Flexi
Commercial in Confidence Blocked Calls for all sectors per BTS / Total Call Attempts all sectors per BTS Blocked Calls for all BTS for each BSC / Total Call Attempts all BTS for each BSC Blocked Calls for all BTSs in each MSC / Total Call Attempts all BTSs in each MSC Blocked Calls for all BTSs in the region + Total Call Attempts for all BTSs in the region
10th February 2009 Blocked Calls for all BTSs in the arop / Total Call Attempts for all BTSs in the arop Blocked Calls for all BTSs nation wide / Total Call Attempts for all BTSs nation wide
TCH BLOCKING RATE
TCH Congestion Ratio Blocked Calls for all Carriers on the sector / TotalCall Attempts for all Carriers on the sector
OCCUPANC Y
Carried Erlang for all Carriers on the sector / Design Erlang for all Carriers on the sector N/A Raw Data Collected at PDSN Level
Carried Erlang for all sectors per BTS / Design Erlang for all sectors per BTS
Carried Erlang for all BTS for each BSC / Design Erlang for all BTSs for each BSC N/A Raw Data Collected at PDSN Level
Carried Erlang for all BTSs for each MSCs / Design Erlang for all BTSs for each MSC N/A Raw Data Collected at PDSN Level
Carried Erlang for all BTSs in the region / Design Erlang for all BTSs in the region
Carried Erlang for all BTSs in the arop / Design Erlang for all BTSs in the arop
Carried Erlang for all BTSs nation wide / Design Erlang for all BTSs nation wide
Data Connection
N/A Raw Data Collected at PDSN Level
Successful Packets for PDSN in the Region / Packet Attempts for all PDSN in the Region 100 (Call Blocked for all MSC in Region / Effective Bids for all MSC in Region)
Successful Packets for PDSN in the AROP / Packet Attempts for all PDSN in the AROP 100 (Call Blocked for all MSC in AROP / Effective Bids for all MSC in AROP)
Successful Packets for PDSN nation wide / Packet Attempts for all PDSN nation wide 100 (Call Blocked for all MSC nation wide / Effective Bids for all MSC nation wide)
Trafficability
N/A Raw Data collected at the MSC Level
Version 1.0
Page 25 of 43
TeNOSS-Flexi
10th February 2009
NOTE: Data Connection (PDSN) and Trafficability (MSC) counters will be collected at the Network Element level and aggregated to the national level only.
For example for drop call, the formula is number of drop/call answer Number of drop BTS 1 BTS 2 BTS 3 5 3 6 Call Answer 100 200 300 Drop call 0.05 0.015 0.02
Now suppose the data above is from BTSs available in Medan City So the total drop call of the Medan city will be (5+3+6)/(100+200+300) This is equal to 0.23 for Medan city. The above data is aggregation of hourly data.
4.2.2 PEAK HOUR REPORT
4.2.2.1 This is the same as Claritys Definition of Busy Hour will use the current Clarity Out of The Box Busy Hour Functionality. 4.2.2.2 Telkom wants the Peak hour report as the report containing the value of each KPIs (i.e. CSSR,HOSR,Drop Call, occupancy, TCH blocking rate) for that hour in which Occupancy is highest. For data aggregated at the BTS, BSC, MSC, Region and National level. 4.2.3 BUSY HOUR REPORT
The Busy Hour is a block of 3 hours which is defined by management prior to running the reports. The Busy Values are the aggregate of the defined 3 hours for the day. The busy hour reports will have the same formats as described sections 4.2.3. These reports should also be aggregated at regional level, MSC level, BSC level, BTS level and Sector level.
Version 1.0
Page 26 of 43
TeNOSS-Flexi
10th February 2009
User should be able to see these reports at any of the aggregated level mentioned above as and when he desire.
4.2.4 DASHBOARD
The Dashboard (or Speedometer display) report is an online reporting tool to Senior Management that provides an at-a-glance perspective on the current status of the project in the context of predetermined metrics for that project. Depending on the organization, those metrics are the different KPIs and other measures critical to the management team. It provides management with a quick understanding of the current project posture, without a detailed explanation of the causes or solutions.
The KPI values are displayed in a Speedometer format and updated on the incoming performance data. The features to be supported by Speedometer are as listed below,
4.2.4.1 KPIs and Thresholds should be indicated in Speedometer type objects and should be updated in real time as new performance values come in from the network. 4.2.4.2 It should also display the real as well as the threshold value. For eg. For CSSR KPI the real value is 94.68 where as the threshold value is 95.3.These values should be displayed as well.
4.2.5 DISPLAY ATTRIBUTES

The system must be capable of allowing the users to change the background display attributes like background colours, background images, etc.
4.2.6 ARCHIVING REQUIREMENTS

Performance data for the network should be available online for reporting purposes as follows;. 60 days of raw data 120 days of daily data 1 year of weekly data 3 years of monthly data
Version 1.0
Page 27 of 43
TeNOSS-Flexi
10th February 2009
4.2.7 ALERT/FLASH GENERATION

System should generate Alert/Flash if performance data is not dumped into the DB for a particular duration of time. For eg., if the performance interval is 5 mins, but no performance data is received for 3 consecutive performance intervals, then it should generate an alert to the user.
4.3 GRAPH DETAILS

The graphs detailed in this section will be produced based on the raw data as it is collected from the network and at the level it is collected at. Ie if the raw data is collected at the Carrier then the graph will be based on Carriers, if the raw data is collected at the Trunk Group then the graph will be based on Trunk Groups etc. Should the any of the below graphs contain measurements that are collected from the raw data at different objects, The graphs will be split so they contain measurement only against the same object. For example Network Performance Graph has ASR which is against MSC and BSS Traffic which is against BSC, the graph will be split into 2 graphs one for MSC ASR and one for BSC Traffic. All graphs are dependent on Formula and Counter completeness and Inventory completeness.
4.3.1 MSC Summary Report

(This is for Stage-2 because we should review the formula and counters completeness, and some inventory part could only be fulfilled in stage-2, e.g. circuit, trunks) Counter Name Counter Description Percentage of subscribers in registered in HLR Percentage of subscribers in registered in VLR Busy Hour Attempt Call Interval of data collection 60 mins Display
%HLR
Dashboard
%VLR
60 mins
Dashboard
%BHCA %BH Traffic
60 mins 60 mins
Dashboard Dashboard
Busy Hour Traffic in percentage
Inventory Specification (level of hierarchy) Location Area
Version 1.0
Page 28 of 43
TeNOSS-Flexi
10th February 2009
MSC & Trunkgroup & HLR
4.3.1
Traffic and Occupancy Graph for a Sector (RF Occupancy) Sector Level delivery Stage-2. Carrier Level Stage-1.
Counter Name Traffic
Counter Description Traffic per Erlangs hour in
Interval of data collection 60 mins
Display Bar
Occupancy
Occupancy per hour l
60 mins
Bar
Inventory Specification (level of hierarchy) MSC BSC BTS Sector Carrier
4.3.2 Trunk Connectivity Performance Graph

(This is for Stage-2 because we should review the formula and counters completeness, and some inventory part could only be fulfilled in stage-2, e.g. circuit, trunks) Counter Name Counter Description Traffic per hour in Erlangs Answer Seizure Ratio Incoming Answer Seizure Ratio Outgoing Blockage per hour Ratio of traffic to the number of Interval data collection 60 mins 60 mins 60 mins 60 mins 60 mins of Display
Traffic ASR Incoming ASR Outgoing Blockage Occupancy
Line Bar Bar Line Line
Version 1.0
Page 29 of 43
TeNOSS-Flexi
Commercial in Confidence circuits available
10th February 2009
Inventory Specification (level of hierarchy) MSC Trunkgroup
4.3.3 Network Performance Graph

(This is for Stage-2 because we should review the formula and counters completeness, and some inventory part could only be fulfilled in stage-2, e.g. circuit, trunks) Counter Name Counter Description % Attempt Seizure ratio to Interval of data collection 60 mins 60 mins Display
ASR BSS traffic
Dashboard Bar
Traffic data for the BSS in Erlangs
Inventory Specification (level of hierarchy) Location Area MSC & BSC Trunkgroup
4.3.4 Msc Sms Performance Graph

Counter Name MO Attempt Counter Description Number of Message Attempts from subscriber to the MSC Number of Message Attempts from MSC to the subscriber Percentage of successful MO messages to the MO Attempts Percentage of Interval of data collection 60 mins Display Line
MT Attempt
60 mins
Line
%MO Rate
Success
60 mins
Dashboard
%MT
Success
60 mins
Dashboard
Version 1.0
Page 30 of 43
TeNOSS-Flexi
Commercial in Confidence Rate successful MT messages to the MT Attempts Originating message failure due to Equipment Failure Times Originating message failure due to Network Fault times Originating message failure due to Receiving Party no response times Originating message failure due to Service Restriction Terminating message failure due to Equipment Failure Times Terminating message failure due to Receiving Party No Response Times 60 mins
10th February 2009
MO Short Message Failures Due To Equipment Failure Times MO Short Message Failures Due To Network Fault Times MO Short Message Failures Due To Receiving Party No Response Times MO Short Message Failures Due To Service Restriction MT Short Message Failures Due To Equipment Failure Times MT Short Message Failures Due To Receiving Party No Response Times
Line
60 mins
Line
60 mins
Line
60 mins
Line
60 mins
Line
60 mins
Line
Inventory Specification (level of hierarchy) Location Area MSC
4.3.5 Cdma Daily Performance Graph

Counter Name Counter Description Interval of data Display
Version 1.0
Page 31 of 43
TeNOSS-Flexi
Commercial in Confidence collection Attempt %Blocking %Failure %Drop %Success %Processor Total Number of Attempts % Call Blocking per hour % Call failure per hour % Call drop per hour % Call per hour Processor utilization success 60 mins 60 mins 60 mins 60 mins 60 mins 60 mins
10th February 2009
Bar Dashboard Dashboard Bar Dashboard bar
Inventory Specification (level of hierarchy) MSC BSC
4.3.6 MSC Call Minutes Graph

Counter Name On-net traffic Counter Description Total on-net traffic in the hour for the selected MSC Total Off-net traffic in the hour for the selected MSC Total traffic (combination of On-net and Off-net traffic) in the hour for the selected MSC Interval of collection 60 mins data Display Bar
Off-net traffic
60 mins
Bar
Total traffic
60 mins
Bar
Inventory Specification (level of hierarchy) Location Area MSC
4.3.7 Occupancy Report for Signaling Data Link
Version 1.0
Page 32 of 43
TeNOSS-Flexi
10th February 2009
(This is for Stage-2 because we should review the formula and counters completeness, and some inventory part could only be fulfilled in stage-2, e.g. circuit, trunks) Counter Name Counter Description Occupancy in percentage of the selected Signaling Data Link per hour Interval of data collection 60 mins Display
%Occupancy
dashboard
Inventory Specification (level of hierarchy) MSC Signalling data links
4.3.8
Other Service Provider Interconnection Performance
(This is for Stage-2 because we should review the formula and counters completeness, and some inventory part could only be fulfilled in stage-2, e.g. circuit, trunks) Counter Name Counter Description Traffic per hour in Erlangs to all the service provider selected. Answer Seizure Ratio Incoming to all the service provider selected. Answer Seizure Ratio Outgoing to all the service provider selected. Blockage per hour Ratio of traffic to the number of circuits available to all the service provider selected. Interval data collection 60 mins of Display
Traffic
Line
ASR Incoming
60 mins
Bar
ASR Outgoing
60 mins
Bar
Blockage Occupancy
60 mins 60 mins
Line Line
Version 1.0
Page 33 of 43
TeNOSS-Flexi
10th February 2009
Inventory Specification (level of hierarchy) MSC Trunk
4.3.9
Maximum concurrent subscribers trend for PDSN
Counter Name Concurrent Subscribers
Counter Description Provides the number of concurrent subscribers logged on to the PDSN server on a daily basis
Interval of collection 60 mins
data
Display bar
Inventory Specification (level of hierarchy) PDSN servers
4.3.11 PDSN Accounting Requests
Counter Name Total Acc Requests Sent Acc Response Received
Counter Description Total Accounting Requests sent Accounting Response Received
Interval of data collection 60 mins 60 mins line line
Display
Version 1.0
Page 34 of 43
TeNOSS-Flexi
10th February 2009
4.3.12 PDSN Authorisation Requests
Counter Name Total Auth Requests Sent Auth Accept
Counter Description Total Authorization Requests Sent Authorization Requests Accepted Authorization Requests Rejected
Interval of data collection 60 mins
Raw Derived Bar
60 mins
Bar
Auth Reject
60 mins
Bar
4.3.13 PDSN Daily Session Statistics
Counter Name Total Arrived Calls
Counter Description Numbers of calls arrived in the day Number of calls connected in the day Number of calls failed in the day Version 1.0
Interval of data collection 60 mins 60 mins 60 mins
Display Line Line Line
Total Calls Connected Total Failed Calls
Page 35 of 43
TeNOSS-Flexi
10th February 2009
4.3.14 PDSN Busy Hour Session Statistics

Counter Name BH Arrived Calls Counter Description Busy Hour (BH) of calls arrived in the day Busy Hour (BH) of calls connected in the day Busy Hour (BH) of calls failed in the day Busy Hour (BH) of Authentications successful in the day Busy Hour (BH) of Authentications failed in the day Interval of data collection 60 mins Display
Bar
BH Calls Connected
60 mins
Bar
BH Failed
Calls
60 mins
Bar
BH Calls Successful Authentication
60 mins
Bar
BH Calls Failed Authentication
60 mins
Bar
4.3.15 PDSN Subscriber Statistics
Version 1.0
Page 36 of 43
TeNOSS-Flexi
Commercial in Confidence Counter Name Date Descriptio n Date for which data is being displayed Total data transmitted to the subscribers in Mbps Total data received from the subscribers in Mbps Average Throughput from PDSN server towards the subscribers in kbps Average Throughput from the Subscribers towards the PDSN server in kbps Interval of data collection 60 mins
10th February 2009 Display
Line
Total data transmitted to subscribers (Mbytes) Total data received from subscribers (Mbytes) Average throughput PDSN --> Subscribers (kbps) Average throughput Subscribers --> PDSN (kbps)
60 mins
Line
60 mins
Line
60 mins
Line
60 mins
Line
4.3.16 PDSN System Utilization

Counter Name %CPU Utilization %Memory Utilization Inventory Specification (level of hierarchy) PDSN Counter Description Interval of data collection 60 mins Display Bar
60 mins
Bar
1.63505.1 Traffic and Occupancy Graph for a E1 (BSC to BTS)

(This is for Stage-2 because we should review the formula and counters completeness) Counter Name Counter Description Interval of data Display
Version 1.0
Page 37 of 43
TeNOSS-Flexi
Commercial in Confidence collection Traffic Traffic per hour in Erlangs for the selected E1 Occupancy per hour for the selected E1 60 mins
10th February 2009
Bar
Occupancy
60 mins
Bar
Inventory Specification (level of hierarchy) MSC BSC BTS Sector Carrier
1.63505.2 Occupancy Report for Signaling Link Channel

(This is for Stage-2 because we should review the formula and counters completeness, and some inventory part could only be fulfilled in stage-2, e.g. circuit, trunks) Counter Name Counter Description Occupancy in percentage of the selected Signaling Link Channel per hour Interval of data collection 60 mins Display
%Occupancy
dashboard
Inventory Specification (level of hierarchy) MSC Signalling Data link Signalling Link Channel
Version 1.0
Page 38 of 43
TeNOSS-Flexi
10th February 2009
Appendices 5 Standard Performance Graphs and KPIs Proposed

This section enlists the Performance graphs and KPIs being proposed to PTT-Flexi Performance team to monitor the network.
5.1 Sample Output of Performance Manager

Below are the embedded files for the sample output of Performance Manager
D:\PTT Telecom\PM Screenshot.doc
5.2 Formula sheet

Following is the embedded sheet of formula that Clarity received from Telkom
FORMULA VENDOR.xls
Following is the embedded sheet containing the formula
D:\PTT Telecom\ PM_Counters.xls
Note: These are live documents and will be updated based on the inputs received from Telkom.
5.3 Performance Escalation Matrix
Version 1.0
Page 39 of 43
TeNOSS-Flexi
10th February 2009
There are 4 levels of escalation at Flexi Telkom. The detailed explanation on each level is described in the below attached file.
D:\PTT Telecom\ PM_counters\Matrix_Escalation.xls
5.4 Performance Reports/Graphs

N o 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Graphs and Report Name MSC Summary Report Traffic and occupancy graph for a cell Trunk connectivity performance graph Network Performnace graph MSC SMS performance summary CDMA daily performnace grpah MSC call minutes graph Occupancy report for signalling data link Interconnection performnace report Maximum concurent subscribers trend for PDSN PDSN AAA Statistics for IPCG Server PDSN AAA Statistics For SBR Server PDSN Daily Session Statistics PDSN Busy Hour Session Statistics PDSN Subscriber Statistics
5.5 Standard CDMA KPIs
Version 1.0
Page 40 of 43
TeNOSS-Flexi
Commercial in Confidence Thereshold value (action taken) 95.3% Raise alarm And send sms 2 Data Connection 94.50% Raise alarm PDSN Carrier Lowes t Unit
10th February 2009
N o 1
Performance Indicator CSSR
Definition
A ratio of call established to call attempt
A percentage of successful packet data connection compare to total packet data connection to MSC Success rate of Mobile Station Handover from one cell to another A ratio of delivery call and call attempt to MSC. It is a capability of MSC to deliver calls on a period of time. A percentage of drop call (voice)
Hand Over Success Rate (Soft)
98.50 % Raise alarm And send sms
Carrier
Traffic ability
98.70 % Raise alarm
MSC
Drop Call
1.30 % Raise alarm And send sms
Carrier
Performance of Power Supply a. Availability
BTS A percentage of availability of power supply such as PLN, Inverter, Rectifier and Battery A percentage of reliability of power supply (electricity and temperature)
b. Reliability
Version 1.0
Page 41 of 43
TeNOSS-Flexi
Commercial in Confidence 7 TCH Blocking Rate 1.80 % Raise alarm And send sms Carrier
10th February 2009 A rate of blocking call due to unavailability of traffic channel(TCH)l in BTS
Occupancy
10% Raise alarm and send sms
Carrier
9 10 11
Downtime Network Downtime Approach Link MTTR (Mean Time To Repair)
5.5.1 Non Performance Related KPIs

Performance Power Supply Availability and Reliability, Downtime Network, Downtime Approach Link and MTTR KPIs are calculated using the durations of Fault Tickets. MTTR will be delivered Stage-1. Power Supply Availability and Reliability, Downtime Network and Downtime Approach Link will be delivered stage-2 The KPI formulas are detailed in reference 2-5 in section 6.
6 References
Business Requirements Specification Version 1.0 Page 42 of 43
TeNOSS-Flexi
10th February 2009
Ref. No.
1 2 3 4 5
Document Name
SOW Availability And Reliability.pdf Down Time Approach Link.pdf Down Time Network Element.pdf MTTR.pdf
Author
Version
Date
12/11/08
Location
7 Glossary
Abbreviation
ADSL AG API CPE CRM CSR DP DSPRP EMS FMO IT MDD MDF NGN NMS NOC OSS PMP PSTN SO SS
Meaning
Asymmetric Data Subscriber Line Access Gateways Application Program Interface Customer Premise Equipment Customer Relations Management Customer Sales Representatives Distribution Point Data Service Provisioning Reengineering Project Element Management System Future Mode of Operation Information Technology Mediation Device Driver Main Distribution Frame Next Generation Networks Network Management System Network Operation Centre Operational Support System Project Management Plan Public Switched Telephone Network Service Order Softswitch [END OF DOCUMENT]
REGION Orig. BD 5000000 JKT 100000000 MDN 12000000 MS 25000000 SBY 13000000 TOTAL 155000000
ANSWERED Term. 5000000 200000000 15000000 20000000 23000000 263000000
Total DROPPED DROPPED (% ) 10000000 100000 1.00% 300000000 1000000 0.33% 27000000 150000 0.56% 45000000 200000 0.44% 36000000 350000 0.97% 418000000 1800000 0.43%
Version 1.0
Page 43 of 43

PTT BRS Performance Manager v1.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PTT BRS Performance Manager v1.0

Uploaded by

Copyright:

Available Formats

TeNOSS-Flexi

10th February 2009

Business Requirement Specification for Performance Management

TeNOSS for DFWN

Business Requirement Specification

Business Requirements Specification

10th February 2009

Revision Number v0.1 v0.2 v0.3

10-11-2008 18-11-2008 27-11-2008

Sanjukta Ray Sanjukta Ray Sanjukta Ray

Sanjukta Ray Stewart Humphreys Stewart Humphreys

Business Requirements Specification

10th February 2009

Business Requirements Specification

10th February 2009

Business Requirements Specification

10th February 2009

1.1 Document Purpose

1.2 Document Scope

1.3 Business Requirements Change Control

Business Requirements Specification

10th February 2009

1.4 Document Exclusions

Business Requirements Specification

10th February 2009

2 Current Business Processes

2.1 Existing Performance Monitoring Process

Business Requirements Specification

10th February 2009

SERVER C: 1. Applies Dashboard VAS and Web Service

Business Requirements Specification

10th February 2009

2.2 NOC Performance Escalation Matrix

Business Requirements Specification

10th February 2009

3 Proposed Business Processes

3.1 Performance Manager

Business Requirements Specification

10th February 2009

3.2 Proposed NOC Performance Escalation Matrix

Business Requirements Specification

10th February 2009

4.1 Interface Requirements

4.2 Functional Requirements

4.2.1 NETWORK MAP

Business Requirements Specification

10th February 2009

4.2.2 PERFORMANCE ALARM

4.2.3 DATA AGGREGATION

Business Requirements Specification

10th February 2009

Business Requirements Specification

10th February 2009

4.2.1.5 Regional Aggregate Reports

Orig. 5000000 1000000 00 1200000 0 2500000 0 1300000 0 1300000 0 1300000 0

Total 1000000 0 3000000 00 2700000 0 4500000 0 3600000 0 3600000 0 3600000 0

REGION DIVRE1 DIVRE2 DIVRE3 DIVRE4 DIVRE5 DIVRE6 DIVRE7

BLOCK 89146 9884500 112257 7993 13044 13044 13044

TOTAL ATTEMPTS 27390025 72585300 39214500 26647700 13376111 13376111 13376111

BLOCK CALL(%) 0.33% 13.62% 0.29% 0.03% 0.10% 0.10% 0.10%

TCH BLOCKING RATE

Business Requirements Specification

10th February 2009

REGION DIVRE1 DIVRE2 DIVRE3 DIVRE4 DIVRE5 DIVRE6 DIVRE7