SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

Software Requirements Specification

For
Performance Management System

submitted to

Bharti Airtel Limited

submitted by

NMSWorks Software Pvt. Ltd., Chennai

B-103, Bava Road
4th Street, Abhiramapuram
Chennai 600 018
Ph: +91-44-2257 9803/ 2257 0433
Fax: +91-44-2257 0473
Web: www.nmsworks.co.in

Confidential & Proprietary

Page 1 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

Revision History

SI

Versi
on

Date

Status

Author

Change Type

Reason
Change

1.0

27-Jul-2010

Draft

Jaikumar B

Added

Initial creation

1.1

19-Nov2010

Draft

Jaikumar B

Added/Modified

1.0 Review
addressed

1.2

3-Jan-2011

Revised
Draft

Jaikumar B

Added/Modified

Inputs from
during
discussion

1.3

29-Jan-2011

Revised
Draft

Jaikumar B

Added/Modified

Review
comments
from BAL on 28Jan
11

1.4

2-Feb-2011

Revised
Draft

Jaikumar B

Added/Modified

Review Inputs with

BAL team on 2 Feb
11

1.5

10-Feb2011

Final
Draft

Jaikumar B

Added / Modified

Review
comments
from BAL on 9Feb 11

Distribution List
SI

Name

Role

Manickavasagam

Delivery Operations Head

Ismail

Lead Software Development

Jaikumar

System Engineer

QA

QA

Anand Srivastava

Customer Representative (AirTel)

Approval
SI

Name

Role

Manickavasagam

Operations Head

Anand Srivastava

Customer Representative (AirTel)

Confidential & Proprietary

Page 2 of 72

for

Inputs

BAL
SLA

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

Identification

Identification Number:
Identification Name:
Title:

PMS Airtel/SRS/Version 1.5 Revision 0.4

SRS of PMS for BAL
Software Requirement Specifications of
CygNet Performance Management System for
BAL, Transmission Network

Abbreviation:
Version No.
Revision No.

Confidential & Proprietary

CygNet PMS SRS

1.5
0

Page 3 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

Table of Contents
1

Statement of Confidentiality ....................................................................................................... 6

Introduction ............................................................................................................................... 7
2.1

Objective ............................................................................................................................. 9

Requirement Analysis ............................................................................................................... 10

CygNet PMS General Requirements ....................................................................................... 12

CygNet PMS System Overview ............................................................................................... 14

5.1

CygNet High Level Architecture.......................................................................................... 14

CygNet PMS - Product Features ................................................................................................ 15

6.1

Encompassability: .............................................................................................................. 15

6.2

Accuracy ............................................................................................................................ 15

6.3

Scalability .......................................................................................................................... 15

6.4

Extensibility ....................................................................................................................... 16

6.5

Flexibility ........................................................................................................................... 16

6.6

Integrability ....................................................................................................................... 16

6.7

Interactiveness .................................................................................................................. 16

6.8

Seamlessness ..................................................................................................................... 16

6.9

Usability ............................................................................................................................ 16

6.10

High Availability ................................................................................................................. 16

CygNet Security Management ................................................................................................... 17

CygNet PMS - Redundancy & Disaster Recovery ........................................................................ 18

8.1

Backup and Restore ........................................................................................................... 18

8.2

Disaster Recovery .............................................................................................................. 18

8.3

Dependencies .................................................................................................................... 20

Feature Requirements .............................................................................................................. 21

Confidential & Proprietary

Page 4 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

9.1

PM Data Collection ............................................................................................................ 23

9.2

PM Data Storage: ............................................................................................................... 24

9.3

GUI Based PM Reports ....................................................................................................... 25

9.4

SLA & Service based PM Reports ........................................................................................ 36

9.5

Comparative PM Reports ................................................................................................... 40

9.6

PM Reports SDH/DWDM ................................................................................................. 47

9.7

PM Reports OTN ............................................................................................................. 49

9.8

Ethernet PM Reports ......................................................................................................... 50

9.9

PM - Database Backup & Restore ...................................................................................... 54

9.10

PMS Application Performance ......................................................................................... 55

9.11

PM Security Management ............................................................................................... 56

10

Integration of OSS/BSS with CygNet PMS .......................................................................... 59

10.1

Metasolv M6 Integration ................................................................................................... 59

10.2

UGIS Fiber Management System Integration ................................................................... 60

10.3

Remedy Trouble Ticketing System Integration ................................................................ 60

10.4

e-CRM Integration ............................................................................................................ 61

11

Hardware & Software Specifications ................................................................................. 62

11.1

Primary Site ....................................................................................................................... 62

11.2

Disaster Recovery Site ....................................................................................................... 66

12

References .......................................................................................................................... 69

13

Abbreviations...................................................................................................................... 70

14

Annexure .............................................................................................................................. 72

Confidential & Proprietary

Page 5 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

1 Statement of Confidentiality

This document contains information confidential to NMSWorks and Bharti Airtel, which are
provided for the sole purpose of permitting Bharti Airtel to evaluate the document submitted
herewith. Reproduction, transmission or translation in any form or by any method, electronic,
manual, mechanical, optical or otherwise or unauthorized circulation is strictly prohibited. This
document shall be treated at all times as a confidential and proprietary document for internal
use only. If you are not authorized to have access to this document or have received it by
mistake, or by deliberation through unauthorized sources, please return it immediately or
inform us at the address given below to arrange for its collection:

NMSWorks Software Pvt. Ltd.

B-103, Bava Road,
4th Street, Abhiramapuram
Chennai 600 018
Ph : +91-44-2257 9803
Fax: +91-44-2257 0473

Confidential & Proprietary

Page 6 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

2 Introduction

Bharti Airtel Limited is Indias largest integrated and the first private telecom services
provider with a footprint in all the 23 telecom circles of India, Since its inception it has been
the forefront of advanced network deployments, and has set the benchmark for other
operators in India.
Bharti Airtel has been structured into three individual strategic business units (SBUs)

Mobile Services,

Airtel Telemedia Services &

Enterprise Services.

The mobile business provides mobile & fixed wireless services using GSM technology
across 23 telecom circles while the Airtel Telemedia Services business offers broadband &
telephone services in 95 cities and we have recently launched India's best Direct-to-Home
(DTH) service, Airtel digital TV and IPTV. The Enterprise services provide end-to-end
telecom solutions to corporate customers and national & international long distance services
to carriers. All these services are provided under the Airtel brand.
Transport Network Group (TNG) is one of the network organization responsible to provide
Long distance services for data and voice services alongwith Mobility backhaul services.
TNG has SDH/DWDM, ASON, Internet backbone, MPLS backbone, Voice switch networks.
There are currently More than 13,000 transport Nodes in the network, 135 IP and MPLS
PoPs and 17 switch locations across the country. TNG offers clear channel bandwidth, L2
VPN, L3VPN, Multicast, video streaming, IPTV/DTH content distribution and to the SBUs.
Bharti has robust network management processes for ensuring high degree of network and
service performance efficiencies.

Today's networks are complex, heterogeneous, and of large size. With the changing Business
scenarios & requirements, proactive network monitoring becomes of vital importance. It

Confidential & Proprietary

Page 7 of 72

SRS for Performance Management System

dated 22nd November 2010

Ref: NMSWorks/Airtel/Performance Management

became imperative to develop mechanism through which one not only monitor the network
health proactively, but also take corrective measures proactively is required.

End-to-end

service performance monitoring becomes crucial aspect given the criticality & sensitivity of the
application to service degradations being run by the customers. Investing in a standards based
Performance Management system will result in cost savings in accommodating future
expansions and integrating with other systems.
CygNet Performance Management solution for Bharti Airtel is such an extensible, standards
based system designed to enable a integrated Performance Management of the network out
of which customized views can be easily extracted.

About the Company

NMSWorks Software Pvt. Ltd. (NMSWorks) is a Software Product and Services Company in
the Network Management System (NMS) and Operation Support System (OSS) Solutions
space and markets the Products with the brand name CygNet. CygNet NMS is a vendor
neutral,

standards

compliant

and

unified

platform

for

Integrated

Management

of

Heterogeneous Telecom and Data Networks.

Founded in 2001 and headquartered at Chennai, India, NMSWorks has been incubated by the
TeNeT group at IIT- Madras, and promoted by Polaris Software Lab Ltd, one of the leading
providers of Software Products & Services in the BFSI sector. Dr. Mani Subramanian, a wellrecognized name in the Network Management field is the Chairman & Technical Advisor of the
company. Dr. Timothy Gonsalves, Professor and Head of the Computer Science Department at
IIT Madras and Prof. Ashok Jhunjhunwala, head of the TeNeT Group at IIT Madras are active
advisors of the Company. The company has been funded by outside investors and is on a
profitable fast-track growth.
NMSWorks is in the fore front of developing Network Management Software and that integrates
and manages Datacom, Telecom, Transport and Broadband access networks. NMSWorks,
over a period of time has been successful in developing a suite of products in the Network
Management space and in the process has accumulated significant domain expertise in the
NMS space. The Companys flagship product, CygNet, clearly distinguishes itself from its
competitive products in the market. It is an Indigenous product and serves the Indian Defence
and Telecom Service Providers.

Confidential & Proprietary

Page 8 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

