Value Added Services KPIs
Purpose
The purpose of these KPIs is to assist Value Added Services staff and management optimise throughput thereby helping reduce costs, and maximise profit. They provide pointers at TValue Added Services performance in the business, both as individuals and contributory components of teams and departments. KPIs use either a single parameter or a combination of parameters, often generated automatically by 'counters' whereby the output is a comprehensive performance indicator in itself. These counters can be built into the Value Added Services tools, the Value Added Services management systems or programmed individually to suit local requirements.Scope
The scope of these Key Performance Indicators is limited to activities, as defined by the organisation, to lie inder the relevant business area. However the data used by and/or collected by the counters and measurement tools could originate from anywhere within - or without - the business. Each individual KPI is reviewed to assess it's "fitness for purpose" on a periodic basis as defined by the KPI owner. This is a temporary message - once each individual 'scope" document is written, it will be replaced within the coding that produced this KPI document.Definitions
Each KPI is described by the following items:- KPI ID Number: contains the full name of the KPI.
- Target Value: contains the max or min threshold
- Frequency: describes the type of measurement i.e. daily, weekly, or monthly.
- Description: this item provides short explanation of the KPI.
- Formula: this item contains the formula composed by the counters for the KPI.
- Counters: this item contains counters used for calculation and described how they are triggered.
- Object Class: this item shows from which element the measurement statistical data are taken.
- Tools: this item shows which tool is used to calculate the KPI.
- Trigger: the event that starts the KPI measurement.
- Terminator: the event that stops the KPI measurement.
- Parameter: the limiting factor in a performance measurement
- Unit Range: this items shows the unit range value of the KPI.
- Review Period: this defines the aging process of the KPI. It helps management ensure it's use is relevant.
- Owner: this item reflects who has the authority to adjust the KPI paramaters and to whom any queries should be addressed concerning the measurements.
- Remark: this item is sometimes added to write notes and additional information.
- Process: the process or processes (or work instruction/procedure) to which this KPI is applicable.
- [3]: sub-counter 3 has to be taken.
- [1,2,4]: sub-counters 1, 2 and 4 have to be added.
- [1 - 4, 7 - 10]: sub-counters 1, 2, 3, 4, 7, 8, 9 and 10 have to be added.
- [all]: all sub-counters have to be added.
Not all Definitions apply to every KPI. Where an element has no value in the database, it is not displayed.
Note that when the average of a series of inputs is calculated, this is taken to be the arithmetic MEDIAN.
Measurables
Click on a button for more details of the KPI.Details
| KPI VAS1 | Voice Mail System Server Availability | |
| Target Value | >99.995% | |
| Frequency | Weekly | |
| Description | Voicemail System is modular, and consists of several service critical MPU units (Message Processing Units). MPU availability KPI is 99.995%, whereby servers should be available 99.995% of the time. Server Availability Statistics shows in daily basis the total downtime for the MPU units, from where the availability percentage can be calculated. | |
| Formula | (Downtime / TotalTime) * 100 | |
| Counter Descriptions |
TotalTime is the minutes of the day multiplied with number of MPUs = MPU count * 24 * 60
Where MPU count = select count (*) from mmsdb..VMU_def Downtime is the total downtime of all MPUs in minutes = ompdb..t_AlarmLog.dTimeOff – ompdb..t_AlarmLog.dTimeOn (in minutes) All rows in t_AlarmLog table should be counted, where: iModule = 88 and iAlCode = 2 and iSeverity = 1 and dTimeOff is not NULL and dTimeOff is within previous day | |
| Object Class | MPU Server | |
| Tools | VMS OMC | |
| Unit Range | % | |
| Remarks & Comment | Input of the measurement is taken from database:, Database: mmsdb, Data Tables:, VMU_def: Includes information of MPU units used in each pool, Database: ompdb, Data Tables:, t_AlarmLog: Includes system alarms, from where the downtime can be calculated. | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS2 | Voice Mail System Link Availability | |
| Target Value | >99.995% | |
| Frequency | Weekly | |
| Description | A link set becomes unavailable because of local blocking, foreign blocking, local and foreign blocking or failure of the remote processor. The specific link set between MSC and VMS server is defined, so the link availability can be measured at MSC | |
| Formula | (1 – (slsUnavailable / Granularity)) * 100 | |
| Counter Descriptions |
slsUnavailable: indicates the time during a measurement time period the link set was unavailable because of local blocking, foreign blocking, local and foreign blocking or failure of the remote processor. The counter is started when the last link of this link set assumes the “inactive” mode and is stopped when the link set is active again.
Granularity: the interval time during measurement period. | |
| Object Class | LINKSET | |
| Tools | SPOTS | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS3 | SMSC Server Availability | |
| Target Value | >99.995% | |
| Frequency | Weekly | |
| Description | Jinny uses one shell server_availability.sh. This shell uses the command fping to check each machine if is still alive each 3 sec and it saves the server availability percentage in one hour in the csv daily file. This shell increments the variable hcpt.server-counter every 3 sec for the machines, increments the variables hcpt.server-IP if this IP is alive, each one hour this shell. | |
| Object Class | SIU & MPU Server | |
| Tools | Jinny OMC | |
| Unit Range | % | |
| Remarks & Comment | The value of Service Request Successful is automatically generated by the system. | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS4 | SMSC Link Availability | |
| Target Value | >99.995% | |
| Frequency | Weekly | |
| Description | Jinny uses one shell link_availability.sh. This shell uses the command snmpget to get the value of siu.bxliux-stat. We do 4 pings every 4 or 5 sec we get the alive counters, increment the variable hcpt.link-available if the system has 2 link or more alive we increment hcpt.link-counter on each test. | |
| Object Class | SIU-MSC Links | |
| Tools | Jinny OMC | |
| Unit Range | % | |
| Remarks & Comment | The value of Service Request Successful is automatically generated by the system. | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS5 | WAP Server Availability | |
| Target Value | >99.995% | |
| Frequency | Weekly | |
| Description | The downtime of MSP service can be indicated as WAP server availability. In principle, no transaction, no service done by MSP. | |
| Formula | (1 – (OOS Duration/Granularity)) * 100 | |
| Counter Descriptions |
OOS duration: indicates the interval during the (active) server(s) goes down until the service becomes up again.
Granularity: the interval time during measurement period. | |
| Object Class | MSP Server | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS6 | WAP Link Availability | |
| Target Value | >99.995% | |
| Frequency | Weekly | |
| Description | WAP signalling is IP-based. There is no counter to measure WAP signalling link availability. | |
| Object Class | N/A | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS7 | MMSC Server Availability | |
| Target Value | >99.995% | |
| Frequency | Weekly | |
| Description | Jinny uses one shell server_availability.sh. This shell uses the command fping to check each machine if is still alive each 3 sec and it saves the server availability percentage in one hour in the csv daily file. This shell increments the variable hcpt.server-counter every 3 sec for the machines, increments the variables hcpt.server-IP if this IP is alive, each one hour this shell. | |
| Object Class | MMSC, MMBOX | |
| Tools | Jinny OMC | |
| Unit Range | % | |
| Remarks & Comment | The value of Service Request Successful is automatically generated by the system. | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS8 | MMSC Link Availability | |
| Target Value | >99.995% | |
| Frequency | Weekly | |
| Description | MMSC signalling is IP-based. There is no counter to measure WAP signalling link availability. | |
| Object Class | N/A | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS9 | USSD Server Availability | |
| Target Value | >99.995% | |
| Frequency | Weekly | |
| Description | AWS USSD solution consists of two systems which manage different purpose: USSD Gateway (to connect to HLRi) and IAS (Application Server)., For application server applies the cluster architecture (active and hot-standby IAS server). If an active IAS went down, it would automatically switch over to the standby one. When the active server became unavailable, the alarm would be raised. And when the backup server has taken over the service, the cleared alarm also raised. The OOS duration is calculated from the time difference between those two alarms generated., The USSD Gateway is stand-alone, so the OOS duration is measured each time the server became unavailable. | |
| Formula | IAS Server Availability = ( 1 – (IAS OOS Duration/Granularity)) * 100, USSD Gateway Availability = ( 1 – (USSD GW OOS Duration/Granularity)) * 100 | |
| Counter Descriptions |
IAS OOS Duration: indicates the interval (in second) during an active server became unavailable until the service taken over by standby one. This measurement is calculated by capturing the time difference of OOS alarm and cleared alarm from USSD OMC.
USSD GW OOS Duration: indicates the interval time when the USSD Gateway server became unavailable. Granularity: the interval time during measurement period. | |
| Object Class | IAS Server, USSD Gateway Server | |
| Tools | USSD OMC | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS10 | USSD Link Availability | |
| Target Value | >99.995% | |
| Frequency | Weekly | |
| Description | A link set becomes unavailable because of local blocking, foreign blocking, local and foreign blocking or failure of the remote processor. The specific link set between HLRi and USSD server is defined, so the link availability can be measured at HLRi (tbd). | |
| Formula | (1 – (OOS Duration/Granularity)) * 100 | |
| Object Class | LINKSET | |
| Tools | @Com | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS11 | PRBT Server Availability | |
| Target Value | >99.995% | |
| Frequency | Weekly | |
| Description | N/A | |
| Formula | (1 – (OOS Duration/Granularity)) * 100 | |
| Object Class | PRBT Server | |
| Tools | PRBT OMC | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS12 | PRBT Link Availability | |
| Target Value | >99.995% | |
| Frequency | Weekly | |
| Description | A link set becomes unavailable because of local blocking, foreign blocking, local and foreign blocking or failure of the remote processor. The specific link set between MSC and PRBT server is defined, so the link availability can be measured at MSC. | |
| Formula | (1 – (slsUnavailable/Granularity)) * 100 | |
| Counter Descriptions |
slsUnavailable: indicates the time during a measurement time period the link set was unavailable because of local blocking, foreign blocking, local and foreign blocking or failure of the remote processor. The counter is started when the last link of this link set assumes the “inactive” mode and is stopped when the link set is active again.
Granularity: the interval time during measurement period. | |
| Object Class | LINKSET | |
| Tools | SPOTS | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS13 | VMS Service Request Successful | |
| Target Value | >99% | |
| Frequency | Weekly | |
| Description | Service Request Successful represents the percentage of the incoming calls which are successfully answered by VMS system. | |
| Formula | (BH Successful Calls / Total BHCA Load) * 100 | |
| Counter Descriptions |
Total BHCA Load: indicates the number of incoming call received by VMS which is measured per busy hour interval (the highest value taken). This measurement is summary of all the VMS service type of calls:
- Direct Retrieval Calls - Two Stage Retrieval Calls - Deposit Calls - Missed Calls BH Successful Calls: indicated the calls which are successfully answered by VMS. This value is taken per busy hour period | |
| Object Class | MPU Server | |
| Tools | VMS OMC | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS14 | SMSC Service Request Successful | |
| Target Value | >99% | |
| Frequency | Weekly | |
| Description | Jinny uses one shell smsc_service_availability. This shell uses the command snmpget to get the value of three counters from the SIU machines gmsc.mo-fsm-ind, gmsc.mo-fsm-tout, jmgt.tcap-dlg-exh. This shell calculates the difference of the rapport (jmgt.tcap-dlg-exh + gmsc.mo-fsm-tout) / (jmgt.tcap-dlg-exh + gmsc.mo-fsm-ind) hourly and saves it on a daily basis. | |
| Counter Descriptions |
The two counters of the gmsc are added on the JINNY-GMSC-MIB
mo-fsm-ind OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Number of MAP requests sent from the SIU to the SMSC" ::= (gmsc 93) mo-fsm-tout OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION¡ "Number of MAP requests not received by the SMSC"::= (gmsc 94) The counter jmgt.tcap-dig-exh is added to the JINNY-MIB.txt jmgt OBJECT IDENTIFIER ::= (generic 17) | |
| Object Class | SIU Server | |
| Tools | Jinny OMC | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS15 | WAP Service Request Successful | |
| Target Value | >99% | |
| Frequency | Weekly | |
| Description | N/A | |
| Object Class | MSP Server | |
| Tools | MSP Server, OMC | |
| Unit Range | % | |
| Remarks & Comment | MSP server is supposed to measures the detail and total number of transactions. | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS16 | MMSC Service Request Successful | |
| Target Value | >99% | |
| Frequency | Weekly | |
| Description | Jinny use two shells get_mms_service_availability.sh and set_mms_service_availability.sh. a- set_mms_service_availability.sh: It checks two log files:, 1- The file /usr/local/apache-2.0.58/logs/access_log, you should count all the lines that contain 10.4.0.10 or mm7tomms.sh. The ones having errors >= 500 will be considered as failed requests., 2- The file /usr/local/apache-1.3.29/logs/access_log, you should count all the lines that contain 10.4.8.86 or mm7tomms.sh. The ones having errors >= 500 will be considered as failed requests., Now the (1 - failed requests / total requests) will be the succeeded rapport for the service availability that will be save in the counter sar.mms-service-availability on the MMS machine., b- get_mms_service_availability.sh: It uses the command snmpget to get the value of the counter sar.mms-service-availability and saves it in a daily basis. | |
| Counter Descriptions |
The second shell (get_mms_service_availability.sh) uses the JINNY-MIB.txt to get the value of the counter sar.mms-service-availability. This mib should contain:
sar; OBJECT IDENTIFIER ::= (generic 16) ;mms-service-availability OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "mms service availability in 1 hour" ::= (sar 2) | |
| Object Class | MMSC Server | |
| Tools | Jinny OMC | |
| Unit Range | % | |
| Remarks & Comment | The value of Service Request Successful is automatically generated by the system. | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS17 | USSD Service Request Successful | |
| Target Value | >99% | |
| Frequency | Weekly | |
| Description | Successful service request is a call which IAS terminates correctly compared with total call attempt incoming to IAS. | |
| Formula | (Completed/Session) * 100 | |
| Counter Descriptions |
Completed: Number of sessions which are successfully terminated by IAS.
Session: Number of session attempt incoming from USSD Gateway into IAS server. | |
| Object Class | IAS server | |
| Tools | USSD OMC | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS18 | PRBT Service Request Successful | |
| Target Value | >99% | |
| Frequency | Weekly | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS19 | VMS Processor Load | |
| Target Value | >20% | |
| Frequency | Weekly | |
| Description | This measurement indicates the CPU load of all active MPU servers. It is automatically measured by the system. | |
| Formula | (1 - ((CPU(L) / CPU(C))) * 100 | |
| Counter Descriptions |
CPU(C): Total CPU Capacity.
CPU(L): CPU Load. | |
| Object Class | MPU server CPU | |
| Tools | The values are reproduced by SDMS Graphical Statistics tool in Comic (Java based web interface for VMS operations) | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS20 | SMSC Processor Load | |
| Target Value | >20% | |
| Frequency | Weekly | |
| Description | This measurement indicates the CPU load of SMSC and SIU servers. It is automatically measured by the system. For load sharing architecture, it will measure CPU load off all servers. For cluster, CPU load is measured only on the active one. | |
| Formula | (1 - ((CPU(L) / CPU(C))) * 100 | |
| Counter Descriptions |
CPU(C): Total CPU Capacity.
CPU(L): CPU Load. | |
| Object Class | SIU & MPU Server CPU | |
| Tools | SMSC OMC | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS21 | WAP Processor Load | |
| Target Value | >20% | |
| Frequency | Weekly | |
| Description | This measurement indicates the CPU load of MSP and CSP servers. It is automatically measured by the system. A simple tool is developed to collect and log the value into file. | |
| Formula | (1 - ((CPU(L) / CPU(C))) * 100 | |
| Counter Descriptions |
CPU(C): Total CPU Capacity.
CPU(L): CPU Load. | |
| Object Class | MSP & TSP Server CPU | |
| Tools | MSM Console | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS22 | MMSC Processor Load | |
| Target Value | >20% | |
| Frequency | Weekly | |
| Description | This measurement indicates the CPU load of the respective server. It is automatically measured by the system. A simple tool is developed to collect and log the value into file. | |
| Formula | (1 - ((CPU(L) / CPU(C))) * 100 | |
| Counter Descriptions |
CPU(C): Total CPU Capacity.
CPU(L): CPU Load. | |
| Object Class | MMSC & MMBOX Server CPU | |
| Tools | MMSC OMC | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS23 | USSD Processor Load | |
| Target Value | >20% | |
| Frequency | Weekly | |
| Description | This measurement indicates the CPU load of IAS and USSD Gateway servers. It is automatically measured by the system. A simple tool is developed to collect and log the value into file. | |
| Formula | (1 - ((CPU(L) / CPU(C))) * 100 | |
| Counter Descriptions |
CPU(C): Total CPU Capacity.
CPU(L): CPU Load. | |
| Object Class | IAS & USSD Gateway Server CPU | |
| Tools | USSD OMC | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS24 | PRBT Processor Load | |
| Target Value | >20% | |
| Frequency | Weekly | |
| Description | Indicates the CPU load of the respective server. It is automatically measured by the system. A simple tool is developed to collect and log the value into file. | |
| Formula | (1 - ((CPU(L) / CPU(C))) * 100 | |
| Counter Descriptions |
CPU(C): Total CPU Capacity.
CPU(L): CPU Load. | |
| Object Class | PRBT Server CPU | |
| Tools | PRBT OMC | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS25 | SMS On-Net Delivery Lag | |
| Target Value | >99% | |
| Frequency | Weekly | |
| Description | The number of successfully delivered on-net SMS within 1 minute, measured at SPBH. This counter is measured every 15 minutes. | |
| Formula | SUCC_SMS_OTG / 15 | |
| Counter Descriptions | SUCC_SMS_OTG: Number of successfully acknowledged short messages that are sent to the SMS gateway (home MSC = serving MSC). | |
| Object Class | EXCHANGE | |
| Tools | SPOTS | |
| Unit Range | No Units | |
| Trigger | SUCC_SMS_OTG: Each time FORWARD SHORT MESSAGE ACK is received by the SMS gateway. | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS26 | SMS On-Net Delivery Success Rate | |
| Target Value | >99.5% | |
| Frequency | Weekly | |
| Description | SMS On-Net Delivery Successful Rate; The ratio between successfully acknowledged outgoing SMS and total outgoing SMS attempt. | |
| Formula | (SUCC_SMS_OTG / SMS_OTG_ATTEMPTS) * 100 | |
| Counter Descriptions |
SUCC_SMS_OTG: Number of successfully acknowledged short messages that are sent to the SMS gateway (home MSC = serving MSC).
SMS_OTG_ATTEMPTS: Number of short messages sent to the SMS gateway (home MSC = serving MSC). | |
| Object Class | EXCHANGE | |
| Tools | SPOTS | |
| Unit Range | % | |
| Trigger | SUCC_SMS_OTG: Each time FORWARD SHORT MESSAGE ACK is received by the SMS gateway., SMS_OTG_ATTEMPTS: Each time FORWARD SHORT MESSAGE is sent to the SMS gateway. | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS27 | MMS On-Net Delivery Lag | |
| Target Value | >99% | |
| Frequency | Weekly | |
| Description | MMS Delivered within 1 minute | |
| Unit Range | No Units | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS28 | MMS On-Net Delivery Success Rate | |
| Target Value | >99% | |
| Frequency | Weekly | |
| Description | MMS Delivery Successful Rate | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS29 | SMS Off-Net Delivery Lag | |
| Target Value | >95% | |
| Frequency | Weekly | |
| Description | The number of successfully delivered off-net SMS within 1 minute, measured at SPBH. This counter is measured every 15 minutes. | |
| Formula | SUCC_SMS_OTG / 15 | |
| Counter Descriptions | SUCC_SMS_OTG: Number of successfully acknowledged short messages that are sent to the SMS gateway (home MSC = serving MSC). | |
| Object Class | EXCHANGE | |
| Tools | SPOTS | |
| Unit Range | No Units | |
| Trigger | SUCC_SMS_OTG: Each time FORWARD SHORT MESSAGE ACK is received by the SMS gateway. | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS30 | SMS Off-Net Delivery Success Rate | |
| Target Value | >95% | |
| Frequency | Weekly | |
| Description | SMS Off-Net Delivery Successful Rate; The ratio between successfully acknowledged outgoing SMS and total outgoing SMS attempt. | |
| Formula | (SUCC_SMS_OTG / SMS_OTG_ATTEMPTS) * 100 | |
| Counter Descriptions |
SUCC_SMS_OTG: Number of successfully acknowledged short messages that are sent to the SMS gateway (home MSC = serving MSC).
SMS_OTG_ATTEMPTS: Number of short messages sent to the SMS gateway (home MSC = serving MSC). | |
| Object Class | EXCHANGE | |
| Tools | SPOTS | |
| Unit Range | % | |
| Trigger | SUCC_SMS_OTG: Each time FORWARD SHORT MESSAGE ACK is received by the SMS gateway., SMS_OTG_ATTEMPTS: Each time FORWARD SHORT MESSAGE is sent to the SMS gateway. | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS31 | MMS Off-Net Delivery Lag | |
| Target Value | >95% | |
| Frequency | Weekly | |
| Description | MMS Delivered within 1 minute | |
| Unit Range | No Units | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS32 | MMS Off-Net Delivery Success Rate | |
| Target Value | >95% | |
| Frequency | Weekly | |
| Description | MMS Delivery Successful Rate | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS33 | SMS International Delivery Lag | |
| Target Value | >95% | |
| Frequency | Weekly | |
| Description | The number of successfully delivered international SMS within 1 minute, measured at SPBH. This counter is measured every 15 minutes. | |
| Formula | SUCC_SMS_OTG / 15 | |
| Counter Descriptions | SUCC_SMS_OTG: Number of successfully acknowledged short messages that are sent to the SMS gateway (home MSC = serving MSC). | |
| Object Class | EXCHANGE | |
| Tools | SPOTS | |
| Unit Range | No Units | |
| Trigger | SUCC_SMS_OTG: Each time FORWARD SHORT MESSAGE ACK is received by the SMS gateway. | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS34 | SMS International Delivery Success Rate | |
| Target Value | >95% | |
| Frequency | Weekly | |
| Description | SMS International Delivery Successful Rate; The ratio between successfully acknowledged outgoing SMS and total outgoing SMS attempt. | |
| Formula | (SUCC_SMS_OTG / SMS_OTG_ATTEMPTS) * 100 | |
| Counter Descriptions |
SUCC_SMS_OTG: Number of successfully acknowledged short messages that are sent to the SMS gateway (home MSC = serving MSC).
SMS_OTG_ATTEMPTS: Number of short messages sent to the SMS gateway (home MSC = serving MSC). | |
| Object Class | EXCHANGE | |
| Tools | SPOTS | |
| Unit Range | % | |
| Trigger | SUCC_SMS_OTG: Each time FORWARD SHORT MESSAGE ACK is received by the SMS gateway., SMS_OTG_ATTEMPTS: Each time FORWARD SHORT MESSAGE is sent to the SMS gateway. | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS35 | MMS International Delivery Lag | |
| Target Value | >95% | |
| Frequency | Weekly | |
| Description | International MMS Delivered within 1 minute | |
| Unit Range | No Units | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |
| KPI VAS36 | MMS International Delivery Success Rate | |
| Target Value | >95% | |
| Frequency | Weekly | |
| Description | International MMS Delivery Successful Rate | |
| Unit Range | % | |
| Process | 3.4 Service Quality Performance Management | The eTOM derived process associated with this KPI, or it supports, is called Service Quality Performance Management |