Download - PTT BRS Performance Manager v1.0
-
7/31/2019 PTT BRS Performance Manager v1.0
1/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
Business Requirement Specification forPerformance Management
For Project:
TeNOSS for DFWN
Release No:
Business Requirement Specification
Business Requirements Specification Version 1.0 Page 1 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
2/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
Document Location
The master copy of this document will be found on the Clarity intranet
Author (s)
Name Organization Designation Document Section
Sanjukta Ray Clarity Business Analyst Performance Manager
Revision History
Date of this revision: 10th Feb, 2008 Date of Next revision: (date)
RevisionNumber
Revision Date Summary of Changes Author Changesmarked
v0.1 10-11-2008 Initial Draft Sanjukta Ray Nv0.2 18-11-2008 Flexi current business processes
details includedSanjukta Ray N
v0.3 27-11-2008 Functional Requirements sectionupdated based on discussions heldwith Flexi users
Sanjukta Ray N
V1.0 12-01-2009 Final BRS Sanjukta Ray N
V1.4 13-02-2009 Updates to Sections 1.4, 4.2.3. Addsections 4.3.16, 4.3.17, 4.3.18 and4.3.19 and 5.5.1
StewartHumphreys
N
V2.0 04-03-2009 Final updates after additionaldiscussions with DFWN Users.
StewartHumphreys
N
Approvals
This document requires the following approvals.
Name Title Signature Date
M. Arif Wibowo Telkom
Desrul TelkomForti Fitrayana TelkomJestar SHS Telkom
Stewart Humphreys ClarityEric Corneles Sansaine Exindo
Business Requirements Specification Version 1.0 Page 2 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
3/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
Distribution
This document has been distributed to
Organisation Representative Position DepartmentM. Arif Wibowo Telkom Project Manager Telkom - DFWN
Desrul Telkom Business Analyst Telkom DFWN
Jestar Telkom Telkom DFWN
Forti Telkom Telkom - DFWNEric Corneles Sansaine Project Manager Sansaine
StewartHumphreys
Clarity Project Manager OSS
Heinz Adrian Clarity Country Manager OSSVictor H Makalew Clarity MDD - Lead OSS
Business Requirements Specification Version 1.0 Page 3 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
4/43
TeNOSS-Flexi Commercial in Confidence 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
Business Requirements Specification Version 1.0 Page 4 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
5/43
TeNOSS-Flexi Commercial in Confidence 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. Performance KPIs
2. 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
Business Requirements Specification Version 1.0 Page 5 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
6/43
TeNOSS-Flexi Commercial in Confidence 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. Any service other than CDMA
3. Any inventory other than Location, Equipment, Cards & Ports for CDMA network
4. Clarity installation, Configuration & training.
Business Requirements Specification Version 1.0 Page 6 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
7/43
TeNOSS-Flexi Commercial in Confidence 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.
Business Requirements Specification Version 1.0 Page 7 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
8/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
2.1.1 Below is the flow diagram for collection and representation of thePerformance 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 database2. Performance data of NE VAS3. Transfer the data needs by executive dashboard
SERVER C:
1. Applies Dashboard VAS and Web Service
Business Requirements Specification Version 1.0 Page 8 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
9/43
TeNOSS-Flexi Commercial in Confidence 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
Business Requirements Specification Version 1.0 Page 9 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
10/43
TeNOSS-Flexi Commercial in Confidence 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 becovered in the relevant BRS
Business Requirements Specification Version 1.0 Page 10 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
11/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
Step Description1 Based on the Performance MDD configuration, the Performance MDD will
collect the performance parameters from the EMS/NMS2 Performance MDD will calculate the KPIs from the performance parameters
collected from EMS/NMS. The formulae are user configurable.3 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 ofemail, the email will be sent to the configured recipient of the notification. Theemail message is configurable.
4 The performance parameters stored in Clarity database can be monitored fromthe Clarity Performance GUI or reports can be developed to show thisperformance data.
5 From the alarm in the AMS a Fault Ticket can be created
6 The first level of trouble-shooting will take place in NOC itself with the engineerslogging onto the equipments remotely to resolve the fault
7 The Network element on which the alarm occurs will be added manually in theFault links section
8 The fault can be resolved by the Fault Management workgroup by logging intothe network element remotely from the EMS/NMS, and the fault ticket isupdated with the actions taken to rectify the problem
9 The Fault ticket will be CLEARED upon satisfactory resolution of the problemafter verifying the alarm cleared time from the EMS / NMS
10 In case of a SLA breach, the same can be reflected to the SLA manager 11 The Supervisor will CONFIRM the fault after verifying whether all the necessary
information has been captured and verifying the alarm clearing time.12 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 bythe respective workgroup
3.2 Proposed NOC Performance Escalation MatrixLevel 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.
Business Requirements Specification Version 1.0 Page 11 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
12/43
TeNOSS-Flexi Commercial in Confidence 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 ageographical 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 Viewand associated with performance indicators that provide asummary view of any Threshold Breeches linked to the equipmentin a Location
4.2.1.3 The Locations on the map must reflect its performance status withcolour 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 iscollected at (Carrier for DCR, TCH Blocking Rate, CSSR, HOSR,Occupancy and MSC for Trafficability and PDSN for DataConnection)
Screen shot of the present system is shown below. This picture is for information only and the
Clarity System will not match this view
Business Requirements Specification Version 1.0 Page 12 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
13/43
TeNOSS-Flexi Commercial in Confidence 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.
Business Requirements Specification Version 1.0 Page 13 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
14/43
TeNOSS-Flexi Commercial in Confidence 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. From a list of values select one or more AROP Areas; or
2. 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.
Business Requirements Specification Version 1.0 Page 14 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
15/43
TeNOSS-Flexi Commercial in Confidence 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
ANSWERED DROPP
ED
DROPPED
(%)Orig. Term. TotalDIVRE1 5000000 5000000
10000000 100000 1.00%
DIVRE2
100000000
200000000
300000000
1000000 0.33%
DIVRE3
12000000
15000000
27000000 150000 0.56%
DIVRE4
25000000
20000000
45000000 200000 0.44%
DIVRE5
13000000
23000000
36000000 350000 0.97%
DIVRE6 13000000 23000000 36000000 350000 0.97%DIVRE7
13000000
23000000
36000000 350000 0.97%
4.2.1.5.2 TCH BLOCKINGRATE
4.2.1.5.3 CSSR
Business Requirements Specification Version 1.0 Page 15 of 43
REGION BLOCKTOTALATTEMPTS
BLOCKCALL(%)
DIVRE1 89146 27390025 0.33%
DIVRE2 9884500 72585300 13.62%
DIVRE3 112257 39214500 0.29%
DIVRE4 7993 26647700 0.03%
DIVRE5 13044 13376111 0.10%
DIVRE6 13044 13376111 0.10%
DIVRE7 13044 13376111 0.10%
-
7/31/2019 PTT BRS Performance Manager v1.0
16/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
REGIONSUCCESSCALL
ATTEMPTORIGIN CSSR(%)
DIVRE1 2664444 27390025 98.04%
DIVRE2 71050404 72585300 97.89%
DIVRE3 38399000 39214500 97.92%
DIVRE4 25636000 26647700 96.21%
DIVRE5 12438000 13376111 92.98%
DIVRE6 12438000 13376111 92.98%
DIVRE7 12438000 13376111 92.98%
4.2.1.5.4 HOSR
REGION HO SUCCESS HO ATTEMPT HOSR(%)
DIVRE1 2664444 27390025 98.04%
DIVRE2 71050404 72585300 97.89%
DIVRE3 38399000 39214500 97.92%
DIVRE4 25636000 26647700 96.21%
DIVRE5 12438000 13376111 92.98%
DIVRE6 12438000 13376111 92.98%
DIVRE7 12438000 13376111 92.98%
4.2.1.5.5 OCCUPANCY
REGION
CARRIEDERLANG
DESIGNERLANG OCCUPANCY(%)
DIVRE1 1049092 8055982 13.02%
DIVRE2 7954193 41854999 19.00%
DIVRE3 1302972 15269121 8.53%
DIVRE4 2303331 6891033 33.47%
DIVRE5 1400282 11411332 13.12%
DIVRE6 1400282 11411332 13.12%
DIVRE7 1400282 11411332 13.12%
4.2.1.6 MSC Aggregate Reports
4.2.1.6.1 Drop Call Ratio
Location Index
ANSWERED DROPPED
DROPPED(%)TYPE Orig. Term. Total
JKT MSC
MSC1 5000000 50000001000000
0 100000 1.00%JKT MSC
MSC2
1000000
00
2000000
00
3000000
00 1000000 0.33%BDG MSC MSC_BD 1200000 1500000 2700000 150000 0.56%
Business Requirements Specification Version 1.0 Page 16 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
17/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
0 0 0BDG MSC
MSC2
25000000
20000000
45000000 200000 0.44%
MDN MSC
MSC_BD
13000000
23000000
36000000 350000 0.97%
4.2.1.6.2 CSSR
LocationTYPE
IndexSUCCESSCALL
ATTEMPTORIGIN CSSR(%)
BD MSC MSC1 2664444 27390025 98.04%
BD MSC MSC2 71050404 72585300 97.89%
BD MSC MSC_BD 38399000 39214500 97.92%
CBN MSC MSC2 25636000 26647700 96.21%CBN MSC MSC_BD 12438000 13376111 92.98%
4.2.1.6.3 HOSR
LocationTYPE
IndexHOSUCCESS
HOATTEMPT HOSR(%)
BD MSC MSC1 2664444 27390025 98.04%
BD MSC MSC2 71050404 72585300 97.89%
BD MSC MSC_BD 38399000 39214500 97.92%
CBN MSC MSC2 25636000 26647700 96.21%
CBN MSC MSC_BD 12438000 13376111 92.98%
4.2.1.6.4 TCH BLOCKING RATE
LocationTYPE
Index BLOCKATTEMPTORIGIN
BLOCKCALL(%)
BD MSC MSC1 89146 27390025 0.33%
BD MSC MSC2 9884500 72585300 13.62%
BD MSC MSC_BD 112257 39214500 0.29%
CBN MSC MSC2 7993 26647700 0.03%
CBN MSC MSC_BD 13044 13376111 0.10%
4.2.1.6.5 OCCUPANCY
Business Requirements Specification Version 1.0 Page 17 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
18/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
LocationTYPE
IndexCARRIEDERLANG
DESIGNERLANG OCCUPANCY(%)
BD MSC MSC1 1049092 8055982 13.02%
BD MSC MSC2 7954193 41854999 19.00%
BD MSC MSC_BD 1302972 15269121 8.53%
CBN MSC MSC2 2303331 6891033 33.47%
CBN MSC MSC_BD 1400282 11411332 13.12%
4.2.1.7 BSC Aggregate Reports
4.2.1.7.1 Dropped Call Ratio
Location
TYPE
Index
ANSWERED DROPPED
DROPPED(%)Orig. Term. Total
MLG
BSC
JR_0 5000000 50000001000000
0 100000 1.00%
MLG
BSC
JR_1
100000000
200000000
300000000 1000000 0.33%
MLG
BSC
MLG_0
12000000
15000000
27000000 150000 0.56%
SBY
BSC
KBL_0
2500000
0
2000000
0
4500000
0 200000 0.44%
SBY
BSC
KBL_1
13000000
23000000
36000000 350000 0.97%
4.2.1.7.2 TCH BLOCKING RATE
LocationTYPE
Index BLOCKATTEMPTORIGIN
BLOCKCALL(%)
MLG BSC JR_0 89146 27390025 0.33%
MLG BSC JR_1 9884500 72585300 13.62%
MLG BSC MLG_0 112257 39214500 0.29%
SBY BSC KBL_0 7993 26647700 0.03%
SBY BSC KBL_1 13044 13376111 0.10%
4.2.1.7.3 OCCUPANCY
Location
TYPE
Index
CARRIED
ERLANG
DESIGN
ERLANG OCCUPANCY(%)MLG BSC JR_0 1049092 8055982 13.02%
Business Requirements Specification Version 1.0 Page 18 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
19/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
MLG BSC JR_1 7954193 41854999 19.00%
MLG BSC MLG_0 1302972 15269121 8.53%
SBY BSC KBL_0 2303331 6891033 33.47%
SBY BSC KBL_1 1400282 11411332 13.12%
4.2.1.7.4 HOSR
LocationTYPE
Index HO SUCCESSHOATTEMPT HOSR(%)
MLG BSC JR_0 2664444 27390025 98.04%
MLG BSC JR_1 71050404 72585300 97.89%
MLG BSC MLG_0 38399000 39214500 97.92%
SBY BSC KBL_0 25636000 26647700 96.21%
SBY BSC KBL_1 12438000 13376111 92.98%
4.2.1.7.5 CSSR
LocationTYPE
BSCSUCCESSCALL
ATTEMPTORIGIN CSSR(%)
MLG BSC JR_0 2664444 27390025 98.04%
MLG BSC JR_1 71050404 72585300 97.89%
MLGBSC MLG_
0 38399000 39214500 97.92%
SBY BSC KBL_0 25636000 26647700 96.21%
SBY BSC KBL_1 12438000 13376111 92.98%
4.2.1.8 BTS Aggregate Reports
4.2.1.8.1 Drop Call Ratio
Location
Index
ANSWERED
DROPPED
DROPPED(%)
TYPE Orig. Term. Total
MLG BTS
BTS0010 5000000 50000001000000
0 100000 1.00%
Business Requirements Specification Version 1.0 Page 19 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
20/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
JKT BTS BTS0011 100000000
200000000
300000000 1000000 0.33%
MLG BTS BTS0012 12000000
15000000
27000000 150000 0.56%
BDG BTS BTS0013 25000000
20000000
45000000 200000 0.44%
MDN BTS BTS0014 13000000
23000000
36000000 350000 0.97%
4.2.1.8.2 HOSR
4.2.1.8.3 CSSR
Location TYPE IndexSUCCESSCALL
ATTEMPTORIGIN CSSR(%)
MLG BTS JR_0_BTS1 2664444 27390025 98.04%
MLG BTS JR_0_BTS2 71050404 72585300 97.89%
MLG BTS JR_0_BTS3 38399000 39214500 97.92%
MLG BTS JR_1_BTS1 25636000 26647700 96.21%
MLG BTS JR_1_BTS2 12438000 13376111 92.98%
MLG BTS MLG_0_BTS1 38399000 39214500 97.92%
SBY BTS KBL_0_BTS1 25636000 26647700 96.21%
SBY BTS KBL_1_BTS1 71050404 72585300 97.89%
4.2.1.8.4 TCH BLOCKING RATE
Business Requirements Specification Version 1.0 Page 20 of 43
Location TYPE IndexHOSUCCESS HO ATTEMPT HOSR(%)
MLG BTS JR_0_BTS1 2664444 27390025 98.04%
MLG BTS JR_0_BTS2 2664444 27390025 98.04%
MLG BTS JR_0_BTS3 2664444 27390025 98.04%
MLG BTS JR_1_BTS1 71050404 72585300 97.89%
MLG BTS JR_1_BTS2 71050404 72585300 97.89%
MLG BTS MLG_0_BTS1 38399000 39214500 97.92%
SBY BTS KBL_0_BTS1 25636000 26647700 96.21%
SBY BTS KBL_1_BTS1 12438000 13376111 92.98%
Location TYPE Index BLOCKATTEMPTORIGIN BLOCK CALL(%)
MLG BTS JR_0_BTS1 89146 27390025 0.33%
MLG BTS JR_0_BTS2 9884500 72585300 13.62%MLG BTS JR_0_BTS3 112257 39214500 0.29%
MLG BTS JR_1_BTS1 7993 26647700 0.03%
MLG BTS JR_1_BTS2 13044 13376111 0.10%
MLGBTS MLG_0_BTS
1 112257 39214500 0.29%
SBY BTS KBL_0_BTS1 7993 26647700 0.03%
SBY BTS KBL_1_BTS1 89146 27390025 0.33%
-
7/31/2019 PTT BRS Performance Manager v1.0
21/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
4.2.1.8.5 OCCUPANCY
Location TYPE Index CARRIED ERLANGDESIGNERLANG OCCUPANCY(%)
MLG BTS JR_0_BTS1 1049092 8055982 13.02%
MLG BTS JR_0_BTS2 7954193 41854999 19.00%
MLG BTS JR_0_BTS3 1302972 15269121 8.53%
MLG BTS JR_1_BTS1 2303331 6891033 33.47%
MLG BTS JR_1_BTS2 1400282 11411332 13.12%
MLG BTS MLG_0_BTS1 1302972 15269121 8.53%
SBY BTS KBL_0_BTS1 1049092 8055982 13.02%
SBY BTS KBL_1_BTS1 2303331 6891033 33.47%
4.2.1.9 Sector Aggregate Reports
4.2.1.9.1 Drop Call Ratio
Location
Index
ANSWERED
DROPPED
DROPP(%)
TYPE
SectorOrig. Term. Total
MLG BTS
BTS0010
Sector1 5000000 5000000
10000000 100000 1.
MLG BTS BTS0010 Sector2
100000000
200000000
300000000 1000000 0.
BDG BTS BTS0012 Sector1
12000000
15000000
27000000 150000 0.
BDG BTS BTS0012 Sector2
25000000
20000000
45000000 200000 0.
MDN BTS BTS0014 Sector1
13000000
23000000
36000000 350000 0.
MDN BTS BTS0014 Sector2
13000000
23000000
36000000 350000 0.
4.2.1.9.2 HOSR
Business Requirements Specification Version 1.0 Page 21 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
22/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
Location TYPE Index SECTORHOSUCCESS
HOATTEMPT HOSR(%)
MLG BTS JR_0_BTS1 Sector 1 2664444 27390025 98.04%MLG BTS JR_0_BTS1 Sector 2 2664444 27390025 98.04%
MLG BTS JR_0_BTS3 Sector 1 2664444 27390025 98.04%
MLG BTS JR_1_BTS1 Sector 1 71050404 72585300 97.89%
MLG BTS JR_1_BTS1 Sector 2 71050404 72585300 97.89%
MLGBTS MLG_0_BTS
1 Sector 1 38399000 39214500 97.92%
SBY BTS KBL_0_BTS1 Sector 1 25636000 26647700 96.21%
SBY BTS KBL_0_BTS1 Sector2 12438000 13376111 92.98%
4.2.1.9.3 CSSR
Location TYPE Index SECTORSUCCESSCALL ATTEMPT ORIGIN CSSR(%
MLG BTS JR_0_BTS1 Sector 1 2664444 27390025 98.04
MLG BTS JR_0_BTS1 Sector 2 71050404 72585300 97.89
MLG BTS JR_0_BTS3 Sector 1 38399000 39214500 97.92
MLG BTS JR_1_BTS1 Sector 1 25636000 26647700 96.21
MLG BTS JR_1_BTS1 Sector 2 12438000 13376111 92.98
MLG BTS MLG_0_BTS1 Sector 1 38399000 39214500 97.92
SBY BTS KBL_0_BTS1 Sector 1 25636000 26647700 96.21SBY BTS KBL_0_BTS1 Sector2 71050404 72585300 97.89
Business Requirements Specification Version 1.0 Page 22 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
23/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
4.2.1.9.4 TCH BLOCKING RATE
Location TYPE IndexSECTOR BLOCK ATTEMPT ORIGIN
BLOCKCALL(%)
MLG BTS JR_0_BTS1 Sector 1 89146 27390025 0.33%
MLG BTS JR_0_BTS1 Sector 2 9884500 72585300 13.62%
MLG BTS JR_0_BTS3 Sector 1 112257 39214500 0.29%
MLG BTS JR_1_BTS1 Sector 1 7993 26647700 0.03%
MLG BTS JR_1_BTS1 Sector 2 13044 13376111 0.10%
MLGBTS MLG_0_BTS
1 Sector 1 112257 39214500 0.29%
SBY BTS KBL_0_BTS1 Sector 1 7993 26647700 0.03%
SBY BTS KBL_0_BTS1 Sector2 89146 27390025 0.33%
4.2.1.9.5 OCCUPANCY
Location TYPE Index
SECTO
R
CARRIED
ERLANG
DESIGN
ERLANG OCCUPANCY(%)MLG BTS JR_0_BTS1 Sector 1 1049092 8055982 13.02%
MLG BTS JR_0_BTS1 Sector 2 7954193 41854999 19.00%
MLG BTS JR_0_BTS3 Sector 1 1302972 15269121 8.53%
MLG BTS JR_1_BTS1 Sector 1 2303331 6891033 33.47%
MLG BTS JR_1_BTS1 Sector 2 1400282 11411332 13.12%
MLGBTS MLG_0_BTS
1 Sector 1 1302972 15269121 8.53%
SBY BTS KBL_0_BTS1 Sector 1 1049092 8055982 13.02%
SBY BTS KBL_0_BTS1 Sector2 2303331 6891033 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.
Business Requirements Specification Version 1.0 Page 23 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
24/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
Step 4: Below is the table containing the aggregation formula at each level for each KPI:
NAME OFKPI
Formula atthe Sectorlevel
Formula atthe BTSlevel
Formula atthe BSClevel
MSC Formula at theregion level
AROP Formula atthe nationallevel
DROP CALL Call dropfor allCarriers onthe sector /AnsweredCall for allCarriers onthe sector
Call dropfor allsectors perBTS /AnsweredCall for allsectors perBTS
Call dropfor all BTSfor eachBSC/Answeredcall for allBTS for each BSC
Call dropfor all BTSfor eachMSC/Answeredcall for allBTS for each MSC
Call drop for allBTSs in theregion/Answeredcall for all BTSsin the region
Call drop forall BTSs in thearop/Answeredcall for allBTSs in thearop
Call drop for allBTSs nationwide/Answeredcall for allBTSs nationwide
CALL SETUPSUCCESSRATECSSR)
OriginationCall SetupSuccessfor allCarriers onthe sector /OriginationCall SetupAttempt forall Carrierson thesector
OriginationCall SetupSuccessfor allsectors perBTS /OriginationCall SetupAttempt forall sectorsper BTS
OriginationCall SetupSuccessfor all BTSfor eachBSC /OriginationCall SetupAttempt forall BTS foreach BSC
OriginationCall SetupSuccessfor all BTSfor eachMSC /OriginationCall SetupAttempt forall BTS foreach MSC
Origination CallSetup Successfor all BTSs inthe region /Origination CallSetup Attemptfor all BTSs inthe region
OriginationCall SetupSuccess for allBTSs in thearop /OriginationCall SetupAttempt for allBTSs in thearop
OriginationCall SetupSuccess for allBTSs nationwide /OriginationCall SetupAttempt for allBTSs nationwide
HAND OVERSUCCESSRATEHOSR)
SuccessfulHandoverfor allCarriers onthe sector /HandoverRequest forall Carrierson thesector
SuccessfulHandoverfor allsectors perBTS /HandoverRequest forall sectorsper BTS
SuccessfulHandoverfor all BTSfor eachBSC /HandoverRequest forall BTS foreach BSC
SuccessfulHandoverfor allBTSs ineachMSC /HandoverRequest forall BTSs ineach MSC
SuccessfulHandover for allBTSs in theregion /HandoverRequest for allBTSs in theregion
SuccessfulHandover forall BTSs in thearop /HandoverRequest for allBTSs in thearop
SuccessfulHandover forall BTSs nationwide /HandoverRequest for allBTSs nationwide
Business Requirements Specification Version 1.0 Page 24 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
25/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
TCHBLOCKINGRATE
TCHCongestionRatioBlockedCalls for all
Carriers onthe sector /TotalCallAttemptsfor allCarriers onthe sector
BlockedCalls for allsectors perBTS / TotalCall
Attemptsall sectorsper BTS
BlockedCalls for allBTS for each BSC /Total Call
Attemptsall BTS foreach BSC
BlockedCalls for allBTSs ineachMSC /
Total CallAttemptsall BTSs ineach MSC
Blocked Callsfor all BTSs inthe region +Total CallAttempts for all
BTSs in theregion
Blocked Callsfor all BTSs inthe arop /Total CallAttempts for
all BTSs in thearop
Blocked Callsfor all BTSsnation wide /Total CallAttempts for all
BTSs nationwide
OCCUPANCY
CarriedErlang forall Carrierson thesector /DesignErlang forall Carrierson thesector
CarriedErlang forall sectorsper BTS /DesignErlang forall sectorsper BTS
CarriedErlang forall BTS foreach BSC /DesignErlang forall BTSsfor eachBSC
CarriedErlang forall BTSsfor eachMSCs /DesignErlang forall BTSsfor eachMSC
Carried Erlangfor all BTSs inthe region /Design Erlangfor all BTSs inthe region
Carried Erlangfor all BTSs inthe arop /Design Erlangfor all BTSs inthe arop
Carried Erlangfor all BTSsnation wide /Design Erlangfor all BTSsnation wide
DataConnection
N/A RawDataCollectedat PDSN
Level
N/A RawDataCollectedat PDSN
Level
N/A RawDataCollectedat PDSN
Level
N/A RawDataCollectedat PDSN
Level
SuccessfulPackets for PDSN in theRegion / Packet
Attempts for allPDSN in theRegion
SuccessfulPackets forPDSN in theAROP /
PacketAttempts forall PDSN inthe AROP
SuccessfulPackets for PDSN nationwide / Packet
Attempts for allPDSN nationwide
Trafficability N/A RawDatacollected atthe MSCLevel
N/A RawDatacollected atthe MSCLevel
N/A RawDatacollected atthe MSCLevel
N/A RawDatacollected atthe MSCLevel
100 (CallBlocked for allMSC in Region /Effective Bidsfor all MSC inRegion)
100 (CallBlocked for allMSC in AROP/ EffectiveBids for allMSC inAROP)
100 (CallBlocked for allMSC nationwide /Effective Bidsfor all MSCnation wide)
Business Requirements Specification Version 1.0 Page 25 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
26/43
TeNOSS-Flexi Commercial in Confidence 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 Call Answer Drop call
BTS 1 5 100 0.05
BTS 2 3 200 0.015
BTS 3 6 300 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 thecurrent 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, TCHblocking rate) for that hour in which Occupancy is highest. For dataaggregated 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.
Business Requirements Specification Version 1.0 Page 26 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
27/43
TeNOSS-Flexi Commercial in Confidence 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 typeobjects and should be updated in real time as new performancevalues 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 is95.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
Business Requirements Specification Version 1.0 Page 27 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
28/43
TeNOSS-Flexi Commercial in Confidence 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 inventorypart could only be fulfilled in stage-2, e.g. circuit, trunks)
Counter Name Counter Description
Interval ofdatacollection
Display
%HLR Percentage of subscribers in
registered in HLR
60 mins Dashboard
%VLR Percentage of subscribers inregistered in VLR
60 mins Dashboard
%BHCA Busy Hour CallAttempt
60 mins Dashboard
%BH Traffic Busy Hour Traffic inpercentage
60 mins Dashboard
Inventory Specification (level of hierarchy)
Location
Area
Business Requirements Specification Version 1.0 Page 28 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
29/43
TeNOSS-Flexi Commercial in Confidence 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 Counter Description Interval of datacollection
Display
Traffic Traffic per hour inErlangs
60 mins 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 someinventory part could only be fulfilled in stage-2, e.g. circuit, trunks)
Counter Name Counter Description
Interval of datacollection
Display
Traffic Traffic per hour inErlangs
60 mins Line
ASR Incoming Answer SeizureRatio Incoming
60 mins Bar
ASR Outgoing Answer SeizureRatio Outgoing
60 mins Bar
Blockage Blockage per hour 60 mins Line
Occupancy Ratio of traffic tothe number of
60 mins Line
Business Requirements Specification Version 1.0 Page 29 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
30/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
circuits available
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 inventorypart could only be fulfilled in stage-2, e.g. circuit, trunks)
Counter Name Counter Description
Interval ofdata
collection
Display
ASR % Attempt toSeizure ratio
60 mins Dashboard
BSS traffic Traffic data for theBSS in Erlangs
60 mins Bar
Inventory Specification (level of hierarchy)
Location
Area
MSC & BSC Trunkgroup
4.3.4 Msc Sms Performance Graph
Counter Name Counter Description
Interval of data collection
Display
MO Attempt Number of Message Attemptsfrom subscriber tothe MSC
60 mins Line
MT Attempt Number of Message Attemptsfrom MSC to thesubscriber
60 mins Line
%MO SuccessRate
Percentage ofsuccessful MOmessages to theMO Attempts
60 mins Dashboard
%MT Success Percentage of 60 mins Dashboard
Business Requirements Specification Version 1.0 Page 30 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
31/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
Rate successful MTmessages to theMT Attempts
MO ShortMessage
Failures Due ToEquipmentFailure Times
Originatingmessage failure
due to EquipmentFailure Times
60 mins Line
MO ShortMessageFailures Due ToNetwork FaultTimes
Originatingmessage failuredue to NetworkFault times
60 mins Line
MO ShortMessageFailures Due ToReceiving Party
No ResponseTimes
Originatingmessage failuredue to ReceivingParty no response
times
60 mins Line
MO ShortMessageFailures Due ToServiceRestriction
Originatingmessage failuredue to ServiceRestriction
60 mins Line
MT ShortMessageFailures Due ToEquipmentFailure Times
Terminatingmessage failuredue to EquipmentFailure Times
60 mins Line
MT ShortMessageFailures Due ToReceiving PartyNo ResponseTimes
Terminatingmessage failuredue to ReceivingParty NoResponse Times
60 mins Line
Inventory Specification (level of hierarchy)
Location
Area
MSC
4.3.5 Cdma Daily Performance Graph
Counter Name Counter Description
Interval ofdata
Display
Business Requirements Specification Version 1.0 Page 31 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
32/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
collection
Attempt Total Number ofAttempts
60 mins Bar
%Blocking % Call Blocking
per hour
60 mins Dashboard
%Failure % Call failure per hour
60 mins Dashboard
%Drop % Call drop per hour
60 mins Bar
%Success % Call successper hour
60 mins Dashboard
%Processor Processor utilization
60 mins bar
Inventory Specification (level of hierarchy)
MSC
BSC
4.3.6 MSC Call Minutes Graph
CounterName
CounterDescription
Interval of datacollection
Display
On-net traffic Total on-net trafficin the hour for theselected MSC
60 mins Bar
Off-net traffic Total Off-net trafficin the hour for theselected MSC
60 mins Bar
Total traffic Total traffic(combination ofOn-net and Off-nettraffic) in the hourfor the selectedMSC
60 mins Bar
Inventory Specification (level of hierarchy)
Location
Area
MSC
4.3.7 Occupancy Report for Signaling Data Link
Business Requirements Specification Version 1.0 Page 32 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
33/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
(This is for Stage-2 because we should review the formula and counters completeness, and some inventorypart could only be fulfilled in stage-2, e.g. circuit, trunks)
Counter Name Counter Description
Interval ofdatacollection
Display
%Occupancy Occupancy inpercentage of theselected SignalingData Link per hour
60 mins 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 inventorypart could only be fulfilled in stage-2, e.g. circuit, trunks)
Counter Name Counter Description
Interval of datacollection
Display
Traffic Traffic per hour inErlangs to all theservice providerselected.
60 mins Line
ASR Incoming Answer SeizureRatio Incoming toall the serviceprovider selected.
60 mins Bar
ASR Outgoing Answer SeizureRatio Outgoing toall the serviceprovider selected.
60 mins Bar
Blockage Blockage per hour 60 mins Line
Occupancy Ratio of traffic tothe number of circuits available toall the serviceprovider selected.
60 mins Line
Business Requirements Specification Version 1.0 Page 33 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
34/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
Inventory Specification (level of hierarchy)
MSC
Trunk
4.3.9 Maximum concurrent subscribers trend for PDSN
Inventory Specification (level of hierarchy)
PDSN servers
4.3.11 PDSN Accounting Requests
CounterName
CounterDescription
Interval ofdatacollection
Display
Total AccRequests Sent
Total AccountingRequests sent
60 mins line
Acc ResponseReceived
AccountingResponseReceived
60 mins line
Business Requirements Specification Version 1.0 Page 34 of 43
Counter Name Counter Description
Interval of datacollection
Display
ConcurrentSubscribers
Provides thenumber of concurrentsubscribers loggedon to the PDSNserver on a dailybasis
60 mins bar
-
7/31/2019 PTT BRS Performance Manager v1.0
35/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
Inventory Specification (level of hierarchy)
PDSN servers
4.3.12 PDSN Authorisation Requests
CounterName
CounterDescription
Interval ofdatacollection
Raw /Derived
Total AuthRequestsSent
TotalAuthorizationRequests Sent
60 mins Bar
Auth Accept AuthorizationRequestsAccepted
60 mins Bar
Auth Reject AuthorizationRequestsRejected
60 mins Bar
Inventory Specification (level of hierarchy)
PDSN servers
4.3.13 PDSN Daily Session Statistics
Business Requirements Specification Version 1.0 Page 35 of 43
Counter Name Counter Description
Interval of datacollection
Display
Total CallsArrived
Numbers of callsarrived in the day
60 mins Line
Total CallsConnected
Number of callsconnected in the day
60 mins Line
Total CallsFailed
Number of callsfailed in the day
60 mins Line
-
7/31/2019 PTT BRS Performance Manager v1.0
36/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
Inventory Specification (level of hierarchy)
PDSN servers
4.3.14PDSN Busy Hour Session Statistics
CounterName
CounterDescription
Interval ofdata
collection
Display
BH CallsArrived
Busy Hour (BH)of calls arrived inthe day
60 mins Bar
BH CallsConnected
Busy Hour (BH)of calls
connected in theday
60 mins Bar
BH CallsFailed
Busy Hour (BH)of calls failed inthe day
60 mins Bar
BH CallsSuccessfulAuthentication
Busy Hour (BH)ofAuthenticationssuccessful in theday
60 mins Bar
BH CallsFailedAuthentication
Busy Hour (BH)ofAuthenticationsfailed in the day
60 mins Bar
Inventory Specification (level of hierarchy)
PDSN servers
4.3.15 PDSN Subscriber Statistics
Business Requirements Specification Version 1.0 Page 36 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
37/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
CounterName
Description
Interval ofdata
collection
Display
Date Date for whichdata is being
displayed
60 mins Line
Total datatransmitted tosubscribers(Mbytes)
Total datatransmitted to thesubscribers inMbps
60 mins Line
Total datareceived fromsubscribers(Mbytes)
Total datareceived fromthe subscribersin Mbps
60 mins Line
Average
throughputPDSN -->Subscribers(kbps)
AverageThroughput from
PDSN server towards thesubscribers inkbps
60 mins Line
AveragethroughputSubscribers--> PDSN(kbps)
AverageThroughput fromthe Subscriberstowards thePDSN server inkbps
60 mins Line
Inventory Specification (level of hierarchy)
PDSN servers
4.3.16 PDSN System Utilization
Counter Name Counter Description Interval of datacollection
Display
%CPU
Utilization
60 mins Bar
%MemoryUtilization
60 mins Bar
Inventory Specification (level of hierarchy)
PDSN
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
Business Requirements Specification Version 1.0 Page 37 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
38/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
collection
Traffic Traffic per hour inErlangs for theselected E1
60 mins Bar
Occupancy Occupancy per hour for the selected E1 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 inventorypart could only be fulfilled in stage-2, e.g. circuit, trunks)
Counter Name Counter Description
Interval ofdatacollection
Display
%Occupancy Occupancy in
percentage of theselected SignalingLink Channel perhour
60 mins dashboard
Inventory Specification (level of hierarchy)
MSC
Signalling Data link
Signalling Link Channel
Business Requirements Specification Version 1.0 Page 38 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
39/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
Appendices
5 Standard Performance Graphs and KPIs ProposedThis section enlists the Performance graphs and KPIs being proposed to PTT-Flexi Performance teamto 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.3Performance Escalation Matrix
Business Requirements Specification Version 1.0 Page 39 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
40/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
There are 4 levels of escalation at Flexi Telkom. The detailed explanation on each level is describedin the below attached file.
D:\PTT Telecom\PM_counters\Matrix_
5.4 Performance Reports/Graphs
No
Graphs and Report Name
1 MSC Summary Report2 Traffic and occupancy graph for a cell
3 Trunk connectivity performance graph
4 Network Performnace graph
5 MSC SMS performance summary
6 CDMA daily performnace grpah
7 MSC call minutes graph
8 Occupancy report for signalling data link
9 Interconnection performnace report
10 Maximum concurent subscribers trend for PDSN
11 PDSN AAA Statistics for IPCG Server
12 PDSN AAA Statistics For SBR Server
13 PDSN Daily Session Statistics
14 PDSN Busy Hour Session Statistics
15 PDSN Subscriber Statistics
5.5 Standard CDMA KPIs
Business Requirements Specification Version 1.0 Page 40 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
41/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
No
PerformanceIndicator
Theresholdvalue
(actiontaken)
Lowest Unit
Definition
1 CSSR 95.3%Raise alarm
And sendsms
Carrier A ratio of callestablished tocall attempt
2 DataConnection
94.50%
Raise alarm
PDSN A percentageof successfulpacket dataconnectioncompare tototal packetdataconnection to
MSC
3 Hand Over Success Rate
(Soft)
98.50 %
Raise alarm
And sendsms
Carrier Success rateof MobileStationHandoverfrom one cellto another
4 Traffic ability 98.70 %
Raise alarm
MSC A ratio of delivery calland callattempt toMSC. It is a
capability ofMSC todeliver callson a period oftime.
5 Drop Call 1.30 %
Raise alarm
And sendsms
Carrier A percentageof drop call(voice)
6 Performance of Power Supply
BTS
a. Availability A percentageof availabilityof power supply suchas PLN,Inverter,Rectifier andBattery
b. Reliability A percentageof reliability ofpower supply(electricity
andtemperature)
Business Requirements Specification Version 1.0 Page 41 of 43
-
7/31/2019 PTT BRS Performance Manager v1.0
42/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
7 TCH BlockingRate
1.80 %
Raise alarm
And sendsms
Carrier A rate of blocking calldue tounavailabilityof traffic
channel(TCH)lin BTS
8 Occupancy 10%
Raise alarmand send
sms
Carrier
9 DowntimeNetwork
10 DowntimeApproach Link
11 MTTR (Mean
Time To Repair)
5.5.1 Non Performance Related KPIs
Performance Power Supply Availability and Reliability, Downtime Network, Downtime Approach Linkand 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 bedelivered 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
-
7/31/2019 PTT BRS Performance Manager v1.0
43/43
TeNOSS-Flexi Commercial in Confidence 10th February 2009
Ref.No.
Document Name Author Version Date Location
1 SOW 12/11/08
2 Availability And Reliability.pdf 3 Down Time Approach Link.pdf
4 Down Time Network Element.pdf 5 MTTR.pdf
7 Glossary
Abbreviation MeaningADSL Asymmetric Data Subscriber Line
AG Access GatewaysAPI Application Program Interface
CPE Customer Premise EquipmentCRM Customer Relations ManagementCSR Customer Sales Representatives
DP Distribution PointDSPRP Data Service Provisioning Reengineering Project
EMS Element Management SystemFMO Future Mode of OperationIT Information Technology
MDD Mediation Device Driver MDF Main Distribution Frame
NGN Next Generation NetworksNMS Network Management System
NOC Network Operation Centre
OSS Operational Support SystemPMP Project Management PlanPSTN Public Switched Telephone NetworkSO Service Order
SS Softswitch
[END OF DOCUMENT]
Orig. Term. Total
BD 5000000 5000000 10000000 100000 1.00%
JKT 100000000 200000000 300000000 1000000 0.33%
MDN 12000000 15000000 27000000 150000 0.56%MS 25000000 20000000 45000000 200000 0.44%
SBY 13000000 23000000 36000000 350000 0.97%
TOTAL 155000000 263000000 418000000 1800000 0.43%
ANSWERED
REGION DROPPED DROPPED (%)