NMSWorks has undertaken certain pioneering work in integrating multi-vendor multitechnology platforms in the Optical Transmission space, which has attracted the attention of
many Telecom Service Providers, like Tata Communications, Bharti Airtel, Vodafone Essar,
Reliance Communications, Tata Teleservices, Idea Cellular, Aircel, BSNL, MTNL, Railtel,
Power Grid Corporation etc and also Telcos in the near shore, Africa and Middle East and
South East Asian countries.
NMSWorks has a full featured Product/Solution for the Management of Multi-vendor Multitechnology Optical Transmission Networks under the brand name CygNet OTNMS. The
Products/Solutions of the company are being deployed by Telecom Service Providers, in India.
Service Impact Analysis (SIA) , Root Cause Analysis (RCA) across multi-vendor platforms &
Performance Management Systems integrating multiple vendor systems have helped Service
providers to provide proactive customer support.
The Optimal Path Computation Algorithm developed by NMSWorks not only automates the
process of Circuit Provisioning but also helps the Service Provider to exploit the full potential
out of the available SDH/DWDM infrastructure. The Circuit Discovery Module in conjunction
with Topology Discovery and Network Inventory Discovery facilitates optimizing the CAPEX,
not only by bandwidth grooming but also by identifying hanging circuits and deleting them.
NMSWorks has also identified the Defence market as a strategic market for the companys
products and solutions.

NMSWorks has been working closely with not only the Defence

Development agencies like DRDO, CAIR etc, but also with Public Sector Enterprises like BEL,
ITI and ECIL, who are in the forefront of supplying Communication systems to Defence.
NMSWorks Shares the vision of the TeNeT group of IIT Madras, in developing World Class
Technologies at affordable prices. Implicit in this approach is the creation of a developmental
environment in India to sustain innovation in the high end technology development space.

2.1 Objective
The purpose of this document is to provide the overall description, specific requirements, the
functionality, constraints, characteristics, dependencies and various features of the
Performance Management System to be developed

Confidential & Proprietary

Page 9 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

3 Requirement Analysis

In the current scenario, performance management is being done with the help of creating PM
profile on different vendor EMSs and then activating the particular port/service which needs to
be monitored. Following are the challenges with the current scenario.
Network comprises of multi- vendor equipments having their own EMSs and single EMS having
multiple PM profiles (Due to limitation of no. of ports in a PM profile) leading to a more complex
situation.
Multi vendor EMSs are being managed by their respective NMS, while traffic is build up across
these systems leading to end to end management as a challenge. This creates islands of
management lacking overall view of Network which can enable it to monitor end to end
services.
Following are the major business goals to be achieved:

Integration of All Vendor EMSs/NMS of existing transport technologies i.e. SDH,DWDM,

ASON in order to have overall view of Network on single platform.

To collect and report service performance information for SLA management purposes:

Performance management capabilities of the Tool will enable BAL to extend service
level guarantees to customers with confidence and to measure accurately the actual
performance against the guarantees.

To collect and report network performance data for own network evaluation purposes:

Performance management capability of the tool will enable BAL to create

comprehensive performance reports from both a network and a service viewpoint, as an
aid to seeing Best and Worst performer in the network, Failure Trends, Current
experience against history.

To collect and report network and service performance data on daily basis for proactive
monitoring of the Network health.

To collect and report co-relation of the PM parameters with the problematic area in the
network for early detection and resolution of the failures i.e. for maintenance purpose.

Confidential & Proprietary

Page 10 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

PMS tool is expected to manage the complete Transmission network, both TNG and
ANG, which comprises of SDH, DWDM, ASON, Packet Transport and OTN
technologies. This work comprises of integration of Performance Management for the
following vendors,

TNG Network

Alcatel

Huawei

ECI

Tellabs

Nortel

ANG Network

Tejas

Seimens

Alcatel

ECI

Huawei

Confidential & Proprietary

Page 11 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

4 CygNet PMS General Requirements

A. The proposed solution is to provide the PMS tool in two phases

Phase 1:
In Phase 1, the User Interface for Report Configuration & Report Presentation and the
Performance Management Adapters for the following vendor systems corresponding to
TNG Network will be implemented
a. Alcatel
b. Huawei
c. ECI
d. Tellabs
e. Nortel

Along with the PM integration of the above vendor systems , Metasolv M6 OSS shall also
be integrated to retrieve and map the inventory information during Phase-I.
Phase 2:
In Phase 2, the following Performance Management Adapters for the following vendor
systems corresponding to ANG Network will be implemented
a. Tejas
b. Siemens
c. Alcatel
d. ECI
e. Huawei

Confidential & Proprietary

Page 12 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

Along with the PM Integration of the above vendor systems, UGIS Fiber Management System
and Remedy Trouble Ticketing system shall be integrated with the PMS Application.

B. PMS Application shall contain software adapters for each of the type of elements.

These

adapters are software modules which will reside in the server called Mediation Server MS.
C. The PM tool shall interface with various vendors NMS/EMS systems as mentioned in
section A above , using available NBI such as SNMP, TMF814, TMF854 or FTP based as
specified in the Integration Requirements.
D. PMS tool shall integrate with Inventory management systems (Metasolv M6) for network
discovery and service definitions enabling network and service level performance
monitoring and reporting through the interface specified in the Integration Requirements.
E. PMS tool needs to be integrated with UGIS fiber database so that proper action can be
triggered for lossy fibers through the interface specified in the Integration Requirements.
F. PMS tool shall also be integrated with Remedy TTS through the defined approach for
integration in the Integration Requirements.
G. Performance Management for all the parameters as specified in the RFP by Bharti Airtel
Ltd,

which are supported by the respective vendor NMS/EMS, will be developed and

deployed for the above types of elements.

H. The Performance measurement will be presented in a report format as specified by BAL
team.
I.

PMS Application will also have an NBI for providing the information gathered from the
EMSs/ NMSs to some other application.

J. PMS Application shall have generic object modeling inside following standard modeling like
TMF814/854 so that future transport technologies support is guaranteed.
K. Performance management operations such as - Enable PM, Disable PM, Set TCA,
Retrieve PM enabled entity, Get PM reports - historic/current needs to be supported by the
PMS tool to perform PM operations on the network via EMS/NMS interfaces of various
vendors as supported by the respective EMS/NMS.
L. The PMS tool platform architecture shall be client/server based where client will be
PC/Laptop based lightweight Web interface.

Confidential & Proprietary

Page 13 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

5 CygNet PMS System Overview

5.1 CygNet High Level Architecture

CygNet PMS is highly customizable and is capable of managing diverse technologies and
vendors. It incorporates a mediation server that translates the proprietary interfaces of network
elements to the TMF 814 format. The core CygNet Server and client provide network
management functionality based on the TMN FCAPS (Fault, configuration, Accounting,

Confidential & Proprietary

Page 14 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

Performance and Security) model. The management functions are performed over a map
based GUI and support several user levels (administrator, operator, etc.) with appropriate
privileges for performing management functions. CygNet manages the network either through
EMS or Agents or the Network Elements directly.
CygNet INMS/OSS has a loosely coupled, modular architecture thereby allowing for mixing
and matching of plug-and-play modules. The Performance Management System is one such
module which interfaces seamlessly with other CygNet modules. The architecture of the Java
middleware version of the product and the relative positioning of the PMS module within the
system is shown below. For the non-middleware version the interfaces between the modules
are replaced by native calls or RMI.

6 CygNet PMS - Product Features

6.1 Encompassability:
The generic standards TMF SID based information model at the core of the product allows it to
encompass a wide variety of network technology including IP, MPLS and Optical networks.
This makes the product future proof. For example the service and resource modeling
encompasses both MPLS and SDH networks. For SDH the service is a raw bandwidth service
and its associated characteristics such as layer rate, the resources are MEs, cross connects
fibers. MPLS networks are again modeled based on services and resources, here the service
could be a VPN service and the associated resources are routers and ports.

6.2 Accuracy
The product works real-time in conjunction with integrity checks to keep the inventory in sync
with the inventory database.

6.3 Scalability
The product's loosely coupled architecture allows, in addition to vertical scalability by using
more powerful computing systems, horizontal scalability by adding more systems to the
product physical configuration. The product comes with an option to adopt an enterprise
architecture and implements them using application servers. These application server based

Confidential & Proprietary

Page 15 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

product configuration provides for expanding the network in a distributed architecture

environment affording massive scalability, by enabling capacity boost on demand.

6.4 Extensibility
The software is so architected, making full use of object orientation, that it supports ease of
extensibility. This ease of extension will be reflected in the ease with which the software can be
configured to handle future tasks. This includes for example, handling new types of networks.

6.5 Flexibility
The PM system's capability to provide different types of reports makes it a flexible product that
can be molded according to specific functional needs ranging from service oriented reports to
resource oriented reports.

6.6 Integrability
The standards based nature of the product supporting generic interfaces allows for easy
integration with other products. The product allows an option to be configured with SOA based
loosely coupled interfaces which will further enhance the integrability.

6.7 Interactiveness
The performance management system is not just a passive repository of information. The
system can send notifications to the user modules about significant events in the PMS which in
turn can be configured as per the requirements of the user.

6.8 Seamlessness
In combination with other CygNet modules the performance management system seamlessly
deploys along with NMS and other OSS components making available the facilities offered by
the performance management system across the enterprise.

6.9 Usability
Intuitive graphical user interfaces makes the product easy to use with minimum training
overheads. The System supports a web based HTML client that can be accessed via a
standard browser.

6.10 High Availability

The setup provides an N+1 local redundancy, Disaster Recovery and External Storage Device
for data backup so that overall system availability is very high. Under normal conditions the DR
servers, N+1 local redundant server and External Storage Device will continuously synchronize
itself with the active server for the information that are needed for the passive server to come

Confidential & Proprietary

Page 16 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

up with the same setup as the active. The synchronization is scheduled at regular interval,
which is configurable.

7 CygNet Security Management

Security management in CygNet does authentication and authorization of the NMS users for
secure access to the NMS. The user will be authenticated on a single sign-on basis.
CygNet identifies several classes of users with different access rights. The system allows
levels of privileges based on passwords. All users have to be authenticated before they log on
to CygNet. For example, administrators may perform many functions including:
Poll Configuration of managed elements
Adding deleting CygNet users
Changing passwords for CygNet users
Users can change their passwords dynamically. Operations that a user is entitled to perform
are restricted based on the password. The passwords are stored in encrypted format in the
database.
Solaris is the OS on top of which all the applications are deployed; the OS will be hardened for
basic security. The system can be further protected by having an external firewall, the firewall
can be opened for few required ports from know IP address to make it more secured.
The Security Management module in CygNet also has Audit Trial module, which maintains a
log of the various operations performed by all the users of the system.

Confidential & Proprietary

Page 17 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

8 CygNet PMS - Redundancy & Disaster Recovery

8.1 Backup and Restore
The Backup and Restore module is the tool that is used to schedule a backup. The Backup
Configurator GUI has three screens.
1. Backup: Used to schedule the backup.
2. Restore: Used to restore
3. Edit: Used to edit the previously scheduled configuration.
Backup menu helps to schedule the backup in the selected Device. The module supports two
types of backup medium.
1. Hard Disk
2. Tape Drive
The user can use any one of the medium to do backup. The backup can be done either ondemand or can be scheduled (daily, weekly etc).
The restore facility allows the user to restore the archived data to the system with minimum
effort with in short period of time.

8.2 Disaster Recovery

Under normal conditions the passive server will continuously synchronies itself with the active
server for the information that are needed for the passive server to come up with the same
setup as the active. The synchronization is scheduled at regular interval, which is configurable.
The active and passive servers monitor each other for the status at regular interval (Heartbeat).
Depending on the result the servers change their status from active to passive or vice versa.
The Heartbeat interval is configurable and the status checking includes the actual applications
and the other software and hardware modules the application depends on. The redundancy
module looks at the three Hardware Subsystems as a single system and takes care switching

Confidential & Proprietary

Page 18 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

to the Disaster setup in case of failures. The operator can decide on the whether the
switchover in case of failure should need manual intervention or should it be Auto-Switchover.

DR SITE

MAIN SITE

SUN
T6340

SUN
T5440

LAN

LAN

SUN
T6320

SUN
T6320

SUN
T6320

SUN
T6340

SUN
T5440

SUN
T6340

SUN
T5440

SUN
T6320

SUN
T6320

SUN
T6320

Tape
Drive

SAN
SWITCH

SAN
SWITCH

SAN
SWITCH

STORAGE

STORAGE

Application Server

Application Server

Database + Redundancy Server

Database Server

Mediation Server

Mediation Server

N+1 Redundant Server

Confidential & Proprietary

Page 19 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

8.3 Dependencies

EMS/NMS shall provide access through NBI/proprietary interface to collect the PM

data at both 15 min and 24 hr granularities for the required KPIs

NBI or the interface provided by the EMS/NMS shall provide options to enable/disable
PM data collection in the respective EMS/NMS.

NBI provided by the EMS/NMS shall support modifying/enabling/disabling thresholds

governing TCA from the respective EMS/NMS

Inventory information shall be provided through offline dumps from Metaslov M6 system
with the required attributes.

UGIS- Fiber Management System dumps shall provide the mapping information of the
fiber pairs connected to the optical ports.

Notifications from PMS server to the Remedy Ticketing system for integration shall be
accepted by the Remedy Ticketing server with the required configurations done.

Confidential & Proprietary

Page 20 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

9 Feature Requirements

The main task of Network management systems is to monitor and control the network
infrastructure. As networks increase in size, heterogeneity and complexity, effective
management of such networks becomes more important and much difficult. Pro-actively
managing the Network's health and performance is indispensable for any critical business and
is something which the administrators of large networks have to put in place.
Goals

Data collection for the KPIs supported by the NE/EMS/NMS

Interpreting the collected data

Disseminating and Reporting the data

Presenting the data

The performance module is made up of following components:

Data Collection Service (Protocol neutral data Collection) This module provides multi
protocol data collection support. Data can be collected from SNMP devices, TMF 814
device like Optical Network Mediation device etc. Default data collection takes place
through the TMF 814 NBI available in the EMS/NMS. The module provides flexibility to
customize the data collection process that suits user requirements by integrating using
the proprietary interfaces provided by the EMS/NMS systems where TMF 814 based
NBI is not available.

Data Collection Objects (Modeling Polling Units) Data collection process has been
modeled using the objects that define what data is to be collected and where to store
the collected data.

Scheduler This module facilitates the scheduled data collection process at specified
interval of time. Based on the given interval of time, Scheduler schedules the data
collection process from the respective NE/EMS/NMS. Scheduler performs the report
generation based on the specifications such as which report should be generated when

Confidential & Proprietary

Page 21 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

(day and time) and how often. Scheduler also schedules the clean up of data base
tables at specified periodicity.

Reports The collected data can be grouped into meaningful sets and represented in
formatted manner called Reports.

Fig . Performance Management - Architecture

Confidential & Proprietary

Page 22 of 72

SRS for Performance Management System

dated 22nd November 2010

Ref: NMSWorks/Airtel/Performance Management

9.1 PM Data Collection

SRS_BAL_PMS_DC1.

PMS shall collect PM data from the respective

EMS/NMS

through its NBI interface or the provided interface for PM data collection for all the ports
that are PM enabled. PM profile creation in the EMS is not required if PM is enabled for
the ports by default and PM data is available through the provided interface.
SRS_BAL_PMS_DC2.

PMS shall poll the PM data to be collected from the EMS/NMS

for the PM Points (Layer Rate/Location/Granularity/Parameter) including all the KPIs

supported by the EMS/NMS for all the enabled ports (PTP/CTP) at regular scheduled
intervals. Respective EMS/NMS shall be polled at optimum poll intervals to retrieve the
latest PM data as supported by the EMS/NMS
SRS_BAL_PMS_DC3.

PMS shall collect data only for the PM points that are enabled or

provision made available for enabling PM in the supported vendor EMS/NMS.

SRS_BAL_PMS_DC4.

PMS shall collect the PM data in both 15 minutes and 24hrs

granularity as supported by the supported optical vendor EMS.

SRS_BAL_PMS_DC5.

PMS shall also provide option to collect the current PM data or

the latest PM data available from the EMS/NMS for debugging in nearest possible realtime for any customer complaints escalation during 24hrs period.
SRS_BAL_PMS_DC6.

PMS shall collect and store for Standard SDH Error parameters

(ES, SES, BBE and UAS), Optical, Power or any vendor specific parameters (Note:
Subjected to PM data availability in supported optical vendor EMS), which shall include
all the KPIs supported by the EMS/NMS.
SRS_BAL_PMS_DC7.

PMS shall log the PM data collection events to verify the data

collection at regular intervals.

SRS_BAL_PMS_DC8.

PMS shall raise alerts for the failure events in PM data collection.

Alerts shall contain appropriate error messages indicating the cause of the failure .
SRS_BAL_PMS_DC9.

PMS shall provide option to enable / disable performance

monitoring on a per managed object basis. It shall also provide the ability to
enable/disable monitoring on a bulk basis. However, enabling/disabpling PM depends
on the support provided by the EMS/NMS through the available interface for PM.
SRS_BAL_PMS_DC10. PMS shall provide facility for automatic initiation
collection

for

the

managed

object

on

EMS/NMS

in

case

of

of PM data
new object

addition/modification in the network as provided by the inventory dumps. PMS shall

provide option to enable PM for the newly added ports .

Confidential & Proprietary

Page 23 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

SRS_BAL_PMS_DC11. PMS shall not have any limitation with respect to maximum
number of monitoring ports/objects being added and also shall have no limitation w.r.t.
enable/disable performance monitoring on no. of monitoring ports/objects, however this
depends on the maximum number of ports supported by the respective EMS/NMS.
SRS_BAL_PMS_DC12. PMS shall provide a consolidated list of the following:
a. PM Enabled ports - for each vendor
b. PM Disabled ports - for each vendor
c. PM Data collected ports - ( subset of the PM Enabled ports)
d. PM enabled but data unavailable ports - ( subset of
the PM Enabled ports)
SRS_BAL_PMS_DC13. PMS shall provide option for near real time or latest PM data
extraction from EMS/NMS objects depending on the respective EMS/NMS current PM
Data availability for extraction.
SRS_BAL_PMS_DC14. PMS shall raise a critical alarm/e-mail notification for define
stakeholders if a performance data collection operation fails. Alarm/Notification detail
shall include source identification, time of failure & associated causes for the failure

9.2 PM Data Storage:

SRS_BAL_PMS_DS1.

PMS shall store raw data collected from the supported optical

vendor EMS/NMS as statistical tables staggered across individual days.

SRS_BAL_PMS_DS2.

PMS shall store the poll configuration data needed for data

collection.
SRS_BAL_PMS_DS3.

PMS shall purge the historical statistical PM data on a periodic

basis as agreed in the purging policy as one year PM data older than one year shall be
archived and deleted from the PMS Database.
SRS_BAL_PMS_DS4.

PMS shall provide options to access the archived PM data

reports.
SRS_BAL_PMS_DS5.

PM Data collection and storage is done for unique PM Points of

the ports of the NE. PM Point is modelled as:

Layer Rate (Optical/RS/MS/HO/LO)

Location (Near End/Far End)

Granularity (15 min/24 hour)

Parameter (ES/SES/UAS/BBE)

Confidential & Proprietary

Page 24 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

9.3 GUI Based PM Reports

SRS_BAL_PMS_REP1.

PMS shall provide GUI based reporting using highly secured

Web Interface.
SRS_BAL_PMS_REP2.

PMS shall provide the following 3 types of reports as suggested

a. Consolidated Reports in Home Page ( Hot Reports)

b. Reports defined using Report Configurator
c. Custom Reports - for user generation
SRS_BAL_PMS_REP3.

PMS shall provide PM Reports at NE and Link level for individual ports

including SDH Error, Optical, Power, Ethernet and any vendor based proprietary KPIs.
Report Attributes
Report Generation Time , user
Port Details Node Name , Node Id ( Optional), Port Name , Port ID ( optional),
Layer Rate
Granularity chosen- 15 min or 24h , Duration - ( period selected for PM Report generation)
PM Report - Graph ( X axis - Time
PM Report Table
Time , KPI1, KPI2,.,KPIn
Sample Report

Confidential & Proprietary

Y - axis -

KPI

Page 25 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

SRS_BAL_PMS_REP4.

dated 22nd November 2010

PMS shall provide PM Reports based on the historical

performance data collected at any monitored point and archived on the server. The
retrieval operation shall allow filtering, based on user settable parameters like Vendor
Type, NE Type, Port Type (PTP/CTP), Circuit Id, Service Name, Customer, Layer Rate,
Port Number, Granularity (15 minutes / 24 hours) and Duration.

Confidential & Proprietary

Page 26 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

SRS_BAL_PMS_REP5.

dated 22nd November 2010

PMS shall facilitate display of reports at any point of time based

on default & user settable time duration by internally collating various raw data files
extracted in discrete steps from network objects/EMS/NMS.
Report Attributes
Report Title
Report Generation Time , user
Port Details : Node Name , Node Id ( Optional), Port Name , Port ID ( optional), Link Name, Link
Id ( if part of any link), Circuit Name, Circuit ID ( If part of any circuit), Layer Rate
Granularity chosen, Duration - By Default Yesterday ( i.e Previous day 00:00 hrs to 23:59 hrs
period to be selected and Report Displayed)
PM - Report - Graphical Representation
Time | KPI1 | KPI 2| KPI 3 | . | .| KPI n
SRS_BAL_PMS_REP6.

PMS shall provide PM Report for 15 minute Granularity of a

particular port and layer rates for maximum of seven days. The following are the options
that would be available for the duration:

Confidential & Proprietary

Page 27 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

Yesterday

- Yesterday 0000 to 2400

Today

- Today 0000 to till latest

Previous 7 days

- till yesterday 2359

This Week

- Current week Monday till today now

Last Week

- Previous week Monday 0000 to Sunday 2359

Custom Option

- From Date Time /To

SRS_BAL_PMS_REP7.

Date

Time

For 24 hour granularity of a port with layer rate, The following are

the options that would be available for the duration:

Yesterday

- Yesterday 0000 to 2400

Today

- Today 0000 to till NOW

Previous 7 days

- till yesterday 2359

This Month

- this month 01 to till date time now

Last Month

- Previous month 01 to end of the month

Custom Option

- From Date Time /To

Confidential & Proprietary

Date

Time

Page 28 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

Confidential & Proprietary

dated 22nd November 2010

Page 29 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

SRS_BAL_PMS_REP8.

dated 22nd November 2010

PMS shall act as a unified source of information for all

performance related reports by the users. It shall support comprehensive set of

performance

reports

for

Multi-vendor

(TNG

ECI,ALCATEL,NORTEL,HUAWEI,TELLABS and ANG - ) equipments on one single

platform at following important entities:
- MS layer
- RS layer
- OTU Layer (OMS, OCH, OTU, ODU)
- TCM layer
- HO/LO Path layers i.e. AU-4,VC-4,VC-3,VC-12 etc
- Ethernet Layer

SRS_BAL_PMS_REP9.

PMS shall provide users to export the PM Report into XLS and

PDF formats.
SRS_BAL_PMS_REP10.

PMS shall present the PM data in both tabular and graphical

representations.
SRS_BAL_PMS_REP11.

PMS shall support scheduling of the PM Report generation by

the user to automate the generation of defined report types.

SRS_BAL_PMS_REP12.

PMS shall also provide option to generate the PM Report for the

defined report types on demand.

NMS shall provide PM Report with Zero suppression, removing all the rows with complete
zeros so as to effectively present only non-zero rows.
Fig : Sample Report Without Zero Suppression

Confidential & Proprietary

Page 30 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

Confidential & Proprietary

dated 22nd November 2010

Page 31 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

Fig : Sample Report With Zero Suppression

Confidential & Proprietary

Page 32 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management
SRS_BAL_PMS_REP13.

PMS shall

dated 22nd November 2010

provide a Report for all the ports in the network

generating/detecting errors as per defined PM parameters with options to filter for a

particular vendor, EMS, NE, customer, service etc.

Report Attributes
Report Title
Report Generation Time , user
Reports Configurator - Provide filters to generate ports with errors for
vendor wise, EMS , NE,Customer/circuit id/ service name for the chosen
period.

Confidential & Proprietary

Page 33 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

SRS_BAL_PMS_REP14.

dated 22nd November 2010

PMS shall provide Bit Error Ratio(BER) report for each

monitored port/circuit provided the BER - KPI is supported by the vendor EMS/NMS
throughthe provided interface.

Report Attributes
Report Generation Time , user
Reports Configurator - Provide filters to generate ports with errors for
vendor wise, EMS , NE,Customer/circuit id/ service name for the chosen
period.
Filter Criteria : Vendor, NE , circuit id, service name.
Granularity : 15 min /24 h Duration : Period for which PM Report is generated
PM Report - Graph ( X axis -

Time

: Y axis BBER, SES, ES, )

PM Report - Table
Time, KPI 1, KPI 2, .., KPI n ( BBER, ES, SES, )

Confidential & Proprietary

Page 34 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management
Time

ES(NE/FE) SES(NE/FE) BBER

(NE)

dated 22nd November 2010

BBER(FE)

B1 ER(NE)

B3 ER
(FE)

Dependency:
BER KPIs supported by the EMS through NBI shall be provided in the PM Report.

SRS_BAL_PMS_REP15.

PMS shall also provide graphical representation of Individual/all

SDH KPIs in compare to BER for service/circuit/port.

SRS_BAL_PMS_REP16.

PMS shall provide option to drill down to finer granularity of time

from 24 hrs period to specific 15 min period for detailed analysis of the KPIs for specific
ports.
SRS_BAL_PMS_REP17.

PMS shall provide customized Reports which can be used as an

analysis on ports/sections for errors/ power levels/ span losses.

SRS_BAL_PMS_REP18.

PMS shall provide full capability to customize the displayed

reports - select text and graph types, include user defined graphics to the report (e.g.
logo) etc.
SRS_BAL_PMS_REP19.

PMS shall enable graphical presentation of all reports with

complete display control as-

- WYSIWYG editor
- Drag & Drop
- Fonts
- Colors
- Multiple document interface (MDI) etc.

Confidential & Proprietary

Page 35 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

PMS shall provide a consolidated report for all vendors for near end and far end monitoring at
different

layer

of

SDH/

DWDM/ASON

Network.

9.4 SLA & Service based PM Reports

SRS_BAL_PMS_SLA1. PMS shall provide PM Reports for the services based on unique
Circuit Ids used by TNG/ANG, based on the mapping information of the network ports
and circuit ids provided from Metasolv M6.

Report Attributes
Report Generation Time , user
Reports Configurator - Filter options to select Customer/circuit id/ service
name for the chosen period.
Filter Criteria : Vendor, NE , circuit id, service name.
Granularity : 15 min /24 h Duration : Period for which PM Report is generated

Confidential & Proprietary

Page 36 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

SRS_BAL_PMS_SLA2. PMS shall provide end to end service (end to end ports
associated with the service) performance monitoring reports for individual circuit/service
along with associated bandwidth, end points, customer name etc.

Report Attributes
Report Generation Time , user
Reports Configurator - Filter options to select Customer/circuit id/ service
Name with Layer rate options ( STM-1/4, E1, DS3,
etc..) for the chosen period.
Filter Criteria : Vendor, NE , circuit id, service name.
Granularity : 15 min /24 h Duration : Period for which PM Report is generated

Confidential & Proprietary

Page 37 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

SRS_BAL_PMS_SLA3. PMS shall compute the Service Availability based on the

occurrence of the UAS for the PTP/CTPs associated with the service monitored for PM.
The service monitored for PM shall be considered down (Not available) for the duration
of UAS observed in the PMS.
SRS_BAL_PMS_SLA4. PMS shall identify the performance degraded circuit/service
based on the ES/SES observed on the associated PTP/CTP.
SRS_BAL_PMS_SLA5. PMS shall provide Service Availability Report for individual
service/circuit for a user defined duration with the following details
- Uptime/SLA of individual service/circuit.
- Downtime of individual service/circuit along with RCA
- achieved SLA against agreed SLA for the customer.
- Down time (UAS) introduced by Customer end/ TNG/ANG part of
the circuit with details

Confidential & Proprietary

Page 38 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

SRS_BAL_PMS_SLA6. SLA inputs such as target SLA KPIs (e.g. 99.999%) against
which SLA computations to be done shall be provided as configurable options.
SRS_BAL_PMS_SLA7. Down time events that are taken for SLA computations shall be
categorized as down time due to TNG/ANG, down time due to Bharti Planned Event
or Customer Planned Events ,etc as the categories defined by the users. Also down
time or UAS introduced by Customer end / TNG/ANG section shall be captured.
SRS_BAL_PMS_SLA8. Down time events that are taken for SLA computations shall have
options to handle exceptions such as down time not due to TNG/ANG, due to /not due
to Bharti or Customer planned events, etc due to the categories predefined by the
users.

SRS_BAL_PMS_SLA9. Service Availability Report of a service/circuit shall provide the

RCA information as the port which caused the PM degradation of the whole
circuit/service

SRS_BAL_PMS_SLA10. A service/circuit shall be considered down only when A end or Z

end port goes down or both ports are down for the respective circuit/service.
SRS_BAL_PMS_SLA11. A service/circuit shall be considered as performance degraded
when the working path goes down and the service is up in the protection path.
( Dependency on PM to be enabled in the EMS/NMS for all the ports associated with
the circuit/service and working/protection path information to be available in the
inventory dump from M6.)
SRS_BAL_PMS_SLA12. A service/circuit shall be considered as performance degraded if
flaps are occurring on any of the ports associated with the service/circuit.
( Dependency on PM to be enabled in the EMS/NMS for all the ports associated with
the circuit/service.)
SRS_BAL_PMS_SLA13. PMS shall provide cumulative uptime/downtime report for all
services/circuits belonging to each customer for a user defined time period.
SRS_BAL_PMS_SLA14. PMS shall provide cumulative report of performance degraded
ports/circuits/services belonging to each customer for a user defined period.

Confidential & Proprietary

Page 39 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

SRS_BAL_PMS_SLA15. PMS shall have capability of service degradation correlation with

the anomalies detected/reported at higher network level carrying the service.
i.e correlating the degradation of the KPIs collected for the network level ports with
their associated circuit id/services to provide the information about the services
impacted due to these ports.

Service degradation correlation and RCA will be provided only when a

service/circuit is down.

For a port identified with degraded performance, the circuits/customer services

affected by the degraded port shall be correlated and provided.

For a individual circuit/service identified with a circuit id which is performance

degraded or completely out of service (down), the root cause port which is the
source of degradation or problem shall be correlated and provided.

SRS_BAL_PMS_SLA16. PMS
rules

by

the

user.

e.g.

shall also provide options to define new correlation

Configuring

threshold

violation

KPIs

for

specific

circuits/ports/services.

9.5 Comparative PM Reports

SRS_BAL_PMS_CMP1. PMS hall provide analysis report of repeat cases (ports/services)
on a user defined interval.
SRS_BAL_PMS_CMP2. PMS shall provide PM Report for trend analysis of performance
on individual service/ circuit/ port.
SRS_BAL_PMS_CMP3. PMS shall provide comparative report on uptime/downtime for
services/circuits for a user defined time period based on customers, locations, circuits
provided.

Confidential & Proprietary

Page 40 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

SRS_BAL_PMS_CMP4. PMS shall provide PM Report on repeat service failure analysis

based on user settable input variables customer name, circuit id, duration etc.

Report Attributes:
Report Generation Time , user
Granularity
: 15 min / 24 hrs
Duration
: Period for which the PM Report is generated
Filter Criteria for Repeat failure Analysis : Customer Name, Circuit ID, Service Type, Duration
Time

Criteria

Port Details

KPI 1

....

KPI n

SRS_BAL_PMS_CMP5. PMS shall provide reporting capability to create comprehensive

performance reports from network viewpoint, through the following reports
- Best and Worst performer Report.
- Utilization/Failure Trend Report.
- Comparison Report between Various NE Groups.
This report shall provide the required analysis details as mentioned above according to the
define rules for specific KPIs for circuits / Service Type / NE Group.
Report Attributes
Report Generation Time , user
Filter Options : Best and Worst performer Report ( e.g. w.r.t service type/ Customer / NE Type/Vendor
)
Duration : Period for which PM analysis Report is generated
Time

Best
Performers

ES

SES

BBE

BBER

Circuit ID1
Circuit ID 2

Confidential & Proprietary

Page 41 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

SRS_BAL_PMS_CMP6. PMS shall provide consolidated report of span loss for each
DWDM section as compared to the designed parameters & reporting deviations, if any.
Report Attributes:
Report Generation Time , user
Reports Configurator - Filter options to select the specific DWDM section
using link name /link id/source port/destination port

SDH Section : Link ID/ Link Name

KPI

Source Port Details

: Optical Power Transmitted, Optical Power Received, Line Out Optical Power Value,
Laser Temperature, Laser Bias Current (LBC), Per-channel Central Wavelength Value,
Per-channel Central Deviation Value, Per-channel OSNR Value, Per-channel Laser
Output Power Value and Span Loss

SDH Section : Link ID/ Link Name

Destination Port Details

KPI

: Optical Power Transmitted, Optical Power Received, Line Out Optical Power Value,
Laser Temperature, Laser Bias Current (LBC), Per-channel Central Wavelength Value,
Per-channel Central Deviation Value, Per-channel OSNR Value, Per-channel Laser
Output Power Value and Span Loss
Dependency
Actual Span loss shall be provided from the KPIs collected and Expected Span loss shall be
provided link distance or Fiber distance is available through Inventory Management System.
SRS_BAL_PMS_CMP7. PMS shall provide consolidated report for high span losses in
SDH sections considering OPT/OPR & the link distance. This depends on the
availability of the link distance and the corresponding port information from the UGIS
Fiber Management system.
Report Attributes
Report Generation Time , user
Granularity : 24 hrs
Duration : Period for which the PM Report is generated

KPIs supported
Optical Power Transmitted, Optical Power Received, Line Out
Optical Power Value, Laser Temperature, Laser Bias Current (LBC),
and Laser Cooling Current Value, Actual Span loss, Expected Span
Loss
Dependency

Confidential & Proprietary

Page 42 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

KPIs supported by the EMS through NBI and the expected span loss for the sections to
be defined to capture the deviations if any.
SRS_BAL_PMS_CMP8. PMS shall provide a cumulative report on all SDH spans in the
network.
Report Description:
CygNet PMS shall provide a cumulative report on all SDH spans in the network with the
following details: Transmitted Power, Received Power, Span loss.
Report Attributes:
Report Generation Time , user
Duration : Period for which PM analysis Report is generated
Period

SDH Section
Name/Link ID

OPT

OPR

Actual Span
Loss

Expected Span
Loss

Dependency:
Actual Span loss shall be provided from the KPIs collected and Expected Span loss shall
be provided link distance or Fiber distance is available through Inventory Management S
System.

SRS_BAL_PMS_CMP9. PMS Shall provide a comparative report for the PM KPIs of two
different ports on a single frame.

Confidential & Proprietary

Page 43 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

Confidential & Proprietary

dated 22nd November 2010

Page 44 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

SRS_BAL_PMS_CMP10.
PM Threshold ReportsPMS shall provide options to configure
user defined thresholds for specific KPIs and generate PM reports based on the threshold
configured. ( Note: User defined thresholds configured shall be applied passively in the
PMS database without affecting the EMS/NMS performance)

SRS_BAL_PMS_CMP11.
In case of threshold violations, PMS shall send e-mail
notifications to the defined stake holders of Remedy TTS for raising TT as defined in the
OSS Integration Requirements.
SRS_BAL_PMS_CMP12.
PMS shall provide options to modify the e-mail addresses of the
stake holders to be notified in case of Threshold violations.
SRS_BAL_PMS_CMP13.
PMS shall report or provide a view for the threshold violation
events on a near real time basis . ( Threshold violation events shall be raised once Data
Collection is completed for the KPIs interested.)
SRS_BAL_PMS_CMP14.
PMS shall provide reports on a periodic and user defined interval
of SDH/DWDM/ASON NE ports having
- Errors exceeding user defined thresholds
- Low Tx/Rx power in comparison to threshold/specification
- High Tx/Rx power in comparison to threshold/specification

Confidential & Proprietary

Page 45 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

Report Description
This report shall provide the violations on a periodic and user defined interval of SDH/DWDM NE ports
having
- Errors exceeding user defined thresholds
- Low Tx/Rx power in comparison to threshold/specification
- High Tx/Rx power in comparison to threshold/specification
Report Attributes
Report Generation Time , user
Granularity : 15 min / 24 hrs
Duration : Period for which the PM Report is generated
Port Details : Port Name , SDH /DWDM NE name
Time Stamp

Violated KPI

Threshold Level

Violated KPI

Threshold Level

Note: Threshold values defined shall be applied in the CygNet PMS Database without affecting the
performance of the respective EMS/NMS
Sample Report

Confidential & Proprietary

Page 46 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

SRS_BAL_PMS_CMP15. PMS shall provide options to configure/modify the thresholds governing

the generation of TCA from the respective EMS/NMS. However, this depends on the
support provided by the EMS through NBI.

9.6 PM Reports SDH/DWDM

SRS_BAL_PMS_OPT1.
PMS shall provide Optical PM Reports for DWDM
interfaces consisting the following KPIs
- DWDM/CWDM line side (multiple wavelengths) total receive power
- DWDM/CWDM line side (multiple wavelengths) total transmit power
- Section Span loss
- Supervisory channel receive power and transmit power
- Optical interfaces client side receive power and transmit power
- Optical interfaces line side receive power and transmit power on a per
channel Basis
- Mux/ Demux input power and output power
- Total Tx/Rx power
- Per channel Tx/Rx power
- DCU losses

SRS_BAL_PMS_OPT2.
PMS shall support section and path PM on SDH
interfaces , providing the following KPIs
- Severely Errored Seconds [SES-FE] Far End
- Errored Seconds [ES-FE] Far End
- Unavailable Seconds [UAS-FE] Far End
- Background Block Error [BBE-FE] Far End
- Severely Errored Seconds [SES-NE] Near End
- Errored Seconds [ES-NE] Near End
- Unavailable Seconds [UAS-NE] Near End
- Background Block Error [BBE-NE] Near End
- Pointer Justification Count Generated [PJCG]

Confidential & Proprietary

Page 47 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

- Pointer Justification Count Detected [PJCD-P]

- Total Bit Error Ratio[BER]
- Total Tx power per port
- Total Rx power per port

Confidential & Proprietary

Page 48 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

9.7

dated 22nd November 2010

PM Reports OTN
SRS_BAL_PMS_OTN1.
PMS shall support PM for OTU layer on G.709 interfaces
with the following KPIs:
- Severely Errored Framing Seconds (loss of alignment or loss of multi-frame)
[OTU-SEFS]
- Code Violation [OTU-CV]
- Errored Seconds [OTU-ES]
- Severely Errored Seconds [OTU-SES]
- Unavailable Seconds [OTU-UAS]
- Code Violation [OTU-CV-FE] Far-End
- Errored Seconds [OTU-ES-FE] Far-End
- Severely Errored Seconds [OTU-SES-FE] Far-End
- Unavailable Seconds [ODU-UAS-FE] Far-End
- FEC Correctable Errors [OTU-FEC]
- FEC Uncorrectable Errors [OTU-FECU]
- Pre FEC BER
- Trail Trace Indication [OTU-TTI]

SRS_BAL_PMS_OTN2.
with the following KPIs:

PMS shall support PM for ODU layer on G.709 interfaces

- Code Violation [ODU-CV]

- Errored Seconds [ODU-ES]
- Severely Errored Seconds [ODU-SES]
- Unavailable Seconds [ODU-UAS]
- Code Violation Far-End [ODU-CV-FE]
- Errored Seconds Far-End [ODU-ES-FE]

Confidential & Proprietary

Page 49 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

- Severely Errored Seconds Far-End [ODU-SES-FE]

- Unavailable Seconds Far-End [ODU-UAS-FE]
- Trail Trace Indication [ODU-TTI]
- Specify other supported ODU PM parameters [provide details]

SRS_BAL_PMS_OTN3.
with the following KPIs

PMS shall support PM for TCM layer on G.709 interfaces

- Code Violation [TCMX-CV]

- Errored Seconds [TCMX-ES]
- Severely Errored Seconds [TCMX-SES]
- Unavailable Seconds [TCMX-UAS]
- Failure Count [TCMX-FC]
- Code Violation Far-End [TCMX-CV-FE]
- Errored Seconds Far-End [TCMX-ES-FE]
- Severely Errored Seconds Far-End [TCMX-SES-FE]
- Unavailable Seconds Far-End [TCMX-UAS-FE]
- Failure Count Far-End [TCMX-FC-FE]

SRS_BAL_PMS_OTN4.
PMS shall support PM for ODU and TCM layer
intermediate path monitoring with the KPIs provided by the EMS/NMS

9.8 Ethernet PM Reports

SRS_BAL_PMS_ETH1. PMS shall support the following cumulative Ethernet LAN (client
interface) PM status parameters.
- Octets Received
- Octets Transmitted

Confidential & Proprietary

Page 50 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

- Frames Received without Errors

- Frames Transmitted without Errors
- Jumbo Frames Received
- Jumbo Frames Transmitted
- Pause Frames Received
- Pause Frames Transmitted
- Time Valid Carrier Present on LAN Interface
- Time Valid Carrier not Present on LAN Interface

SRS_BAL_PMS_ETH2. PMS shall support the following cumulative Ethernet LAN (client
interface) PM error parameters.
- Frames Received with Errors
- Frames Received and Discarded with Errors
- Frames not Transmitted due to Errors
- Frames Transmitted with Errors
- Frames Received and Discarded due to Congestion (buffer overflow)
- Frames not Transmitted due to Congestion (buffer overflow)
- Frames Received with FCS Errors
- Frames Received with Alignments Errors
- Frames Received with MAC Errors
- Frames not Transmitted due to MAC Errors
- Symbol Errors Count
- Oversized Frames Received (over provisionable MTU)
- Runts Received (< 64 bytes with CRC errors)
- Jabbers Received (>1548 bytes with CRC errors)

Confidential & Proprietary

Page 51 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

SRS_BAL_PMS_ETH3. PMS shall support the following binned Ethernet LAN (client
interface) PM error parameters.
- Protocol Violations LAN Receiver (count of frames received with errors)
- Errored Seconds LAN Receiver (number of seconds where at least one frame
has an error)
- Severely Errored Seconds LAN Receiver (number of seconds where at least
10% of the frames have errors or the link is down).
- Unavailable Seconds LAN Receiver (starts after 10 SES, reset after 10
seconds that are not SES).
- Protocol Violations LAN Transmitter (count of frames not transmitted due to
errors)
- Errored Seconds LAN Transmitter (number of seconds where at least one
frame has an error)
- Severely Errored Seconds LAN Transmitter (number of seconds where at least
10% of the frames have errors or the link is down)
- Unavailable Seconds LAN Transmitter (starts after 10 SES, reset after 10
seconds that are not SES)
- Frames Received and Discarded due to congestion (buffer overflow)
- Frames not Transmitted due to congestion (buffer overflow)
- Frames Received with FCS Errors
- Frames Received with Alignments Errors
- Frames Received with MAC Errors
- Frames not Transmitted due to MAC Errors
- Oversized Frames Received (over provisionable MTU)

Confidential & Proprietary

Page 52 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

SRS_BAL_PMS_ETH4. PMS shall support the following cumulative Ethernet WAN (SDH)
PM status parameters
- WAN (GFP) Frames Received without Errors
- WAN (GFP) Frames Transmitted without Errors

SRS_BAL_PMS_ETH5. PMS shall support the following cumulative Ethernet WAN

(SDH) PM error parameters
- WAN (GFP frames) Received with Errors (GFP header errors, GFP FCS
errors, invalid/unsupported GFP frames).
SRS_BAL_PMS_ETH6.
- Oversized GFP Frames Received (over provisionable
MTU)PMS shall support the following binned Ethernet WAN (SDH)
PM error parameters.
- Protocol Violations WAN Receiver (count of frames received with GFP errors)
- Errored Seconds WAN Receiver (number of seconds where at least one
frame has an error)
- Severely Errored Seconds WAN Receiver (number of seconds where at least
10% of the frames have errors or the WAN link is down)
- Unavailable Seconds WAN Receiver (starts after 10 SES, reset after 10
seconds that are not SES)
- Oversized WAN (GFP) Frames Received (over provisionable MTU)
SRS_BAL_PMS_ETH7. PMS shall support the following binned Virtual Concatenation
(SDH)

PM error parameters

- Seconds of Loss of Multi-frame (level 1 or 2)

- Seconds of Sequence Number Mismatch
- Seconds of Loss of Alignment
- Seconds of LCAS Bandwidth Reduction

Confidential & Proprietary

Page 53 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

9.9

dated 22nd November 2010

PM - Database Backup & Restore

SRS_BAL_PMS_BKP1. PMS shall support full back for all the data archived , consisting
the following information:
-

PMS Application information

PMS Database Information

Application Logs/System Logs

User Task Logs

System Configuration information

SRS_BAL_PMS_BKP2. PMS shall log the successful completion of Backup activity

scheduled periodically.
SRS_BAL_PMS_BKP3. PMS shall log the unsuccessful Backup activity and the same
shall be raised as alarm/e-mail notification to the respective stake holders.
SRS_BAL_PMS_BKP4. In addition to full database backups, incremental online data
replication between the redundant servers shall be done so that there is less than 15
mins of data loss in the event of hardware failure, in line with Bharti Backup/Restoration
policies.
SRS_BAL_PMS_BKP5. In the primary site, if any one of the following servers namely
PMS Application Server, Mediation Server1, Mediation Server2,Mediation Server3
encounters a failure, the application will be restored in the N:1 Redundant Application
server available in the primary site with the latest incremental backup data.
SRS_BAL_PMS_BKP6. In the primary site, incase of any failure encountered by the
Database server, the 1:1 Redundant Database server shall take over as the Database
server with the latest incremental Database backup available.
SRS_BAL_PMS_BKP7. In case of total failure of the primary site, the application shall be
taken over by the servers installed in the DR location with the latest backup data with
minimum downtime ( 5 to 10 mins) required to exchange the heartbeat for hot standby
and startup of the servers in the DR location.
SRS_BAL_PMS_BKP8. PMS shall provide options to configure the duration of retaining
the raw PM data collected from the respective NE/EMS/NMS . Typically 15 min raw
data to be retained for 3 months and 24 hrs granularity raw data to be retained for 12
months at any instance.

Confidential & Proprietary

Page 54 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

SRS_BAL_PMS_BKP9. PMS shall provide options to configure the duration of generated

reports and processed data stored in the PMS Database. Typically such data shall be
stored in PMS Database for minimum 6 months.
SRS_BAL_PMS_BKP10.PMS shall purge the expired data on FIFO basis.

9.10 PMS Application Performance

SRS_BAL_PMS_APP1. PMS shall support procedures for auto recovery with latest
available backup files post catastrophic failure.
SRS_BAL_PMS_APP2. PMS shall also support manual procedures for recovering the
application with the latest available complete and incremental backups.
SRS_BAL_PMS_APP3. PMS shall monitor the memory used by the application and
available free memory to avoid any memory leak.
SRS_BAL_PMS_APP4. PMS Application shall ensure that no process shall suffer
performance degradation due to loading of another process.
SRS_BAL_PMS_APP5. Incase of complete failure of the application, the total time for
restoration of the tool shall not exceed more than 5mins per GB of Database size.
SRS_BAL_PMS_APP6. PMS shall have the capability to record the failures occurring in
both active and stand-by mode.
SRS_BAL_PMS_APP7. PMS shall have the capability to report the type and number of
transient failures/switch over in the active and stand by mode.
All the software application upgrade releases shall be backward compatible to the previous
release.

Confidential & Proprietary

Page 55 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

9.11

dated 22nd November 2010

PM Security Management

SRS_BAL_PMS_SEC1. PMS shall provide options to add and delete new users for the
application

SRS_BAL_PMS_SEC2. PMS shall provide password authentication for the respective

users created by the admin user.

Confidential & Proprietary

Page 56 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

SRS_BAL_PMS_SEC3. PMS shall have the ability to get users authenticated via
RADIUS.
SRS_BAL_PMS_SEC4. Password authentication for multiple users shall be created within
the PMS application
SRS_BAL_PMS_SEC5. PMS shall provide options to create users with different level of
privileges like administrator, user with different privileges.

SRS_BAL_PMS_SEC6. PMS shall provide options for admin users to modify the
privileges provided for the users.

Confidential & Proprietary

Page 57 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

SRS_BAL_PMS_SEC7. PMS shall enable limitation to access report configurator,

performance reports, based on the user rights as to be specified by BAL.
SRS_BAL_PMS_SEC8. PMS shall provide options for privileged users to define new
reports based on existing pre-defined reports.
SRS_BAL_PMS_SEC9. PMS shall provide options for privileged users to save the report
definitions for other users to access.
SRS_BAL_PMS_SEC10. PMS shall provide options for respective users to change their
own passwords.

SRS_BAL_PMS_SEC11. PMS shall provide options to restrict the PM reports for users
based on region, circuit id, service type, customer name etc.
SRS_BAL_PMS_SEC12. PMS shall provide options to customize the login provided for
respective users, e.g to modify the logo, font ,theme.
SRS_BAL_PMS_SEC13. PMS shall have the ability to capture log of activities performed
by a user with date/time stamp.
SRS_BAL_PMS_SEC14. PMS shall allow import of the raw performance files collected
from the NE/EMS/NMS into the Client or standalone machine for the exported files for
users with proper permissions
SRS_BAL_PMS_SEC15. PMS shall provide the list of users logged into the application
client of PMS at any instance.

Confidential & Proprietary

Page 58 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

10 . Integration of OSS/BSS with CygNet PMS

10.1 Metasolv M6 Integration

SRS_BAL_PMS_OSS1. PMS shall have one way ( M6 to PMS) integration with Metasolv
M6 Inventory Management system using the offline dumps provided from Metasolv M6
as identified during the feasibility study of the Integration requirements.
SRS_BAL_PMS_OSS2. Inventory information dump from Metasolv M6 in the form of
staging tables shall be integrated with the CygNet PMS Database with ref to the
schema corresponding to Metasolv M6 Database dump.
SRS_BAL_PMS_OSS3. PMS Database shall update the offline dumps of Metasolv M6 at
regular intervals to update the changes in the Inventory information.
SRS_BAL_PMS_OSS4. Incremental dumps provided on daily basis for updating the
inventory information which shall include the additions/modifications done in M6
inventory shall be used for updating the additions/modifications.
SRS_BAL_PMS_OSS5. Complete dumps that would be provided once in 15 days with
the deleted inventory information in M6 inventory shall be used for updating the
additions/modifications.
SRS_BAL_PMS_OSS6. PMS shall have the inventory information of all the
Transmission Network assets ( NEs/ports) and customer services (end to end
termination points - circuit information ) provided by Metasolv M6 offline dump.
SRS_BAL_PMS_OSS7. The information regarding mapping of the circuit ids to the
corresponding Transmission Network assets (NEs/ports) and customer service details
shall be retrieved from the Metasolv M6 Database through the dumps provided and
stored in the PMS database.

Confidential & Proprietary

Page 59 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

10.2 UGIS Fiber Management System Integration

SRS_BAL_PMS_OSS8. PMS shall have one way (UGIS to PMS) integration with UGIS
small world FMS using the offline dumps provided from UGIS as identified during the
feasibility study of the Integration requirements.
SRS_BAL_PMS_OSS9. Optical Fiber information dump from UGIS in the form of
staging tables shall be integrated with the CygNet PMS Database with ref to the
schema corresponding to UGIS Database dump.
SRS_BAL_PMS_OSS10.PMS Database shall update the offline dumps of UGIS at regular
intervals to update the changes in the Optical Fiber information.
SRS_BAL_PMS_OSS11.Incremental dumps provided on daily basis for updating the
inventory information which shall include the additions/modifications done in UGIS
inventory shall be used for updating the additions/modifications.
SRS_BAL_PMS_OSS12.The information regarding mapping of the fiber pairs to the
corresponding Transmission Network assets (NEs/ports) and shall be retrieved from the
UGIS Database through the dumps provided and stored in the PMS database. Using
this mapping information, PMS shall provide section wise performance data for the
links using these fiber pairs so that proactive repairs can be done when OPT/OPR
values exceed the desired per km loss value eliminating signal degraded or errored
links.
SRS_BAL_PMS_OSS13.PMS shall provide the comparison of the designed fiber length
and the actual fiber length using the fiber length details obtained from UGIS integration.

10.3 Remedy Trouble Ticketing System Integration

SRS_BAL_PMS_OSS14.PMS shall integrate with Remedy TTS for raising tickets when
there are incidents of violation/degradation in the defined KPIs of the services
monitored by PMS.
SRS_BAL_PMS_OSS15.PMS shall send e-mail notifications for TCA instances to the
Remedy TT system.
SRS_BAL_PMS_OSS16.PMS shall provide options to configure the email id for forwarding
the TCA notifications.

Confidential & Proprietary

Page 60 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

10.4 e-CRM Integration

SRS_BAL_PMS_OSS17. PMS shall integrate with e-CRM system in Phase II for
including the Customer SLA information, customer service priority ( i.e
gold/silver/platinum etc) in SLA computation for service based PM Reports.
SRS_BAL_PMS_OSS18. PMS shall retrieve the unique reference id for mapping the
circuit ids in ANG and TNG network domain to enable us for end to end circuit
performance monitoring.
SRS_BAL_PMS_OSS19.PMS shall be provided with the required attributes from e-CRM
system integration through the interface that would be mutually agreed with the
necessary details.

Confidential & Proprietary

Page 61 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

11 . Hardware & Software Specifications

11.1 Primary Site

Confidential & Proprietary

Page 62 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

Hardware Specifications
Blade Enclosure
Description

Qty

Sun Blade 6000 Chassis with Gen-2 midplane, 2*6000W PS modules, 6 redundant rear
fan modules
1 Sun Blade 6000 Chassis with Generation 2 midplane, 10U, 2x 6000W power supply
modules, 6 redundant rear fan modules, 1 Chassis Monitoring Module, Rack Mount Rail Kit,
Accessory Kit with Dongle and RJ45-DB9 adapter, 9 server module filler panels, 20 PCIe

PWR CORD, QTY 4, AC, 16A, EPAC

SB6000 NEM 10-port GbE

Dongle Cbl II; RJ45,2xUSB,DB9

SB6000 Chassis Doc Kit

Mediation Servers
Sun Blade T6320 Server: 1*8 Core 1.4GHz UltraSPARC T2 CPU, 32GB RAM, 2*146GB
SAS HDD, 2*DP FC + DP GbE HBA - Qty 3
T6320 XATO base with one 8 core 1.4GHz UltraSPARC T2, no REM, no Disk, RoHS6

Qty
3

Pre-install S10U7 for T6320

4GB FB DIMM Kit: consist of two 2 GB dual rank FB DIMM. RoHS-5. X-Option.

24
6

146GB 10K RPM 2.5" SAS disk

SB RAID 0/1 REM II

3
6

Drive Bay Filler Panel

Dual 4Gb FC Dual GbE HBA

Sun Cluster 3.2 for Sun Blade T6320 Server
Sun Cluster 3.2 server license for Sun Blade T6320 Server Module. One license required per
server. Invoice only.

Confidential & Proprietary

Page 63 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

Application Servers
Sun Blade T6340 Server: 2*8 Core 1.4GHz UltraSPARC T2+ CPU, 32GB RAM, 2*146GB SAS
HDD, 2*DP FC + DP GbE HBA - 2 qty

Qty

Sun Blade T6340 XATO Base, Two 1.4GHz 8 core UltraSPARC T2+ processors, service
processor with ILOM 3.0, No DIMM, No disk, No REM, No FEM, RoHS6, For factory integration
only.

Pre-install S10U7 for T6340

2x2GB FB DIMM for T6340

16

146GB 10K RPM 2.5" SAS disk

SB RAID 0/1 REM II

T6340 DIMM Filler Panel

Dual 4Gb FC Dual GbE HBA

Sun Cluster 3.2 for Sun Blade T6340 Server

Sun Cluster 3.2 server entitlement fee for Sun Blade T6340. One entitlement required per server.
Invoice only.

Database Servers
Sun SPARC Enterprise T5440 Server : 2*8 Core 1.4GHz UltraSPARC T2+ CPU, 32GB RAM,
2*146GB SAS HDD, 2*FC HBA - 2 qty
Sun SPARC Enterprise T5440 Sever 4 RU Chassis, including common components motherboard,
four power supplies, four fans, and service processor board. CPUs, memory, disks, DVD,
rackmount kit and cable management arm not included. For Factory Integration

Qty
2

Sun SW Preinstall 05/09 S10U7

T5440 Cable Mgmt. Arm
NORTH AMERICAN/ASIA PWRCD RoHS
146 GB, 10K, 2.5 SAS, Nemo
FJ T5440-DVD R/W,8X,Slot
T5440 CPU module, 8 core, 64 threads, 1.4 Ghz with 16 GB, 4 x 4 GB DIMMs, with one memory
board. For Factory Integration Only

2
2
8
4
2

T5440 Disk Filler Panel

T5440 Rail Kit,Tools required
T5440 CPU/Mem. Filler Panel
4Gb FC Single Port HBA
Sun Cluster 3.2 for Sun SPARC Enterprise T5440 server
Sun Cluster 3.2 server entitlement fee for Sun SPARC Enterprise T5440. One entitlement required
per server. Invoice only.

4
2
8
4

Solaris 10 10/09 Media Kit

SC agent lic x HA Oracle

1
1

Confidential & Proprietary

Page 64 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

Software Specifications
OS

: Solaris 10, Cent OS RHEL (LINUX) - 4.3

Database

: Oracle 11g Standard edition

Third Party

: JRE 2 Runtime Environment, JacORB (CORBA) ,

Apache Web Server / Tomcat

Confidential & Proprietary

Page 65 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

11.2 Disaster Recovery Site

Confidential & Proprietary

Page 66 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

Hardware Specifications
Blade Enclosure
Description
Sun Blade 6000 Chassis with Gen-2 midplane, 2*6000W PS modules, 6 redundant rear
fan modules

Qty

1 Sun Blade 6000 Chassis with Generation 2 midplane, 10U, 2x 6000W power supply modules,
6 redundant rear fan modules, 1 Chassis Monitoring Module, Rack Mount Rail Kit, Accessory Kit
with Dongle and RJ45-DB9 adapter, 9 server module filler panels, 20 PCIe

PWR CORD, QTY 4, AC, 16A, EPAC

SB6000 NEM 10-port GbE

Dongle Cbl II; RJ45,2xUSB,DB9

SB6000 Chassis Doc Kit

Mediation Servers
Sun Blade T6320 Server: 1*8 Core 1.4GHz UltraSPARC T2 CPU, 32GB RAM, 2*146GB SAS
HDD, 2*DP FC + DP GbE HBA - 3 qty
T6320 XATO base with one 8 core 1.4GHz UltraSPARC T2, no REM, no Disk, RoHS6

Pre-install S10U7 for T6320

4GB FB DIMM Kit: consist of two 2 GB dual rank FB DIMM. RoHS-5. X-Option.

24
6

146GB 10K RPM 2.5" SAS disk

SB RAID 0/1 REM II

3
6

Drive Bay Filler Panel

Dual 4Gb FC Dual GbE HBA

Confidential & Proprietary

Page 67 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

Application Servers
Sun Blade T6340 Server: 2*8 Core 1.4GHz UltraSPARC T2+ CPU, 32GB RAM, 2*146GB
SAS HDD, 2*DP FC + DP GbE HBA

Sun Blade T6340 XATO Base, Two 1.4GHz 8 core UltraSPARC T2+ processors, service
processor with ILOM 3.0, No DIMM, No disk, No REM, No FEM, RoHS6, For factory integration
only.

Pre-install S10U7 for T6340

2x2GB FB DIMM for T6340

8
2

146GB 10K RPM 2.5" SAS disk

SB RAID 0/1 REM II

1
2

T6340 DIMM Filler Panel

Dual 4Gb FC Dual GbE HBA

Database Servers
Sun SPARC Enterprise T5440 Server : 2*8 Core 1.4GHz UltraSPARC T2+ CPU, 32GB
RAM, 2*146GB SAS HDD, 2*FC HBA

Sun SPARC Enterprise T5440 Sever 4 RU Chassis, including common components

motherboard, four power supplies, four fans, and service processor board. CPUs, memory,
disks, DVD, rackmount kit and cable management arm not included. For Factory Integration

Sun SW Preinstall 05/09 S10U7

T5440 Cable Mgmt. Arm

NORTH AMERICAN/ASIA PWRCD RoHS

146 GB, 10K, 2.5 SAS, Nemo

FJ T5440-DVD R/W,8X,Slot

T5440 CPU module, 8 core, 64 threads, 1.4 Ghz with 16 GB, 4 x 4 GB DIMMs, with one
memory board. For Factory Integration Only

T5440 Disk Filler Panel

T5440 Rail Kit,Tools required

T5440 CPU/Mem. Filler Panel

4Gb FC Single Port HBA

Confidential & Proprietary

Page 68 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

Software Specifications
OS

: Solaris 10, Cent OS RHEL (LINUX) - 4.3

Database

: Oracle 11g Standard edition

Third Party

: JRE 2 Runtime Environment, JacORB (CORBA) ,

Apache Web Server / Tomcat

12. References

[1] BAL Planning Team , RFP for PM tool OSS_Compliance dated 15th Dec 09 Revision 1, 15th Dec 2009.
[2] NMSWorks, Inventory_Attributes_reqd.xls- revision 1.1, 3rd Nov 2010 .

Confidential & Proprietary

Page 69 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

13 . Abbreviations

Sl
No.

Acronym

Expansion

ANG

ASON

BBE

Background Block Error.

BER

Bit Error Ratio.

CWDM

Coarse Wavelength Division Multiplexing.

CORBA

Common Object Request Broker Architecture.

DWDM

Dense Wavelength Division Multiplexing.

DR

Demux

10

EMS

11

ES

Errored Seconds

12

FTP

File Transfer Protocol.

13

FE/NE

14

FCS

Frame Check Sequence.

15

FIFO

First In First Out.

16

GUI

Graphical User Interface.

17

GFP

Generic Framing Procedure.

18

GB

Giga Byte.

19

HTML

20

HO

21

INMS

22

IP

23

KPI

Key Performance Indicator.

24

LO

Lower-Order.

25

LAN

26

LCAS

Access Netork Group

Automatically Switched Optical Network.

Disaster Recovery.
Demultiplexing.
Element Management System.

Far End / Near End.

Hyper Text Markup Language.

Higher-Order.
Integrated Network Management System.
Internet Protocol.

Local Area Network.

Link Capability Adjustment Scheme.

Confidential & Proprietary

Page 70 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

27

MPLS

Multi Protocol Label Switching.

28

Mux

Multiplexing.

29

MAC

Macintosh.

30

MTU

Maximum Transmission Unit.

31

NMS

Network Management System.

32

NBI

North Bound Interface.

33

NE

Network Element.

34

OTN

Optical Transport Network.

35

OSS

Operational Support System.

36

OS

37

OTU

Optical Transport Unit.

38

OMS

Optical Multiplex Section.

39

OCH

Optical Channel.

40

ODU

Optical Data Unit.

41

OPT

Optical Power Transmitted

42

OPR

Optical Power Received

43

PM

44

PMS

Performance Management System.

45

PDF

Portable Document Format.

46

RFP

Request for Proposal .

47

RMI

Remote Method Invocation.

48

RCA

Root Cause Analysis

49

RE

50

RADIUS

51

SDH

Synchronous Digital Hierarchy.

52

SLA

Service Level Agreement.

53

SNMP

54

SID

Shared Information Data.

55

SOA

Service Oriented Architecture.

56

SRS

Software Requirement Specifications.

57

SES

Severely Errored Seconds.

58

TNG

Transport Network Group

59

TT

60

TMF

Tele-Management Forum

61

TTS

Trouble Ticketing System

62

TCA

Threshold Crossing Alert

Operating System.

Performance Management.

Remote Error.
Remote Authentication Dial in User Service.

Standard Network Management Protocol.

Trouble Ticket.

Confidential & Proprietary

Page 71 of 72

SRS for Performance Management System

Ref: NMSWorks/Airtel/Performance Management

dated 22nd November 2010

63

TMN

Telecommunication Management Network.

64

TCM

Tandem Connection Monitoring.

65

Tx/Rx

66

TACACS

67

UAS

Unavailable Second.

68

VPN

Virtual Private Network.

69

WAN

Wide Area Network.

70

XLS

Microsoft Excel.

Transmit / Receive.
Terminal Access Controller Access-Control System.

14 . Annexure

I.

PMS-SRS-Annexure-I-Inventory_Attributes_reqd-M6-UGIS.xls - provides the details of the

attributes required for the integration with M6 & UGIS OSS. This shall be updated with the
details that would be provided for e-CRM integration.

II. PMS-SRS-Annexure-II.doc - contains the KPIs supported by the respective EMS/NMS. This shall
be updated for each vendor during the integration process.

Confidential & Proprietary

Page 72 of 72